vpinmame crashes whenever I enable external dmd. Turns out it's a bad path to a mapped network drive. Not sure how to correct to a full network path in a "baller installer + Rudy's complete update of 11/23 and 05/24" installation.

From dmdDevice.log:

[1] 2024/05/21 00:22:40.545 ERROR | System.TypeInitializationException: The type initializer for 'PinMameDevice.DmdDevice' threw an exception. ---> System.IO.FileNotFoundException: /share/vPinball/VisualPinball/VPinMAME/DmdDevice64.dll

at System.Diagnostics.FileVersionInfo.GetVersionInfo(String fileName)

at LibDmd.Common.PathUtil.GetAssemblyVersion(String& fullVersion, String& sha)

at LibDmd.DmdDevice.DmdDevice..ctor(IConfiguration config)

at PinMameDevice.DmdDevice.DeviceInstance..ctor()

at PinMameDevice.DmdDevice..cctor()

--- End of inner exception stack trace ---

at PinMameDevice.DmdDevice.Open()

The path: ~~/share/vPinball/VisualPinball/VPinMAME/DmdDevice64.dll~~

Should be \\MYNAS/share/vPinball/VisualPinball/VPinMAME/DmdDevice64.dll

I'm not sure where the freezy dmdext is picking up the path. I can reproduce the same error in freezy dmdext 2.2.1 and 2.2.2.

I probably missed the memo on NOT installing vPinball on a NAS drive. I'm 150 tables in and they play ok on virtual dmd as long as I never enable DMDext. But most pup packs are not happy without external dmd.. I'll probably reinstall on a local drive. In the meantime, if anybody can suggest a way to update the path to dmddevice.dll/dmddevice64.dll, I'll test it out.