1488 replies to this topic

[fuzzel]

rev3556 is up:

 

- add "Player" / "BWRendering" reg-entry: experimental fake Black&White rendering, which can be tremendously faster on tablets (0 (off) or 1 (better quality) or 2 (could be faster on some very slow/old devices)). Currently only works without dynamic AO and any kind of AA disabled
- make script editor UI look a bit better in 4K
- fix regression so that the default font name (i.e. courier) is not used anymore in the script editor if the registry setting is empty
- add strength parameter for the (optional) legacy/VP9-like keyboard nudging code, can be set in the 'Keys, Nudge and DOF' preferences dialog

- cleanups
 

Edited by fuzzel, 17 November 2018 - 05:24 PM.

[Aubrel]

 

Hi, I have digital nudges on my cab (keys) and with VP9 the effect was great (a little too much but great and usefull).

With VPX I have approx no effect on the ball direction and in my case nudging appears to be mostly useless (I can't save any ball by nudging left/right anymore).

Edit : I know it's still working because elements and stopped balls still move when I nudge.

 

I've tried the "Legacy/VP9-Style nudge" option in VPX but with this option the result is really abused : 5cm deplacement of the ball each time (way more than the result with VP9).

I use 10.5 version of VPX and defaut tables settings. It would be very nice to lower a lot the effect of the "Legacy/VP9-Style nudge" option in the next VPX release

 

Anyway, thanks for all: VPX is awsome!!

 

The next build will feature an additional strength setting in the key/nudge/dof dialog. Please test it and let me know if that is good enough (and also what you would recommend as a setting there to better match VP9).

 

 

Thank you for the new beta and this update!!

Already tested with success on a few tables, having the ability to set the strength is just perfect !!
- To reach the same result as VP9 on my cab, it should be set at approx 40%
- To be perfect for me (so a little less exaggereted than with VP9) I set it at 30%

BTW I have a strange configuration: only 2 tactile switches hidden under the rails (left & right).
To nudge I have to hit my cab (rails) and the contact is very quick (so a very quick key action) but now, like that, it's just perfect!!

You have made my day! Thanks a lot guys!! Your are amazing and VPX too!

Edited by Aubrel, 17 November 2018 - 09:45 PM.

[toxie]

- add "Player" / "BWRendering" reg-entry: experimental fake Black&White rendering, which can be tremendously faster on tablets (0 (off) or 1 (better quality) or 2 (could be faster on some very slow/old devices)). Currently only works without dynamic AO and any kind of AA disabled
 

 

Just a comment on that one: I did A LOT of experiments in the last months regarding faster rendering on low end devices, such as tablets. Turns out the major factor why it's slow is: memory bandwidth.  :/

The bad thing with that is that there is not much one can do except for reducing memory traffic, so that's why i introduced this weird grayscale rendering mode, which cuts required bandwidth mostly in half, which immediately translates also to ~2x performance on my tablet for most tables.  

 

So maybe that's better to play in grayscale than not at all (as it would be to slow) for some of you, too.

[Thalamus]

Options are always nice and I think you've given the guys that are still running on low performance specs a true gift here. Maybe we're so lucky that they even stop playing VP9 and help out to make VPX tables better ;-)

[toxie]

Black and White is really more of a last resort though. It's for the desperate. 

[NailBuster]

Hey Guys,  thinking of an Idea (or workaround) for allowing front-end to pass command line parameters that can be accessed in table script...

 

something like:   

 

vpinballx.exe -play "xxxx" -c1 "something" -c2 "anotherthing"

 

and in table script be able to just do

 

if GetCustomParam(1) = "something" Then xxxxx

 

Would be cool to allow frontend to pass parameters to same vpx file so it can allow lots of different 'run-types'.... run with PinUP pack...run without, change cgamename....

[hanzoverfist]

Absolutely the right place to ask for that, and i'd love to have that, too, btw..

 

I guess doing this on a per-table basis would not make sense, as the majority of table authors might just ignore touch-support..

So would doing this globally be good enough?

 

and please think in terms of portrait mode as well.

[blechsm]

Hello,

 

for the new Bumper Skirt animation I have a bug report (or feature request ?):

 

In many EM pinballs two bumpers are operated in parallel by the same relay. That means when Bumper 1 is hit both Bumper 1 and 2 rings move down.

In VP i simulate this by calling "Bumper2.PlayHit()" in "Sub Bumper1_Hit()" and vice versa.

 

Unfortunately for Bumper2 this plays not only the ring animation (which is intended) but now also the skirt animation (which looks rather unrealistic because there is actually no ball nearby).

 

Is it possible for "PlayHit()" to

- play only the ring animation

- or enable/disable the skirt animation by a parameter ? (I do not know any posible other intention for "PlayHit()" ).

 

Thank you and Best Regards,

Gunter

[fuzzel]

Hello,
 
for the new Bumper Skirt animation I have a bug report (or feature request ?):
 
