Won't launch cmd for dmdext after upgrade of PinballX

[Tom Speirs]

Im releasing 5.94. Lets see what turns up.

[Tom Speirs]

It really should all be fixed now. Post the log with the latest when you get a chance. Im building it now.

There were definitly some issues so its not you but hopefully all fixed now.

The new version will at least show me if im going crazy! It will report the type of device used.

[Mike_da_Spike]

18 minutes ago, Tom Speirs said:

The new version will at least show me if im going crazy! It will report the type of device used.

Aren't we all crazy ???

I will try to get some logs today (but right now, my head feels like it is exploded and didnt drink any booze), maybe others can post logs  as well.

[Tom Speirs]

I live in hope. Other than you I hear next to nothing.

[Mike_da_Spike]

So all is goodi f you don't hear anything. 

It must be my Dutch temperament that I moan a lot .... (ask scutters about it 😜)

[Tom Speirs]

Yeah, your super chill. Kudos.

[Tom Speirs]

I just tested with Freezy virtual DMD. That's working fine. That's the best I can test.

[Mike_da_Spike]

In the past I tested with Freezys virtual as well and that worked. moved the DMDdevice.ini from virtual to real, gave me hanging pinballX when table was lanched.

I tried 5.94 for me.
PinballX initialized the real DMD correct, and I launched directly a table
Takes again 9 seconds from launch till pinball closes XDMD and starts the emulator command to launch the table

 

But no DMD within Visual Pinball.
Returning to PBX, give me the DMD video again

Attached are the log files.

When I use Freezy's dmd device64.dll (and remove pindmd.dll from the pinballx directory), the DMD is initialized withing Pinballx and working

13:03:26.70  23-4-2023:  Real DMD Initialized
13:03:26.70  23-4-2023:  Device:DMDDevice.dll

Closing down XDMD is working fast as well, and table works with Vpinmame

but PinballX is not responding

Key's to exit emulator doesn't work.
Alt-tab shows that the backglass video is still their

but at a sudden moment :

Eventlog only shows an app hang event :

Fault bucket 1993404121035946545, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: PinballX.exe
P2: 1.0.0.0
P3: 641cef7e
P4: 246f
P5: 134217732
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.37396143-1d7d-46f3-b52a-83e0d2938889.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1d8145a9-12c3-46df-a7cf-9f4ab4f153e0.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.af18e650-bcc2-47df-b6be-ea777094cb3e.tmp.txt
\\?\C:\Users\micha\AppData\Local\Temp\WER.35cbc49d-a72a-43cd-b730-897487c1b852.tmp.appcompat.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.e4d9a539-382d-4286-a45d-5819a8a23b45.tmp.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppHang_PinballX.exe_e3ddf147f596981793f91657772779f23c196d_808ef1e3_0002f110-59ae-4216-a798-a109f18d55fa

Analysis symbol: 
Rechecking for solution: 0
Report Id: e843dfc5-b40d-4ef4-b370-d6a8f260e7af
Report Status: 268435456
Hashed bucket: 8f166f380775ca1a0ba9fe7c9025ba31
Cab Guid: 0

Nothing usable/usefull in the WER file as well

log.txt XDMDlog.txt log_DMDdevice.txt

[chadman]

Mike, sorry for the delay.  I did try attract mode and it never came on.  I really never use it, but when I put in a time of 1 or 2 min, it does not start like I would expect.  I also notice the delay to start compared to 5.81.  I really thought it was working in my last post, but I still have issues with VPX tables and the dmd not starting.  When I initially tested, I did not have one failure, but it was only a few tables.  I have not tried the latest version but will load that up here and give it a shot and report back.  The real color dmd sure is cool, but always gives a little more grief.  I just love the look of a real dmd.

[chadman]

I just opened a closed a bunch of fx3 and vpx tables.  The dmd worked great on all the tables I just tested.  I was using 5.94 for this test.

log.txt

[Mike_da_Spike]

30 minutes ago, chadman said:

I just opened a closed a bunch of fx3 and vpx tables.  The dmd worked great on all the tables I just tested.  I was using 5.94 for this test.

log.txt 12.52 kB · 1 download

Nice ! If you launch pinballx, wait for a couple of minutes, and launch a fx3 table. Is that still working as well?

