 No.23371
Robbbert Moderator
3 days ago
|
Other recent requests for mods to the UI have been closed quite firmly. Lets see how this one goes. |
|---|---|
 No.23372
Augusto Tester
2 days ago
|
One of the worst sins is someone trying to say orders and enjoy enslaving and stealing talent from other peoples. I didn't expect to see someone doing this in the direction of my friends mamedevs. I had created another topic and this one because of two problems: - mamedevs use overclocking settings for debugging and don't like to see users using it for gameplay. - this topic ... text editors change the text formatting of mame.ini so can break mame.ini and MAME can't load any game or system. Here is Linux and that problem happen a lot. These are really two details that need attention. My posts are reporting bugs or saying about idea to be read by mamedevs, but I'm not a programmer and so has chance I'm saying something that's not coherent with MAME. MAME has details that make different compared to other emulators. MAME not is a toy that can be changed here and there as other emulators do, being because I had done a previous topic about overclocking settings. However it's mamedev decision to make MAME better and easier to configure, but may have other priorities. |
 No.23374
hap Developer
2 days ago
|
Changing bgfx_screen_chains in mame.ini works fine for me*. How does your text editor modify mame.ini causing MAME failing to load it? I tried to break it here by converting to UTF16 for example, and to my surprise MAME still loaded mame.ini fine. ~~~~~~~~~~~~~~~~~~~~~ *: although changing it to "none" causes MAME to crash randomly for me, but that's just bgfx being bgfx and having bugs. FWIW here is 0.277 symbols: ----------------------------------------------------- Exception at EIP=00007ff633d4410c (bgfx_chain_entry::setup_view(texture_manager&, int, unsigned short, unsigned short, int, unsigned short&, unsigned short&) const+0x03dc): ACCESS VIOLATION While attempting to read memory at 0000000000000000 ----------------------------------------------------- RAX=0000000000000000 RBX=000001e428ba64f0 RCX=0000000000000000 RDX=000001ae8796d0c0 RSI=00000035a1308b80 RDI=00000035a1308ba0 RBP=00000035a1308bb0 RSP=00000035a1308b00 R8=0000000000000006 R9=00000035a1308ba0 R10=0000000000000006 R11=000000000000000f R12=000001e41673c930 R13=0000000000000000 R14=0000000000000000 R15=00000035a1308b70 ----------------------------------------------------- Stack crawl: 00000035a1308c40: 00007ff633d4410c (luaopen_lfs+0xae915c) 00000035a1308d60: 00007ff633d4452c (luaopen_lfs+0xae957c) 00000035a1308e70: 00007ff633bbc4f8 (luaopen_lfs+0x961548) 00000035a1308ef0: 00007ff63374e4f2 (luaopen_lfs+0x4f3542) 00000035a1308f90: 00007ff63374e679 (luaopen_lfs+0x4f36c9) 00000035a13090e0: 00007ff632581fce (renderer_bgfx::draw(int)+0x041e) 00000035a1309140: 00007ff62e60b8a3 (win_window_info::draw_video_contents(HDC__*, bool)+0x0063) 00000035a1309250: 00007ff62e610086 (win_window_info::video_window_proc(HWND__*, unsigned int, unsigned long long, long long)+0x0736) 00000035a1309280: 00007ff62e610369 (winwindow_video_window_proc_ui(HWND__*, unsigned int, unsigned long long, long long)+0x0009) 00000035a1309410: 00007ffc9389ef5c (CallWindowProcW+0x060c) 00000035a13094b0: 00007ffc9389dfbb (SendMessageW+0x092b) 00000035a1309510: 00007ffc9389d814 (SendMessageW+0x0184) 00000035a1309560: 00007ff62e60baf1 (win_window_info::update()+0x01e1) 00000035a13095a0: 00007ff62e619bea (windows_osd_interface::update(bool)+0x003a) 00000035a1309630: 00007ff62e6dcddb (video_manager::frame_update(bool)+0x00ab) 00000035a13096a0: 00007ff62b12fdf3 (screen_device::vblank_begin(int)+0x0233) 00000035a1309710: 00007ff62b156f6b (device_scheduler::timeslice()+0x014b) 00000035a1309860: 00007ff62b15410f (running_machine::run(bool)+0x01bf) 00000035a130ee70: 00007ff62e5f0bfb (mame_machine_manager::execute()+0x020b) 00000035a130f250: 00007ff6324de5b9 (cli_frontend::start_execution(mame_machine_manager*, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&)+0x03c9) 00000035a130f500: 00007ff6324deb6d (cli_frontend::execute(std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&)+0x004d) 00000035a130f560: 00007ff62e5eb2a9 (emulator_info::start_frontend(emu_options&, osd_interface&, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&)+0x0029) 00000035a130f930: 00007ff6341f7eac (luaopen_lfs+0xf9cefc) 00000035a130fa00: 00007ff626ee13b1 (__tmainCRTStartup+0x0231) 00000035a130fa30: 00007ff626ee14e6 (mainCRTStartup+0x0016) 00000035a130fa60: 00007ffc935d7374 (BaseThreadInitThunk+0x0014) 00000035a130fae0: 00007ffc94fbcc91 (RtlUserThreadStart+0x0021) Here is gdb with current build: Thread 1 received signal SIGSEGV, Segmentation fault. 0x00007ff747b3f296 in bgfx_chain_entry::setup_view(texture_manager&, int, unsigned short, unsigned short, int, unsigned short&, unsigned short&) const () (gdb) bt #0 0x00007ff747b3f296 in bgfx_chain_entry::setup_view(texture_manager&, int, unsigned short, unsigned short, int, unsigned short&, unsigned short&) const () #1 0x00007ff747b3f69c in bgfx_chain_entry::submit(int, chain_manager::screen_prim&, texture_manager&, unsigned short, unsigned short, unsigned short, float, float, float, float, unsigned int, bool, int) () #2 0x00007ff7479b1d1f in bgfx_chain::process(chain_manager::screen_prim&, int, int, texture_manager&, osd_window&) () #3 0x00007ff7474c1dd2 in chain_manager::process_screen_quad(unsigned int, unsigned int, chain_manager::screen_prim&, osd_window&) () #4 0x00007ff7474c1f62 in chain_manager::process_screen_chains(unsigned int, osd_window&) () #5 0x00007ff746258af5 in renderer_bgfx::draw(int) () #6 0x00007ff7421052fc in win_window_info::draw_video_contents(HDC__*, bool) () #7 0x00007ff742109ab6 in win_window_info::video_window_proc(HWND__*, unsigned int, unsigned long long, long long) () #8 0x00007ffc9389ef5c in USER32!CallWindowProcW () from C:\WINDOWS\System32\user32.dll #9 0x00007ffc9389dfbb in USER32!SendMessageW () from C:\WINDOWS\System32\user32.dll #10 0x00007ffc9389d814 in USER32!SendMessageW () from C:\WINDOWS\System32\user32.dll Backtrace stopped: previous frame inner to this frame (corrupt stack?) |
 No.23375
