bicarus

i can guarantee you that enabling bemanitools 5 api will not affect your performance in any way lol

[2023/12/17 04:05:01] W:BM2D: CreateLayer() 指定したレイヤーは存在しません page_megamix_stagemain [2023/12/17 04:05:01] W:signal: exception raised: EXCEPTION_ACCESS_VIOLATION [2023/12/17 04:05:01] I:signal: printing callstack [2023/12/17 04:05:01] I:stackwalker: 000000018044FE13 (soundvoltex): (unknown): dll_entry_main [2023/12/17 04:05:01] I:stackwalker: 000000018046620C (soundvoltex): (unknown): dll_entry_main Game tried to load a graphics file (page_megamix_stagemain) but failed to find the file. Almost certainly, you skipped an update, so now you are missing files. hint: it's probably 2023091200, or 2023102400.

It's like that for everyone, regardless of CPU,GPU, even bemanitools/spicetools, just seems to be poorly optimized live2d. On NVIDIA, ~100FPS. On AMD with 9on12, way lower FPS than that.

sounds about right, i was surprised that early epolis data supported wasapi at all, as no real cabs use them now, i guess it was just left over code from resident and now they decided to remove it

yes you put the game directory path

What did you enter into "Exceed Gear Data Directory" in the webui? Because it should NOT be the directory for your asphyxia plugin. It should be directory path of your game.

did you get the latest plugin from https://github.com/22vv0/asphyxia_plugins/releases?

Yes but that's server side. Most people don't want to edit any scripts, they use monkey brain to drag and drop files to a web-based patcher and expect things to work.

Oh yeah, I forgot about all these server side things. Good catch. Surely, someone can figure out a hex edit to patch those out in client side, as the plugins don't have a toggle for these?

Try slightly older version https://github.com/spice2x/spice2x.github.io/releases/download/23-10-30/spice2x-23-10-30.zip This is happening because you don't have an NVIDIA GPU, yet you have nvapi64.dll on your system, so it crashes when the game tries to load it.

Try spice2x and post the log.txt. Original spicetools isn't designed for Valkyrie Model, so it requires a bunch of hacks to make it work. At the very minimum you need the KFC I/O hack, which is broken in the patcher. That is probably why it crashed with I/O error in spicetools. Spice2x can do UFC I/O better. There are few problems. 1.Like the other user said, you might want to try G spec instead of F. 2.Your spice2x version is very old. You should update. It will provide more information in the log about what resolution is attempted when launching the game. 3. You are forcing into 120hz in the log. I assume you meant to put 144. 4. Your log says "Main display not supported TARGET FRAMERATE." which means your monitor might not support the correct resolution. You may want to go to your GPU settings (like NVIDIA control panel) and enable GPU resolution scaling first. I should also note, I'm unsure if the patcher has the correct patches for 144hz. Maybe you should just leave it at default first and use G spec, which will boot into 120Hz automatically. It's not really recommended that you use custom refresh rates, because some animations will not play correctly, and menu sound effects won't line up.

You forgot to check off "force note target". You may also need to use the force refresh rate option in spice. Also, I'm pretty sure the Force BIO2 patch is broken on that website, your game may crash if you use it. You need to keep vsync on, instead of capping the max frame rate, otherwise your game will be out of sync.

Most likely you have a duplicate file, one in D:\sdvx\sdvx6\soundvoltex.dll, and also in D:\sdvx\sdvx6\modules\soundvoltex.dll. Make sure you only have one, and keep the one from the update.

You have a funky datecode so no clue where the crash is inside the DLL, but usually, this error: [2023/12/07 21:33:31] W:dll_entry_init: Failed to boot Camera. [2023/12/08 11:33:47] W:signal: exception raised: EXCEPTION_INT_DIVIDE_BY_ZERO [2023/12/08 11:33:47] I:signal: printing callstack means you have a webcam connected, which can be fixed by turning on SDVX Disable Cameras -sdvxdisablecams option.

