neil81992 Posted June 30, 2025 Posted June 30, 2025 Hi I'm trying to figure out why my external dmd image will randomly freeze. I wanted to check the dmddevice log - where should this be located? There is a text file in my vpinmame folder but it doesn't appear to be updating. Can anyone help? Thanks
Cliffy Posted June 30, 2025 Posted June 30, 2025 (edited) yes it should only be in vpinmame folder. The logging level is set in the DmdDevice.log.config. This is the minimum you should have in the rules section at the bottom; <rules> <logger name="*" minlevel="warn" writeTo="console" /> <logger name="*" minlevel="warn" writeTo="file" /> </rules> The other levels are Info and Trace Edited June 30, 2025 by Cliffy
outhere Posted June 30, 2025 Posted June 30, 2025 3 hours ago, neil81992 said: Hi I'm trying to figure out why my external dmd image will randomly freeze. I wanted to check the dmddevice log - where should this be located? There is a text file in my vpinmame folder but it doesn't appear to be updating. Can anyone help? Thanks By default the log for freezy will be in the visual pinball folder but you can change the default in the DmdDevice.log.config
neil81992 Posted June 30, 2025 Author Posted June 30, 2025 1 hour ago, outhere said: By default the log for freezy will be in the visual pinball folder but you can change the default in the DmdDevice.log.config Thanks - below is the contents of the dmddevice.log.config - what part details where the log will be updated and saved? <?xml version="1.0" encoding="utf-8" ?> <nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.nlog-project.org/schemas/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/nlog/NLog/wiki/Targets for possible targets. See https://github.com/nlog/NLog/wiki/Layout-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="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="warn" writeTo="console" /> <logger name="*" minlevel="warn" writeTo="file" /> </rules> </nlog>
neil81992 Posted June 30, 2025 Author Posted June 30, 2025 1 hour ago, Cliffy said: yes it should only be in vpinmame folder. The logging level is set in the DmdDevice.log.config. This is the minimum you should have in the rules section at the bottom; <rules> <logger name="*" minlevel="warn" writeTo="console" /> <logger name="*" minlevel="warn" writeTo="file" /> </rules> The other levels are Info and Trace Thanks Cliffy. My log is set to warn as you have advised. Should this generate a text log each time a table is loaded? I can't locate that info
Cliffy Posted June 30, 2025 Posted June 30, 2025 (edited) Well, as @outhere noted it depends on which dmddevice.dll's you're using so if using Lucky1's it will be in vpinmame, if Freezy's it will be in your vpinball, visual pinball or whatever your folder is named where the vpinballx.exe resides. You can edit the config file under "target" to point the log where you like. Example; <target xsi:type="File" name="file" fileName="E:\Vpinball\Vpinmame\DmdDevice.log" Now, I would try Trace instead of Warn and see what details show up in the log. If you are using dmdext.exe it also has it's own log and config EDIT: I just tried adding a path to the dmddevice.log in the config but it was ignored so scratch that. Use the log in the vpinball folder if that is the one being written to. You can see in file explorer by the modification date which one is being used. Edited June 30, 2025 by Cliffy update
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now