1972 replies to this topic

[Drybonz]

not for existing tables though

 

Weird.  I'm getting an auto-generated .ini the first time I launch a table.  This just started.

 

I just updated my motherboard and cpu, and thinking I was going to be able to max everything with a new i9, but found that I have a steady microstutter in the ball movement... I'm sure I've either forgotten something in the x64 installation, or missed a setting somewhere, so I'm still working on it.  Everything was harder than it should have been this time.

[wiesshund]

bug report it in github

[lminimart]

 

not for existing tables though

 

Weird.  I'm getting an auto-generated .ini the first time I launch a table.  This just started.

 

I just updated my motherboard and cpu, and thinking I was going to be able to max everything with a new i9, but found that I have a steady microstutter in the ball movement... I'm sure I've either forgotten something in the x64 installation, or missed a setting somewhere, so I'm still working on it.  Everything was harder than it should have been this time.

 

What build are you running? I'm on VPinballX-10.8.0-1591-062e55d-Release-win-x64 as of this weekend. Had been running with frame pacing for weeks without issue using an older build. Now, I'm finding with frame pacing on, I get periods of stutter and the FPS meter goes steady red when this happens. These stuttering fits usually let up after a while. Seems related to the ball rendering actually. When the ball isn't on-screen things usually calm down. But really, it's more or less random. I'm going back to vsync for now to see how that fares.

[unclewilly]

Anyone have an issue with the newest build when trying to enter the nudge settings in the 32 but dx version I think 1610. I get a crash and cannot enter that options menu but only with 32 bit dx

[spacegoogie]

 

 

not for existing tables though

 

Weird.  I'm getting an auto-generated .ini the first time I launch a table.  This just started.

 

I just updated my motherboard and cpu, and thinking I was going to be able to max everything with a new i9, but found that I have a steady microstutter in the ball movement... I'm sure I've either forgotten something in the x64 installation, or missed a setting somewhere, so I'm still working on it.  Everything was harder than it should have been this time.

 

What build are you running? I'm on VPinballX-10.8.0-1591-062e55d-Release-win-x64 as of this weekend. Had been running with frame pacing for weeks without issue using an older build. Now, I'm finding with frame pacing on, I get periods of stutter and the FPS meter goes steady red when this happens. These stuttering fits usually let up after a while. Seems related to the ball rendering actually. When the ball isn't on-screen things usually calm down. But really, it's more or less random. I'm going back to vsync for now to see how that fares.

I thought it was just me.

[Drybonz]

What build are you running?

 

Thanks.  I'll try going back a few builds... it's tough for me to troubleshoot these changes right now until I get everything set up and ironed out again.

[lminimart]

I just played for over an hour with vsync instead of frame pacing and I don't think I saw a single issue. Something *seems* to have regressed with frame pacing, but... that's just the view from my basement! I'll be curious to hear other reports.

[Drybonz]

I just played for over an hour with vsync instead of frame pacing and I don't think I saw a single issue. Something *seems* to have regressed with frame pacing, but... that's just the view from my basement! I'll be curious to hear other reports.

 

Is this still on 1591 that you mentioned, above, or are you on the latest and just having better results with vsync?

[lminimart]

Still on 1591. Just switched from frame pacing to vsync to see if frame pacing was the thing that changed for the worse. Seems like maybe?

[BostonBuckeye]

Starting with version 1596 there is now an "Assets" folder that downloads in the zip file. Can someone please let me know where I need to place these files in order for VPX to run properly. Thanks.

[wiesshund]

Starting with version 1596 there is now an "Assets" folder that downloads in the zip file. Can someone please let me know where I need to place these files in order for VPX to run properly. Thanks.

Those are not for vpx to run properly

Those are for table authors to mess with, though i dont know what a few of them are

 

Weird.  I'm getting an auto-generated .ini the first time I launch a table.  This just started.

 

Maybe it only does it when opening a table containing overrides?
maybe it is exporting them out to an INI and removing them from the table file?

[BostonBuckeye]

 

Starting with version 1596 there is now an "Assets" folder that downloads in the zip file. Can someone please let me know where I need to place these files in order for VPX to run properly. Thanks.

Those are not for vpx to run properly

Those are for table authors to mess with, though i dont know what a few of them are

 

 

Thanks. For some reason I am getting some errors when I try to run any table starting with version 1596. The last version that runs properly for me is 1593. 

 

 

