1353 replies to this topic

[chepas]

Hey no worries, I can understand it's kind of hacked in, so it would be nice to see what others think of the current values.

[Ben Logan]

Fuzzel,

You guys are amazingly responsive to our community's requests for features. Thanks so much. VP is a daily source of fun for me and the family.

[BorgDog]

I'm not sure the light.duration is working right.  seems to get stuck on state 2 and although it shows state 1 or state 0 it doesnt' seem to change, only state 2 has an effect on it once it has run.  test table link below.

 

launch the table. it has a text box showing the "state" of one of the bumper lights.

tap center nudge key (default space bar) it should do a 3 second blink pattern, note at the end it says state=2 for the light, should be 1

tap left flipper, it will turn off lights for a short time, then back on, again says state=2 should be 1

tap right flipper.  it SHOULD turn off the lights, box says light.state=0, but the lights remain on.

 

anything that does a duration with a state of 2 seems to run the blink but leaves it at state 2 although showing what you set it for (in this table it would be 1 and the lights are on, but showing state=2), just a state=0 statement seems to have no effect (right flipper in this example)

 

running latest beta 2786

table---->  https://dl.dropboxus...urationtest.vpx

 

also would it be possible to add an initial state to the command?  so light.duration initialstate, time-ms, end state ?

 

so I could have a light that is normally on, in one statement say light.duration 0, 1000, 1 have the light turn off, stay that way for 1000ms then turn on?

 

thanks

[fuzzel]

rev2790 is up:

 

- fix mouse panning speed
- extend the parameters of light.duration to define a start state e.g. light1.Duration 0,1000,2 (stay off for 1000ms and then blink)
- fix duration time calculation for off state
 

Edited by fuzzel, 13 September 2016 - 01:07 PM.

[BorgDog]

damn awesome fuzzel!

 

edit:  well OK, I spoke too soon.  seems it's still not letting go of the lights.  on the same test table I posted above (oh, had to fix the duration commands first), the right flipper just does a light.state=0 to turn off the lights, which works fine except once you run one of the duration commands (left flipper or center nudge/space bar), the light.state=0 flashes really briefly then the lights come back on.

Edited by BorgDog, 13 September 2016 - 01:19 PM.

[chepas]

Spot on Fuzzel, well done. That's perfect.

[fuzzel]

damn awesome fuzzel!
 
edit:  well OK, I spoke too soon.  seems it's still not letting go of the lights.  on the same test table I posted above (oh, had to fix the duration commands first), the right flipper just does a light.state=0 to turn off the lights, which works fine except once you run one of the duration commands (left flipper or center nudge/space bar), the light.state=0 flashes really briefly then the lights come back on.

Ah yes...Will fix that later...stupid little bug

Edited by fuzzel, 13 September 2016 - 07:38 PM.

[fuzzel]

rev2791 is up:

 

- fix light duration handling

[BorgDog]

rev2791 is up:

 

- fix light duration handling

 

Thanks fuzzel works great!  Really liking the middle mouse button panning as well.

[BorgDog]

rev2786 is up:

 

- use middle mouse button to pan the editor view not alt+mouse move
- expose Version,VPBuildVersion,VersionMajor/Minor/Revision both globally and in table properties to avoid confusion
- fix versionmajor/minor/revision

 

running v2791, versionmajor and versionminor return correct values but all I'm getting for versionrevision is a 0  I was going to put in a check since I'm using the light.duration to pop up a message if versionrevision<2791

[allknowing2012]

I did notice that JP's table (and perhaps others) use the variable "Version".  Not sure if its worth changing at this point though.

[toxie]

thats not an issue. all are still supported, as for revision: please do not use this in official table releases, as we might not include this into the final 10.2 release.

Edited by toxie, 14 September 2016 - 03:07 PM.

[jpsalas]

I did notice that JP's table (and perhaps others) use the variable "Version".  Not sure if its worth changing at this point though.

No problem, I can change that variable on the tables I made. I only use it to display the table's version in the DMD, so I can simply change it to myVersion, for example.

[wrd1972]

 

rev2791 is up:

 

- fix light duration handling

 

Thanks fuzzel works great!  Really liking the middle mouse button panning as well.

 

What pans with the middle button? This got my attention.

[freneticamnesic]

the editor

[freneticamnesic]

so I like being able to move in the editor with the middle button, but shouldn't the movement be 1:1? It feels like it's about .9:1 or something right now

[BorgDog]

You on the latest beta? It seems fairly close to 1:1 or 2:1 at most to me. I know the first version of it was way off.

[freneticamnesic]

Yea it's close enough that I'll get used to it fast but I figure since we're on the subject it would be worth mentioning. The mouse moves farther than the table. If I move the mouse 9 inches the table moves 8

[Drybonz]

I really like the new panning feature... thanks for adding that.  I think it would be great if we could assign it to the space bar to be consistent with PS, AI, etc...

[grunger106]

Is it possible to introduce a setting to specify the source of analog nudge/tilt detection?

I have a USB interface for the button input which is seen by the OS as a Joystick and also Freestyle Pro, under Win10 the nudging works but it's not possible to get a Warning/Tilt.

I had assumed this maybe due to the fact VP can see multiple joystick inputs and isn't sure which one it is supposed to look to for tilt events?

I do have an IPac ready to install which should show up as a keyboard, but I've not had a chance to install it yet....

(Or I may be completely incorrect in my logic - In which case sorry!)

Edited by grunger106, 15 September 2016 - 09:19 AM.