mtl_170hc not writing the nvram when in pinballX front end and showpindmd 1 about dmd-extensions

[vpinsteve]

Hello. Adding this to the end of the table script fixes this problem. Thanks to Rob Ross for the suggestion.

Sub Table_exit()
Controller.Stop
End sub

[vpinsteve]

I just spent a bit of time with the brandy new 10.3.1 in there and exact same results.

[freezy]

Thanks, could you post download links of the table(s), the ROM, the ROM patch, the VP build and VPM build so I can reproduce?

[vpinsteve]

Absolutely. https://www.dropbox.com/s/4ku1gpwmgkfru8n/dmd-extTestPackage.zip?dl=0
180 MB, I just copied all the files to this zip

[freezy]

Cheers!

No link restriction here whatsoever, next time feel free to just paste them!

[freezy]

Thanks, that was the next thing I wanted to look at!

So basically you're saying that it was a table bug? Any explanation why it only happened with external DMD enabled?

[vpinsteve]

Well, no. I have no explanation, good point. The other variable is this only happens in the pinballX front end. When launch the table in vpinballX.exe stand alone, no problems writing nvram when showpindmd1. soooo... meh.

In the end, seems like a table_end should be there in the script anyway? So adding the subroutine to any table to fix this problem should probably just be done. Might just be fixing other things at the same time. For example, before adding the table_end if I launch the table from pinballX, and then exit the table without actually launching a game, vpinballx.exe would crash. Adding the table_end fixed that too.

So I'd be happy to run any scenarios if we wanted to look further into it. I could enable some fancy logging, install a debug version if available or anything like this and run through things. Just not sure it's worth more consternation if this simple script fix does the trick.

[freezy]

Hmm maybe it would be even better to report this to the VP devs? I mean changing anything in a script shouldn't crash the program.