bicarus

I would recommend starting clean from scratch because i think you have messed up some update files along the way for example: [2023/06/05 18:20:01] I:avs-ea3: overwriting ext 2021091500 with 2023040400 from C:\Users\junne\Desktop\LDJ-003-2022101900 (V-M's)\contents\prop\bootstrap.xml this isn't common, 20210915 is CastHour. -exec bm2dx.dll - remove, not needed -url http://localhost:8083/ - needed for asphyxia -card0 ***** - needed for asphyxia -iidx - not needed -iidxdisablecams - OK -iidxtdj OK -modules modules OK -e C:\Users\junne\Desktop\LDJ-003-2022101900 (V-M's)\contents\prop\ea3-config.xml - not needed -a C:\Users\junne\Desktop\LDJ-003-2022101900 (V-M's)\contents\prop\app-config.xml - not needed -v C:\Users\junne\Desktop\LDJ-003-2022101900 (V-M's)\contents\prop\avs-config.xml - not needed -b C:\Users\junne\Desktop\LDJ-003-2022101900 (V-M's)\contents\prop\bootstrap.xml - not needed -api 1337 -apipass ***** - only needed if you need SpiceCompanion -io - not needed -audiobackend asio - you have RealTek ASIO and that often doesn't work with IIDX, recommend removing this option and just use wasapi -loglevel misc

[2023/06/05 16:11:27] I:avs-core: log level: fatal try setting Log Level (-loglevel) option to "misc" and share log again, becuase you have it set to "fatal" it may hide some problems

ok, you say "freezes and crashes" but i don't see anything in the log, so it sounds like it's not actually a crash can you perhaps screen shot (or video) what you are seeing, maybe there is an error message somewhere. remember that you can change the game language to English instead of Japanese so you can read the message.

are you using the latest asphyxia plugin? also i have no idea why you are manually specifying full paths to XML like that... that's a weird thing to do. in fact you don't need like 80% of the options you are specifying

there is an option in spicecfg (Disable Touch Card Input / -touchnocard)

[2023/06/05 00:52:42] I:graphics::d3d9: D3D9Ex fullscreen display mode for adapter 0: Width: 1920, Height: 1080, RefreshRate: 60, Format: D3DFMT_X8R8G8B8, ScanLineOrdering: 1 The game failed to launch at 1080p@120hz so you probably get a monitor error. Usually solved by setting GPU resolution scaling in NVIDIA control panel or similar [----/--/-- --:--:--] W:mounttab: boot(/dev/nvram2,/dev/nvram) mount error(80070011) you also have nvram mount error, see guide for how to fix https://docs.google.com/document/d/1SFfRb9nQK-riCdKChFprocVr97TqUxYra63wSK2fplo/edit#heading=h.kq3q8goqednp

It's normal.

You have: W:mounttab: boot(/dev/nvram2,/dev/nvram) mount error(80070011) Follow the guide again and see the section about the error above on how to fix, and try again

follow guide first - https://docs.google.com/document/d/1SFfRb9nQK-riCdKChFprocVr97TqUxYra63wSK2fplo/edit?usp=drivesdk [2023/05/19 20:50:12] M:audio::wasapi: WrappedIAudioClient::Stop [2023/05/19 20:50:12] M:audio::wasapi: WrappedIAudioClient::Reset [2023/05/19 20:50:12] M:audio::wasapi: WrappedIAudioClient::Stop [2023/05/19 20:50:12] M:audio::wasapi: WrappedIAudioClient::Reset [2023/05/19 20:50:12] M:imgui_impl_spice: shutdown Seems like the game is shutting down by itself (and then crashing), usually this is bad server configuration, or graphics issue (game window is closing by itself) Using latest Asphyxia plugin? can you remove -smartea and -eamaint? Can you try windowed mode?

[2023/05/15 16:25:25] W:signal: exception raised: EXCEPTION_ILLEGAL_INSTRUCTION [2023/05/15 16:25:25] I:signal: printing callstack [2023/05/15 09:25:27] M:ea3-pos: ea3_report_posev: "/coin/reset", 1 [2023/05/15 09:25:27] M:ea3-pos: ea3_posev_show_debug: slot[0]: coin 0, service 0, credit 0(0+0), from_coin 0, to_credit 0, player 0 [2023/05/15 09:25:27] M:ea3-pos: ea3_posev_show_debug: slot[1]: coin 0, service 0, credit 0(0+0), from_coin 1, to_credit 1, player 1 [2023/05/15 16:25:26] I:stackwalker: 0000000180205F29 (bm2dx): (unknown): (unknown) seems like another illegal instruction error, I think it's because your processor does not support SSE4.1 (not just SSE4.2), I don't think there is any way to fix this to run on your 15 year old PC...sorry

if you are using asphyxia, turn off -ea, and only use -url

seems like network error, are you using latest asphyxia plugin from this thread? [2023/05/14 22:04:39] M:avs-core: ignoring folder creation for '/dev/nvram': unsupported fs type 1. Download spice2x https://spice2x.github.io/ 2. Follow guide https://docs.google.com/document/d/1SFfRb9nQK-riCdKChFprocVr97TqUxYra63wSK2fplo 3. edit avs-config.xml following guide

looking at the disassembled code that crashed, it seems to be crashing when it tries to connect to network (kac_yosen), so most likely an issue with asphyxia plugin?

because you have a really old processor, you have to use SSE4.2 patch, and when you do that, it's been known that wasapi will never work, it will not make sound. i'm sorry, but i think my instructions are clear, but you keep doing different things... you NEED to set -iidxsounddevice asio, not wasapi, and then -iidxasio to FlexASIO or ASIO4ALL. No other option will work for you, becuase your processor is from 2005-2008. you should keep audio to 44.1khz and enable exclusive mode. if you did this and still get no sound, then your asio4all or flexasio setting is wrong, and i can't help with that why don't you try first with ONLY the sse4.2 patch enabled, and not mess with other things? post the whole log.txt file, "M:" means it's not an error, just a misc message.

1. use turksigara to check SSE 4.2 patch 2. set -iidxsounddevice to asio 3. set iidxasio to FlexASIO 4. Follow https://github.com/dechamps/FlexASIO/blob/master/CONFIGURATION.md If you can't figure out FlexASIO, then just use ASIO4ALL instead.

full log would be better, but usually, crash in 18023dbd6 means audio failed to initialize, make sure you follow the guide & use exclusive audio, or if using shared mode hex edit, set audio device to 44.1khz https://docs.google.com/document/d/1SFfRb9nQK-riCdKChFprocVr97TqUxYra63wSK2fplo/edit https://www.emuline.org/topic/2401-arcade-pc-beatmania-iidx-28-bistrover-bemani/?do=findComment&comment=145505

it stopped working because, as I noted previously, one of the patches turned on Valkyrie Cabinet mode, and Valkyrie Cabinet does not have number pad, only touch screen. You can follow instructions here to disable it back - Or, you can download spice2x, keep valkyrie mode, and use the sub screen overlay and use your mouse (https://spice2x.github.io/) (old spicetools on github does not work properly with Exceed Gear Valkyrie mode) Or, you can keep Valkyrie mode, but enable hex edits to enable KFC I/O, which will allow numpad again.

IIDX requires SSE 4.2. There is a hex edit to patch out the SSE 4.2 instructions, but it causes WASAPI audio to crash (this is noted on mon's Bemani Patcher as a warning, but it is not present on Turkish patcher. This means you HAVE to use ASIO with the game and skip wasapi entirely. To do this, set -iidxsounddevice to asio, and -iidxasio to ASIO4ALL. Your 3rd attempt (log.txt3) was close, but you didn't specify -iidxasio. by the way, FlexASIO might work significantly better than ASIO4ALL with IIDX, many more options and better compatibility. Even then, it still might not work. Like I said, Casthour and RESIDENT are known to not work well with old processors without SSE 4.2.

Advanced > I/O Modules > Enable DEVICE Module should be OFF

game can connect to asphyxia, but if you get networt error, you probably have bad asphyxia plugin? get iidx-asphyxia-v1.4.3_a3.zip and try again? also you have -device option which is not needed.

[2023/05/11 15:24:19] M:audio::wasapi: WrappedIAudioClient::IsFormatSupported [2023/05/11 15:24:19] W:audio::wasapi: WrappedIAudioClient::IsFormatSupported failed, hr=0x8889000e [2023/05/11 14:24:32] W:SuperstepSound: Audio device is not available!!! Audio issue, if you set the game to use exclusive audio, then ensure your audio device can support exclusive mode @ 44.1khz. If you used shared mode hex edit, then make sure you set your audio device to 44.1khz. did you enable local server, or asphyxia? post log.txt?

[2023/05/11 00:04:51] M:graphics::d3d9: IDirect3D9::CreateDevice hook hit (0, 1, 0x4d0512, D3DCREATE_MULTITHREADED | D3DCREATE_MIXED_VERTEXPROCESSING, 0x10a55a50, 0x10a55a88) [2023/05/11 00:04:51] I:graphics::d3d9: D3D9 presentation parameters for adapter 0: BackBufferWidth: 768, BackBufferHeight: 1360, Format: D3DFMT_A8R8G8B8, BackBufferCount: 1, MultiSampleType: 0, MultiSampleQuality: 0, SwapEffect: 1, Windowed: 0, EnableAutoDepthStencil: 1, AutoDepthStencilFormat: D3DFMT_D24S8, Flags: 0, FullScreen_RefreshRateInHz: 0, PresentationInterval: D3DPRESENT_INTERVAL_ONE [2023/05/11 00:04:52] I:graphics::d3d9: IDirect3D9::CreateDevice failed, hr=0x8876086c [2023/05/11 00:04:52] M:graphics::d3d9: IDirect3D9::CreateDevice hook hit (0, 1, 0x4d0512, D3DCREATE_MULTITHREADED | D3DCREATE_SOFTWARE_VERTEXPROCESSING, 0x10a55a50, 0x10a55a88) [2023/05/11 00:04:52] I:graphics::d3d9: D3D9 presentation parameters for adapter 0: BackBufferWidth: 768, BackBufferHeight: 1360, Format: D3DFMT_A8R8G8B8, BackBufferCount: 1, MultiSampleType: 0, MultiSampleQuality: 0, SwapEffect: 1, Windowed: 0, EnableAutoDepthStencil: 1, AutoDepthStencilFormat: D3DFMT_D24S8, Flags: 0, FullScreen_RefreshRateInHz: 0, PresentationInterval: D3DPRESENT_INTERVAL_ONE [2023/05/11 00:04:52] I:graphics::d3d9: IDirect3D9::CreateDevice failed, hr=0x8876086c [2023/05/11 00:04:52] M:graphics::d3d9: IDirect3D9::CreateDevice hook hit (0, 2, 0x4d0512, D3DCREATE_MULTITHREADED | D3DCREATE_HARDWARE_VERTEXPROCESSING, 0x10a55a50, 0x10a55a88) [2023/05/11 00:04:52] I:graphics::d3d9: D3D9 presentation parameters for adapter 0: BackBufferWidth: 768, BackBufferHeight: 1360, Format: D3DFMT_A8R8G8B8, BackBufferCount: 1, MultiSampleType: 0, MultiSampleQuality: 0, SwapEffect: 1, Windowed: 0, EnableAutoDepthStencil: 1, AutoDepthStencilFormat: D3DFMT_D24S8, Flags: 0, FullScreen_RefreshRateInHz: 0, PresentationInterval: D3DPRESENT_INTERVAL_ONE [2023/05/11 00:04:52] I:graphics::d3d9: IDirect3D9::CreateDevice failed, hr=0x8876086a game tried to create a window but failed. I know you have -adjustorientation but it doesn't work all the time, from my experience. You should rotate screen orientation to portrait in Windows, and make sure your monitor can support 1366x768.

do the hex edit (patches) and also use -graphics-force-refresh in spice to make it launch at desired refresh rate you should never disable vsync, it is required for the game to run properly honestly though, anything other than 60hz / 120hz you're going to have bad time (overlapping sprites, animations at wrong speed, etc), there is a difference between running it and having it playable. I would stick to 120Hz. This does mean that if you want to play windowed, you have to set the Windows desktop refresh rate to 120hz before launching the game. valkyrie mode doesn't work properly in windowed mode.

if you disable valkyre mode then the game is expected to run at 60FPS which might seem choppy, you need to enable hex edits to make it run at different framerate.

that's weird, couple things to try try deleting dev/nvram folder make sure all the game files are not marked "read only" in windows make sure you're not seeding torrent from game folder remove -iidxbio2fw option (this is for real arcade cabs only) - usually this results in USB I/O error not a crash, but worth a try anyway