1856 replies to this topic

[SmedleyB]

@LoadedWeapon What other monitors do you run on your setup and which screens were visible for Futurama? Do the backglass and/or fulldmd screens take up the entirety of the monitors, for example?

[LoadedWeapon]

@LoadedWeapon What other monitors do you run on your setup and which screens were visible for Futurama? Do the backglass and/or fulldmd screens take up the entirety of the monitors, for example?

Yes I run a 2k backglass at 165hz and a 1920x1080 full dmd at 60hz
You can pm me or join our discord to keep this post clear.

Edited by LoadedWeapon, 24 April 2024 - 04:41 PM.

[terry guignard]

Is anyone running a 144 or 165hz playfield monitor with a 60hz backglass and/or fulldmd monitor?
If you're also running Win11, could you do me a favor and run Futurama in GL exclusive fullscreen and let me know if you see any stutter, or rather is the stutter any worse than when running under fullscreen DX?

This is pertaining to the issue I opened here: https://github.com/v...all/issues/1487

You don't have to read the whole thing, just the very last comment. Windows 11 has some improvements when it comes to handling dual monitors with different refresh rates and I'm trying to find if moving from win10 to Win11 will allow me to use GL stutter free.

...as I type this I am also realizing that perhaps since I run a vert backglass monitor and place both my backglass and dmd windows on it, not running the b2s or pup windows in fullscreen across all of their monitor like most folks do, maybe that's part of the problem.

I  don't know if this would help you any.....I'm running windows 11 23H2 since dec....i5 12400f ...4060ti...2monitors 144hz playfield 60hz backglass....I've been playing arround with every setting. Tried GL ,Windowed and fullscreen I don't realy get stutter but less lifelike play.  I've choosed to stick with RC1-DX,less issues with certain games, frame pacing set at 120 but my monitors are set to their max frame rate. All my settings in VPX are allmost maxed out..I've also stopped using F11 to get monitoring of Fps and Latency because of inconsisty every time I open and close the same table.Bee'n only setting by game play and not by numbers,in other words using the force... I have pup's and regular B2s running well, I have no stutter....Screen shots on page 91

[SmedleyB]

 

@LoadedWeapon What other monitors do you run on your setup and which screens were visible for Futurama? Do the backglass and/or fulldmd screens take up the entirety of the monitors, for example?

Yes I run a 2k backglass at 165hz and a 1920x1080 full dmd at 60hz
You can pm me or join our discord to keep this post clear.

 

It won't let me send you a msg, can you send me one?
 

Here's the relevant info:

 

I've got everything written up on github. It's a lot, but last 2 comments are all you really need.

https://github.com/v...all/issues/1487

 

I pretty firmly believe it's Windows DWM causing the tearing by lowering the refresh on my 165 monitor down to 120.

For Futurama, I run a 1440x810 window for backglass and 1280x720 fulldmd window on my vert 1440x2560 monitor. The oddest behavior is if via the pup pack editor, I disable either the backglass or fulldmd window and leave only one or the other up and running, I get no tearing. But if I leave them both on, I get tearing.

Edited by SmedleyB, 24 April 2024 - 05:49 PM.

[kaledev]

I've noticed in 10.8 RC3 (and the latest from actions, maybe others) - the DOF Controller Options in the VPX options no longer works. I still have DOF, but if I try changing the flippers to soundfx (or others), the DOF still works as normal instead of cutting it off. I noticed that the registry keys in "Software\Visual Pinball\Controller" aren't changing when I change the menu options. They DO seem to still change in 10.7. Anyone else encountered this?

[Ltek]

I think this is an Option Menu (F12 tweak menu)  bug... Last few RC when making a selection inside a row/option (a choice inside a given option) the change to so fast its nearly impossible to control. Problem is for sure when adjusting Table's Vertical position and many that have a long list of choices in that option.  ( series of numbers, Night/Day, etc)

 

 

Is there a fix?

Edited by Ltek, 01 May 2024 - 03:08 PM.

[Duracuir]

Hi guys ,
 
I ve got Windows report errors when i open and close VpinballX.ini . errrors BEX64 concerning nvoglv64.dll
I can play despite this error but it's annoying to have it.
 
I tried multiple things :
 
- Deleting ini to recreate it when launching vpx
- Clean install of lastests nvidia video drivers
- Update of .Net Framawork and C++ redistribuables
- Update vpinmame to lastest version

 

Pease I need help

[CrimsonTurtle8]

How many people do we think haven't upgraded to 10.8? There are some VPX 10.8 features I've heard only work in 10.8 that I'd love to use, but I don't want my tables to be broken if played by people who aren't constantly downloading the cutting edge beta version.

[kaledev]