cuavas Administrator
2 days ago
|
This is one of those things that’s rather difficult to do given how MAME works. (Yeah, the whole options system has major issues, but that’s another story.) But that aside, MAME definitely won’t refuse to run games just because the amount of space between option names and values is wrong. I can’t believe a text editor would corrupt the file in a way that MAME doesn’t load at all. |
|
No.23376
Augusto Tester
2 days ago
|
@hap "although changing it to "none" causes MAME to crash randomly for me, but that's just bgfx being bgfx and having bugs" Here happen randomly that problem when changing to "none". Perhaps is issue in bgfx and not anything related in editing mame.ini ? @cuavas "I can’t believe a text editor would corrupt the file in a way that MAME doesn’t load at all." Here strangely when using Kate to edit mame.ini exactly then trying load MAME happen that problem and I need edit the mame.ini removing all in front of "bgfx_screen_chains" and then start MAME GUI and using the option "Save Settings" and MAME will load games and system normally. Now I had edited the mame.ini using Kate and MAME load correctly. That strange behavior is random ... I had used UTF-8 being bgfx_screen_chains none mame.ini has several number of options, but few need in GUI because for example in MAME current version "bgfx_backend" has issues if selecting vulkan so users changing it will create much issues. In any way changing "bgfx_screen_chains" in GUI is better than in mame.ini. |
|
No.23378
Augusto Tester
1 day ago
edited on: 4 hours ago
|
If mame.ini is edited bgfx_screen_chains none and then start MAME shinobi the game load correctly. If in next loading shinobi was selected screen effect crt-geom that bgfx shader will work in current game loaded, but in next start MAME can't load shinobi and crash with message "Segmentation fault". Need delete shinobi.cfg. I had created this topic as if the error was related text editor breaking mame.ini, but I see it's related with another problem. That bug are happening in MAME recent versions. Anyway would be good to change "bgfx_screen_chains" settings using GUI. Need create another bug report. |