1972 replies to this topic

[jpsalas]

I'm a little confused by the Direct X vs GL versions at this point.  if I am manually updating the version that came with Baller Installer, would I update using the DirectX or GL version?  

 

Use the GL version if you are using VR, otherwise use the DirectX version.

[Junkyerd]

up sorry double post

Edited by Junkyerd, 09 August 2023 - 07:41 PM.

[Mrtr32]

@jpsalas

 

What DirectX version are you using with VPX8?

 

I'm currently testing on Windows 7 Pro with DirectX 11

 

Thanks

Edited by Mrtr32, 09 August 2023 - 08:51 PM.

[wiesshund]

@jpsalas

 

What DirectX version are you using with VPX8?

 

I'm currently testing on Windows 7 Pro with DirectX 11

 

Thanks

 

VPX uses directX 9.0c regardless of what OS you have

[jpsalas]

 

@jpsalas

 

What DirectX version are you using with VPX8?

 

I'm currently testing on Windows 7 Pro with DirectX 11

 

Thanks

 

VPX uses directX 9.0c regardless of what OS you have

 

 

Yes, that's right, wiesshund.

 

I download it directly from Microsoft:

Download DirectX Redist (June 2010) from Official Microsoft Download Center

[Mrtr32]

After testing intensively VPX8, the table issues come from the Maximum Framerate parameter in the Video/Graphics options
With the previous VPX versions I always limited the FPS to 1 to make the table faster for playback
In VPX8 limiting the FPS to 1 slowdown the table considerably and make it unplayable.
This is the reason why VPINMAME don't interact properly with the table

Currently the solution is to leave the Maximum Framerate value at 0.

Edited by Mrtr32, 10 August 2023 - 02:26 PM.

[wiesshund]

 

After testing intensively VPX8, the table issues come from the Maximum Framerate parameter in the Video/Graphics options
With the previous VPX versions I always limited the FPS to 1 to make the table faster for playback
In VPX8 limiting the FPS to 1 slowdown the table considerably and make it unplayable.
This is the reason why VPINMAME don't interact properly with the table

Currently the solution is to leave the Maximum Framerate value at 0.

 

VPX 8 uses max framerate for max frame rate
VSync is its own dropdown
So id suggest not setting max framerate to 1

[Mrtr32]

@wiesshund

 

Tried the Max framerate value at 0 on my cab with a RTX3090 and the ball dont move smootly on some tables.

the ball move by step and this is very annoying.

Edited by Mrtr32, 10 August 2023 - 05:04 PM.

[wiesshund]

@wiesshund

 

Tried the Max framerate value at 0 on my cab with a RTX3090 and the ball dont move smootly on some tables.

the ball move by step and this is very annoying.

what do you have the vsync dropdown set as?

[wiesshund]

@Mtr32
Running bloodmachines 2.0 on my antique GPUless laptop
the ball rolls smooth, table runs at 40fps (40 fps is all i am getting on this)
Check what you have for sync settings

 

ok i lied
if i enable exclusive full screen it will run between 50 and 60, i just cant see the DMD

ball is not jerky though

[dacstyle]

I'm using GL version with the option FRACE PACING and max framerate set to 0 and it works SUPER SMOOTH

[Mrtr32]

[wiesshund]

 

 

some reason i am only seeing a blank image?

[Mrtr32]

@wiesshund

 

I can't copy/paste my screenshot to the forum

 

Tried frame pacing option without success
No VSynch settings in VPX8 give me the same smooth ball mouvement as in VPX7 with FPS limits option to 1 VSYNCH for every frame (avoids tearing)

Edited by Mrtr32, 10 August 2023 - 07:08 PM.

[wiesshund]

how many fps does vpx say it is rendering if you hit F11?

[Mrtr32]

@wiesshund

 

120.0 fps because I limited my monitors to 120Hz

144.0 fps when I limit my monitors to 144Hz

 

Only some heavy tables like Blood Machines having ball stutters issues.

 

Most of the table work great with smooth ball mouvements.

 

My computer and Video card is blazing fast!

Edited by Mrtr32, 10 August 2023 - 09:15 PM.

[wiesshund]

@wiesshund

 

120.0 fps because I limited my monitors to 120Hz

144.0 fps when I limit my monitors to 144Hz

 

Only some heavy tables like Blood Machines having ball stutters issues.

 

Most of the table work great with smooth ball mouvements.

 

My computer and Video card is blazing fast!

frame pacing as sync method should come out smooth
Any difference if you select just vertical sync?

incidentally frame pacing gives mad fast flipper responses, pretty much only limited to the latency of your controller

so it is best for for things to work using that option

[Mrtr32]

@wiesshund

 

With the frame pacing option, I don't see a big improvement when the ball move.

 

After testing all the video settings with VPX7 before, I noticed a big performence improvement with the FPS Limiter/Vsync option to (1) VSYNCH for every frame (avoids tearing)

 

 

I don't know why this feature has been removed in VPX8 and if an improvement can be done in VSynch option to prevent the ball stutters issues?

[Wylte]

@wiesshund
 
With the frame pacing option, I don't see a big improvement when the ball move.
 
After testing all the video settings with VPX7 before, I noticed a big performence improvement with the FPS Limiter/Vsync option to (1) VSYNCH for every frame (avoids tearing)
 
 
I don't know why this feature has been removed in VPX8 and if an improvement can be done in VSynch option to prevent the ball stutters issues?

FPS limiter hasn't been removed, just modified. The equivalent of the old "1" would be to enter 120 or 144 to match your refresh rate.

[Drybonz]

Only some heavy tables like Blood Machines having ball stutters issues.

 

Where do you have your other video settings?  Some of them, like AA, supersampling, sharpening, etc... are really heavy users.  You might have to back something off a bit.

 

*edit*  Also... don't forget in 10.8 we now have the option to use custom, per table .ini files to edit settings for a single table.

Edited by Drybonz, 10 August 2023 - 11:24 PM.