321 replies to this topic

[sliderpoint]

Try disable at91jit in registry for that rom ... might be it

 

\\hkcu\software\freeware\mtl_170c\at91jit - set it to 0

 

Tried that, no effect for me.

 

-Mike

[Thalamus]

Well, reason for asking is that I believe I saw your error on my desktop computer when I tested the rom via setup.exe. But, with that key set to zero the game would run despite setup.exe crashing. Ah - yes, now I remember. Carny or Rob said something about that setup.exe doesn't check that key so. You sure you've tried the game with it setup to zero ?

[sliderpoint]

Yes, tried both from just setup for VPM and running through the table first from VP. I usually try both because it was mentioned that some worked only though VP (which is weird, but ok)

 

-Mike

[freezy]

Thanks for the reports guys. The incompatibility error is by far the most frequent one appearing in my crash logs. I'll try spending some more time reproducing it so it can finally be fixed.

[Andypc]

I am getting really frustrated as I am getting nothing but the tables crashing

 

I have tried everything suggested in this thread and tried the DMDdevice.dll from both this thread and the one from VpinMame 2.8. I have edited the .ini and .config files as suggested, but nothing works!!

 

at91jit - set it to 0 - for the rom.

 

Created folder c:\temp\ and made sure permissions were set to full, but no crash log generated in that folder  

[freezy]

Where did you copy your DLL? Where is DmdDevice.log.config? What's in DmdDevice.log.config?

[Andypc]

DLL downloaded from post 1 in this thread (Version 1.5)

DMDDevice.dll in c:\Windows\SysWOW64

DMDDevice.ini in c:\Windows\SysWOW64

DmdDevice.log.config in c:\Windows\SysWOW64

 

DMDDevice.log.config:-

 

<?xml version="1.0" encoding="utf-8" ?>
<nlog xmlns="http://www.nlog-proj...chemas/NLog.xsd"
      xmlns:xsi="http://www.w3.org/20...Schema-instance"
      xsi:schemaLocation="http://www.nlog-proj...chemas/NLog.xsd NLog.xsd"
      autoReload="true"
      throwExceptions="false"
      internalLogLevel="Off" internalLogFile="c:\temp\nlog-internal.log" >

  <targets>

    <!--
            add your targets here
            See https://github.com/n...og/wiki/Targets for possible targets.
            See https://github.com/n...ayout-Renderers for the possible layout renderers.
        -->

    <target name="console" xsi:type="ColoredConsole" useDefaultRowHighlightingRules="false"
         layout="${pad:padding=4:inner=[${threadid}]} ${date} ${pad:padding=5:inner=${level:uppercase=true}} | ${message} ${exception:format=ToString}">
      <highlight-row condition="level == LogLevel.Trace" foregroundColor="DarkGray" />
      <highlight-row condition="level == LogLevel.Debug" foregroundColor="DarkGray" />
      <highlight-row condition="level == LogLevel.Info" foregroundColor="Gray" />
      <highlight-row condition="level == LogLevel.Warn" foregroundColor="Yellow" />
      <highlight-row condition="level == LogLevel.Error" foregroundColor="Red" />
      <highlight-row condition="level == LogLevel.Fatal" foregroundColor="Magenta" />
    </target>

    <target xsi:type="File" name="file" fileName="c:\temp\DmdDevice.log"
       layout="${pad:padding=4:inner=[${threadid}]} ${date} ${pad:padding=5:inner=${level:uppercase=true}} | ${message} ${exception:format=ToString}"
       replaceFileContentsOnEachWrite="false"
       deleteOldFileOnStartup="true"/>

  </targets>

  <rules>
    <logger name="*" minlevel="Trace" writeTo="console" />
    <logger name="*" minlevel="Trace" writeTo="file" />
  </rules>
</nlog>

Why are all those web addresses in the DMDDevice.log.config?

[Thalamus]

its just comments - <!-- means beginning of comment, and it ends with -->

 

What about posting c:\temp\DmdDevice.log

Edited by Thalamus, 09 March 2017 - 12:21 AM.

[Andypc]

