4027 replies to this topic

[kiwi]

 

The video resolution settings change by itself when it is changed a second time, usually it moves to the resolution before the native one of the screen.

 

In the other PC choose a different resolution (the second time), if I open the video options a third time, the Windowed resolution is automatically selected.

[batch]

I tried to uncheck the square "Layers"

 

 

Crash report VPX rev4351
============
Process: vpinballx.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:00441B11
Attempt to write to 0x0000002F
Thread ID: 0x3D10 [15632]

Call stack
==========
00441B11 vpinballx.exe (0x0AEB9EB0 0x7732A040 0x00442880 0x00000000)
00442880 vpinballx.exe (0x0019E28C 0x03126968 0x03126904 0x0019e28c)
00442788 vpinballx.exe (0x00000345 0x0019E28C 0x0019E28C 0x03126904)
00427F69 vpinballx.exe (0x0000004E 0x00000345 0x0011041E 0x000d041c)
004407F0 vpinballx.exe (0x0000004E 0x00000345 0x0019E28C 0xffffffff80006011)
00426122 vpinballx.exe (0x000D041C 0x0000004E 0x00000345 0x0019e28c)
773347AB USER32.dll AddClipboardFormatListener + 0x4B (0xFFFFFFFF8B1474FF 0x7767700D 0x69E85700 0xffffffff8b00001b)
8510247C  (0x7767700D 0x69E85700 0xFFFFFFFF8B00001B 0x75f685f0)
8B1474FF  (0x69E85700 0xFFFFFFFF8B00001B 0x75F685F0 0x3302eb2f)
7767700D WINTRUST.dll MsCatFreeHashTag + 0x16D (0xFFFFFFFF8B00001B 0x75F685F0 0x3302EB2F 0x6770a1f6)
69E85700  (0x75F685F0 0x3302EB2F 0x6770A1F6 0xffffffffb0ff0077)
8B00001B  (0x3302EB2F 0x6770A1F6 0xFFFFFFFFB0FF0077 0x000000c4)
75F685F0 SHELL32.dll Ordinal660 + 0x57BF0 (0x6770A1F6 0xFFFFFFFFB0FF0077 0x000000C4 0x23ac15ff)
3302EB2F  (0xFFFFFFFFB0FF0077 0x000000C4 0x23AC15FF 0xffffffffc0850062)
6770A1F6  (0x000000C4 0x23AC15FF 0xFFFFFFFFC0850062 0x308b1674)
B0FF0077  (0x23AC15FF 0xFFFFFFFFC0850062 0x308B1674 0x1074f685)

Environment
===========
Date/time: 7/12/2020, 16:00:03:752
Number of CPUs: 8
Processor type: 586
System: Windows 10 (10.0 18363)

Memory status
=============
Total Reserved: 123864K (120M) bytes
Total Commited: 381516K (372M) bytes
Total Free: 3688860K (3602M) bytes
Largest Free: 2095468K (2046M) bytes

Registers
=========
EAX=00000000 EBX=0019DD7C ECX=030A0000 EDX=030A0000
ESI=0DB48ED0 EDI=03126968 EBP=6770A1F6 ESP=004260E8 EIP=B0FF0077
FLG=00210246 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Mini dump saved successfully.

[fuzzel]

I tried to uncheck the square "Layers"

 

 

Crash report VPX rev4351
============
Process: vpinballx.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:00441B11
Attempt to write to 0x0000002F
Thread ID: 0x3D10 [15632]