How many people do we think haven't upgraded to 10.8? There are some VPX 10.8 features I've heard only work in 10.8 that I'd love to use, but I don't want my tables to be broken if played by people who aren't constantly downloading the cutting edge beta version.

I've only had a few tables break out of a couple hundred - mostly very old ones. But you can keep a copy of 10.7 and run them using that as an alternate launcher.

[jtrosky]

The issue I'm running into now is that newer tables require latest version of vpinmame - but the newer versions of vpinmame seem to break some tables - and I don't know of a way to have multiple versions of vpinmame depending on the table...

I recently updated to the latest vpinmame and found it broke lights on AC/DC, for example...

[ryesteve]

 

How many people do we think haven't upgraded to 10.8? There are some VPX 10.8 features I've heard only work in 10.8 that I'd love to use, but I don't want my tables to be broken if played by people who aren't constantly downloading the cutting edge beta version.

I've only had a few tables break out of a couple hundred - mostly very old ones. But you can keep a copy of 10.7 and run them using that as an alternate launcher.

 

 

That doesn't work when it's vpinmame breaking the tables.  

 

I'd been resistant to upgrade to the latest beta, but I've given up on waiting.  There are more tables now that need the new version than tables that are broken by it.  

[kaledev]

The issue I'm running into now is that newer tables require latest version of vpinmame - but the newer versions of vpinmame seem to break some tables - and I don't know of a way to have multiple versions of vpinmame depending on the table...

I recently updated to the latest vpinmame and found it broke lights on AC/DC, for example...

AC/DC did break for me, but worked when I run it with 32b, may be a different error!

[CrimsonTurtle8]

 

 

How many people do we think haven't upgraded to 10.8? There are some VPX 10.8 features I've heard only work in 10.8 that I'd love to use, but I don't want my tables to be broken if played by people who aren't constantly downloading the cutting edge beta version.

I've only had a few tables break out of a couple hundred - mostly very old ones. But you can keep a copy of 10.7 and run them using that as an alternate launcher.

 

 

That doesn't work when it's vpinmame breaking the tables.  

 

I'd been resistant to upgrade to the latest beta, but I've given up on waiting.  There are more tables now that need the new version than tables that are broken by it.  

 

Interesting. That might have answered my question. Granted, there may also be hundreds of lurker players who just casually download and play tables as they come without ever really talking in the forums. Like my tables have way more downloads than I thought I'd ever get and not many written reviews. There are lots of silent people out there enjoying VPX, and I worry most of them just are happy with 10.7

[GHOSTfaceKILLr7]

 

 

 

How many people do we think haven't upgraded to 10.8? There are some VPX 10.8 features I've heard only work in 10.8 that I'd love to use, but I don't want my tables to be broken if played by people who aren't constantly downloading the cutting edge beta version.

I've only had a few tables break out of a couple hundred - mostly very old ones. But you can keep a copy of 10.7 and run them using that as an alternate launcher.

 

 

That doesn't work when it's vpinmame breaking the tables.  

 

I'd been resistant to upgrade to the latest beta, but I've given up on waiting.  There are more tables now that need the new version than tables that are broken by it.  

 

Interesting. That might have answered my question. Granted, there may also be hundreds of lurker players who just casually download and play tables as they come without ever really talking in the forums. Like my tables have way more downloads than I thought I'd ever get and not many written reviews. There are lots of silent people out there enjoying VPX, and I worry most of them just are happy with 10.7

 

I'm not going to sugar coat it. It's going to be a nightmare combing through your collection of thousand plus tables to find what is broken after updating to the latest vpx, vpinmame, flexdmd, pup and so on. Don't get me started on the multiple VP forums, GitHub and all the info you'll need to sift through to find script fixes on some of these broken tables.

 

Speaking for myself I have all the tables I could ever want and I willingly went through the nightmarish process of getting all of them to work with the latest updates.

With that being said I'm at my wits end having a bunch of tables break every time I update just to get the newest VPW table in my collection.

Once the final VPX 10.8.0 is released I'll comb through all my tables one last time, fix whatever needs fixing and I'm retiring from the hobby for a couple years.

[Urko]

The issue I'm running into now is that newer tables require latest version of vpinmame - but the newer versions of vpinmame seem to break some tables - and I don't know of a way to have multiple versions of vpinmame depending on the table...

I recently updated to the latest vpinmame and found it broke lights on AC/DC, for example...

Most authors are using the latest VPX and Vpinmame to create their tables, and i am sure have been for months now.

I have had no issues with any overall.

[kaledev]

I did have to go through every single table and update the Window pov because I couldn't get a defaulted one to look normal and every single table was slightly different - that took a few weeks and was annoying.

[unclewilly]

I don't see much happening on github for the 10.8, only on the 10.8.1 and Standalone. Should we be expecting, the 10.8 final release soon?