1488 replies to this topic

[markrock76]

Toxie

 

The lighting on Tron G5k version reacts differently in newest beta.  Beta 3592 is first image, newest beta is second image.  I'm not here to say which is better but when the ball hits the targets it looks like an explosion as in the last pic.  It is much more intense than in the picture.

 

 

 

[sliderpoint]

Getting lots of reports (and I randomly get it too) of crash with new TAF release.  On play  Getting compile error: unknown error.  Sometimes a few of them.  Sometimes will end with Error:
Fatal Error: shader compilation failed! Unknown (0xffffffff: n/a) at c:\projects\vp10\renderdevice.cpp:802

(typed that from the window, may not have the right number of 'ff's')

 

Then this is the crash text:

Crash report VPX rev3653
============
Process: VPinballX.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:004D2885
Attempt to read from 0x00000000
Thread ID: 0x2FE4 [12260]

Call stack
==========
004D2885 VPinballX.exe (0x02DE4990 0x15E62120 0x00000000 0x00000000)
004D3B77 VPinballX.exe (0x00072468 0x00C808F4 0x001C069E 0x00008012)
004B5811 VPinballX.exe (0x00000000 0x00000111 0x00008012 0x005f0742)
0052A542 VPinballX.exe (0x00008012 0x0052D0B0 0x005F0742 0x00000111)
0052D1B0 VPinballX.exe (0x005F0742 0x00000111 0x00008012 0x00a80718)
7549BF1B user32.dll AddClipboardFormatListener + 0x49B (0x0052D0B0 0x005F0742 0x00000111 0x00008012)
754983EA user32.dll DispatchMessageW + 0x97A (0x0052D0B0 0x00000000 0x00000111 0x00008012)
7547BECA user32.dll SendMessageW + 0x3AA (0x035A8E00 0x00000000 0x00A80718 0x00000000)
7547BC57 user32.dll SendMessageW + 0x137 (0x005F0742 0x00000111 0x00008012 0x00a80718)
6EBB4FB1 COMCTL32.dll CreateToolbar + 0x4C81 (0x00000202 0x00000000 0x0072003F 0x00000202)
6EBB5F10 COMCTL32.dll CreateToolbar + 0x5BE0 (0x00A80718 0x00000202 0x00000000 0x0072003f)
7549BF1B user32.dll AddClipboardFormatListener + 0x49B (0x6EBB53D0 0x00A80718 0x00000202 0x00000000)
754983EA user32.dll DispatchMessageW + 0x97A (0x6EBB53D0 0x00000000 0x00000202 0x00000000)
75497C9E user32.dll DispatchMessageW + 0x22E (0x0019FA18 0x0051F143 0x0019F9B4 0x00000000)
7548CDD0 user32.dll DispatchMessageA + 0x10 (0x0019F9B4 0x00000000 0x0069C978 0x00000000)
0051F143 VPinballX.exe (0x00000000 0x0069C978 0x00288000 0x00683420)
0051F2A6 VPinballX.exe (0x00400000 0x00000000 0x02D42B0E 0x00000001)
00530FC7 VPinballX.exe (0x00288000 0x73828460 0x4B92295B 0x0019ffdc)
73828484 KERNEL32.DLL BaseThreadInitThunk + 0x24 (0x00288000 0x4ADD4BE0 0x00000000 0x00000000)
76F841C8 ntdll.dll RtlAreBitsSet + 0x88 (0xFFFFFFFFFFFFFFFF 0x76F9F348 0x00000000 0x00000000)
76F84198 ntdll.dll RtlAreBitsSet + 0x58 (0x02B70530 0x00288000 0x00000000 0x78746341)

Environment
===========
Date/time: 4/3/2019, 15:14:35:447
Number of CPUs: 8
Processor type: 586
System: Windows 10 (10.0 17134)

Memory status
=============
Total Reserved: 200424K (195M) bytes
Total Commited: 2295604K (2241M) bytes
Total Free: 1698212K (1658M) bytes
Largest Free: 1657920K (1619M) bytes

Registers
=========
EAX=00000000 EBX=1630C0C0 ECX=00000006 EDX=0019EAE8
ESI=998CC390 EDI=15E62650 EBP=0019FFEC ESP=0019FFE4 EIP=76F84198
FLG=00010202 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Mini dump saved successfully.

[3rdaxis]

No sorry. If the clipping boundaries for the camera would change all camera settings for all tables would also change.

lol, I always pick the good ones, lol.

[bord]

At restart the current beta assigns the playfield to my second monitor (designated as monitor 2 in Windows 10), which is 2k and makes my 4k screen secondary. Really annoying.

[BrandonLaw]

Getting lots of reports (and I randomly get it too) of crash with new TAF release.  On play  Getting compile error: unknown error.  Sometimes a few of them.  Sometimes will end with Error:
Fatal Error: shader compilation failed! Unknown (0xffffffff: n/a) at c:\projects\vp10\renderdevice.cpp:802
(typed that from the window, may not have the right number of 'ff's')
 
Then this is the crash text:

Crash report VPX rev3653
============
Process: VPinballX.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:004D2885
Attempt to read from 0x00000000
Thread ID: 0x2FE4 [12260]

Call stack
==========
004D2885 VPinballX.exe (0x02DE4990 0x15E62120 0x00000000 0x00000000)
004D3B77 VPinballX.exe (0x00072468 0x00C808F4 0x001C069E 0x00008012)
004B5811 VPinballX.exe (0x00000000 0x00000111 0x00008012 0x005f0742)
0052A542 VPinballX.exe (0x00008012 0x0052D0B0 0x005F0742 0x00000111)
0052D1B0 VPinballX.exe (0x005F0742 0x00000111 0x00008012 0x00a80718)
7549BF1B user32.dll AddClipboardFormatListener + 0x49B (0x0052D0B0 0x005F0742 0x00000111 0x00008012)
754983EA user32.dll DispatchMessageW + 0x97A (0x0052D0B0 0x00000000 0x00000111 0x00008012)
7547BECA user32.dll SendMessageW + 0x3AA (0x035A8E00 0x00000000 0x00A80718 0x00000000)
7547BC57 user32.dll SendMessageW + 0x137 (0x005F0742 0x00000111 0x00008012 0x00a80718)
6EBB4FB1 COMCTL32.dll CreateToolbar + 0x4C81 (0x00000202 0x00000000 0x0072003F 0x00000202)
6EBB5F10 COMCTL32.dll CreateToolbar + 0x5BE0 (0x00A80718 0x00000202 0x00000000 0x0072003f)
7549BF1B user32.dll AddClipboardFormatListener + 0x49B (0x6EBB53D0 0x00A80718 0x00000202 0x00000000)
754983EA user32.dll DispatchMessageW + 0x97A (0x6EBB53D0 0x00000000 0x00000202 0x00000000)
75497C9E user32.dll DispatchMessageW + 0x22E (0x0019FA18 0x0051F143 0x0019F9B4 0x00000000)
7548CDD0 user32.dll DispatchMessageA + 0x10 (0x0019F9B4 0x00000000 0x0069C978 0x00000000)
0051F143 VPinballX.exe (0x00000000 0x0069C978 0x00288000 0x00683420)
0051F2A6 VPinballX.exe (0x00400000 0x00000000 0x02D42B0E 0x00000001)
00530FC7 VPinballX.exe (0x00288000 0x73828460 0x4B92295B 0x0019ffdc)
73828484 KERNEL32.DLL BaseThreadInitThunk + 0x24 (0x00288000 0x4ADD4BE0 0x00000000 0x00000000)
76F841C8 ntdll.dll RtlAreBitsSet + 0x88 (0xFFFFFFFFFFFFFFFF 0x76F9F348 0x00000000 0x00000000)
76F84198 ntdll.dll RtlAreBitsSet + 0x58 (0x02B70530 0x00288000 0x00000000 0x78746341)

Environment
===========
Date/time: 4/3/2019, 15:14:35:447
Number of CPUs: 8
Processor type: 586
System: Windows 10 (10.0 17134)

Memory status
=============
Total Reserved: 200424K (195M) bytes
Total Commited: 2295604K (2241M) bytes
Total Free: 1698212K (1658M) bytes
Largest Free: 1657920K (1619M) bytes

Registers
=========
EAX=00000000 EBX=1630C0C0 ECX=00000006 EDX=0019EAE8
ESI=998CC390 EDI=15E62650 EBP=0019FFEC ESP=0019FFE4 EIP=76F84198
FLG=00010202 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Mini dump saved successfully.

Have to say....4 hours if not more into the new TAF on current beta even going back to freezy’s 1.7.1 for the color ROM and not one crash. Don’t jinx it!!

[sliderpoint]

Have to say....4 hours if not more into the new TAF on current beta even going back to freezy’s 1.7.1 for the color ROM and not one crash. Don’t jinx it!!

 

 

LOL, I understand where you are coming from, but the rest of us want that stability too!  heh.

[toxie]

I don't think we should mix VPX with the special VR version at the moment. We are planning to integrate that but not for 10.x.
So again sorry I don't want to add another flag/ option just to satisfy another tool that isn't maintained directly by us at the moment.

 

Still, Caligula could add something to the VR branch that does something like that. Just reach out to him in the corresponding thread.

[Halen]

Crash with new TAF release. 

 

Crash report VPX rev3653

============

Process: VPinballX.exe

Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:004D2885

Attempt to read from 0x00000000

Thread ID: 0x22F8 [8952]

 

Call stack

==========

004D2885 VPinballX.exe (0x02D671E0 0x16CD6EC0 0x00000000 0x00000001)

004D3B77 VPinballX.exe (0x0007244E 0x005E0548 0x008108F4 0x0019fb05)

004B5811 VPinballX.exe (0x00000000 0x00000000 0x0069C978 0x00000000)

0051F0F0 VPinballX.exe (0x00000000 0x0069C978 0x00267000 0x00683420)

0051F2A6 VPinballX.exe (0x00400000 0x00000000 0x02CE25FA 0x00000001)

00530FC7 VPinballX.exe (0x00267000 0x76D70160 0x0019FFDC 0x7708662d)

76D70179 KERNEL32.DLL BaseThreadInitThunk + 0x19 (0x00267000 0x142A25C5 0x00000000 0x00000000)

7708662D ntdll.dll RtlGetAppContainerNamedObjectPath + 0xED (0xFFFFFFFFFFFFFFFF 0x770A51B9 0x00000000 0x00000000)

770865FD ntdll.dll RtlGetAppContainerNamedObjectPath + 0xBD (0x02B70530 0x00267000 0x00000000 0x78746341)

 

Environment

===========

Date/time: 5/3/2019, 17:36:02:978

Number of CPUs: 4

Processor type: 586

System: Windows 10 (10.0 17763)

 

Memory status

=============

Total Reserved: 240044K (234M) bytes

Total Commited: 2312780K (2258M) bytes

Total Free: 1641416K (1602M) bytes

Largest Free: 1604660K (1567M) bytes

 

Registers

=========

EAX=00000000 EBX=1728A460 ECX=00000006 EDX=0019F100

ESI=9BACF7F0 EDI=16CD86E0 EBP=0019FFEC ESP=0019FFE4 EIP=770865FD

FLG=00010206 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B

 

 

Mini dump saved successfully.

[luvthatapex]

Is the latest 10.6 beta the most stable? I am running 10.6 from 11-2018 and TAF was the first table that said I needed an updated 10.6

[toxie]

It's reasonably stable..

[fuzzel]

 

Getting lots of reports (and I randomly get it too) of crash with new TAF release.  On play  Getting compile error: unknown error.  Sometimes a few of them.  Sometimes will end with Error:
Fatal Error: shader compilation failed! Unknown (0xffffffff: n/a) at c:\projects\vp10\renderdevice.cpp:802

(typed that from the window, may not have the right number of 'ff's')

 

Then this is the crash text:

Crash report VPX rev3653
============
Process: VPinballX.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:004D2885
Attempt to read from 0x00000000
Thread ID: 0x2FE4 [12260]

Call stack
==========
004D2885 VPinballX.exe (0x02DE4990 0x15E62120 0x00000000 0x00000000)
004D3B77 VPinballX.exe (0x00072468 0x00C808F4 0x001C069E 0x00008012)
004B5811 VPinballX.exe (0x00000000 0x00000111 0x00008012 0x005f0742)
0052A542 VPinballX.exe (0x00008012 0x0052D0B0 0x005F0742 0x00000111)
0052D1B0 VPinballX.exe (0x005F0742 0x00000111 0x00008012 0x00a80718)
7549BF1B user32.dll AddClipboardFormatListener + 0x49B (0x0052D0B0 0x005F0742 0x00000111 0x00008012)
754983EA user32.dll DispatchMessageW + 0x97A (0x0052D0B0 0x00000000 0x00000111 0x00008012)
7547BECA user32.dll SendMessageW + 0x3AA (0x035A8E00 0x00000000 0x00A80718 0x00000000)
7547BC57 user32.dll SendMessageW + 0x137 (0x005F0742 0x00000111 0x00008012 0x00a80718)
6EBB4FB1 COMCTL32.dll CreateToolbar + 0x4C81 (0x00000202 0x00000000 0x0072003F 0x00000202)
6EBB5F10 COMCTL32.dll CreateToolbar + 0x5BE0 (0x00A80718 0x00000202 0x00000000 0x0072003f)
7549BF1B user32.dll AddClipboardFormatListener + 0x49B (0x6EBB53D0 0x00A80718 0x00000202 0x00000000)
754983EA user32.dll DispatchMessageW + 0x97A (0x6EBB53D0 0x00000000 0x00000202 0x00000000)
75497C9E user32.dll DispatchMessageW + 0x22E (0x0019FA18 0x0051F143 0x0019F9B4 0x00000000)
7548CDD0 user32.dll DispatchMessageA + 0x10 (0x0019F9B4 0x00000000 0x0069C978 0x00000000)
0051F143 VPinballX.exe (0x00000000 0x0069C978 0x00288000 0x00683420)
0051F2A6 VPinballX.exe (0x00400000 0x00000000 0x02D42B0E 0x00000001)
00530FC7 VPinballX.exe (0x00288000 0x73828460 0x4B92295B 0x0019ffdc)
73828484 KERNEL32.DLL BaseThreadInitThunk + 0x24 (0x00288000 0x4ADD4BE0 0x00000000 0x00000000)
76F841C8 ntdll.dll RtlAreBitsSet + 0x88 (0xFFFFFFFFFFFFFFFF 0x76F9F348 0x00000000 0x00000000)
76F84198 ntdll.dll RtlAreBitsSet + 0x58 (0x02B70530 0x00288000 0x00000000 0x78746341)

Environment
===========
Date/time: 4/3/2019, 15:14:35:447
Number of CPUs: 8
Processor type: 586
System: Windows 10 (10.0 17134)

Memory status
=============
Total Reserved: 200424K (195M) bytes
Total Commited: 2295604K (2241M) bytes
Total Free: 1698212K (1658M) bytes
Largest Free: 1657920K (1619M) bytes

Registers
=========
EAX=00000000 EBX=1630C0C0 ECX=00000006 EDX=0019EAE8
ESI=998CC390 EDI=15E62650 EBP=0019FFEC ESP=0019FFE4 EIP=76F84198
FLG=00010202 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Mini dump saved successfully.

That's strange. It looks like your graphic card driver or the DX9 support of that driver doesn't like the shader code. The crash is just the result that no ball shader is available later in the init phase.

[sliderpoint]

I get them on both cab and laptop.  Both have nvidia video cards.  It's not only on TAF.  I get it on other tables as well (pin-bot).  The oddest thing, like others is that it's just not every single time.  Some times it works fine.

 

-Mike

[Outhere]

Hey awesome VP devs: I'm also have an issue with a defaulting to 640 x 480 resolution using exclusive fullscreen.  My specific issue is if I change ANYTHING in the video options, the resolution section jumps to the resolution listed at the very top which is 640 x 480.  even if I choose my preferred resolution (3840x2160) , it doesn't seem to save it. A work around is I need to select "set to high end pc" which automatically sets the proper resolution (4K and all options are turned on) then deselect everything I don't want.  Once I click ok it saves it but if I go back and select ANY option, the resolution jumps back in the menu to 640x480.  Note that I am running VP in 4K.   version 3650 also does this.  I hadn't tried any other version since the change to "Video/graphics option" so can't confirm if it goes back to that version (the one that lists "display 1" beside the resolution.  What version is this?  I can try it out and let you know if the very first version with these changes does this

 

toxie: you running a 4K VP?

I decided to try exclusive full screen today (running Version 3653) And having the same problem as above

-

Version 3592 does not do this

[The Loafer]

it was reported on another forum that the monitor id in windows doesn't seem to match VP's.  This is NOT my resolution issue since my monitor ID seems to match ok but just letting you know others are getting this issue

 

https://vpinball.com...s/reply/116936/

[Schlabber34]

 

 

Getting lots of reports (and I randomly get it too) of crash with new TAF release.  On play  Getting compile error: unknown error.  Sometimes a few of them.  Sometimes will end with Error:
Fatal Error: shader compilation failed! Unknown (0xffffffff: n/a) at c:\projects\vp10\renderdevice.cpp:802

(typed that from the window, may not have the right number of 'ff's')

 

Then this is the crash text:

Crash report VPX rev3653
============
Process: VPinballX.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:004D2885
Attempt to read from 0x00000000
Thread ID: 0x2FE4 [12260]

Call stack
==========
004D2885 VPinballX.exe (0x02DE4990 0x15E62120 0x00000000 0x00000000)
004D3B77 VPinballX.exe (0x00072468 0x00C808F4 0x001C069E 0x00008012)
004B5811 VPinballX.exe (0x00000000 0x00000111 0x00008012 0x005f0742)
0052A542 VPinballX.exe (0x00008012 0x0052D0B0 0x005F0742 0x00000111)
0052D1B0 VPinballX.exe (0x005F0742 0x00000111 0x00008012 0x00a80718)
7549BF1B user32.dll AddClipboardFormatListener + 0x49B (0x0052D0B0 0x005F0742 0x00000111 0x00008012)
754983EA user32.dll DispatchMessageW + 0x97A (0x0052D0B0 0x00000000 0x00000111 0x00008012)
7547BECA user32.dll SendMessageW + 0x3AA (0x035A8E00 0x00000000 0x00A80718 0x00000000)
7547BC57 user32.dll SendMessageW + 0x137 (0x005F0742 0x00000111 0x00008012 0x00a80718)
6EBB4FB1 COMCTL32.dll CreateToolbar + 0x4C81 (0x00000202 0x00000000 0x0072003F 0x00000202)
6EBB5F10 COMCTL32.dll CreateToolbar + 0x5BE0 (0x00A80718 0x00000202 0x00000000 0x0072003f)
7549BF1B user32.dll AddClipboardFormatListener + 0x49B (0x6EBB53D0 0x00A80718 0x00000202 0x00000000)
754983EA user32.dll DispatchMessageW + 0x97A (0x6EBB53D0 0x00000000 0x00000202 0x00000000)
75497C9E user32.dll DispatchMessageW + 0x22E (0x0019FA18 0x0051F143 0x0019F9B4 0x00000000)
7548CDD0 user32.dll DispatchMessageA + 0x10 (0x0019F9B4 0x00000000 0x0069C978 0x00000000)
0051F143 VPinballX.exe (0x00000000 0x0069C978 0x00288000 0x00683420)
0051F2A6 VPinballX.exe (0x00400000 0x00000000 0x02D42B0E 0x00000001)
00530FC7 VPinballX.exe (0x00288000 0x73828460 0x4B92295B 0x0019ffdc)
73828484 KERNEL32.DLL BaseThreadInitThunk + 0x24 (0x00288000 0x4ADD4BE0 0x00000000 0x00000000)
76F841C8 ntdll.dll RtlAreBitsSet + 0x88 (0xFFFFFFFFFFFFFFFF 0x76F9F348 0x00000000 0x00000000)
76F84198 ntdll.dll RtlAreBitsSet + 0x58 (0x02B70530 0x00288000 0x00000000 0x78746341)

Environment
===========
Date/time: 4/3/2019, 15:14:35:447
Number of CPUs: 8
Processor type: 586
System: Windows 10 (10.0 17134)

Memory status
=============
Total Reserved: 200424K (195M) bytes
Total Commited: 2295604K (2241M) bytes
Total Free: 1698212K (1658M) bytes
Largest Free: 1657920K (1619M) bytes

Registers
=========
EAX=00000000 EBX=1630C0C0 ECX=00000006 EDX=0019EAE8
ESI=998CC390 EDI=15E62650 EBP=0019FFEC ESP=0019FFE4 EIP=76F84198
FLG=00010202 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Mini dump saved successfully.

That's strange. It looks like your graphic card driver or the DX9 support of that driver doesn't like the shader code. The crash is just the result that no ball shader is available later in the init phase.

 

 

I thought the same when i read through that pile of numbers, letters and symbols!

 

 

[toxie]

I get them on both cab and laptop.  Both have nvidia video cards.  It's not only on TAF.  I get it on other tables as well (pin-bot).  The oddest thing, like others is that it's just not every single time.  Some times it works fine.

 

-Mike

 

Are these running the same NVIDIA driver? Could you try updating it?

[GInsonic]

Which Nvidia driver version do you have installed? I once had one version, which had extreme troubles with VPX and produced weird crashes, but it was two or three versions below the actual one!

[Schlabber34]

I have an odd problem with the new PF prim feature. VPX6 rev3618 (still on this one because of the stabilty issues) gives me black lines around cutouts on the prim PF. I have some images to show the problem. Any idea? The blender file and the texture image was OK as seen on the pictures:

Editor:

https://1drv.ms/u/s!...bz-S3SNH3LDyH-A

VPX ingame:

https://1drv.ms/u/s!...aSCYZ52_7lovoFw

Blender, no lines:

https://1drv.ms/u/s!...cHnk1ujbcXjyvag

PF texture image:

https://1drv.ms/u/s!...d1FKZHziGj2I_QA

[fuzzel]

Could be a precision thing with the texture coordinates when cutting out holes from the playfield mesh.Blender is very precise here where dx9 isn't.

[Schlabber34]

I guess we have to live with the black lines then!?

 

Where does the black colour come from? Is it the DT or FS background image that is showing on the edges?

 

Thanks for answering!