1353 replies to this topic

[Ben Logan]

Toxie,

I tested your new flipper editor options for a couple hours this morning. They work great!

For all tables I tested, an EOS Torque value of .5 worked nicely. Lower than that, and we started to possibly venture into floppy flipper territory.

On my rig, the EOS Angle needed a value of 20 in order to pull off low-voltage moves. On Cactus Canyon, I set it quite a bit higher at 32. It varied from table to table, probably dependent upon and interactive with flipper mass and strength settings. Wasn't able to test long enough to draw any conclusions about how these relate to one another. Wish I didn't have to leave for a week right now, because these are super exciting times for VP!

Cirques Voltaire( DMD embedded in playfield version) was the only table that I tested that didn't play well with 10.2. Left and right flippers behaved vastly differently, despite being set to same values. I only mention it as a point of interest.

It's great that we have both nFozzy's code and now Toxie and Fuzzel's solution for access to low voltage flips. Amazing gifts to the community! Both work great. The two solutions differ in feel just a bit -- which is a plus. Options are wonderful. The nice thing about Toxie and Fuzzel's solution is that it's so easy to adjust and tune -- baked right into the editor.

For tables on which nFozzy's code is preferred, should the EOS Angle value be set to zero, or left at 6?

Cheers to your brilliance and generosity, guys!

[toxie]

Nice that it works so well for you, thanks for the quick feedback!

 

If you use nFozzy's code, maybe really leave it at 6 (same for EOS Torque, leave at default value), maybe lower (3). But not too low, otherwise the original code snippet 'gets lost': it simulated the 'low voltage' only when you hold the flipper up, or are close to the up position with flipper button held. For example could be important for drop catches

and even more live catches

 

EDIT: others, please also share your feedback for the new flipper code, so that i can tweak it some more if necessary.

Edited by toxie, 18 July 2016 - 06:45 PM.

[Drybonz]

So, nFozzy's code can co-exist peacefully with the new VPX beta, then?

[toxie]

Of course (as you asked multiple times already ).

Just make sure that always just one of them is used at the same time, otherwise it could be weird.

[Drybonz]

Of course (as you asked multiple times already ).

Just make sure that always just one of them is used at the same time, otherwise it could be weird.

 

I must have missed your answer.  Thanks.

[unclewilly]

Cool new beta to test

[Ben Logan]

Great to see you, UncleWilly.

[toxie]

Indeed! 

[fuzzel]

rev2716 is up:

 

- add one-way wire trigger mesh shape
- change plunger park position to 0.01 and add a bit of table info
- change default park position to 0.01 as requested
- add core.vbs changes
- add arngrims changes, so that each toy can now be configured to be 0 (sound effect), 1 (DOF) or 2 (both)
- fix hit distance check for hit targets
 

[Drybonz]

Are those core.vbs changes anything that the end user types should know about specifically?

[fuzzel]

not really but new tables may need it.

[gabrom78]

Would it be possible to run or  continue a WIP table from 10.1 to 10.2 beta?

[toxie]

Yes, 10.2 will always stay fully backwards compatible to 10.0 and 10.1. Just not the other way round.

[fuzzel]

Indeed and at a later point of the 10.2 development we will increase the file format version too. So at that point you'll get a warning if you try to load a 10.2 table with 10.0 or 10.1.
So as long as you don't use new 10.2 stuff in your table it should be playable in all 10.x versions.

[ClarkKent]

Thank you fuzzel an toxie - you guys are incredible! I wonder how you find so much time to develop all the wonderful things for VPX!?

[fuzzel]

Ha me too

[toxie]

Its a good motivation when you know that people actually will use certain features..

[ClarkKent]

Just curious - can the kicker already be used without legacy mode or is the problem still there?

[hauntfreaks]

feature request: can there be normal maps for the playfield?

[fuzzel]

Just curious - can the kicker already be used without legacy mode or is the problem still there?

Yes but only on the playfield and not on a raised one. There is something fishy with the friction handling if the ball rolls on wall and travels into a kicker. So as long as the kicker is on the playfield it should be ok.

feature request: can there be normal maps for the playfield?

Should be possible but I haven't checked the code yet. What you want to achieve with a normal map on the playfield?