Jump to content

Anyone know what this means


Robsonmeg46
 Share

Recommended Posts

3 hours ago, Pook said:

My layouts can are graphically intensive, so needs a bit more resources I'd assume. Nothing that I can control apart from making smaller layouts.

What about making v-tech layouts like you called mine back in the day rofl, I’ve had this error on ones I made and others of similar size. I think it’s just mfme having a hissy fit now and again

  • Like 2
Link to comment
Share on other sites

MFME does this occasionally as internally it's mainly written in the old school C way (unmanaged aka unsafe code).  Unless you are super careful when programming in this way, it's really easy to do stuff like 'trash memory' or 'corrupt pointers' etc, which results in these types of errors.

There's nothing that can be done to fix this I'm afraid. 

In normal use, ie. when simply playing layouts, it happens very rarely (less allocs, more battle-tested code) - compared to editing layouts (which involves more allocating/deallocating memory/pointers etc), so it's not much of an issue for end users playing layouts :)

Edited by johnparker007
  • Like 1

[ Arcade Simulator ] Pre-alpha installer: http://arcadesimulator.net  |  Known Issues: https://tinyurl.com/yz4uom2e  |  Donation info: https://tinyurl.com/yzvgl4xo
[ Community Drive ] The drive: http://tinyurl.com/yckze665
[ Fruit Machine Database ] Initial google sheets (WIP): https://tinyurl.com/2c5znxzz
[ Fruit Machine ROM  Archive ] The archive: https://tinyurl.com/3jhzbueb

[ MFME Launch ] Source code: https://github.com/johnparker007/MFMELaunch
[ Oasis ] Source code: https://github.com/johnparker007/Oasis
[ Sound ROM Editor ] Source code: https://github.com/johnparker007/SoundRomEditor

Link to comment
Share on other sites

 Share

×
×
  • Create New...