[RESOLVED] PBX v6.20 - Cant exit VP10 and return to the PBX browser. PBX freezes and must be force closed.

[wrd1972]

I have a super annoying problem where when trying to exit VP10 back to the PBX browser, things seem to freeze.

 

This all seemed to start when I upgraded to 6.11, and I am now also seeing it on 6.20. Not sure what rev I had prior to 6.11, but this never ever happened. The issue seems to be random, but it can also happen quite frequently on certain tables. When this happens, I have to force close PBX. To make it even more annoying, the mouse pointer disappears after a forced close. Grrrr.

 

When Playing VP10 through the editor, all tables exit properly. No problem there. I do run a 3-screen setup if it matters, and when in the browser, I show a topper image and a backglass image on my two stacked monitors in the backbox. Not sure if its related, but when I do have a successful return to the PBX browsing menu, its taking nearly twice as long as it used to.

 

I saw in a similar thread that it might be exclusive full screen. I tried turning it off, problem remains. Also, I dont recall switching anything up on my cab that might have started this.

 

Right now PBX is nearly unusable, and I really dont want to switch to a new front end. Any ideas?

 

Thanks.

 

log.txt PinballX.ini

[Mike_da_Spike]

Your log file is a file without launching a table or without the issue.

Checking your log file, the Fscreen exclusive hack isn't enabled as well.
can you enable this, reproduce the issue and post the log file back ? that would Help Tom a lot

 

[scutters]

5 hours ago, wrd1972 said:

To make it even more annoying, the mouse pointer disappears after a forced close. Grrrr.

While troubleshooting this issue set the mouse not to be hidden. It'll help save some of the pain;

 

Also, are you using joytokey or similar (as it looks like not all buttons are mapped in pinballx) if so what are the mappings there, and what are VPX key and button mappings? (screenshot of vpx preferences screen will help)

[wrd1972]

Will do on both points. Thanks and I will replay back, but it wont be till early-mid next week.

[Mike_da_Spike]

I've added a workaround to my cabinet for instances when PinballX crashes and I lose the taskbar and mouse pointer.
I created a "Relaunch Pinball" shortcut that executes a batch file, terminating any plugin and restarting PinballX.

taskkill /FI "IMAGENAME eq PinballX.exe" /f
taskkill /FI "IMAGENAME eq AnyCPUPluginWrapperx64.exe" /f
taskkill /FI "IMAGENAME eq AnyCPUPluginWrapperx86.exe" /f
C:\pinball\PinballX\PinballX.exe"

When Pinball crashes, I can press the Windows key on the keyboard and search for 'relaunch_PinballX'. This command will terminate all processes, restart PinballX, and if I close it immediately, it will restore the mouse and taskbar.

[Mike_da_Spike]

I also did some tests, and it appears the issue arises after upgrading to VPX 10.8 RC5.
The problem consistently occurs when launching the second table.
Reverting to version 6.10 or lower does not resolve the issue for me.
The log file does not reveal any clues.
The issue persists even after disabling all my plugins and my real DMD. Please refer to the attached video for more details.
@Tom Speirs somethign you want to take a look when VPX 10.8 is released or already want to look at it ?
In the video at 1:15, I pressed the exit button, but PinballX did not respond.

log.txt PinballX.ini

[Draco1962]

6 hours ago, Mike_da_Spike said:

I also did some tests, and it appears the issue arises after upgrading to VPX 10.8 RC5.
The problem consistently occurs when launching the second table.
Reverting to version 6.10 or lower does not resolve the issue for me.
The log file does not reveal any clues.
The issue persists even after disabling all my plugins and my real DMD. Please refer to the attached video for more details.
@Tom Speirs somethign you want to take a look when VPX 10.8 is released or already want to look at it ?
In the video at 1:15, I pressed the exit button, but PinballX did not respond.

 

log.txt 4.53 kB · 1 download PinballX.ini 15.47 kB · 0 downloads

Are there any indications in Windows Event Viewer? Be sure to retest once it moves beyond release candidate.

[Mike_da_Spike]

On 11/29/2024 at 2:01 PM, Draco1962 said:

Are there any indications in Windows Event Viewer? 

No, as it is an application hung, it will only shows the WER in the event log on the moment it detects that the application is hanging
WER error :

