321 replies to this topic

[jocooter]

I'm using latest build with no problems

Sent from my A0001 using Tapatalk

[sliderpoint]

That's really a weird error. It usually means some 32/64-bit conflict. You're using normal 32-bit VPM, right? I've manually cleaned my build folder and recompiled again, if the attached build works, then fuck you Visual Studio...

 

DmdDevice.zip

 

Well VS is safe for now.  It's not working for me. I would guess it's something with my setup.  Others are able to work without issue.  I'll try it on another system soon.

 

-Mike

[freezy]

Which OS and bitness are you running if I may ask? 

[sliderpoint]

Win10 64Bit

 

32bit vpinmame.dll

 

VP/Vpinmame both in the same folder on D:\VP

 

The modified ROMs do run without the external option checked.

 

edit,  Also this is just from the TEST button of Setup.exe for vpminmame, I haven't started one with a VP table yet.

 

-Mike

Edited by sliderpoint, 15 February 2017 - 03:42 PM.

[alistaircg]

ok im four gin and tonics in over here.

 

Simply... can I replace my broken Data East Star Wars DMD with a colour monitor ?

[freezy]

Win10 64Bit

 

32bit vpinmame.dll

 

VP/Vpinmame both in the same folder on D:\VP

 

The modified ROMs do run without the external option checked.

 

edit,  Also this is just from the TEST button of Setup.exe for vpminmame, I haven't started one with a VP table yet.

 

-Mike

 

Oh you literally have VPM in the same folder as VP. Not as in "a subfolder in VP". Any particular reason for this setup?

[sliderpoint]

Just easier.  Only use VPM with VP so it made sense.  Scripts in Scripts folder, Tables in tables folder, roms in roms folder etc.

 

-Mike

[roar]

ok im four gin and tonics in over here.

 

Simply... can I replace my broken Data East Star Wars DMD with a colour monitor ?

 

In a real Data East Pinball Machine? Not a virtual Pinball Machine? No.

[alistaircg]

 

ok im four gin and tonics in over here.

 

Simply... can I replace my broken Data East Star Wars DMD with a colour monitor ?

 

In a real Data East Pinball Machine? Not a virtual Pinball Machine? No.

 

Both Actually, now that im sober

[jocooter]

ok,i have noticed some issues now that ive been able to play. i have a couple roms that displayed twice(once on bottom half, once on top half). and some have RGB timing making cluttered 

[bosvrucht]

 

ok im four gin and tonics in over here.

 

Simply... can I replace my broken Data East Star Wars DMD with a colour monitor ?

 

In a real Data East Pinball Machine? Not a virtual Pinball Machine? No.

 

 

I think you can,  but it will not be cost effective.  The more expensive 192x128 screens (baywatch), are now routinely replaced by an lcd using things like "dmd extender".

[shadowshd]

First of all a big thank you guys for making things better and better and for your hard work and support

I don't know if I can post issues here Freezy, but I've asked on another forum and still can't get DMDDevice.dll work on my machine.

I've copied DMDExt' DMDDevice.dll and DMDDevice.ini in my SysWow64 folder and nowhere else.
If I launch a test in VPM's Setup.exe, everything runs fine.

But when I launch a table, whatever version of VP I use, backglass displays, playfield displays, DOF runs and Visual Pinball exits by itself without any error message.

Here's a crash log if it can help :

Crash report VPX rev2898
============
Process: VPinballX.exe
Reason: 0xE0434352 - UNKNOWN at 0023:76ADA832
Thread ID: 0xEC4 [3780]

