Cyprian

Hi Steven, the latest beta works fine. Thanks Regards Cyprian

I see strange characters in TRACE.TXT. The app was compiled with VASM, maybe there is something wrong with label's format in .PRG file

Hi Steven, my clean GEM test app causes SteemDebug SSE 32bit to crash and close, and SteemDebug SSE 64bit version shows "System Error" - "System exception $C0000005 at $0000080E080E1008" It works ok under Steem64D3D and Steem32D3D. I can share the source code and binary but not publicly. Just let me know how to share it (email, PM forum, discord, etc). Thanks Regards Cyprian

great, thanks

Hi Steven, I wonder if TRACE.txt checkbox could be moved from Startup to the Debugger (e.g. to SSE menu)? To be honest, I forgot about this checkbox and in the new version of Steam (where this checkbox was unchecked) I was wondering why the trace file was not generated. My first thought was that something was not clicked correctly in the LOG or SSE menu, or Control Mask browser. Thanks Regards Cyprian

Hi Steven, would it be possible to separate "borders" settings for color and monochrome monitors? In case of color monitor, the border can be useful - there are some demos showing effects in overscan. But with SM124 the border is useless to me. So, every time I switch from color to mono or vice versa, I have to toggle this border option, which is a bit tedious. Thanks Regards Cyprian

Hi Steven, I completely forgot about that. Thanks a lot, it works fine for me.

Hi Steve, would it be possible to separate "borders" settings for color and monochrome monitors? In case of color monitor, the border can be useful - there are some demos showing effects in overscan. But with SM124 the border is useless to me. So, every time I switch from color to mono or vice versa, I have to toggle this border option, which is a bit tedious. Thanks Regards Cyprian