In many EM pinballs two bumpers are operated in parallel by the same relay. That means when Bumper 1 is hit both Bumper 1 and 2 rings move down.
In VP i simulate this by calling "Bumper2.PlayHit()" in "Sub Bumper1_Hit()" and vice versa.
 
Unfortunately for Bumper2 this plays not only the ring animation (which is intended) but now also the skirt animation (which looks rather unrealistic because there is actually no ball nearby).
 
Is it possible for "PlayHit()" to
- play only the ring animation
- or enable/disable the skirt animation by a parameter ? (I do not know any posible other intention for "PlayHit()" ).
 
Thank you and Best Regards,
Gunter

I'll take a look...

[TerryRed]

Hey Guys,  thinking of an Idea (or workaround) for allowing front-end to pass command line parameters that can be accessed in table script...

 

something like:   

 

vpinballx.exe -play "xxxx" -c1 "something" -c2 "anotherthing"

 

and in table script be able to just do

 

if GetCustomParam(1) = "something" Then xxxxx

 

Would be cool to allow frontend to pass parameters to same vpx file so it can allow lots of different 'run-types'.... run with PinUP pack...run without, change cgamename....

 

@Toxie or @fuzzel

 

Of course, I too think this would be a great idea.

[fuzzel]

I'm on it...

[fuzzel]

rev3569 is up:

 

- add support for up to 9 custom start parameters (range 1-9). Usage: "Vpinball.exe -c1 param1 -c2 param2" sets two custom parameter "param1" and "param2". In the script use: GetCustomParam(1) to get "param1" and GetCustomParam(2) to get "param2"
- add EnableSkirtAnimation to enable/disable skirt animation via script
- fix messagebox popping up on table start
- fix script editor crash if core.vbs was not found
- add success message when pressing compile and there are no errors
- fix script UI button not toggling on window close and some more minor cleanups
- cleanups
 

Edited by fuzzel, 22 November 2018 - 04:36 PM.

[Fleep]

Great update ! Thank you for everything you do


Sent from my iPhone using Tapatalk

[wrd1972]

Is there any reason why I should NOT just go ahead and use 10.6 beta for all of my tables on the cab? It cant hose up tables that were stable with 10.5. Is that correct?

[randr]

I found in my last three builds I have to rotate the triggers 180 for inlanes.. seems silly but really seems they should just be that way and only have to rotate them if needed for other switches. Not a huge deal maybe I’m not picking right trigger? Unless it’s a loop you should have to rotate it but again not a big deal

[toxie]

Is there any reason why I should NOT just go ahead and use 10.6 beta for all of my tables on the cab? It cant hose up tables that were stable with 10.5. Is that correct?

 

Should be fine. Especially as long as you do not save any tables with 10.6.

[jpsalas]

rev3569 is up:

 

- add support for up to 9 custom start parameters (range 1-9). Usage: "Vpinball.exe -c1 param1 -c2 param2" sets two custom parameter "param1" and "param2". In the script use: GetCustomParam(1) to get "param1" and GetCustomParam(2) to get "param2"
- add EnableSkirtAnimation to enable/disable skirt animation via script
- fix messagebox popping up on table start
- fix script editor crash if core.vbs was not found
- add success message when pressing compile and there are no errors
- fix script UI button not toggling on window close and some more minor cleanups
- cleanups
 

 

I don't know if this was intentional, but in this revision the script editor doesn't show in the taskbar anymore, and it makes it quite difficult to work with two scripts at the same time.  I use to set two scripts side by side so I could copy/paste what I needed for a new table, but now it looks like the script editor is linked to the main VPX window, and it is always on top of the VPX table. I think this must be a "bug"

[ClarkKent]

Is it possible to add an alphanumeric display like the one for DMDs for desktop view?

[Aubrel]

It seems like CV's integrated DMD isn't shown anymore through ramps and plastics with recent CPX versions :

https://www.vpforums...=14#entry404027

 

Any hope for a fix?

Thanks

[toxie]

 

rev3569 is up:

 

- add support for up to 9 custom start parameters (range 1-9). Usage: "Vpinball.exe -c1 param1 -c2 param2" sets two custom parameter "param1" and "param2". In the script use: GetCustomParam(1) to get "param1" and GetCustomParam(2) to get "param2"
- add EnableSkirtAnimation to enable/disable skirt animation via script
- fix messagebox popping up on table start
- fix script editor crash if core.vbs was not found
- add success message when pressing compile and there are no errors
- fix script UI button not toggling on window close and some more minor cleanups
- cleanups
 

 

I don't know if this was intentional, but in this revision the script editor doesn't show in the taskbar anymore, and it makes it quite difficult to work with two scripts at the same time.  I use to set two scripts side by side so I could copy/paste what I needed for a new table, but now it looks like the script editor is linked to the main VPX window, and it is always on top of the VPX table. I think this must be a "bug"

 

 

There was actually a potential bug with the window creation, and this was my supposed fix. But i can restore the other behavior, no problem.