[RESOLVED] PinballX not updating NVRAM for VPX tables on exit

[hoffguy]

I've been fighting this off and on for a few weeks but haven't made any progress, so time to post.

I get absolutely zero NVRAM updates for any VPX table when launched from PinballX and exited using the emulator exit key set in PBX settings. If I Q,Q to graceful exit VPX, or F3 to table restart, the NVRAM updates just fine. This goes for every table that I have. No high score updates, no rom settings updates, nothing. 

I've searched a bunch and tried everything I could find from past posts on this forum including:

• run vpx and pinballx as administrator
• check pinemhi nvram path
• disable pinemhi
• disable windows VSS
• not using alternateexe or vp9, only vpx
• change emulator exit and pinballx exit to different buttons
• check that names in game manager match the table files exactly
• deleted NVRAM files
• making a 10s wait .bat Launch After in case it was a timing thing

 

I've run out of things I can find to try. I've attached pinballx.ini and a log.txt. The log is of me opening AFM, setting freeplay off in the rom, exiting to PBX menu, then relaunching AFM to check and exiting. Any ideas on what I can try to get this working?

log.txt PinballX.ini

[Mike_da_Spike]

I had exactly the same issue and took a long time for me to figure it out. But for me it is working like a charm now and run pinemhi leaderboard without an issue

 

 

[hoffguy]

4 minutes ago, Mike_da_Spike said:

I had exactly the same issue and took a long time for me to figure it out. But for me it is working like a charm now and run pinemhi leaderboard without an issue

 

 

Thanks, but I've been through that thread top to bottom and tried everything. I'm not using the leaderboard plugin, I tried disabling pinemhi by renaming to .ini_, and I disabled windows VSS. And it is not just one or two tables, it is every table I have, so I doubt it is the tablescript problems that scutters had in every single one of them.

[Mike_da_Spike]

Did you check eventlog for any errors during pinballx exit ?

Pinballx is using pinemhi and that was causing my issue as well. Not because I run pinemhi leaderboard (but if all is working for you, you should install pinemhi leaderboard!)

 

[hoffguy]

1 minute ago, Mike_da_Spike said:

Did you check eventlog for any errors during pinballx exit ?

Pinballx is using pinemhi and that was causing my issue as well. Not because I run pinemhi leaderboard (but if all is working for you, you should install pinemhi leaderboard!)

 

• Hide Mike_da_Spike's signature
• Hide all signatures

I looked in windows eventlog and could not find any errors related to pinballx, but still disabled VSS just to be sure. 

[Mike_da_Spike]

6 minutes ago, hoffguy said:

I looked in windows eventlog and could not find any errors related to pinballx, but still disabled VSS just to be sure. 

My errors where not related to pbx as well, but events where there at the same time I exit a table

I also did a lot of testing. Launching a table in another way to get vp closed with qq.  Realy pain in the ass to figure it out.

Could be antivirus software, or backup program as well

[scutters]

This may well not be a factor, but it looks weird so worth ruling it out..

In your ini you have;

[VisualPinball]
Enabled=True
WorkingPath=C:\Visual Pinball
TablePath=C:\Visual Pinball\Tables
Executable=C:\Visual Pinball\VPinballX.exe

With the working path set and then included in executable path as well, so in the log on table launch you then get a launch string like;

"C:\Visual Pinball\C:\Visual Pinball\VPinballX.exe /play -"C:\Visual Pinball\Tables\Attack from Mars (Bally 1995) g5k 1.1.vpx""

Remove the path from executable entry.

 

Assuming that doesn't fix it,

• what happens when you delete an nvram and exit a table via pinballx - is a new nvram created?
• Pinballx running as admin, fine..  but no other compatibility settings set?
• Try running with EnableFullScreenExclusiveHack=True set to false for VP
• After that it as it sounds like you're pretty computer savvy running a procmon trace with a filter on the nvram folder may show if nvram is being locked by something, and if so what process.

[hoffguy]

16 hours ago, scutters said:

This may well not be a factor, but it looks weird so worth ruling it out..

In your ini you have;

[VisualPinball]
Enabled=True
WorkingPath=C:\Visual Pinball
TablePath=C:\Visual Pinball\Tables
Executable=C:\Visual Pinball\VPinballX.exe

With the working path set and then included in executable path as well, so in the log on table launch you then get a launch string like;

"C:\Visual Pinball\C:\Visual Pinball\VPinballX.exe /play -"C:\Visual Pinball\Tables\Attack from Mars (Bally 1995) g5k 1.1.vpx""

Remove the path from executable entry.

 

Assuming that doesn't fix it,

• what happens when you delete an nvram and exit a table via pinballx - is a new nvram created?
• Pinballx running as admin, fine..  but no other compatibility settings set?
• Try running with EnableFullScreenExclusiveHack=True set to false for VP
• After that it as it sounds like you're pretty computer savvy running a procmon trace with a filter on the nvram folder may show if nvram is being locked by something, and if so what process.

 

Fixing the executable path did it. Thank you so much for the eagle eye spot. Funny how that only caused this one specific issue. Thanks also for the procmon mention, I knew something like that had to exist but couldn't find the right words to google to find it. That will come in handy in the future, no doubt.