bicarus

did you try this?

plug in is not fully updated yet for epolis, you need to wait download latest spice2x beta. you also need to apply "force tdj" hex edit if you want TDJ.

[2023/10/25 01:18:07] W:SuperstepSound: Audio device is not available!!! Your ASIO4ALL does not seem to be working properly. Recommend uninstalling it & using FlexASIO instead, or just use WASAPI. Try different NVIDIA driver. [2023/10/25 00:21:43] W:signal: exception raised: EXCEPTION_ILLEGAL_INSTRUCTION It's crashing on vpermd instruction. Seems like you have a really old processor (AMD FX 8320), which not supported. did you apply "Unlock all songs" hex edit? post full log.txt file, because what you showed is not really an error, so the problem must be somewhere else.

Download spice2x and follow https://rentry.org/iidxdump

You used: -exec bm2dx.dll -url http://localhost:8083 -smartea -eamaint 0 -iidx -iidxdisablecams -modules modules -api 78 -apipass ***** You need to remove the following to get IO to work: -exec bm2dx.dll -iidx or, you can enable -io. If you're trying to enable TDJ, you have to set -iidxtdj AND enable the hex edit.

EPOLIS 2023101800 Hex edit for "Increase Game Volume" 0x89F135 : ff 90 98 00 00 00 -> 90 90 90 90 90 90 hint for the future: look for the routine that calls GainWithHardLimiter@BMSoundLib2017 and nop out the caller

OK, I think I figured out why TDJ crashes like this when selecting a mode in Epolis. W:signal: exception raised: EXCEPTION_ACCESS_VIOLATION I:signal: printing callstack I:stackwalker: 00000001802ECC74 (bm2dx): (unknown): (unknown) I:stackwalker: 00000001805019D7 (bm2dx): (unknown): (unknown) I:stackwalker: 00000001804D7E3A (bm2dx): (unknown): (unknown) I:stackwalker: 0000000180737CC2 (bm2dx): (unknown): (unknown) I:stackwalker: 0000000180736669 (bm2dx): (unknown): (unknown) I:stackwalker: 00000001807B230B (bm2dx): (unknown): dll_entry_main I:stackwalker: 00000001807AC2AB (bm2dx): (unknown): dll_entry_main I:stackwalker: 000000018077CD80 (bm2dx): (unknown): (unknown) I:stackwalker: 0000000180791ED8 (bm2dx): (unknown): (unknown) I:stackwalker: 00000001803F14BB (bm2dx): (unknown): (unknown) I:stackwalker: 0000000180792A4A (bm2dx): (unknown): dll_entry_main Solution: Edit iidx@asphyxia\pug\31pccommon.pug Delete the last line (tourism_booster), save Restart, and it should no longer crash.

Go into Test Menu, sound options and increase the volume from 20 to 30, it helps a little.

Seems like hex edit for "Increase Game Volume" has not been ported to epolis yet.

I see something similar, crash after selecting a mode. I think this is a bug in asphyxia plugin, because it doesn't happen on new cards, or when playing without a card. EDIT: this only happens to TDJ mode. LDJ is fine. What does it fix? Seems like you just applied a bunch of hex edits.

Are you talking about EPOLIS? There is always a lot of confusion about how TDJ or subscreen works and a lot of bad information, but I can confirm that it works with the latest spice2x as intended. See screenshot attached Try the following: * Make sure you use the latest beta spice2x. * Do not check any hex edits or spice options to disable the sub screen, do not enable single monitor mode * For Epolis, must enable hex edit "Force TDJ mode" I can confirm that both the subscreen overlay works, and also a physical second monitor. For subscreen overlay: press Page Up to show subscreen window on main screen, and use your mouse and click on it. Only one monitor needed. For physical second screen: you can't use a mouse, you have to hook up a touch screen (or just bring up the subscreen overlay on the primary screen and click with mouse) Using a tablet with SpiceCompanion is still possible, but it's really not necessary, but a lot of people fall into the trap thinking that it's the only option...

download spice2x follow https://rentry.org/iidxdump enable -ea, or follow instructions to set up asphyxia try again

depends on your dac, not your headphones... especially if it supports ASIO. You should just try it.,.,.

Pretty sure old bemanitools had card insert key hardcoded to + key on numpad (or was it - key?). For wide screen you have to force it from your GPU.

Update to latest spice2x instead of spicetools and it will work.

I used google translate but if you want omni, you need to have omnimix. It sounds like you don't have omnimix installed. This is not a great place to ask about popnhax..

Use option in spicecfg, "Disable Touch Card Insert" (-touchnocard)

You downloaded the wrong file. WRONG: popnhax-main.zip (this is the source code for code developers) WRONG: "Enter the popnhax folder in the dist folder within the popnhax-main folder and rename the ifs_hook.dll file to popnhax.dll file." don't do this. I don't even know who told you this... RIGHT: popnhax_v1.9.zip from https://github.com/CrazyRedMachine/popnhax/releases/tag/v1.9 Comes with everything you need. Try again. No need to rename any files, just extract. Don't rename ifs_hook.dll, just copy as is.

popnhax.xml file goes next to popnhax.dll, not prop. also, update to latest spice2x.

When you launch, you get a CMD window showing spice logs, you will also be able to find popnhax logs in there, indicating what failed. popnhax doesn't output to spice's log.txt, so you have to copy paste from the CMD window.

How to use ASIO hook with spice: 1. DO NOT use patcher shared wasapi. Instead, use default (exclusive wasapi) 2. Use spice2x 3. Spice Audio Hook Backend to asio (-audiobackend asio) 4. Set Spice Audio Hook ASIO Driver ID (-asiodriver id 0) - if 0 doesn't work change to different number How it works: Game --> Exclusive WASAPI --> Spice --> ASIO --> Speakers

[2023/10/02 09:27:38] M:audio::wasapi: WrappedIAudioClient::IsFormatSupported [2023/10/02 09:27:38] W:audio::wasapi: WrappedIAudioClient::IsFormatSupported failed, hr=0x88890008 [2023/10/02 09:27:38] I:avs-ea3: soft id code: LDJ:J:A:X:2023090500 [2023/10/02 09:27:38] I:avs-ea3: calling ea3 boot [2023/10/02 09:27:40] W:SuperstepSound: Audio device is not available!!! Audio error. Read the guide again about what to do with your audio device.

That's how it is in Japan region.

why are you running with -9on12? also, you're on 2021121400... you might want to try newer data, season 1 data has lots of graphics issues

post log.