Call stack
==========
00441B11 vpinballx.exe (0x0AEB9EB0 0x7732A040 0x00442880 0x00000000)
00442880 vpinballx.exe (0x0019E28C 0x03126968 0x03126904 0x0019e28c)
00442788 vpinballx.exe (0x00000345 0x0019E28C 0x0019E28C 0x03126904)
00427F69 vpinballx.exe (0x0000004E 0x00000345 0x0011041E 0x000d041c)
004407F0 vpinballx.exe (0x0000004E 0x00000345 0x0019E28C 0xffffffff80006011)
00426122 vpinballx.exe (0x000D041C 0x0000004E 0x00000345 0x0019e28c)
773347AB USER32.dll AddClipboardFormatListener + 0x4B (0xFFFFFFFF8B1474FF 0x7767700D 0x69E85700 0xffffffff8b00001b)
8510247C  (0x7767700D 0x69E85700 0xFFFFFFFF8B00001B 0x75f685f0)
8B1474FF  (0x69E85700 0xFFFFFFFF8B00001B 0x75F685F0 0x3302eb2f)
7767700D WINTRUST.dll MsCatFreeHashTag + 0x16D (0xFFFFFFFF8B00001B 0x75F685F0 0x3302EB2F 0x6770a1f6)
69E85700  (0x75F685F0 0x3302EB2F 0x6770A1F6 0xffffffffb0ff0077)
8B00001B  (0x3302EB2F 0x6770A1F6 0xFFFFFFFFB0FF0077 0x000000c4)
75F685F0 SHELL32.dll Ordinal660 + 0x57BF0 (0x6770A1F6 0xFFFFFFFFB0FF0077 0x000000C4 0x23ac15ff)
3302EB2F  (0xFFFFFFFFB0FF0077 0x000000C4 0x23AC15FF 0xffffffffc0850062)
6770A1F6  (0x000000C4 0x23AC15FF 0xFFFFFFFFC0850062 0x308b1674)
B0FF0077  (0x23AC15FF 0xFFFFFFFFC0850062 0x308B1674 0x1074f685)

Environment
===========
Date/time: 7/12/2020, 16:00:03:752
Number of CPUs: 8
Processor type: 586
System: Windows 10 (10.0 18363)

Memory status
=============
Total Reserved: 123864K (120M) bytes
Total Commited: 381516K (372M) bytes
Total Free: 3688860K (3602M) bytes
Largest Free: 2095468K (2046M) bytes

Registers
=========
EAX=00000000 EBX=0019DD7C ECX=030A0000 EDX=030A0000
ESI=0DB48ED0 EDI=03126968 EBP=6770A1F6 ESP=004260E8 EIP=B0FF0077
FLG=00210246 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Mini dump saved successfully.

fixed

rev4356 is up:

 

- fix problem with loading of some screwed up tables

- fix gate animation issue when open function was used before

- fix potential null pointer issue (when using layers)

Edited by fuzzel, 07 December 2020 - 04:28 PM.

[fripounet]

little question

vpx11 project with vulkan definitively abandoned (because now vpe) ?

[Mitchell]

I just realize that the Pull Speed on the plunger change from (VPX 10.6.1) 0.05 to (VPX beta) 0.5. Same speed. Just different numbers. Was it a typo in the VPX source? Left a 0 out.

 

All this time I thought something is wrong. Now I know why the Plunger Speed is very slow. All I had to do is delete that 0 out. lol

 

Thanks for the fixes.

Edited by Mitchell, 08 December 2020 - 02:22 AM.

[Thalamus]

There is more to the plunger in 10.7. You can now cancel out in that the plunger goes back and forth. Believe it was Michael that came up with this nice addition. Instead of adjusting values, there should be a  option to un-/tick to get to the old behavior.

[Mitchell]

Auto-Plunger is way too strong. It like shooting pool. I don't use that. I always leave it unchecked.

 

All I did is just change the first box numbers.

Attached Files

•  Screenshot (194).png   6.92KB   4 downloads

Edited by Mitchell, 08 December 2020 - 09:47 AM.

[wiesshund]

Auto-Plunger is way too strong. It like shooting pool. I don't use that. I always leave it unchecked.

 

All I did is just change the first box numbers.

Auto plunger is what ever strength you make it
And you would only use it when making a table that had no hand operated one
Like ACDC for example.
It has no manual pullback plunger, just an auto plunger.

Though i am pretty sure you can script a normal plunger to work as an auto plunger anyways?

[toxie]

I just realize that the Pull Speed on the plunger change from (VPX 10.6.1) 0.05 to (VPX beta) 0.5. Same speed. Just different numbers. Was it a typo in the VPX source? Left a 0 out.

 

All this time I thought something is wrong. Now I know why the Plunger Speed is very slow. All I had to do is delete that 0 out. lol

 

