bicarus

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

[----/--/-- --:--:--] W:mounttab: boot(/dev/nvram2,/dev/nvram) mount error(80070011) follow guide and modify avs-config.xml

were you running valkyrie mode before? as I posted before, one of the patches contain a change to XML file that turns on valk mode, and people might not want that also try running without asphyxia, and just -ea instead to see if that helps (if it's a server issue) would recommend post the full log.txt to see what's going on

spice.exe spicecfg.exe spice64.exe should be inside contents folder

you're not supposed to turn off vsync, you need it on... sounds like your game is launching at 60Hz...need to make sure the game launches at correct refresh rate

when you start a song, it shows you a preview of where the first note will fall by default, it only previews it for easy songs (level 5 I think?) if you enable it, then it enables it for all difficulties usually this is a setting changed on webui, but you can do this using hex edits too

if you are using shared wasapi patches, it has high latency, so better to use exclusive mode wasapi if you are using realtek audio drivers, uninstall it, and use windows default drivers instead if audio effects are on, disable all of them https://www.emuline.org/topic/1915-arcade-pc-sdvx-vivid-wave/page/67/#comment-145982

post log.txt please try wasapi first and then post log (asio is harder to get right)

[2023/05/05 16:43:01] I:avs-ea3: soft id code: KFC:J:G:A:2022071200 The "G" means you are running valkyrie mode, and windowed mode doesn't work for valkyrie. Seems like KFC-2021051800-2022071200 update contains a new ea3-config.xml and would have overwritten what you had before updating edit prop\ea3-config.xml and change <dest __type="str">G</dest> to <dest __type="str">F</dest> (and then apply hex edits if you want 120fps or anything else)

you can try -monitor option in spice are you running valk mode? maybe post log?

What is the resolution of the monitor? The game window is 1080x1920, so your monitor must be at least 1920 pixels tall. If not, you can use the Window Size option and make it smaller. another thing - sdvx tends to work better with -9on12 option (often fixes white screen / black screen issues)

It's not necessary to modify ea3-config.xml and change the<services> and <services_localstrap__type="str"> tags (step #5). Step 12 is sufficient (set the service URL in spicecfg) This applies to all spicetools. For btools, it's still needed (since you don't have any way to change the service URL in btools) It doesn't hurt to change it, but because the XML file is encoded in SHIFT-JIS, if you open it up in things like notepad, you can accidentally corrupt the file and make it fail to load.