Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
CarnyPriest

SAMBuild3.2 beta thread

Recommended Posts

I am having a major issue with Vpinmame. I am using 10.5 Final / latest 10.6 beta and the latest 3.2 beta/Sambuild r4658 although this has been an issue since Vpinmame3.1. I am also using freeze 1.7.1. Table starts fine with good frame rate an no issues. Come back an hour later and it's stutter city!!!!! There is a serious memory or timing issue that gets worse the longer a table is loaded!!
 
Everything is installed correctly. PC Spec is not an issue and getting 200+fps when I start the table. I can start a table and it plays absolutely perfect. Come back an hour later as it's awful. Not an overheating issue. If I close VPX and restart it plays perfect again. This is serious memory leak or timing issue that has been introduced since Vpinmame 3.1. I think it is only happening with VNI colour roms.
 
If I go back to an earlier Vpinmame the problem goes away, so definitely a code issue.
 
Any help would be appreciated

Share this post


Link to post
Share on other sites

The issue was the log file. This solved my issue, Thanks to Terry for the solution.

If you have a “DmdDevice.log.config” file, you need to edit that file and make sure that if the <rules> section looks like this:

<rules>
< logger name=”” minlevel=”Trace” writeTo=”console” />
< logger name=”” minlevel=”Trace” writeTo=”file” />
< /rules>

…it needs to be changed to:

<rules>
< logger name=”” minlevel=”info” writeTo=”console” />
< logger name=”” minlevel=”info” writeTo=”file” />
< /rules>

Same with the “dmdextlog.config”. The <rules> section should look like:

<rules>
< logger name=”*” minlevel=””info” writeTo=”console” />
< /rules>

This is to disable logging for when colouring is being used. Apparently it can cause performance issues for some people. It’s only needed for those who are colour modding DMDs and are troubleshooting.

Does this need to be reported to Freezy?

Share this post


Link to post
Share on other sites
10 hours ago, Andypc said:

The issue was the log file. This solved my issue, Thanks to Terry for the solution.

If you have a “DmdDevice.log.config” file, you need to edit that file and make sure that if the <rules> section looks like this:

<rules>
< logger name=”” minlevel=”Trace” writeTo=”console” />
< logger name=”” minlevel=”Trace” writeTo=”file” />
< /rules>

…it needs to be changed to:

<rules>
< logger name=”” minlevel=”info” writeTo=”console” />
< logger name=”” minlevel=”info” writeTo=”file” />
< /rules>

Same with the “dmdextlog.config”. The <rules> section should look like:

<rules>
< logger name=”*” minlevel=””info” writeTo=”console” />
< /rules>

This is to disable logging for when colouring is being used. Apparently it can cause performance issues for some people. It’s only needed for those who are colour modding DMDs and are troubleshooting.

Does this need to be reported to Freezy?

 

I informed about this way back...but I think he should know that its still causing issues, and the default log.config files that come with dmdext should be set to "info" to avoid this....since 98% of people don't need it set to anything else.

Share this post


Link to post
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now

×