Thanks for the fixes.

This is the new behavior that mfuegemann submitted (thanks!). You can get the old one in the settings, if needed.

[batch]

I copied some elements from the example table to the one I'm working on, and the "Layers" window of my table appears in the other one

 

 

And when I go back to my table, the "Layers" window is blank, and the other table name is checked

 

 

And then, the "Layers" window of the two tables are blank

 

Can it be because I renamed the layers of my table ?

[Pin-Pete]

Found something weird, while playing Bally's Speakeasy. The roulette ball won't stop at all.

[toxie]

>And when I go back to my table, ... ... , and the other table name is checked

 

 

At least this part will be fixed in the next build.

Edited by toxie, 08 December 2020 - 03:46 PM.

[wiesshund]

opened two tables, to copy something from one table script to the other

then closed the other table
Clicked on the layers panel and

Crash report VPX rev4356
============
Process: VPinballX.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:00442953
Attempt to read from 0x00000044
Thread ID: 0x1500 [5376]

Call stack
==========
00442953 VPinballX.exe (0x0019E274 0x032099E8 0x03209984 0x0019e274)
0044279C VPinballX.exe (0x00000345 0x0019E274 0x0019E274 0x03209984)
00427F69 VPinballX.exe (0x0000004E 0x00000345 0x000104F0 0x000104e8)
004407F0 VPinballX.exe (0x0000004E 0x00000345 0x0019E274 0x0000004e)
00426122 VPinballX.exe (0x000104E8 0x0000004E 0x00000345 0x0019e274)
754AEF6B user32.dll AddClipboardFormatListener + 0x4B (0xFFFFFFFF8B1474FF 0x7767700D 0x69E85700 0xffffffff8b00001b)
8510247C  (0x7767700D 0x69E85700 0xFFFFFFFF8B00001B 0x75f685f0)
8B1474FF  (0x69E85700 0xFFFFFFFF8B00001B 0x75F685F0 0x3302eb2f)
7767700D  (0xFFFFFFFF8B00001B 0x75F685F0 0x3302EB2F 0x6770a1f6)
69E85700 mscorlib.ni.dll (0x75F685F0 0x3302EB2F 0x6770A1F6 0xffffffffb0ff0077)
8B00001B  (0x3302EB2F 0x6770A1F6 0xFFFFFFFFB0FF0077 0x000000c4)
75F685F0  (0x6770A1F6 0xFFFFFFFFB0FF0077 0x000000C4 0x23ac15ff)
3302EB2F  (0xFFFFFFFFB0FF0077 0x000000C4 0x23AC15FF 0xffffffffc0850062)
6770A1F6 System.Core.ni.dll (0x000000C4 0x23AC15FF 0xFFFFFFFFC0850062 0x308b1674)
B0FF0077  (0x23AC15FF 0xFFFFFFFFC0850062 0x308B1674 0x1074f685)

Environment
===========
Date/time: 8/12/2020, 03:43:01:651
Number of CPUs: 4
Processor type: 586
System: Windows 10 (10.0 19042)

Memory status
=============
Total Reserved: 161948K (158M) bytes
Total Commited: 662712K (647M) bytes
Total Free: 3369580K (3290M) bytes
Largest Free: 2095424K (2046M) bytes

Registers
=========
EAX=00000000 EBX=754921C0 ECX=0A898E88 EDX=00000001
ESI=2B94BB98 EDI=032099E8 EBP=6770A1F6 ESP=004260E8 EIP=B0FF0077
FLG=00210206 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Failed to save minidump.

[fuzzel]

fixed with the next build

[arcadezz]

Posted 16 October 2020 - 10:47 AM

Hi, when I update to the later versions of VPX 7 beta, I get "pinball missing" on alot of tables, for instance Addams Family. Any idea why? If I roll back to VPX 6 final or the earlier version of VPX 7 beta, it works fine. Any help is appreciated, thanks.

 

I am still having issues with "pinball missing on most tables after trying the VPX 7 beta"....sorry to repost, but would like to use the latest beta and cannot figure out the issue, any advice on why this is happening? I read a post about key bindings in the preferences > "keys, Nudge and DOF" menu? The LMagnaSave and RmagnaSave keys should be bound to something else than the Left Flipper and Right Flipper keys..... I tried this with no luck

 

