1488 replies to this topic

[untomatin]

Hello, until yesterday everything worked correctly in the cabinet that I am assembling.

In the VP video options I had VSync = 1 and the FPS were exactly 60, without stuttering.

But today when testing some tables I noticed that the frames do not reach 60, they remain at 58/59. If I put VSync = 0 the frames rise to 105/140  depends on the table.

I understand that the idea is to match the FPS with the 60hz of the TV.

Can anybody help me?

Thank you!

Edited by untomatin, 17 June 2020 - 12:39 AM.

[Thalamus]

No, what you want is to keep the fps above or equal to your refresh rate. So, being above isn't a issue. However. with vsync off, you might experience tearing. So, using vsync is kind of need to try and experiment thing. If you are running Win10, maybe your graphics driver was updated by M$ ? It's a common problem. I would never ever trust M$ to run automatic updates on my cab.

[untomatin]

Thanks for the reply!
But finally it was stupid of me. As I am assembling my cabinet, somehow the HDMI cable was almost disconnected   , when I fixed this it worked properly again. I spend two days in forums and youtube with this topic 

By the way, VSync = 1 works very well for me, since my tv supports 60hz, everything flows very well.
I have win10, an old i7 and a GTX 1060 3gb.

Thanks again!

[Katicajaneva]

While playing Black Rose, and also on CFTBL when i got extra ball...BUT i played the CFTBL table after and didn't had any problem again



Crash report VPX rev3788
============
Process: VpinballX.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:004D536C
Attempt to read from 0x08BFC764
Thread ID: 0x11AC [4524]

Call stack
==========
004D536C VpinballX.exe (0x316439E4 0x000305FC 0x000305FE 0x02ec8b70)
004D1B20 VpinballX.exe (0x00000004 0x02EC8B70 0x000305FC 0x000305fe)

Environment
===========
Date/time: 15/7/2020, 04:54:08:627
Number of CPUs: 12
Processor type: 586
System: Windows 10 (10.0 18363)

Memory status
=============
Total Reserved: 195384K (190M) bytes
Total Commited: 250972K (245M) bytes
Total Free: 3747884K (3660M) bytes
Largest Free: 2095428K (2046M) bytes

Registers
=========
EAX=00000000 EBX=80004000 ECX=00000004 EDX=00030000
ESI=000305FE EDI=08BFC740 EBP=00000000 ESP=0019F530 EIP=004B6CA1
FLG=00010246 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Mini dump saved successfully.

Edited by Katicajaneva, 21 July 2020 - 07:55 PM.

[Thalamus]

3788 is the latest 10.6beta build. I'm not sure what was changed, but, you would do better to download 10.6.1. I've played those tables you mention a lot, extra balls too and no crashes.

[batch]

When I open the VPX version of Class of 1812, I get this error message (VP9 version works fine)

 

 

And in the "VPinball / script" folder there's a special VBS file for this table (that's why I post this message in this topic)

 

 

In table script, there's the following line:

 

LoadVPM "02800000", "Class1812.VBS", 3.50

Edited by batch, 14 August 2020 - 08:01 AM.

[batch]

Forget about it, I didn't have the last scripts version

[batch]

I still use VP10.6 official, waiting for a stable VP10.7 version, but I've installed the last  "VPX_7_beta_rev4291" and the last "VPinMAME33_beta_08_2020" (so I use the last versions of vbs scripts)

 

I know VP10.6 won't be developped anymore, but perhaps it can be the same behaviour with VP10.7

 

I'm updating all my tables and have to open and close them very often, and had several VPX crashes

 

Here is the last crash report

 

Crash report VPX rev3788
============
Process: VPX6LAST.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:2C5493E1
Attempt to write to 0x2EB50000
Thread ID: 0x2F28 [12072]

Call stack
==========
2C5493E1 vpinmame.dll (0x2C9F0614 0x2C463956 0xFFFFFFFFFFFFFFFF 0x2c44f595)
2C46E054 vpinmame.dll (0xFFFFFFFFFFFFFFFF 0x2C44F595 0x2CA001F0 0x2c9ffa10)
2C463956 vpinmame.dll (0x2CA001F0 0x2C9FFA10 0x2C9FFA28 0x00000000)
2C44F595 vpinmame.dll (0x00000000 0x00000010 0x2C9F0618 0x00000080)
2C46F0F6 vpinmame.dll (0x00000020 0x1FF552F8 0x4DCBFDF8 0x2c983be8)
2C44F043 vpinmame.dll (0x1FF552F8 0x2C462AA0 0x00000001 0x2c9f6db0)
2C44E7F2 vpinmame.dll (0x00000843 0x2C983BE8 0x4DCBFF70 0x00000001)
2C462982 vpinmame.dll (0x0CCBB010 0x00000000 0x768E8A60 0x00000006)
2C4626BA vpinmame.dll (0x4DCBFEE8 0x7760AE8E 0x00000006 0x7760ae8e)
7760AE8E ntdll.dll RtlAllocateHeap + 0x3E (0x00000006 0x7760AE8E 0x08DFCB10 0x77038590)
7760AE8E ntdll.dll RtlAllocateHeap + 0x3E (0x00000004 0x2C97FC88 0x2C97FBE8 0x2c8d49d8)
2C5D216C vpinmame.dll (0x00000000 0x0CBBDA70 0x0CBBDA70 0x2c8d49d8)
2C5D216C vpinmame.dll (0x2C82ADF4 0x0CBBDA70 0x4DCBFF70 0x00000000)
2C5D216C vpinmame.dll (0x00000000 0x0CCBB010 0x768E8A60 0x2c5c0d9b)

Environment
===========
Date/time: 8/9/2020, 11:04:20:40
Number of CPUs: 8
Processor type: 586
System: Windows 10 (10.0 18363)

Memory status
=============
Total Reserved: 317288K (309M) bytes
Total Commited: 1646728K (1608M) bytes
Total Free: 2230224K (2177M) bytes
Largest Free: 1866176K (1822M) bytes

Registers
=========
EAX=00000000 EBX=00000000 ECX=FF1ADA86 EDX=2EB50002
ESI=2D654DA0 EDI=00000579 EBP=00000000 ESP=4DCBFF38 EIP=2C5C8BD3
FLG=00010202 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Mini dump saved successfully.

Edited by batch, 08 September 2020 - 02:18 PM.

[Snaptick]

 

Hey guys, just for reference, when I updated to VPX beta 6 (R3541)… the table Vector (Bally 1982) v1.2 no longer works and gives an error trying to run fast flips (Line 226: Object Doesn't support this Property or method: VPMFlips.CallbackL) ...

 

The older version of core.vbs from the 15th of July (VPX 5 version) works fine though....

I guess this is an older method to use the fastflips. I simply removed those two lines, 226 and 227, and changed the Solenoids = 0 with Solenoids = 2, and fastflips seems to work fine (checked with F11)

 

This totally worked - I was scratching my head for a while on this one. Thank you!