bicarus

[----/--/-- --:--:--] 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.

maybe try a fresh copy of ea3-config.xml - the file is encoded with SHIFT-JIS which can mess up in a lot of text editors. the guide isn't entirely correct, it's not necessary to modify it, you can do everything in spicecfg.

you have a bunch of nvram related errors [----/--/-- --:--:--] W:mounttab: boot(/dev/nvram2,/dev/nvram) mount error(80070002) [----/--/-- --:--:--] W:boot: logger: /dev/raw/log does not exist [----/--/-- --:--:--] W:boot: logger: cannot create /dev/raw/log [----/--/-- --:--:--] W:boot: logger: cannot create log file [2023/05/01 22:38:57] W:avs-core: failed to create '/dev/raw' folder at 'D:/LDJ/contents/dev/raw': Filename too long [2023/05/01 22:38:57] W:avs-core: failed to create '/dev/nvram2' folder at 'D:/LDJ/contents/dev/nvram': Filename too long this means you have a bad prop\avs-config.xml. One of the shared data for Resident contained many bad XML files. Such is life when dealing with leaked n-0 data. edit prop\avs-config.xml and remove these lines: <vfs name="boot" fstype="fs" src="D:/LDJ/contents/dev/raw" dst="/dev/raw" opt="vf=1,posix=1"/> <vfs name="boot" fstype="fs" src="D:/LDJ/contents/dev/nvram" dst="/dev/nvram2" opt="vf=0,posix=1"/> and replace with: <vfs name="boot" fstype="fs" src="dev/raw" dst="/dev/raw" opt="vf=1,posix=1"/> <vfs name="boot" fstype="fs" src="dev/nvram" dst="/dev/nvram" opt="vf=1,posix=1"/> and try again. This allows the game to create dev/raw and dev/nvram folder inside the game directory, instead of trying to create them in D:\ drive (which you might not have) (same post as below)

By the way, there is a known issue with AMD Ryzen 3900X processor that makes Gitadora freeze on the loading screen, due to a processor bug. To workaround, try updating firmware, and if that still doesn't work, disable SMT (simultaneous multithreading) in the BIOS. You can also download spice2x and see if you can modify the Processor Affinity and reduce the number of processor the game can use (to half of what is available).

Thank you, will give it a try, I had no idea you can use the keyboard??? lolll the data shared previously is 230404, but they didn't supply the XML file with it, so it's just the date code showing wrong you can just edit prop\ea3-config.xml if you really care it's a completely different problem now so now you have the arguments working (see 3rd line in your file again) [2023/04/29 16:13:15] M:ea3-server: sizeof(struct client_t)=600. [2023/04/29 16:13:15] M:ea3-server: memsiz=95664. [2023/04/29 16:13:15] W:ea3-server: avs_net_listen() failed.ffffffff. [2023/04/29 16:13:15] M:xrpc: comm failed [2023/04/29 16:13:15] M:xrpc: services.get failed. but you forgot to specify a server, turn on -ea (or figure out how to turn on asphyxia)

If you look at the 3rd line in your file, you can see that none of the arguments worked (it's blank). Try again with spice2x maybe, you're using an old build of spice. you need newest version of windows 10 or 11.

echoing this, i just ran to this as well after updating, would appreciate if anyone has updated iidx plugin for asphyxia for 2023040400

did you do the right 120fps patches? maybe try this too if nvidia? vvvv

spice2x: https://spice2x.github.io/ (old spicetools doesn't work properly with spcecompanion for resident) spicecompanion android: https://play.google.com/store/apps/details?id=spicedev.spicecompanion spicecompanion iOS: https://apps.apple.com/us/app/spicecompanion/id1512681974 and then enable spiceAPI in spicecfg.exe, set a port number

full log would be more helpful, but make sure you don't have duplicate files (for example, don't have bm2dx.in contents and also in modules) - common mistake when downloading many patches from emuline since they can have different locations You indeed have an audio problem: [2023/04/28 16:24:48] M:audio::wasapi: WrappedIAudioClient::GetMixFormat [2023/04/28 16:24:48] I:audio::wasapi: IAudioClient::Initialize hook hit [2023/04/28 16:24:48] I:audio::wasapi: ... ShareMode : AUDCLNT_SHAREMODE_SHARED [2023/04/28 16:24:48] I:audio::wasapi: ... StreamFlags : AUDCLNT_STREAMFLAGS_EVENTCALLBACK | AUDCLNT_STREAMFLAGS_NOPERSIST [2023/04/28 16:24:48] I:audio::wasapi: ... hnsBufferDuration : 100000 [2023/04/28 16:24:48] I:audio::wasapi: ... hnsPeriodicity : 100000 [2023/04/28 16:24:48] I:audio: Wave Format: [2023/04/28 16:24:48] I:audio: ... SubFormat : {00000001-0000-0010-8000-00AA00389B71} [2023/04/28 16:24:48] I:audio: ... nChannels : 63312 [2023/04/28 16:24:48] I:audio: ... nSamplesPerSec : 44100 [2023/04/28 16:24:48] I:audio: ... nAvgBytesPerSec : 4201545752 [2023/04/28 16:24:48] I:audio: ... nBlockAlign : 61088 [2023/04/28 16:24:48] I:audio: ... wBitsPerSample : 16 [2023/04/28 16:24:48] I:audio: ... wValidBitsPerSample : 16 [2023/04/28 16:24:48] I:audio: ... dwChannelMask : SPEAKER_FRONT_LEFT | SPEAKER_FRONT_RIGHT [2023/04/28 16:24:48] W:audio::wasapi: IAudioClient::Initialize failed, hr=0x80070057 if your macbook only supports 48khz, you have to route it through ASIO, but you forgot to set -iidxsounddevice option to asio, and -iidxasio to ASIO4ALL. That being said, you're not going to have a good experience playing the game if you force audio upsampling from 44.1khz to 48khz, your game will frequently be out of sync.

If you pressed "Naive" button in spicecfg to map keys, try again by using "Bind" button instead. If that still doesn't work, then it's your keyboard. post your log.txt.

For 230404: Prevent Windows volume change (stop game from setting it to 100% on launch) bm2dx.dll, offset 0x48C50A F3 0F 10 0D 8a 63 E0 00 48 8B 4C 24 60 FF 94 24 90 00 00 00 => F3 0F 10 0D 8a 63 E0 00 48 8B 4C 24 60 31 c0 90 90 90 90 90 This basically just prevents the game from calling IAudioEndpointVolume::SetMasterVolumeLevelScalar. Applies to both wasapi and asio.

did you also use -graphics-force-refresh? if you look at log.txt you can tell what refresh rate it's launching

Get rid of stale d3d9.dll from your folder. Also, you have to post the whole log file, not just a blurry screenshot that shows like 20 lines.

in NVIDIA control panel make sure vsync settings are set to "Application Controlled", and not "on" or "off. Setting it to "application controlled" is the best way to make the main screen 120 and sub screen 60 (make sure gsync is off of course, and don't set FPS limiter either, just let the game do it)... touch screen or not doesn't matter, that has no effect on display whatsoever, don't worry about that. that being said, if you don't have a touch screen, you can't use the subscreen anyway... becuase you have to use the mouse and click on the main screen, not sub screen, so just turn on -graphics-force-single-adapter option and it use with subscreen overlay (Page Up button)