Viewing Issue Advanced Details
|ID||Category [?]||Severity [?]||Reproducibility||Date Submitted||Last Update|
|05173||Interface||Major||Always||Mar 23, 2013, 02:11||Mar 23, 2013, 18:08|
|Tester||sandheaver||View Status||Public||Platform||MAME (Self-compiled)|
|Assigned To||Resolution||Fixed||OS||Windows Vista/7 (64-bit)|
|Version||0.148u1||Fixed in Version||0.148u3||Build||64-bit|
|Fixed in Git Commit||Github Pull Request #|
|Summary||05173: burnin option not functioning|
|Description||The -burnin option does not produce a burnin image.|
|Steps To Reproduce||
Run mame with the -burnin option. At the end of emulation, snap/romname/burnin-0.png should appear.
Bug is identified by the generation of a 0-length file named snap/romname/burnin- at the end of emulation.
|Affected Sets / Systems|
|There are no relationship linked to this issue.|
Mar 23, 2013, 14:19
Actually, I think the could should output a "burnin-*TAG*.png" now, where *TAG* is the screen tag (now there are no more screen 0, screen 1 etc. so it makes not much sense to save burnin-0 etc.)
I've just fixed the code to output such a file correctly, but I'm not sure how the resulting png is expected to be used, so let me know if this bug can be closed or if there is anything else to be fixed...
Mar 23, 2013, 17:09
I'm actually not sure how to use the burnin image, either. I was going to generate one and work it out. (I imagine that if the burnin image exists it will be overlaid without intervention, but, again, I wanted to test it.)
I didn't know the screen IDs were changed... sorry about the error in the description.
Mar 23, 2013, 18:08
np. probably burnin-0 was indeed the output name when the option was added and you could not have been aware of the later change :)
Anyway, according to Tafoid, you can take the png given by MAME to create a custom artwork which overlays the png to your screen, so the MAME side is now fixed.
Thanks for reporting the problem.