| ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 06605 | Gameplay | Critical (emulator) | Always | Jun 5, 2017, 22:05 | Jun 14, 2021, 20:44 |
| Tester | Tafoid | View Status | Public | Platform | MAME (Official Binary) |
| Assigned To | Resolution | Fixed | OS | Windows Vista/7/8 (64-bit) | |
| Status [?] | Resolved | Driver | |||
| Version | 0.186 | Fixed in Version | 0.233 | Build | 64-bit |
| Fixed in Git Commit | 83e21e9 | Github Pull Request # | |||
| Summary | 06605: gradius4: Crash during Test Mode Rom Check with -video d3d | ||||
| Description |
Rom 7K is the last one that checks OK, then an exception. -nodrc has no effect:----------------------------------------------------- |
||||
| Steps To Reproduce |
-mame64 gradius4 -Set Test Mode Dip to ON -mame64 gradius4 -Let test happen.. |
||||
| Additional Information | |||||
| Github Commit | |||||
| Flags | |||||
| Regression Version | |||||
| Affected Sets / Systems | gradius4 | ||||
|
Attached Files
|
 0000.png (417,707 bytes) Jun 7, 2017, 16:36 Uploaded by B2K24 | ||||
| 0002.png (3,515 bytes) Jun 7, 2017, 16:36 Uploaded by B2K24 | |||||
| sscope.png (488,971 bytes) Jan 8, 2020, 20:57 Uploaded by Firewave sscope
| |||||
| sscope2.png (489,838 bytes) Jan 8, 2020, 20:58 Uploaded by Firewave | |||||
 No.13888
B2K24 Senior Tester
Jun 7, 2017, 16:36
|
I can't exactly reproduce this as outlined unless I'm not understanding something. When the test is running, the graphics board and device checks all complete. It then informs me about a RTC CHECKSUM ERROR, PRESS TEST SWITCH TO CONTINUE. When I execute the MASK ROM CHECK from test menu, it seems to check the first two and then MAME crashes with nothing logged into command prompt window. |
|---|---|
 No.13889
Tafoid Administrator
Jun 7, 2017, 18:02
edited on: Jun 7, 2017, 18:07
|
Are you using -video opengl ? With that, I get the screens you show above. Default is d3d and with that I get the crash as I described. The MASK ROM issue with crash is already logged. 06322 |
|
No.13893
B2K24 Senior Tester
Jun 7, 2017, 21:43
edited on: Jun 7, 2017, 21:45
|
I originally had bgfx defaulted. It didn't occur to me to try different video modes. This can definitely be reproduced with -video auto or -video d3d I should've taken notice to d3d stuff in the stack trace output (my bad) Confirming.. |
 No.14603
Firewave Senior Tester
Jan 2, 2018, 19:34
|
I am not able to reproduce that crash with any -video mode on Linux. And on Windows it only happens with "-video d3d" - all other modes are fine. |
|
No.14631
Firewave Senior Tester
Jan 7, 2018, 00:29
|
Error #1: UNADDRESSABLE ACCESS: reading 0x00000004238f0688-0x00000004238f068c 4 byte(s) # 0 mame64.exe!texture_info::set_data [../../../../../src/osd/modules/render/drawd3d.cpp:2269] # 1 mame64.exe!texture_info::texture_info [../../../../../src/osd/modules/render/drawd3d.cpp:2106] # 2 mame64.exe!d3d_texture_manager::update_textures [s:/_Emulation/msys64/mingw64/include/c++/7.2.0/bits/unique_ptr.h:825] # 3 mame64.exe!renderer_d3d9::begin_frame [../../../../../src/osd/modules/render/drawd3d.cpp:662] # 4 mame64.exe!renderer_d3d9::draw [../../../../../src/osd/modules/render/drawd3d.cpp:235] # 5 mame64.exe!win_window_info::video_window_proc [../../../../../src/osd/windows/window.cpp:1393] # 6 mame64.exe!winwindow_video_window_proc_ui [../../../../../src/osd/windows/winmenu.cpp:23] # 7 USER32.dll!CallWindowProcW +0x4dc (0x00007ff932b4b85d <USER32.dll+0xb85d>) # 8 USER32.dll!CallWindowProcW +0x376 (0x00007ff932b4b6f7 <USER32.dll+0xb6f7>) # 9 USER32.dll!SendMessageW +0x34f (0x00007ff932b4ade0 <USER32.dll+0xade0>) #10 USER32.dll!SendMessageW +0xf7 (0x00007ff932b4ab88 <USER32.dll+0xab88>) #11 mame64.exe!win_window_info::update [../../../../../src/osd/windows/window.cpp:889] #12 mame64.exe!windows_osd_interface::update [../../../../../src/osd/windows/video.cpp:94] #13 mame64.exe!video_manager::frame_update [../../../../../src/emu/video.cpp:229] #14 mame64.exe!screen_device::vblank_begin [../../../../../src/emu/screen.cpp:1525] #15 mame64.exe!screen_device::device_timer [../../../../../src/emu/screen.cpp:998] #16 mame64.exe!device_scheduler::timeslice [../../../../../src/emu/device.h:520] #17 mame64.exe!running_machine::run [../../../../../src/emu/machine.cpp:350] #18 mame64.exe!mame_machine_manager::execute [../../../../../src/frontend/mame/mame.cpp:236] #19 mame64.exe!cli_frontend::start_execution [../../../../../src/frontend/mame/clifront.cpp:257] #20 mame64.exe!cli_frontend::execute [../../../../../src/frontend/mame/clifront.cpp:273] #21 mame64.exe!emulator_info::start_frontend [../../../../../src/frontend/mame/mame.cpp:336] #22 mame64.exe!main [../../../../../src/osd/windows/winmain.cpp:315] Note: @0:01:58.443 in thread 7292 Note: instruction: mov (%rdi) -> %ecx |
|
No.17333
Firewave Senior Tester
Jan 8, 2020, 20:56
edited on: Jan 8, 2020, 21:39
|
Testing with 0.217 I cannot reproduce this with either gradius4, nbapbp, sscope or sscope2. Also the Dip Switch is now called "Skip Post" and it needs to be disabled. I do see failures in the checks for the second board in sccope and sscope2 though. terabrst does completely go into the weeds during the check. |
 No.17337
Hydreigon Tester
Jan 9, 2020, 01:49
edited on: Jan 9, 2020, 03:20
|
I renamed it to "Skip Post" because the manual states that dip switch needs to be disabled (similar to Namco System 23). Silent Scope, Silent Scope 2 and (maybe) Hang Pilot crash regardless of video mode and drc enabled/disabled from my end. I'm using MAME 64bit on Windows 10. As for Hang Pilot, you have to comment out the init that patches the roms so it can boot in post normally. I personally think Hang Pilot shouldn't be marked as working because of relying on program rom patches (hence my suggestion to emulate the step lock but idk what drives those commands). |
|
No.18982
Osso Moderator
Jun 14, 2021, 20:44
|
Fixed by Ville Linde. |