12 replies to this topic

[tttttwii]

Issue:

When starting a game in VPX everything runs smooth and fast without any performance issues. After playing 3-4 games, the games starts to stutter, a few games later the whole system is running very slow (unplayable). I tried to narrow the issue down by switching everything on/off. It is not PinballX, it happens in all vpinball versions (9.x, VPX, PM5 etc.). If B2S server is diables, everything runs smoothly over a long time. Turning off everything in vid options in VPX to improve performance is not helping: in the beginning everything is smooth, lateron stuttering starts (after 10-15 mins). It is the B2S server!

 

My Specs:

- fastest I5, GTX760 with 2MB, Win10, 500 MB SSD, 8 GB memomy

- I guess the speed of my rig is not the issue.
 

Questions:

- is anyone else experiencing the same issues?

- Might this be a memory leak issue in the B2S server?

- Has somebody solverd this issue / are there any hints what I can improve?

 

Thanks in advance!

Edited by tttttwii, 29 May 2016 - 08:16 AM.

[STAT]

Do you use Backglasses in EXE Mode ? ( rightClick on Backglass .. Edit .. Save )

Table Example ? maybe you try it again with another directb2s File ... if another exists ...

Edited by STAT, 29 May 2016 - 08:43 AM.

[tttttwii]

It is not related to any specific B2S file, same issue with all backglasses. All are running in exe mode. To increse frame skip is not the solution.

[markrock76]

I had the exact same situation when I first installed on a Windows 8 machine.  I thought I had to have compatibility mode checked and set to Windows XP but that is what caused the problem.  Make sure that is not checked.  Also make sure the monitor refresh rate in Windows for all your monitors is 60 and not 59.

[tttttwii]

I had the exact same situation when I first installed on a Windows 8 machine.  I thought I had to have compatibility mode checked and set to Windows XP but that is what caused the problem.  Make sure that is not checked.  Also make sure the monitor refresh rate in Windows for all your monitors is 60 and not 59.

Thanks for you answer. Are you referring to the b2sserverexe.exe or vpinball.com? Have you set the refresh rates in the Nvdia panel?

[Westworld]

> Have you set the refresh rates in the Nvdia panel?

 

yes - or at least check.

I replaced my backglass TV last week and did not found the place for "Game" setting with the new Samsungs. Without this setting the backglass was not running at the same refresh rate as playfield and that produced major stutter...

It is mandatory that all screens run in game mode - then all should be able to run in 60 or 59 herz, but not mixed.

 

All my tables are using B2S. There are obviously serveral bugs in the server and without source they will be never be fixed. Too bad, as only some minor ones are remaining...

But as long you can run the server as EXE speed should not be the issue. As EXE is launched every time, a memory leak would solve itself, simply because the exe is restarted every time. 

There are some some extreme tables there I needed to reduce animation speed and skip some frames, but that is an exception, not a rule (with GTX 970, it was a rule with 570).

[markrock76]

I was referring to VPinball exe.  And Nvidia showed my refresh rate at 60 but windows showed it at 59.  I could change it to 60 but it would always revert back and not stick.  So in Nvidia I created a custom refresh rate of 61 and when I choose that in Windows properties it sticks. This just keeps my fps from dropping below 60 and causing stutter.  I also do vsync at 1 for VPX; VP9 and physmod I don't.  I just let them run wide open and they do fine no stutter.  I get no stutter in VPX either even with reflections and Quality AA, I can even run 4x AA on some tables and it looks great and runs great.  I have Win10, intel i-7 4790 3.6ghz, Nvidia gtx750ti

[wrd1972]

Im glad this came up. DB2S backglasses in general, rob resources from VP9/10 on my pincab. This usually results in a slightly less than buttery smooth ball play. Regardless, its not unplayable.

 

On all of my backglasses, I max out the skip settings to reduce the impact. I am running .exe in the settings as well as 60Hz. Just wish there was more that could be done to reduce the impact.

[shannon1]

I'm having a problem with VP 10.1 running B2S in exe mode. When I don't run a B2S in exe mode I get stutter like crazy, but when I do run it in exe the ball is smooth as butter. The problem is I get this error every time. I do not have DOF on my cab I have the cController.txt=0. I am running Windows10.
I'm still having this problem and when I downloaded the new Buckaroo table I get the same error messages.
http://www.vpforums....-1463885207.png
http://www.vpforums....-1463968506.jpg
I hope someone can help before I blow up my cab!

[tttttwii]

Part of the issue seems to be vsync. I experimented with several settings in the NVDIA control panel : adaptive, on, ... This setting combined with Vpinball setting and having all 3 monitors on 60Hz might help. But nevertheless, as west world saids, I think that there are memory leaks...

 

I cancelled FXAA postprocessing and went to brute-force 4x FXAA without any performance decrease on my rig.

Edited by tttttwii, 30 May 2016 - 05:49 AM.

[Rotrax]

In Windows 10 is defender on. This causes serious problems

Verstuurd vanaf mijn HTC One mini met Tapatalk

[tttttwii]

Thanks to everyone giving improvement hints. I tried everything, which improved the performance but have not solved the FPS drain issue. Win 10 (which was upgraded from Win7) seems not to be compatible with the B2S server.

 

Finally I installed Win7 and everything is working fine!

 

Another obervation:

 

FPS under similar setup/options in Win10: ~120 FPS in Win7: ~ 150 FPS.

[DJRobX]

I think it's just a B2S design issue.   Some directb2s backglasses are fine while others are not.   It won't be fixed either, since B2S is closed source and Herweh isn't working on it anymore. 

 

I just upgraded to an i7 CPU and Nvidia 960GTX and still see clear performance degradation from some .directb2s files.   

 

Interestingly I have found no correlation between directb2s complexity and the performance hit.   Some B2S'es that look complicated don't take any resource drain at all.  While others that just seem to have a few little flickering lights cause a massive FPS drop.    And yes I've played around with the solenoid/light polling settings, they make no difference. 

 

99% of the time I just take a screen grab of the backglass and just delete the Directb2s file.   PinballX and/or Hyperpin will leave the image up there.  Most real pinball machines don't have animated backglasses anyway. DOF will still work fine.   Having a stutter-free pinball experience is WAY more important!