30 replies to this topic

[nFozzy]

Does that happen with all tables? What is your framerate?

Edited by nFozzy, 03 December 2017 - 11:33 PM.

[elabree]

Hi Pinball Fan & Enthusiast,

 

My FPS is ~236 (322.4 avg)

Physics is < 0.5%

Scripts about 10%

 

Left flipper keypress to rotate: 994.1 ms  (211 f) to eos: 1010.8 ms (214 f).

 

Sometimes it is not responding at all or stuck at eos...

http://www.vpforums....&showfile=12124

http://www.vpforums....s&showfile=7464

 

I have just tried a different table (Terminator 2 jugement day). The flippers behave the same (not responding, huge delay, stuck at EOS). So it's not the table.

Edited by elabree, 04 December 2017 - 12:18 PM.

[nFozzy]

Could be a conflict between pinmame, b2s, and VP10. Search for 'stuck flipper'.

[elabree]

Hi NFozzy,

 

That's it:

In the preferences under Keys, Nudge and DOF mark "Disable B2S"

 

Maybe it is cause by both pinmame and the b2s server displaying the DMD.

 

Anyhow the flippers are working now for both tables.

 

Thanks,

Egon.

[RogerRoger]

In my Desktop setup, I've found that if Controller.txt has forcedisableB2S=1 and Disable B2S flag is checked, some tables actually perform worse, so I assume these two settings are mutually exclusive. I get more ball stuttering and ball physics glitching, mostly. Makes we wonder if the script contains calls for B2S but the flag is disabled, does it affect performance?

[DJRobX]

I don't think the controller.txt file is even read on modern VPX tables that use controller.vbs.  

 

And yes I've seen a few reports that when both the B2S internal DMD and VPM are trying to update the same region, slowdowns can happen.  You can go into the B2S settings and disable the internal DMD on problem B2Ses also.    Or hide the VPM DMD, if B2S has a nicer DMD (usually for games like F-14 Tomcat, Funhouse, etc...)

Edited by DJRobX, 06 December 2017 - 03:28 AM.

[jangus]

Hi Pinball Fan & Enthusiast,
 
My FPS is ~236 (322.4 avg)
Physics is < 0.5%
Scripts about 10%
 
Left flipper keypress to rotate: 994.1 ms  (211 f) to eos: 1010.8 ms (214 f).
 
Sometimes it is not responding at all or stuck at eos...
http://www.vpforums....&showfile=12124
http://www.vpforums....s&showfile=7464
 
I have just tried a different table (Terminator 2 jugement day). The flippers behave the same (not responding, huge delay, stuck at EOS). So it's not the table.

How do I Time the flipper respons Time?

[Thalamus]

Press F11 and read the output of the left flipper key-press.

[jangus]

Thanks Thalamus.

I did press F11 and got some information. But none of the flipper key-presses would give any information about the response time for the flippers. I attached an image of what the F11 showed on my screen.

 

This thread is a bit old. But maybe there still are some interests in the cause of the delay in the flippers.

I have a 46" playfield monitor and it has allways given me a delay. The TV is connected using HDMI. Some people have told me that it might be the HDMI that is responsible for the delay.
So I made tests with two smaller monitors using DVI and DisplayPort. Both of monitors did not give any delay issues that I noticed.

Today I ordered a new TV for the playfield, a 45” as there were no longer any 46” available. I talked with a seller in the phone before I ordered the TV. He told me that the delay where mainly because I used a 120Hz TV, that gives a bit smother image of movements at the cost of a small delay. The TV that I ordered is a 60Hz and with a DisplayPort. It will be interesting to see if it will fix the delay.

 

[Kernel]

I think you are using vp9, not VPX.
To reduce lag try disabling all image improvement options on tv and enable game mode if there is one.

[jangus]

Yes, I used VP9. I will retry with VPX. Thanks

Have no game mode on the TV.