Log Name:      Application
Source:        Windows Error Reporting
Date:          30-11-2024 14:57:31
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      
User:          PINBALL\Mike DA Spike
Computer:      Pinball
Description:
Fault bucket 1226237216090557334, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: PinballX.exe
P2: 1.0.0.0
P3: 66df0000
P4: 1078
P5: 134217732
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.3f2992d7-412e-4b9a-ba71-af2b486540b6.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ad136d4a-f146-4066-807b-eaecbd3d37be.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.27ad1b0a-502a-42f3-9f8d-e97aab8de0b8.tmp.txt
\\?\C:\Users\micha\AppData\Local\Temp\WER.f2aafdd6-9bfe-48ce-a5b1-161bbcc743f8.tmp.appcompat.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.2c057cb5-5a87-4123-ac22-193326987e33.tmp.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppHang_PinballX.exe_a391e1cfb3666a33d37f28fcb867cd7ae1d2bf8b_043bd839_ba784386-165b-4cc1-88b1-3b9b6e9b93a9

Analysis symbol: 
Rechecking for solution: 0
Report Id: 669dda09-a1c0-49ca-9890-b844433cbf3d
Report Status: 268435456
Hashed bucket: 2cc36e32695a04a6610478404b710b96
Cab Guid: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows Error Reporting" Guid="{0ead09bd-2157-539a-8d6d-c87f95b64d70}" />
    <EventID>1001</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2024-11-30T13:57:31.9703709Z" />
    <EventRecordID>5518</EventRecordID>
    <Correlation />
    <Execution ProcessID="7528" ThreadID="8856" />
    <Channel>Application</Channel>
    <Computer>Pinball</Computer>
    <Security UserID="S-1-5-21-3876027899-2469441806-1619404739-1001" />
  </System>
  <EventData>
    <Data Name="Bucket">1226237216090557334</Data>
    <Data Name="BucketType">5</Data>
    <Data Name="EventName">AppHangB1</Data>
    <Data Name="Response">Not available</Data>
    <Data Name="CabId">0</Data>
    <Data Name="P1">PinballX.exe</Data>
    <Data Name="P2">1.0.0.0</Data>
    <Data Name="P3">66df0000</Data>
    <Data Name="P4">1078</Data>
    <Data Name="P5">134217732</Data>
    <Data Name="P6">
    </Data>
    <Data Name="P7">
    </Data>
    <Data Name="P8">
    </Data>
    <Data Name="P9">
    </Data>
    <Data Name="P10">
    </Data>
    <Data Name="AttachedFiles">
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.3f2992d7-412e-4b9a-ba71-af2b486540b6.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ad136d4a-f146-4066-807b-eaecbd3d37be.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.27ad1b0a-502a-42f3-9f8d-e97aab8de0b8.tmp.txt
\\?\C:\Users\micha\AppData\Local\Temp\WER.f2aafdd6-9bfe-48ce-a5b1-161bbcc743f8.tmp.appcompat.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.2c057cb5-5a87-4123-ac22-193326987e33.tmp.xml</Data>
    <Data Name="StorePath">\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppHang_PinballX.exe_a391e1cfb3666a33d37f28fcb867cd7ae1d2bf8b_043bd839_ba784386-165b-4cc1-88b1-3b9b6e9b93a9</Data>
    <Data Name="AnalysisSymbol">
    </Data>
    <Data Name="Rechecking">0</Data>
    <Data Name="ReportId">669dda09-a1c0-49ca-9890-b844433cbf3d</Data>
    <Data Name="ReportStatus">268435456</Data>
    <Data Name="HashedBucket">2cc36e32695a04a6610478404b710b96</Data>
    <Data Name="CabGuid">0</Data>
  </EventData>
</Event>

App error :

Log Name:      Application
Source:        Application Hang
Date:          30-11-2024 14:57:33
Event ID:      1002
Task Category: Hanging Events
Level:         Error
Keywords:      
User:          SYSTEM
Computer:      Pinball
Description:
The program PinballX.exe version 1.0.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Hang" Guid="{c631c3dc-c676-59e4-2db3-5c0af00f9675}" />
    <EventID>1002</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>101</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2024-11-30T13:57:33.6348402Z" />
    <EventRecordID>5519</EventRecordID>
    <Correlation />
    <Execution ProcessID="17388" ThreadID="3120" />
    <Channel>Application</Channel>
    <Computer>Pinball</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="AppName">PinballX.exe</Data>
    <Data Name="AppVersion">1.0.0.0</Data>
    <Data Name="ProcessId">0x1b70</Data>
    <Data Name="StartTime">0x1db432e694fcbd6</Data>
    <Data Name="TerminationTime">87</Data>
    <Data Name="ExeFileName">D:\Pinball\PinballX\PinballX.exe</Data>
    <Data Name="ReportId">669dda09-a1c0-49ca-9890-b844433cbf3d</Data>
    <Data Name="PackageFullName">
    </Data>
    <Data Name="PackageRelativeAppId">
    </Data>
    <Data Name="HangType">Cross-thread</Data>
  </EventData>