No log was generated?

[OzBlackKnight]

Huh, really.

 

@sliderpoint, @shadowshd, @OzBlackKnight, does that happen with you as well?

No.

 

Try disable at91jit in registry for that rom ... might be it

 

\\hkcu\software\freeware\mtl_170c\at91jit - set it to 0

 

Tried that, no effect for me.

 

-Mike

 

Ditto.

[freezy]

@Andypc: Given your config is correct and no log is written, that makes it very improbable that PinDMD.dll is loaded before VPM crashes. So you might need to hang out at the other place and try to get this resolved.

 

The web addresses are documentation about the format of the log config file.

[poposchmatzer]

Then VPinMAME is limited to 4 shades. To get 16 shades support for sam roms, let's say I want make the DMD authentic as possible, I have to create a .pal file with an editor?

 
The archive with the patch contains the *.pal file you need. It just doesn't say anything about it in the readme.txt file.
You will not get pretty looking DMD with only 4 shades available. To be honest, I find that adjusting it to something different than the standard orange looks better than trying to go color on some of these. But, if you have 16 shades available. Then its a whole different ballgame.

I like one color 16 shades best, too.
For this, I only need the .pal, right? And I only need pin2dmd to create one,right?
Cheers

Why ist the name of the programm forbidden?

Edited by poposchmatzer, 09 March 2017 - 02:32 PM.

[STAT]

No, Pin(2)DMD

Edited by STAT, 09 March 2017 - 03:21 PM.

[roar]

If you are getting tables crashing and are running in fullscreen don't forget to set your ddraw = 0 in the registry for your game/rom. You've just added a new rom that may not have that setting. I've stubbed my toe on this one a number of times.

Edited by roar, 09 March 2017 - 03:40 PM.

[poposchmatzer]

Thank's STAT

[Andypc]

Unfortunatly I have tried a couple of the things suggested today. i.e. ddraw = 0, Re-install VpinMame and run set-up. As soon as I check use external DMD (dll) it crashes when I open the table. My set-up and VpinMame work without any issues for hundreds of tables, but I can't get colour DMD's working at all

[Andypc]

I just followed these instructions. I installed C++ 2015 and re-booted, as it wasn't installed.

-----------

Install Instructions

1. Get the latest release, copy the content of the zip file to your hard drive, preferable in your PATH, and unblock the .exe file (right-click, properties, unblock).
2. Download and install the Visual C++ Redistributable for Visual Studio 2015.

Test

1. Open a command prompt ([Windows]+[R], cmd, [enter])
2. Type dmdext test [enter]

You should see a test image on your DMD as well as on a virtual DMD.

--------------------

 

This is what happened:-

---------------

Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Pinball>cd c:\temp

c:\temp>dmdext test

Unhandled Exception: System.TypeInitializationException: The type initializer fo
r 'DmdExt.DmdExt' threw an exception. ---> System.MissingMethodException: Method
 not found: 'Int32 System.Environment.get_CurrentManagedThreadId()'.
   at NLog.LogFactory.<GetCandidateConfigFileNames>d__a..ctor(Int32 <>1__state)
   at NLog.LogFactory.get_Configuration()
   at NLog.LogFactory.GetLogger(LoggerCacheKey cacheKey)
   at NLog.LogManager.GetCurrentClassLogger()
   at DmdExt.DmdExt..cctor()
   --- End of inner exception stack trace ---
   at DmdExt.DmdExt.Main(String[] args)

c:\temp>

--------------

 

 

Even the Test Fails

[sliderpoint]

@andypc You have VPM installed to the C:\Temp directory?  All the instructions say to put all the files in the same folder as your vpinmame.dll  (or the windows\syswow64 folder).

 

I did not know you could try the dmdext test thing.  I tried that and it did run.  So my issue is not the same as yours I suppose.

 

-Mike

[Andypc]

Just put all the files in my Vpinmame folder with my vpinmame.dll and ran the test again from the command promt. The result was exactly the same as above!

[Thalamus]

This isn't easy to debug. Would it be possible for you to put up a screenshot of you vpinmame folder ?