So I just installed version 1613 and when I launch a table VPX says it can't open "BallEnv.exr", "AODither.webp" and "EnvMap.webp". So don't these files need to be placed somewhere now for VPX to run correctly?

Edited by BostonBuckeye, 17 October 2023 - 01:29 AM.

[Drybonz]

maybe it is exporting them out to an INI and removing them from the table file?

Maybe it only does it when opening a table containing overrides?

 

Yeah, there were a few recent actions, like this one, that seem like they go with what you are saying.  

 

Remove AA from table properties (use ini override instead) · vpinball/vpinball@a3f8d76 (github.com)

 So I just installed version 1613 and when I launch a table VPX says it can't open "BallEnv.exr", "AODither.webp" and "EnvMap.webp". So don't these files need to be placed somewhere now for VPX to run correctly?

 

All the stuff in the build updates just goes in your Visual Pinball folder in the same directory structure that you get with the update.  Just copy and paste it all in there.

Edited by Drybonz, 17 October 2023 - 03:50 AM.

[wiesshund]

Thanks. For some reason I am getting some errors when I try to run any table starting with version 1596. The last version that runs properly for me is 1593. 

 

 

 

 

So I just installed version 1613 and when I launch a table VPX says it can't open "BallEnv.exr", "AODither.webp" and "EnvMap.webp". So don't these files need to be placed somewhere now for VPX to run correctly?

 

 

you wont get that error if
you use the entire beta zip instead of trying to selectively pick and choose parts

 

or simply dont open one of the example tables that came with it, no other table would be looking for said assets
no other table would even know about them

[BostonBuckeye]

 

Thanks. For some reason I am getting some errors when I try to run any table starting with version 1596. The last version that runs properly for me is 1593. 

 

 

 

 

So I just installed version 1613 and when I launch a table VPX says it can't open "BallEnv.exr", "AODither.webp" and "EnvMap.webp". So don't these files need to be placed somewhere now for VPX to run correctly?

 

 

you wont get that error if
you use the entire beta zip instead of trying to selectively pick and choose parts

 

or simply dont open one of the example tables that came with it, no other table would be looking for said assets
no other table would even know about them

 

 

Thanks. I placed the entire "assets" folder in the "VisualPinball" folder and now it works properly. All set.

[Drybonz]

Still on 1591. Just switched from frame pacing to vsync to see if frame pacing was the thing that changed for the worse. Seems like maybe?

 

I rolled back to 1577 (because I already had it downloaded) but still getting ball stutter with vsync and frame pacing, but FP seems to be slightly better, so I still have something else going on.  Messed around with video settings and they all seem to be where they should be, so probably something with my installation... probably something obvious.

[Tiki]

I was running into the same problem with OpenGL, DMDs would be behind the screen in Full Screen DeskTop.

I was only using GL because DX was giving me some rendering some bad jaggy textures while GL wasn't. Then I learned I needed to check Alterative Depth Buffer Processing in Graphics Options, and that problem was solved and am happily running DX now without problems.

As for performance, I didn't notice much of a difference between the two, I was getting 60fps in both at 3840x2160 60hz and more or less medium settings.

There is a workaround for showing dmd and backglass, found by Jarr3 and Cliffy:
Set your Screenwidth -1
Meaning: If you have 1920x1080, set it to 1919x1079

In GL Playfield is acting as fullscreen, even if it is set to windowed. This is a bug. With this workarround vpx gl shows Backglass and DMD on Desktop 1 Screen.

Hope this bug will be fixed soon, because GL is unplayable for all ppl playing on only one screen.
https://github.com/v...ball/issues/742

Edited by Tiki, 17 October 2023 - 12:52 PM.

[Guinness]

Interesting little hack, one that shouldn't be need to be done but hey it works

[wiesshund]

or run GL like this

 

[ssangster]

 

Still on 1591. Just switched from frame pacing to vsync to see if frame pacing was the thing that changed for the worse. Seems like maybe?

 

I rolled back to 1577 (because I already had it downloaded) but still getting ball stutter with vsync and frame pacing, but FP seems to be slightly better, so I still have something else going on.  Messed around with video settings and they all seem to be where they should be, so probably something with my installation... probably something obvious.

 

I am finding that if I mess about with the sync settings (frame pacing and adaptive) and change from dx to gl and vice versa, the frame rate seems to get worse every time I change something. When I overwrite with a newer build, things go back to a steady frame rate. I am on the edge of having the power to run these new tables, so maybe that has something to do with it.