1488 replies to this topic

[BoltBait]

Something I noticed in VPX v5 is that the custom table CARtoons plays the end of game chimes too fast (compared to v4).  It also counts the bonus score too fast on some tables.

 

Is this something that will be addressed in VPX v6?  Or, will the tables need to be updated?

[Thalamus]

@BordBait : I remember that I meantioned something very simular for Aztec a while back. DjRobX fixed it by adjustimg one value in the script. Might be that it is all that is required this time around too. I just need to find what he did and why.

[toxie]

 

Been quiet in here. Must mean the latest 10.6 beta is about ready for prime time!

Sent from my SAMSUNG-SM-G935A using Tapatalk

 

I think they are simply enjoying the summer holidays

 

 

Plus enjoying https://en.wikipedia...al_of_the_Night a bit too much.. 

[Rawnei]

 

 

Been quiet in here. Must mean the latest 10.6 beta is about ready for prime time!

Sent from my SAMSUNG-SM-G935A using Tapatalk

 

I think they are simply enjoying the summer holidays

 

 

Plus enjoying https://en.wikipedia...al_of_the_Night a bit too much.. 

 

 

Nice, one of the games I kickstarted.

 

Got it on Switch!

[Schlabber34]

Question guys:

 

Does anyone have a problem with a different monitor brightness in Exclusive Fullscreen compared to Fullscreen windowed? Never had that before, but i haven't been installing tables in 6 months now. There were a ton of Win and VPX updates inbetween. Fullscreen looks horribly bright and white'ish, windowed looks like it should. It's almost like Exclusive Fullscreen is ignoring my NVidia colour settings! I checked the colour range with a 0,0,0 black image. Colour range seems to be at Full in EFS!

 

I had to use the NVidia colour/brightness/contrast settings because my PF monitor was broken and you couldn't use the settings buttons anymore. The difference in the brightness settings would fit to what i see on the screen. The monitor was set way to bright and i had to reduce it in the NVidia control panel. If i turn the NVidia settings off, everything looks like what i see in VPX EFS-mode! When i make screen shots of both they look exactly the same. So it must be some sort of filter.

 

All updates made, newest drivers installed!

 

Win10; GTX950; Pentium DualCore; 4GB ram

 

Any ideas?

 

Thanks!

Edited by Schreibi34, 10 August 2019 - 12:21 PM.

[fuzzel]

I think it has to do with the updated lighting shading code in 10.6. But that's a quick guess

[Schlabber34]

Thanks for answering, fuzzel!

 

But you should see that in the screen shots, right? Like i said, if i make a screen shot of both modes, they look exactly the same. It's like the NVidia colour settings (which are applied like a filter to the VPX rendering result i guess?) are turned off in exclusive full screen mode.

 

Keep in mind that not many guys use the NVidia colour settings. Most people do it via the monitor settings. To make it even worse, my settings are really extreme.

 

Could someone please try and turn on the NVidia colour setting and lower the brightness to 20%. You should now be able to see the difference between EFS and WFS.

 

Thanks guys!!

[flupper1]

Bug report (or maybe tricky detail of coding in VPX):

While tuning Totan I found something really unexpected: using the script statement "table1.width" a lot slows VPX down really bad. I saw it first on my laptop which has a not so fast graphics card and on battery slows down the processor. I replicated the problem on my development system (core i7 7700k and GTX 1080Ti). On the latter my framerate without this statement is about 240fps (4k, no AA), and with 20x this statement in a timer event:  "test=table1.width" (timer interval 10), the fps is reduced to 45fps (!!).

On my battery powered laptop (no power attached so the processor is is eco mode), the FPS went from 60fps to 80fps, just by removing the reference to "table1.width" (was called 7 times or something per timer event, due to the many balls in Totan).

On White Water the effect was less substantial, the fps went from 106 to 116 on my laptop.

The script workaround is of course to only get the table1.width value in a global variable once, but it was really unexpected to me that this statement is so costly. I think that every table that has this statement in use for ball shadows or something, can be faster especially on lower end systems.

[BorgDog]

Thanks for the heads up on that @flupper1, I'll be sure to change how I do that in future works.  Another that does the same thing is the EVAL statement.

[DJRobX]

@fuzzel, @toxie

 

The reason table.width is slow is because the get_Width function is calling:

 

g_pvp->SetStatusBarUnitInfo("", true);

 

This in turn causes a windows SendMessage to the status bar object, which is ... slow.

 

This same line is in a few other strange places (like plunger get x, y).   Not sure why you'd want to update the status bar on a READ of these values.   Writes maybe ... but even then you probably want to check that the table is not playing before trying to do an update to the regular vp window.

 

-- Rob 

Edited by DJRobX, 12 August 2019 - 01:30 AM.

[fuzzel]

Right will change that asap

[toxie]

Thanks for answering, fuzzel!

 

But you should see that in the screen shots, right? Like i said, if i make a screen shot of both modes, they look exactly the same. It's like the NVidia colour settings (which are applied like a filter to the VPX rendering result i guess?) are turned off in exclusive full screen mode.

 

Keep in mind that not many guys use the NVidia colour settings. Most people do it via the monitor settings. To make it even worse, my settings are really extreme.

 

Could someone please try and turn on the NVidia colour setting and lower the brightness to 20%. You should now be able to see the difference between EFS and WFS.

 

Thanks guys!!

 

Sounds like a NVIDIA driver issue to me. Have you tried a recent driver, but from a different driver branch? Use: https://www.nvidia.d...nd.aspx?lang=de and then select for example one from R418 or R410 instead of R430 (or vice versa).

 

 

 

Been quiet in here. Must mean the latest 10.6 beta is about ready for prime time!

Sent from my SAMSUNG-SM-G935A using Tapatalk

 

I think they are simply enjoying the summer holidays

 

 

Plus enjoying https://en.wikipedia...al_of_the_Night a bit too much.. 

 

 

Nice, one of the games I kickstarted.

 

Got it on Switch!

 

 

I hope i can finally 100% it soon (like all the other Metroidvanias i played ). And then back to finishing up the VPX/VPM release finally.

[Schlabber34]

Thanks toxie! Will try...

[vogliadicane]

Not sure, if people realized, but since a few revs, when you switch back to force exclusive fullscreen mode from windowed, the last setting is taken, so you don't have to search through all the mass of options again.

Very handy, thanks Fuzzel and Toxie.

[fripounet]

can you integrate reshade (open source), for its quality and ease of use (real time), for optimized management of lights and colors specific to pinball?

or get in touch with crosire (reshade developer)

Edited by fripounet, 12 August 2019 - 07:09 PM.

[fuzzel]

Sorry but that thing won't work for VPX because of the static render step we do at the beginning.

[toxie]

I personally know crosire, but why should we even include reshade? It's postprocessing that can already be used with VPX right now by dropping in the d3d9 dll of reshade.

 

Changing other parameters/VPX-specific-stuff in realtime is also already possible via the F6-Camera/Material/Light edit mode.

[fripounet]

I personally know crosire, but why should we even include reshade? It's postprocessing that can already be used with VPX right now by dropping in the d3d9 dll of reshade.

 

Changing other parameters/VPX-specific-stuff in realtime is also already possible via the F6-Camera/Material/Light edit mode.

precisely, to be able to use the d3d11.dll because it does not seem to work with vpx....

[fuzzel]

That's because we're using dx9

[toxie]

But for reshade there is no difference if you use d3d9.dll and d3d11.dll as far as i know. The only thing that COULD be different is if the game outputs HDR (i.e. as the very final buffer), which both of these titles don't, as far as i know.