Call stack
==========
76ADA832 KERNELBASE.dll RaiseException + 0x62 (0xFFFFFFFFE0434352 0x00000001 0x00000005 0x20d5eaec)
682D352F clr.dll GetPrivateContextsPerfCounters + 0x341FF (0x00000000 0xFFFFFFFF8521FBFC 0x20D5EBFC 0x20d5ca88)
683FC0CB clr.dll CreateHistoryReader + 0x1BE1B (0xFFFFFFFF8521FCC4 0x20D5F778 0x681743B0 0x094e0010)
68411A19 clr.dll CreateHistoryReader + 0x31769 (0x20D5F150 0x093DC39C 0x00000103 0x20d5f2c8)
66CF27FA clrjit.dll (0x094E3D14 0x3A20AA98 0x094E1A34 0x094e0010)
66CE1A52 clrjit.dll (0x094E3D14 0x094E18F8 0x20D5F7E0 0x094e0010)
66CE1C47 clrjit.dll (0x094E3114 0x094E18F8 0x20D5F7E0 0x094e0010)
66CE3326 clrjit.dll (0x20D5F5D8 0x20D5F774 0x00103810 0x00000000)
66CE3C3B clrjit.dll (0x20D5F778 0x20D5F7E0 0x20D5F5D8 0x20d5f774)
66CE3D89 clrjit.dll (0x093D7244 0x20D5F778 0x20D5F7E0 0x20d5f5d8)
66CE3EDA clrjit.dll (0x20D5F778 0x20D5F7E0 0x20D5F5D8 0x20d5f774)
66CE49D5 clrjit.dll (0x66D5A508 0x20D5F778 0x20D5F7E0 0x00103810)
6816FEFF clr.dll CoUninitializeEE + 0x1B79F (0x20D5F7E0 0x00103810 0x00000000 0x20d5f730)
6816FFDC clr.dll CoUninitializeEE + 0x1B87C (0x20D5F7E0 0x00103810 0x00000000 0x20d5f730)
68170021 clr.dll CoUninitializeEE + 0x1B8C1 (0x20D5F7E0 0x00103810 0x00000000 0x20d5f730)
6817027F clr.dll CoUninitializeEE + 0x1BB1F (0x00000000 0x00000000 0xFFFFFFFF8521EB4C 0x07300718)
6817052A clr.dll CoUninitializeEE + 0x1BDCA (0x07300718 0x00000000 0x07300718 0xffffffff8521eb54)
681717B0 clr.dll CoUninitializeEE + 0x1D050 (0x00000000 0xFFFFFFFF8521EC4C 0x20D5FCF0 0x20d5fc90)
681530E9 clr.dll DllCanUnloadNowInternal + 0x9C9 (0x20D5FC90 0x093DC39C 0x00000000 0x308c988c)
6812EF51 clr.dll (0x00000000 0x00000000 0x00000000 0x3f800000)
22537636  (0x00000008 0x00000000 0x044C0050 0x306be8c0)
22537501  (0x00000008 0x00000000 0x00000006 0x225374e0)
0934D7B9  (0x2E8EDE18 0x00000008 0x00000000 0x306be8c0)
2E6320B2 vpinmame.dll (0x2E8EDE18 0x00000008 0x00000000 0x306be8c0)
2E62FD3B vpinmame.dll (0x00000020 0x00000000 0x2E5064D5 0x03c3eeb0)
2E50640E vpinmame.dll (0x00000000 0x1C280880 0x20D5FF80 0x2e67344c)
2E5312C2 vpinmame.

Environment
===========
Date/time: 16/2/2017, 15:02:12:352
Number of CPUs: 8
Processor type: 586
System: Unknown Windows version - 6.2 ()

Memory status
=============
Total Reserved: 209964K (205M) bytes
Total Commited: 966496K (943M) bytes
Total Free: 3017780K (2947M) bytes
Largest Free: 2095744K (2046M) bytes

Registers
=========
EAX=20D5EA28 EBX=00000005 ECX=00000005 EDX=00000000
ESI=20D5EAEC EDI=00000001 EBP=20D5FF4C ESP=20D5FF44 EIP=2E5312C2
FLG=00000216 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B

Failed to save minidump.

Thanks

Edited by shadowshd, 16 February 2017 - 02:52 PM.

[freezy]