It's right there on the first post. Don't expect it to work though, there is no IO support.

There may be multiple problems, but yes, AVX2 is one of your problems. From your log: [2023/11/30 21:34:06] M:cpuutils: dumping processor information... [2023/11/30 21:34:06] M:cpuutils: vendor : GenuineIntel [2023/11/30 21:34:06] M:cpuutils: brand : Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz [2023/11/30 21:34:06] M:cpuutils: family : 6 [2023/11/30 21:34:06] M:cpuutils: model : 58 [2023/11/30 21:34:06] M:cpuutils: stepping : 9 [2023/11/30 21:34:06] M:cpuutils: uarch : INTEL_IVB [2023/11/30 21:34:06] M:cpuutils: features : fpu tsc cx8 clfsh mmx aes erms f16c sse sse2 sse3 ssse3 sse4_1 sse4_2 avx pclmulqdq smx cx16 popcnt rdrnd ss [2023/11/30 21:34:06] M:cpuutils: SSE4.2 : supported [2023/11/30 21:34:06] M:cpuutils: AVX2 : NOT supported <-------------------------------------------------- [2023/11/30 21:36:05] W:signal: exception raised: EXCEPTION_ILLEGAL_INSTRUCTION [2023/11/30 21:36:05] I:signal: printing callstack [2023/11/30 21:36:05] W:qcl::CExceptionObserver::Save: ディレクトリ作成失敗:0x80070002 [2023/11/30 21:36:05] I:stackwalker: 0000000180400146 (bm2dx): (unknown): (unknown) [2023/11/30 21:36:05] I:stackwalker: 00000001803F7AFE (bm2dx): (unknown): (unknown) see this post for a fix:

That's not how you use spice. Maybe follow a guide? https://rentry.org/iidxdump edit: i see that you typed your own post into your quote... sigh. You can't just randomly enable settings and hope for the best. You might have completely fucked up the config file, so maybe delete %appdata%\spicetools.xml and try again.

I don't have a suggestion on *why* it's being logged (maybe bad data? because I don't see this) but if you want to mask the problem, you can set -loglevel to "fatal" in spicecfg.

Please rephrase your question. Don't know what your problem is. Not sure what you mean by "no api server". Also, attach the whole log.txt as a file, not copy paste parts of it. You have LOTS of options that you should not be using.... -cfg this is for opening the configurator, not launching a game -kfcontrol this is for people with sound voltex cabs... -iidxbio2fw this is for people with IIDX cabs.... and you don't usually want it -wintouch -touchemuforce This is for touch screens in TDJ mode, and even then, there is no need for them -audiobackend waveout this will make your game sound like shit or no sound at all why don't you click "Reset Configuration" button at the bottom in Advanced tab and try fresh?

Have you seen bemaniutils implementation? https://github.com/DragonMinded/bemaniutils/blob/48331ac092f3067954cabda8be4798836f95b40c/bemani/backend/iidx/copula.py#L23

Don't ever force v-sync off in bemani games lol. Almost all of them rely on v-sync being on. It's OK for the game to drop to 119.94 FPS or whatever, it's really not a big deal, IIDX can figure out the stable framerate during monitor check. If you go to an arcade and observe the monitor check on a Lightning Model, it stabilizes at like 119.xx Hz, not 120.

What is different in Epolis is that the game will ask for very small buffers, so if your sound card can't keep up, it will sound bad. You can also try 48khz... or try FlexASIO instead. Don't see anything obviously wrong, so I would suspect corrupt OS.

aclayers.dll is a Windows component, possibly you have some corrupt OS files causing the crash. try sfc /scannow, or windows repair.... you might want to try the latest spice2x beta as well. full log.txt might be helpful.

https://iidx.org/touch_monitor btw, **not** recommended that you get random Chinese ones off Amazon or Ali, because usually their touch response really sucks better to get good known models used off ebay or something.

this feature is not present in arcade right now, it usually comes later when BPL is in season