</Event>

WER file :

WER.1dbffcaa-b8ce-4279-ad9b-46ac033adb9e.tmp.WERInternalMetadata.xml

EDIT :
For me it helped now to TURN OFF full exclusive mode hack 🤔(I don't get it)

 

[scutters]

Must admit i'm a bit behind on VPX updates on the cab, but i've tried RC5 on the desktop..

For me VPX RC5 GL version exited ok from PinballX 6.20 (with VPX set to fullscreen or windowed)

But the VPX RC5 DX version if set to exclusive full screen didn't close properly from PinballX (the visual pinball player window closes, but not the VPX editor) and PinballX would then hang. Changing VPX video preferences to use the full screen but windowed worked ok.

Edit - the vpx fullscreen exclusive hack option in PinballX didn't seem to have any effect for me (or running pinballx as admin)

[Mike_da_Spike]

49 minutes ago, scutters said:

from PinballX (the visual pinball player window closes, but not the VPX editor) and PinballX would then hang. Changing VPX video preferences to use the full screen but windowed worked ok.

Looks like more differrent issues.

For me pinballx is in a hung state after it loads the table and my vpx is set to full screen exclusive mode.

Odd thing is, that DX and GL are working fine on my test pc with pinballx

Maybe we should wait,as @Draco1962mentioned earlier, until vpx 10.8 will be official released and gather all the issues we find

[wrd1972]

Okay the full screen hack was already turned off. Thanks for the tip on how to show the mouse. It is now easier to force close PBX when it barfs.

So you guys think this is releated to latest Pinmame. That seems consistent because the issue seems to show up on newer VPM tables. It does not seem to happen on simple VPM tables, and never happens on EM tables.

 

Do you guys need anything else from me? Looking forward to the fix.

 

Oh yeah. Does the long pause when exiting VP10 back to the browser menu have something to do with this issue? The return time to the browser media is easily twice as long as it used to be.

[scutters]

On 12/2/2024 at 1:49 AM, wrd1972 said:

Do you guys need anything else from me? 

Can you confirm what version of VPX (and DX or GL), VPM and freezy you're using? We're assuming at the moment that it's a VPX 10.8 RC5 issue (or maybe VPM). But if you're running 10.7 then that goes out of the window.

If you are running 10.8 RC5 then maybe either try switching to the other variant (DX/GL) or try with RC4 instead.

[wrd1972]

I am currently using 6.20. I first noticed this on 6.13.

At this time, I dont want to touch VPM because everytime I do, something gets jacked up. Yes, I am running 10.8 RC5.

Right now, PBX is unusable in my Pincab, so I will need try something else. I do appreciate you guys jumping on this because I am sure there are many others having the problem. But again, I much prefer to use PBX. I will monitor this thread for updates.

[Draco1962]

Why can't you go back to the non-release candidate version of VPX?

[Mike_da_Spike]

As most new tables need 10.8 and that still in RC phase. In development for more than 2 years now, but Toxie want to release a final version of 10.8 around Christmas. 

Btw.Since I turned off the fullscreen hack al is working fine for me

And if you don't have issues with pbx 6.12 and lower, use an older version of PBX .

[wrd1972]

Like Mike said. Newer tables need 10.8.

I might try an older version of PBX, but I am going to blindly assume that the issue might still be there. Hopefully, they will release 10.8 final and you guys can find the bug.

[keithhov]

I too had exit problems with all the most recent versions of pbx and vpx/pinmame..

For now I am using 10.80 rev 1995 and pbx 6.11(something newer might work but I had 6.11 installer handy) and everything is working perfectly.  Between new versions of windows builds, vpx betas and more there are just so many variables right now , very confident it will all be back to normal sooner than later.

 

 

[Draco1962]

5 hours ago, keithhov said:

I too had exit problems with all the most recent versions of pbx and vpx/pinmame..

For now I am using 10.80 rev 1995 and pbx 6.11(something newer might work but I had 6.11 installer handy) and everything is working perfectly.  Between new versions of windows builds, vpx betas and more there are just so many variables right now , very confident it will all be back to normal sooner than later.

 

 

Agreed. 23H2 dust hadn't settled and 24H2 was rushed and the Windows 11 community is paying for it in spades. Not just here but across various other forums for software and devices. 

 

6 hours ago, wrd1972 said:

Like Mike said. Newer tables need 10.8.

I might try an older version of PBX, but I am going to blindly assume that the issue might still be there. Hopefully, they will release 10.8 final and you guys can find the bug.

Thanks. I seem to recall that mentioned in another thread now that you mention it. I think keeping current and staying the present course is best, assuming your patience can handle the anticipation. 

[Mike_da_Spike]

9 hours ago, keithhov said:

For now I am using 10.80 rev 1995

You known that you use a release between rc3 and rc4 ? Rc5 is version 2015 and latest is 2035 ? So with 1995 you are running a bit behind.

Maybe we should share our pinballx settings and our visual pinball settings, to check if we find differrences. But best is when 10.8 has been official released with the latest pinmame en directb2s.

 

[scutters]

On 12/1/2024 at 10:16 AM, scutters said:

Must admit i'm a bit behind on VPX updates on the cab, but i've tried RC5 on the desktop..

For me VPX RC5 GL version exited ok from PinballX 6.20 (with VPX set to fullscreen or windowed)

But the VPX RC5 DX version if set to exclusive full screen didn't close properly from PinballX (the visual pinball player window closes, but not the VPX editor) and PinballX would then hang. Changing VPX video preferences to use the full screen but windowed worked ok.

Edit - the vpx fullscreen exclusive hack option in PinballX didn't seem to have any effect for me (or running pinballx as admin)

Same behaviour as above using VPX 10.8 RC6 released today. DX version doesn't exit cleanly and PinballX hangs, GL version exits ok and PinballX returns to wheel when in fullscreen mode.

[keithhov]

10 hours ago, Mike_da_Spike said:

You known that you use a release between rc3 and rc4 ? Rc5 is version 2015 and latest is 2035 ? So with 1995 you are running a bit behind.

Maybe we should share our pinballx settings and our visual pinball settings, to check if we find differrences. But best is when 10.8 has been official released with the latest pinmame en directb2s.

 

Yeah I realize 1995 is a bit behind, I seem to be able to play all newer releases, especially VPW tables in full with no limitations that I am aware of.  I will try 2037 tonight and see how it interacts with pinballx 6.11 and 6.20.... I kinda think windows builds/nvida drivers are causing most of the problems but that's purely a guess.

 

[keithhov]

10.8 v2037 seems to work fine by itself....played fish tales for a few mins in 4k, steady 144 frames......2037 seems to work fine with pinballx version 6.11, exit takes me back to wheel menu instantly..........installed pinballx 6.20 and I am back to slow exits...not horrible but about 6 to 7 seconds of black screen then wheel menu..... tried both fullscreen hack options. 

I do get a error when installing 6.20 around C++, I don't get the error when installing 6.11.  Might trying to manually reinstall C++ if one of you experts thinks it could be part of the problem. 

[wrd1972]

22 hours ago, scutters said:

Same behaviour as above using VPX 10.8 RC6 released today. DX version doesn't exit cleanly and PinballX hangs, GL version exits ok and PinballX returns to wheel when in fullscreen mode.

I will try GL and see if it helps. What would I expect to see different by using GL over DX?

[wrd1972]

Okay I switched PBX to GL, and yes, it seems to close and return to the browser. BUT, after a few successful table loads, it freezes on the loading screen. So now kind of the opposite issue like seen in DX. Damnit.

 

Edit. It always hangs on the third attempt to load a table.

[Mike_da_Spike]

9 hours ago, wrd1972 said:

I will try GL and see if it helps. What would I expect to see different by using GL over DX?

I didn't notice any difference between DX and GL.
I think it's more to create a better 3d experience, used by  VR, 3d anaglyphic, head tarcking, but also for non windows machines (as they won't dupport DX9).

I installed RC6, as well and experience the same issue. it just hangs after the message "VPX Full screen exclusive focus hack set".
Turning this off resulsts now in the same issue

@wrd1972 Can you do a test for me ?
Rename in the PinballX folder the file PINemHi.exe to PINemHi.exe_ and redo your test (with DX or GL, but I only checked DX). For me itresulted that I could launch, play and close tables and return to PinballX agan (even with "Full screen exclusive focus hack" enabled)