New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MAME BGFX - metal (Mac API) crashes since MAME 0.177 ever since #1032

Closed
estefan3112 opened this Issue Jan 27, 2017 · 6 comments

Comments

Projects
None yet
2 participants
@estefan3112

estefan3112 commented Jan 27, 2017

Hi, I have been following the BGFX development in MAME since its introduction into the official builds, and it just rocks in MAME!

However, since version 0.177, the bgfx-metal shader crashes on every Mac I tried. In my blog for MAME on Macs, I have documented the regression here:
https://mameonmacs.blogspot.co.at/2016/09/mame-0177-first-impressions.html

The other bgfx shaders are not affected, so I have been constantly using bgfx-opengl without any troubles.

On Macs you should be able to reproduce the error with any game and any frontend, or just via the command line, e.g.
./mame64 -video bgfx -str 60 -noafs -bgfx_screen_chains crt-geom-deluxe -bgfx_backend metal -artcrop -noreadconfig -nosleep -nothrottle elevator
Comment: With the crt-geom-deluxe shader, the game runs in black screen, and when pressing Esc, MAME quits with "CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces."

./mame64 -video bgfx -str 60 -noafs -bgfx_screen_chains hlsl -bgfx_backend metal -artcrop -noreadconfig -nosleep -nothrottle elevator
Comment: With the HLSL shader, the game quits with Abort trap: 6

Please feel free to ask me for any additional information, unfortunately I have no talent for coding, but I would like to help wherever possible.

My blog on MAME in Macs with a lot of BGFX stuff: https://mameonmacs.blogspot.co.at

Many thanks, Stefan

@bkaradzic bkaradzic added the bug label Jan 27, 2017

@estefan3112

This comment has been minimized.

Show comment
Hide comment
@estefan3112

estefan3112 Aug 8, 2017

Hi, just to let you know that in r0ni's current MAME 0.188 build, the METAL backend works with me - http://sdlmame.lngn.net (considered as official Mac MAME build). However, r0ni compiles MAME under 10.9 with an updated LLVM installed through MacPorts. His make command is make PTR=1 TARGETOS=macosx TOOLS=1 NOWERRROR=1 -j5. Whereas the official compile instructions are just make -j5. I am under 10.12, but r0ni's compile still works for me. I will try to find out whether different compile instructions make the difference. Cheers.

estefan3112 commented Aug 8, 2017

Hi, just to let you know that in r0ni's current MAME 0.188 build, the METAL backend works with me - http://sdlmame.lngn.net (considered as official Mac MAME build). However, r0ni compiles MAME under 10.9 with an updated LLVM installed through MacPorts. His make command is make PTR=1 TARGETOS=macosx TOOLS=1 NOWERRROR=1 -j5. Whereas the official compile instructions are just make -j5. I am under 10.12, but r0ni's compile still works for me. I will try to find out whether different compile instructions make the difference. Cheers.

@estefan3112

This comment has been minimized.

Show comment
Hide comment
@estefan3112

estefan3112 Mar 2, 2018

Happy to report that the BGFX Metal backend now works in MAME 0.195, also if self-compiled. There seem to be other issues right now, such as a non-functioning hlsl chain, but in overall, it seems fair to close here.

estefan3112 commented Mar 2, 2018

Happy to report that the BGFX Metal backend now works in MAME 0.195, also if self-compiled. There seem to be other issues right now, such as a non-functioning hlsl chain, but in overall, it seems fair to close here.

@estefan3112 estefan3112 closed this Mar 2, 2018

@bkaradzic

This comment has been minimized.

Show comment
Hide comment
@bkaradzic

bkaradzic Mar 2, 2018

Owner

If you have issues like these in the future, the best would be to create simple repro inside bgfx examples, so that I can debug it. Something not working in MAME might be multiple things unrelated to bgfx, so simple repro inside bgfx examples would focus to just bgfx issue.

Owner

bkaradzic commented Mar 2, 2018

If you have issues like these in the future, the best would be to create simple repro inside bgfx examples, so that I can debug it. Something not working in MAME might be multiple things unrelated to bgfx, so simple repro inside bgfx examples would focus to just bgfx issue.

@estefan3112

This comment has been minimized.

Show comment
Hide comment
@estefan3112

estefan3112 Mar 2, 2018

Hmmm, I try to understand your suggestion with my limited knowledge :). Unfortunately I do not code. Should I just try out the examples on my machine and report back? Sorry but it seems to be beyond my capabilities, still eager to understand :-).

estefan3112 commented Mar 2, 2018

Hmmm, I try to understand your suggestion with my limited knowledge :). Unfortunately I do not code. Should I just try out the examples on my machine and report back? Sorry but it seems to be beyond my capabilities, still eager to understand :-).

@bkaradzic

This comment has been minimized.

Show comment
Hide comment
@bkaradzic

bkaradzic Mar 2, 2018

Owner

Examples are likely to work. You can report issue to MAME team, and they can then figure out what's wrong with bgfx and report it here.

Owner

bkaradzic commented Mar 2, 2018

Examples are likely to work. You can report issue to MAME team, and they can then figure out what's wrong with bgfx and report it here.

@estefan3112

This comment has been minimized.

Show comment
Hide comment
@estefan3112

estefan3112 Mar 3, 2018

Eager to help and to learn :-). Do you know whom to contact at MAME? When I reported this issue into mametesters, they just told me that I should contact you...

estefan3112 commented Mar 3, 2018

Eager to help and to learn :-). Do you know whom to contact at MAME? When I reported this issue into mametesters, they just told me that I should contact you...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment