338 replies to this topic

[chas]

i see that some new tables have been made in the 915platform in the latest uploads on the homepage.

i dont see it in the getting started files.

all i could find was 914 and 912 which i already have.

where is it?

[JohnnyDoe]

You can find it in koadics nightly builds here:

https://www.dropbox....VPinball Builds

Edited by JohnnyDoe, 18 February 2013 - 07:38 AM.

[chas]

You can find it in koadics nightly builds here:

https://www.dropbox....VPinball Builds

you lost me.

are you sure you posted the correct site?

i see ver331 to 445exec.

[JohnnyDoe]

The link is correct. The 9.15 is not out yet, one of the upcoming builds will become 9.15. These are the ones to use if you want Star Wars Trilogy to work for example, it uses something called primitives that is supported by the latest builds..

[tipoto]

Perfect, a thread about vp915.

So I investigated a little bit about the problem with the EMreels and it seems that the issue starts from version rev389, (rev388 works fine).

 

I don't know who is working on VP915, but it would be great to take a look at this issue please. There is a very simple way to test VP, you just have to launch T2 Chrome, if there are some glitches, it means the EMreels don't work like in VP914.

 

Thank you!

[toxie]

okay, thanks for the notice.. i'll see what happened there..

[toxie]

Okay, i just had a look at it.. Overall i wanted to improve the numerical precision there, but unfortunately this meant that the positions can be slightly off again (in comparison to 9.1.4)..

If this is a fundamental problem, then i'll revert this, otherwise i would like to keep it like that..

[jpsalas]

It is a long time since I have done anything with reels, but in the older Vp9 I always had to overlap the reels by 1 unit, If not you never knew if you were going to see black lines (empty lines) or not. If this is fixed then I mean it is good. I see my older table Elvira and the Party Monsters 1.03 (the one made with reels made by highrise and me) still works and it looks nice. But just now I only have a very small resolution on my portable.

[toxie]

Would be good to get some feedback then for the newer builds if stuff like that has been fixed now (otherwise more work might have to be done there).. I only have limited VP editor artistic skills, so i dunno if my coder art stuff i test there is representative, and testing existing tables always just tests the workarounds that have been done there already, so also useless for me..

[Aurich]

The black lines issue JP brings up can be solved with the right AA settings, I managed to eliminate them a while ago myself.

I see the pixel shifting that tipoto brings up in the new builds (I'm not at the lastest, have to look up #, but it's past 389), and his T2 table is such a showcase for what going crazy (in a good way) can do for you visually in VP that I think it's always worth fixing.

[toxie]

I agree there, but the question is: Should we go for fixing existing bugs so less workarounds are necessary (which are actually used in both versions of T2 Chrome), or should we just keep legacy around, so each new VP author/table using old features has to deal with using whacky hacks to make it work?

(I vote for the first solution )

[marauder]

I'm not a table author but being a software engineer myself, I think that the long term strategic bet should definitely be to fix the bugs and not perpetuate the workarounds. I can understand that it may be frustrating for authors to correct tables that worked well before but as more tables are built by the same or other authors the benefits in the future will greatly outweigh the initial inconvenience.

[hmueck]

I agree there, but the question is: Should we go for fixing existing bugs so less workarounds are necessary (which are actually used in both versions of T2 Chrome), or should we just keep legacy around, so each new VP author/table using old features has to deal with using whacky hacks to make it work?

(I vote for the first solution )

 

 

Can't you put in a check for the table name and use the old routine in case the name contains "tipoto"?

Do you know how much work it is for him to "fix dat shit"?

[Aurich]

I agree there, but the question is: Should we go for fixing existing bugs so less workarounds are necessary (which are actually used in both versions of T2 Chrome), or should we just keep legacy around, so each new VP author/table using old features has to deal with using whacky hacks to make it work?
(I vote for the first solution )

I'm always in favor of progress over having to hold back for legacy reasons. That's always going to mean leaving someone or something behind at some point, and you have to strike a balance obviously. It's exciting to see progress still being made in the quality and capabilities of VP tables.

I wonder if there isn't a middle ground, where you use the browser model and support some kind of "quirks" mode? So a line in the script that renders reels using an older method. Then you could easily update old tables to still work, while moving forward with new ones.

Edit: which is basically what hmueck was suggesting above I guess.

Edited by Aurich, 18 February 2013 - 06:20 PM.

[tipoto]

Ok, if all the problems we had with the EMreels are fixed, I thing it's better to keep it this way.

But I have to double check this with some tests, because I remember in VP914, the EMreels behavior was different than vp912, but it was as illogical as before, so I spent time to fix some textures and cheat on others to compensate, what a waste of time .

If we don't have to cheat anymore in any texture in the future, I think it's great and I am 100% with you to keep this new version and I will spend the necessary time to fix T2 of course.

[toxie]

That's whats still missing and where i need feedback on it.. Is the EMreels behaviour still weird or is it now better than before?

Would be cool if you can give some feedback for T2..

[Aurich]

That's whats still missing and where i need feedback on it.. Is the EMreels behaviour still weird or is it now better than before?
Would be cool if you can give some feedback for T2..

toxie which daily build do you need feedback on? 445? I can upgrade to the latest and verify if the issue is still there.

[toxie]

It's not about the issue that T2 looks strange now, but if the original issue that requires T2 to use workarounds still is there..

[tipoto]

That's whats still missing and where i need feedback on it.. Is the EMreels behaviour still weird or is it now better than before?

Would be cool if you can give some feedback for T2..

I can't say yet, it's why I have to do some tests. I'll try to do them soon.

Hopefully everything will be fixed with your new version

[luvthatapex]

I see vp915 build 450 is available. Whats new in this release? I checked the repository and there are no comments... thanks!