1972 replies to this topic

[SmedleyB]

Looking for ideas for further testing of the issue linked below to help me rule out that this is a problem in the GL build vs something unique to my machine. I've tried about everything that google could identify over the past decade related to gaming FPS issues using dual monitors with different refresh rates and nothing has effected the behavior. (Hardware scaling on GPU, various Nvidia settings using extended config tools, playfield at 120hz &

backglass at 60hz, etc, etc)

 

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

 

The testufo.com martian shows a steady, locked 165fps on my main monitor while I am seeing tearing / ball stutter in GL VPX and also while VPX's F11 reports a steady hardware synched ~165fps.

Edited by SmedleyB, 28 February 2024 - 03:14 PM.

[wrd1972]

Drivers are up to date.

Okay some tables load directly and some dont. I will keep trying to figure why that is.

[Urko]

Putting this here , hope noone minds rather than make its own thread.

 

Window Top Z ofs

Window Bottom Z ofs

 

Experimenting with these settings, i tend to make a mess of the table.

Does one just adjust them until you get the look to your liking ?

 

I dont full understand the settings, even though i realise they adjust the slope of each half of the table.

[SmedleyB]

Putting this here , hope noone minds rather than make its own thread.

 

Window Top Z ofs

Window Bottom Z ofs

 

Experimenting with these settings, i tend to make a mess of the table.

Does one just adjust them until you get the look to your liking ?

 

I dont full understand the settings, even though i realise they adjust the slope of each half of the table.

 

Did you read through this? https://www.vpforums...=51455&p=533759
 

It's basically personal preference. Some tables ship with the real-world glass height and if you don't like the way VPX draws it, feel free to override. Other tables are missing the glass height data or have just plain wrong data....then for sure it's up to you to dial in the POV.
 If your playfield monitor is in the realm of 10 degrees, another good way to "cheat" is temporarily make the side rails visible and align them evenly to the sides of your monitor. That's an easy way to avoid black space in the top corners of your monitor.

[Urko]

 

Putting this here , hope noone minds rather than make its own thread.

 

Window Top Z ofs

Window Bottom Z ofs

 

Experimenting with these settings, i tend to make a mess of the table.

Does one just adjust them until you get the look to your liking ?

 

I dont full understand the settings, even though i realise they adjust the slope of each half of the table.

 

Did you read through this? https://www.vpforums...=51455&p=533759
 

It's basically personal preference. Some tables ship with the real-world glass height and if you don't like the way VPX draws it, feel free to override. Other tables are missing the glass height data or have just plain wrong data....then for sure it's up to you to dial in the POV.
 If your playfield monitor is in the realm of 10 degrees, another good way to "cheat" is temporarily make the side rails visible and align them evenly to the sides of your monitor. That's an easy way to avoid black space in the top corners of your monitor.

 

Found this as well but thanks for your info too.

https://github.com/v...s/View Setup.md

[Umpa]

Looking for ideas for further testing of the issue linked below to help me rule out that this is a problem in the GL build vs something unique to my machine. I've tried about everything that google could identify over the past decade related to gaming FPS issues using dual monitors with different refresh rates and nothing has effected the behavior. (Hardware scaling on GPU, various Nvidia settings using extended config tools, playfield at 120hz &
backglass at 60hz, etc, etc)
 
https://github.com/v...all/issues/1487
 
The testufo.com martian shows a steady, locked 165fps on my main monitor while I am seeing tearing / ball stutter in GL VPX and also while VPX's F11 reports a steady hardware synched ~165fps.

I can tell you from my experience when running tables with PupPacks to get rid of the ball stutter, I changed frame pacing to vsync. Then it was smooth.

Sent from my SM-A536U using Tapatalk

[Ltek]

Bug Report... [RC1] DX 64bit crashes to desktop on exit when videos on playfield

 

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

[kiwi]

According to the drawings, the measurements of the Granny and the Gators playfield are 20 1/4 x 24 1/2 inches.

 

Edit: I'm not sure, maybe even Baby Pacman has the same measurements.

Edited by kiwi, 10 March 2024 - 04:38 PM.

[RYSr]

currently running Vpin _ GL master v1923 with no issues.

Decided to try 10.8.1 v2090 as well as latest v2121 from GetHub,  All the straight lines look like saw teeth. Any Ideas

[Urko]

10.8.1 is experimental, stick to 10.8.0 Master files.

Edited by Urko, 11 March 2024 - 01:49 AM.

[RYSr]

10.8.1 is experimental, stick to 10.8.0 Master files.

Thanks, I know it's experimental, but was wondering if there was something that needed upgrading software wise to run 10.8.1, the way it looks is totally unusable. I,m using Win 10 and Steam for the VR. I'm using the 64 bit versions on VP related apps. I just thought I missed something. I will post to GitHub if no one has an idea what's causing it here. Some one needs to try 10.8.1 some times to keep it on track... It's easy enough to revert back to a working version.

Edited by RYSr, 11 March 2024 - 01:09 PM.

[hmueck]

There's a bug in 10.8.1 starting rev 1878: VR resolution is linked to the resolution of the preview window.

[RYSr]

There's a bug in 10.8.1 starting rev 1878: VR resolution is linked to the resolution of the preview window.

Thanks hmueck, Then this is a known problem ? No need to post on GitHub? Just wait for a fix..

[hmueck]

Yes, there's an open issue for this problem since December: https://github.com/v...all/issues/1291

[Bradbury1]

Does anyone else have the problem that the Visual Pinball X 10.8.0 Release Candidate 2 DirectX 64 Exe is recognized as a trojan by Windows Defender?

[jpsalas]

Yes, this happens from time to time, mostly because the EXE files used to be compressed, and Windows Defender didn't liked compressed EXE files It didn't like VBS files too. So I simple put the whole VP path as an exception folder with s batch file like this:

 

powershell -Command Add-MpPreference -ExclusionPath "C:\Visual_Pinball"

 

This will speed up VP too, as Windows won't bother monitoring the folder, and I even add the EXE file too, like this:

 

powershell -Command Add-MpPreference -ExclusionProcess "c:\Visual_Pinball\VPinballX.exe"

 

And I do the same with the other VP EXE files too

[Bradbury1]

Thank you so much! I will put that into practice and I am glad that it is probably no real threat.

[Urko]

Does anyone else have the problem that the Visual Pinball X 10.8.0 Release Candidate 2 DirectX 64 Exe is recognized as a trojan by Windows Defender?

Norton does too, i just ignore.

[terry guignard]

Does anyone else have a problem with Visual Pinball X 10.8.0 Release Candidate 2 DirectX 64 Exe that some tables are not loading, or working properly? etc.Guns N Roses (Data East 1994) VPW v1.1  ,,,,,I revert back to candidate 1 ,all ok? im using vpinmame v3.6-822-66be20f

Edited by terry guignard, 19 March 2024 - 01:27 AM.

[Urko]

Does anyone else have a problem with Visual Pinball X 10.8.0 Release Candidate 2 DirectX 64 Exe that some tables are not loading, or working properly? etc.Guns N Roses (Data East 1994) VPW v1.1  ,,,,,I revert back to candidate 1 ,all ok?

Have you updated your Vpinmame ?

Forget that, its late here, it must be ok or it wouldnt work with candidate 1.

Edited by Urko, 19 March 2024 - 01:22 AM.