[Tom Speirs]

Mike, at least its initializing XMD and PinDMD3 properly for you now. It wasn't doing that the other day.

As far as I can see I fixed everything I could. I have nothing else for now.

Hopefully we will figure it.

You seem to have a huge delay unitializing PimDMD3 or Video playback on DMD. Not sure why.

[Tom Speirs]

In fact, its timing out and not shutting down.

[Tom Speirs]

I'm releasing 5.95 in a minute. It has a 30 second timeout shutting it down rather than 8 seconds.

Just so I can properly identify and highlight the issue for all. 

It may well just be you Mike. Don't know yet.

[Tom Speirs]

I can see the initialize shutdown also takes about 7.5 seconds for Chadman then later takes around 4 seconds. It is also doing other things here though so could be taking less.

[Tom Speirs]

Please try 5.96. It will at least give me some better insight into what is going on if you both try.

[Mike_da_Spike]

4 hours ago, Tom Speirs said:

You seem to have a huge delay unitializing PimDMD3 or Video playback on DMD. Not sure why.

ok. thats not good. So maybe my device is not fine.

On the other side : If I don't use XDMD during PinballX, but initialize FlexDMD via plugin (that also may have a delay during start of Pinballx), when game starts, it just leave FlexDMD open, but stops displaying anaything, so it will not lock the dmd (i asume)

So instead of closing and re-initialize the DMD when game starts/end, it just stop displaying anything on the real DMD when game starts and start displaying when game is stopped. Maybe this is not the propper way and causing memory leaks or high CPU, but never run into a problem of this

Tested 5.96

I have good and bad news  
But lets wait for that for the screensaver tests

I thought we had some good news as well. but tested more and didn't work quit wel

1. Launch Table directly after PBX is started 
   XDMD is closing fast, but 15 seconds delay after closing down XDMD and set plugin data
   Exiting table shows DMD videos within PBX
2. Launch same table again after it was closed
   XDMD is closed after 7 seconds when table launch is initiated, After that table is launched quickly 
   Exiting table shows DMD videos within PBX
3. After exiting previous table, wait for screensaver mode and launch Table
   Good news : DMD is showing when table is launched during screensaver mode !
   Bad news : I must have a lot of patience to start a table when I launch it during screensaver mode. As it took nearly 3 1/2 minute before the launch command takes place after the table was launched (and table launch and getting PinballX to background took only 10 seconds)
   Exiting table shows DMD videos within PBX
4. Exit previous table and wait again for screensaver mode.
   Actually launch of table (executable) now tooks 20 seconds after I pressed the button, but when table was launched, no DMD
   Returning to PinballX results that I don't have DMD videos on the DMD
   I don't see it initialized in the log either
    

For the test all the plugins where disabled

I really don't have a clue what's going on.
Attached log files, and the XDMDlog.txt 

 

 

log.txt XDMDlog.txt

[Tom Speirs]

That xdmd log looks odd. Is that correct?

[Mike_da_Spike]

Yeah, its overwrites everytime, and this was when i closed the last table and returned to pinballx. It couldn't initialize the dmd at that moment 

My assumption is that xdmd didn't close correctly when table launched and when try to initilize when table closed, it shows this

[Mike_da_Spike]

I checked the pindmd_log.txt in my backup from that moment, but that was a complete empty file. Not sure why

[chadman]

Mike, I do see the same thing you mentioned.  If I let PinballX sit for 10 min and then start an FX3 table the DMD goes out and never starts again until I relaunch PinballX.

 

[Mike_da_Spike]

24 minutes ago, chadman said:

Mike, I do see the same thing you mentioned.  If I let PinballX sit for 10 min and then start an FX3 table the DMD goes out and never starts again until I relaunch PinballX.

 

can you post the logs for Tom ?
Also the xdmdlog.txt and pindmd_log.txt

thanks !

[chadman]

Here the logs I just got.

log.txt XDMDlog.txt pinDMD_log.txt DmdDevice.log

[Tom Speirs]

Sorry, ive been travelling. Ill take a look. At least we are narrowing it down.

Can you confirm, just leaving it does the same, rather than entering screensaver too?

[Tom Speirs]

I think it might be a buffer overrun. Please try the attached. Thanks.

XDMD.7z