Thanks

[wiesshund]

 

Posted 16 October 2020 - 10:47 AM

Hi, when I update to the later versions of VPX 7 beta, I get "pinball missing" on alot of tables, for instance Addams Family. Any idea why? If I roll back to VPX 6 final or the earlier version of VPX 7 beta, it works fine. Any help is appreciated, thanks.

 

I am still having issues with "pinball missing on most tables after trying the VPX 7 beta"....sorry to repost, but would like to use the latest beta and cannot figure out the issue, any advice on why this is happening? I read a post about key bindings in the preferences > "keys, Nudge and DOF" menu? The LMagnaSave and RmagnaSave keys should be bound to something else than the Left Flipper and Right Flipper keys..... I tried this with no luck

 

Thanks

 

 

Did you try clearing the nvram?
That usually clears up the pinballs missing error for me
 

Dont think the magnasave key bindings would have any effect, other than during actual game play, if a table makes use of them at all
A lot of people have them bound to the same key as flippers for simplicity

[arcadezz]

 

 

Posted 16 October 2020 - 10:47 AM

Hi, when I update to the later versions of VPX 7 beta, I get "pinball missing" on alot of tables, for instance Addams Family. Any idea why? If I roll back to VPX 6 final or the earlier version of VPX 7 beta, it works fine. Any help is appreciated, thanks.

 

I am still having issues with "pinball missing on most tables after trying the VPX 7 beta"....sorry to repost, but would like to use the latest beta and cannot figure out the issue, any advice on why this is happening? I read a post about key bindings in the preferences > "keys, Nudge and DOF" menu? The LMagnaSave and RmagnaSave keys should be bound to something else than the Left Flipper and Right Flipper keys..... I tried this with no luck

 

Thanks

 

 

Did you try clearing the nvram?
That usually clears up the pinballs missing error for me
 

Dont think the magnasave key bindings would have any effect, other than during actual game play, if a table makes use of them at all
A lot of people have them bound to the same key as flippers for simplicity

 

 

I did try deleting the NVRAM and the issue persists.

Also, I noticed any VPX version before and including VPX_7_beta4142 works fine, as soon as I update to any version past VPX_7_beta 4142, the "missing pinball" error starts and I cant start the table.

I am running VPinMAME33_beta & SAMBuild_r5240 if that helps any. Thanks.

Edited by arcadezz, 09 December 2020 - 08:31 PM.

[wiesshund]

not sure if deleting the cfg file for the rom would help?

Just tested 
Table File: The Adams Family (Bally 1992).vpx      https://www.vpforums...&showfile=11651

ROM: TAF_L7.zip

VPX Version: Visual PinballX 10.7 revision 4356

VpinMame Version:  3.3 beta  11/2/2020 build by Toxie with Taito and Votrax optimizations

 

Machine tested on
DeLL Latitude E5430
Intel HD4000 gpu
i5 3230M cpu

8gb ram

 

So, slow PC, should not gloss over any issues

Unable to reproduce issue here

 

Would not seem that it is inherently the beta in and of itself
Question is, what is the external mitigating factor?

You do not have any vbs files in the table folder at all, do you?

 

 

[Thalamus]

Please, move installation question out of the beta thread. Uninstall and reinstall vp using the "one-in-all" installer to the same location as previous. Create your own thread if you have to. If 10.7beta has such oddities going on I would have reported it ages ago. There is many of us, jumping back and forth with different versions and we would have addressed this already. If you can come up with a conclusion of something that needs to be know for the beta, that is when you use this thread.

Edited by Thalamus, 10 December 2020 - 05:41 AM.

[toxie]

 

I did try deleting the NVRAM and the issue persists.

Also, I noticed any VPX version before and including VPX_7_beta4142 works fine, as soon as I update to any version past VPX_7_beta 4142, the "missing pinball" error starts and I cant start the table.

 

As it might still be a legit error though:

Could you please test via https://vpinball.com...s/vp-10-7-beta/ which revision is the first to fail? Is it already rev 4144?