Also copy DmdDevice.log.config to the same folder, open it and change "fileName" on line 27 to a path writable by non-admin (SysWOW64 isn't). Then try again and paste that log, that's the interesting part.

[Thalamus]

ok,i have noticed some issues now that ive been able to play. i have a couple roms that displayed twice(once on bottom half, once on top half). and some have RGB timing making cluttered 

 

I guess this is what you see ?

 

https://github.com/f...sions/issues/32

 

Could you guys, that have this working - please tell me what DMD you are using - virtual, *******, PinDMD[1,2,3] ?

[freezy]

Yeah and if anyone has a real screenshot instead of the photoshopped one in the GitHub issue that would be great.

 

@jocooter: Also, "a couple roms" is not very specific. In order to fix stuff I need to be able to reproduce your problem and for that it would be great to know which ROMs you're talking about. In any case, a log would be useful as well. Also, not sure what you mean by "cluttered RGB timing".

[shadowshd]

@Freezy, here's the log sir :

[8] 2017/02/18 18:38:15.756  INFO | Determined color path from VPinMAME.dll location: C:\Visual Pinball\VPinMAME\altcolor  [8] 2017/02/18 18:38:15.779  INFO | [vpm] Open() 
 [8] 2017/02/18 18:38:15.785  INFO | [vpm] Set_4_Colors_Palette() 
 [8] 2017/02/18 18:38:15.785  INFO | Setting palette to 4 colors... 
 [8] 2017/02/18 18:38:15.804  INFO | [vpm] PM_GameSettings(1) 
 [8] 2017/02/18 18:38:15.804  INFO | Enabling game colorization 
 [8] 2017/02/18 18:38:15.812  INFO | Setting game name: fh_905h 
 [8] 2017/02/18 18:38:15.812  INFO | Setting color: #FFFF5820 
 [8] 2017/02/18 18:38:35.327 ERROR | System.BadImageFormatException: Impossible de charger le fichier ou l'assembly 'dmdext, Version=1.5.0.0, Culture=neutral, PublicKeyToken=null' ou une de ses dépendances. Tentative de chargement d’un programme de format incorrect.
Nom de fichier : 'dmdext, Version=1.5.0.0, Culture=neutral, PublicKeyToken=null'
   à PinMameDevice.DmdExt.Init()
   à PinMameDevice.DmdDevice.GameSettings(String gameName, UInt64 hardwareGeneration, IntPtr options)


AVT : la journalisation de liaison d'assembly est désactivée.
Pour activer la journalisation des échecs de liaison d'assembly, attribuez la valeur 1 à la valeur de Registre [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD).
Remarque : une certaine perte de performance est associée à l'enregistrement dans le journal des échecs de liaison d'assembly.
Pour désactiver cette fonctionnalité, supprimez la valeur de Registre [HKLM\Software\Microsoft\Fusion!EnableLog].

 

My system is french, so I'll translate the ERROR line :

 [8] 2017/02/18 18:38:35.327 ERROR | System.BadImageFormatException: Unable to load the file or the assembly 'dmdext, Version=1.5.0.0, Culture=neutral, PublicKeyToken=null" or one of its dependencies. 
Attempting to load an invalid format program.
Filename : 'dmdext, Version=1.5.0.0, Culture=neutral, PublicKeyToken=null'
 to PinMameDevice.DmdExt.Init()
 to PinMameDevice.DmdDevice.GameSettings(String gameName, UInt64 hardware Generation, InPtr options)

If think it isn't necessary to translate the whole log, but if needed I will

 

I have added in my PATH variable C:\Games\DMDExt, where all files from DMDExt v1.5 have been unzipped.

 

Thanks

[freezy]

Thanks, that's the same problem as sliderpoint. No idea how to fix but I'll look into it some more. Et pas de soucis pour les erreurs en français!

[shadowshd]

Merci Freezy

If you need testing and/or feed-back don't hesitate to ask, it will be a pleasure to help

Have a nice night

++

[OzBlackKnight]

Hi Freezy,

 

I unfortunately have the same error as sliderpoint and shadowshd.

 

My system is Windows 7 64 bit, with the latest (15 Feb 2017) DmdDevice.dll and DmdDevice.ini in the C:\Windows\SysWOW64 directory and no where else.

The DMDExt v1.5 works without issue from a command line prompt. ie DMDExt test. Anymore info required?

 

 [1] 2017/02/22 10:02:07.271  INFO | Determined color path from VPinMAME.dll location: D:\Pinball\Virtual Pinball\altcolor 

 [1] 2017/02/22 10:02:07.286  INFO | Launching VPinMAME API. 

 [1] 2017/02/22 10:02:07.286  INFO | [vpm] Open() 

 [1] 2017/02/22 10:02:07.286  INFO | [vpm] Set_4_Colors_Palette() 

 [1] 2017/02/22 10:02:07.286  INFO | Setting palette to 4 colors... 

 [1] 2017/02/22 10:02:07.286  INFO | [vpm] PM_GameSettings(1) 

 [1] 2017/02/22 10:02:07.286  INFO | Enabling game colorization 

 [1] 2017/02/22 10:02:07.286  INFO | Setting game name: acd_168 

 [1] 2017/02/22 10:02:07.286  INFO | Setting color: #FFFF5820 

 [1] 2017/02/22 10:02:07.447 ERROR | System.BadImageFormatException: Could not load file or assembly 'dmdext, Version=1.5.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An attempt was made to load a program with an incorrect format.

File name: 'dmdext, Version=1.5.0.0, Culture=neutral, PublicKeyToken=null'

   at PinMameDevice.DmdExt.Init()

   at PinMameDevice.DmdDevice.GameSettings(String gameName, UInt64 hardwareGeneration, IntPtr options)

 

WRN: Assembly binding logging is turned OFF.

To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.

Note: There is some performance penalty associated with assembly bind failure logging.

To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

[OzBlackKnight]

OK. After further testing, these crashes only occur when using TEST while running Setup.exe of VPinMAME. Everything works fine when running VPX or Physmod5. Spiderman and Avengers in particular look awesome. :-)