sa1am Posté(e) le 27 décembre 2023 Partager Posté(e) le 27 décembre 2023 1219 patcher https://patch.573.gay/sdvx6 Lien vers le commentaire Partager sur d’autres sites More sharing options...
sa1to Posté(e) le 27 décembre 2023 Partager Posté(e) le 27 décembre 2023 anyone have an idea how to solve the following error? [2023/12/28 04:12:35] W:property: get_error: prop==NULL [2023/12/28 04:12:35] W:StoryComponent: xml read error data/others/story/story_scripts.xml, 9, 9 [2023/12/28 04:12:35] W:property: destroy: prop==NULL [2023/12/28 04:12:35] I:Attach: out APPMAINFLOW [2023/12/28 04:12:35] W:afp-sys: "XCd229cc000033" layer ID 0 is not layer ID. [2023/12/28 04:12:35] W:BM2D: CreateLayer() 指定したレイヤーは存在しません shutter_default [2023/12/27 15:12:35] W:signal: exception raised: EXCEPTION_ACCESS_VIOLATION [2023/12/27 15:12:35] I:signal: printing callstack [2023/12/27 15:12:35] I:stackwalker: 000000018017B18D (soundvoltex): (unknown): (unknown) [2023/12/27 15:12:35] I:stackwalker: 000000018017AA8D (soundvoltex): (unknown): (unknown) [2023/12/27 15:12:35] I:stackwalker: 000000018053E530 (soundvoltex): (unknown): dll_entry_main [2023/12/27 15:12:35] I:stackwalker: 00000001804C2AA1 (soundvoltex): (unknown): dll_entry_main [2023/12/27 15:12:35] I:stackwalker: 00000001804C2034 (soundvoltex): (unknown): dll_entry_main [2023/12/27 15:12:35] I:stackwalker: 00000001802C00C0 (soundvoltex): (unknown): dll_entry_main [2023/12/27 15:12:35] I:stackwalker: 00000001802C005D (soundvoltex): (unknown): dll_entry_main [2023/12/27 15:12:35] I:stackwalker: 00000001802BFF65 (soundvoltex): (unknown): dll_entry_main [2023/12/27 15:12:35] I:stackwalker: 000000000044F8E7 (spice64): (unknown): (unknown) [2023/12/27 15:12:35] I:stackwalker: 00000000004012EE (spice64): (unknown): (unknown) [2023/12/27 15:12:35] I:stackwalker: 0000000000401406 (spice64): (unknown): (unknown) [2023/12/27 15:12:35] I:stackwalker: 00007FF952A8257D (KERNEL32): (unknown): BaseThreadInitThunk [2023/12/27 15:12:35] I:stackwalker: 00007FF954CEAA78 (ntdll): (unknown): RtlUserThreadStart Lien vers le commentaire Partager sur d’autres sites More sharing options...
bicarus Posté(e) le 27 décembre 2023 Partager Posté(e) le 27 décembre 2023 57 minutes ago, sa1to said: anyone have an idea how to solve the following error? [2023/12/28 04:12:35] W:property: get_error: prop==NULL [2023/12/28 04:12:35] W:StoryComponent: xml read error data/others/story/story_scripts.xml, 9, 9 [2023/12/28 04:12:35] W:property: destroy: prop==NULL [2023/12/28 04:12:35] I:Attach: out APPMAINFLOW [2023/12/28 04:12:35] W:afp-sys: "XCd229cc000033" layer ID 0 is not layer ID. [2023/12/28 04:12:35] W:BM2D: CreateLayer() 指定したレイヤーは存在しません shutter_default [2023/12/27 15:12:35] W:signal: exception raised: EXCEPTION_ACCESS_VIOLATION [2023/12/27 15:12:35] I:signal: printing callstack [2023/12/27 15:12:35] I:stackwalker: 000000018017B18D (soundvoltex): (unknown): (unknown) [2023/12/27 15:12:35] I:stackwalker: 000000018017AA8D (soundvoltex): (unknown): (unknown) [2023/12/27 15:12:35] I:stackwalker: 000000018053E530 (soundvoltex): (unknown): dll_entry_main [2023/12/27 15:12:35] I:stackwalker: 00000001804C2AA1 (soundvoltex): (unknown): dll_entry_main [2023/12/27 15:12:35] I:stackwalker: 00000001804C2034 (soundvoltex): (unknown): dll_entry_main [2023/12/27 15:12:35] I:stackwalker: 00000001802C00C0 (soundvoltex): (unknown): dll_entry_main [2023/12/27 15:12:35] I:stackwalker: 00000001802C005D (soundvoltex): (unknown): dll_entry_main [2023/12/27 15:12:35] I:stackwalker: 00000001802BFF65 (soundvoltex): (unknown): dll_entry_main [2023/12/27 15:12:35] I:stackwalker: 000000000044F8E7 (spice64): (unknown): (unknown) [2023/12/27 15:12:35] I:stackwalker: 00000000004012EE (spice64): (unknown): (unknown) [2023/12/27 15:12:35] I:stackwalker: 0000000000401406 (spice64): (unknown): (unknown) [2023/12/27 15:12:35] I:stackwalker: 00007FF952A8257D (KERNEL32): (unknown): BaseThreadInitThunk [2023/12/27 15:12:35] I:stackwalker: 00007FF954CEAA78 (ntdll): (unknown): RtlUserThreadStart This means you're missing a file. [2023/12/28 04:12:35] W:BM2D: CreateLayer() 指定したレイヤーは存在しません shutter_default Lien vers le commentaire Partager sur d’autres sites More sharing options...
sa1to Posté(e) le 27 décembre 2023 Partager Posté(e) le 27 décembre 2023 28 minutes ago, bicarus said: This means you're missing a file. [2023/12/28 04:12:35] W:BM2D: CreateLayer() 指定したレイヤーは存在しません shutter_default thanks...tried to reinstalled and got a new error instead... any ideas? [2023/12/28 05:42:50] W:imagefs: bad image size(0) [2023/12/28 05:42:50] W:imagefs: cannot open '/mnt/bm2d/rfs0r1/data/graphics/common/cmn_j.ifs'(80070005) [2023/12/28 05:42:50] W:BM2D: avs_fs_mountに失敗しました。mountpoint = /mnt/bm2d/ngp0/mnt/bm2d/rfs0r1/data/graphics/common/cmn_j.ifs [2023/12/28 05:42:50] I:GraphicUtility: LoadingIFS finish @Thread: common/cmn_j.ifs log.txt Lien vers le commentaire Partager sur d’autres sites More sharing options...
bicarus Posté(e) le 27 décembre 2023 Partager Posté(e) le 27 décembre 2023 21 minutes ago, sa1to said: thanks...tried to reinstalled and got a new error instead... any ideas? [2023/12/28 05:42:50] W:imagefs: bad image size(0) [2023/12/28 05:42:50] W:imagefs: cannot open '/mnt/bm2d/rfs0r1/data/graphics/common/cmn_j.ifs'(80070005) [2023/12/28 05:42:50] W:BM2D: avs_fs_mountに失敗しました。mountpoint = /mnt/bm2d/ngp0/mnt/bm2d/rfs0r1/data/graphics/common/cmn_j.ifs [2023/12/28 05:42:50] I:GraphicUtility: LoadingIFS finish @Thread: common/cmn_j.ifs log.txt 454.68 kB · 0 downloads It's exactly as it says, something is wrong with your graphics files (data/graphics/common/cmn_j.ifs) again. You probably missed some updates. Lien vers le commentaire Partager sur d’autres sites More sharing options...
sa1to Posté(e) le 27 décembre 2023 Partager Posté(e) le 27 décembre 2023 (modifié) 2 hours ago, bicarus said: It's exactly as it says, something is wrong with your graphics files (data/graphics/common/cmn_j.ifs) again. You probably missed some updates. edited Modifié le 28 décembre 2023 par sa1to Lien vers le commentaire Partager sur d’autres sites More sharing options...
Rydi Posté(e) le 28 décembre 2023 Partager Posté(e) le 28 décembre 2023 How to Patch SDVX PLUS to 1219? Lien vers le commentaire Partager sur d’autres sites More sharing options...
ICUS Posté(e) le 28 décembre 2023 Partager Posté(e) le 28 décembre 2023 how can i fix this error? it crashed in single match result loading screen using [2023/12/27 21:33:52] I:Detach: in ALTERNATIVE_GAME_SCENE [2023/12/27 21:33:52] I:Detach: out ALTERNATIVE_GAME_SCENE [2023/12/27 21:33:52] I:Attach: in RESULT_SCENE [2023/12/27 21:33:52] I:Attach: out RESULT_SCENE [2023/12/27 21:33:52] I:CPJOBaseScene: LoadThread start. [2023/12/27 21:33:52] M:GraphicUtility: LoadingIFS start @Thread: ver06/result_battle.ifs [2023/12/27 21:33:52] I:GraphicUtility: LoadingIFS finish @Thread: ver06/result_battle.ifs [2023/12/27 21:33:52] M:GraphicUtility: LoadingIFS start @Thread: ver06/result_battle_ko.ifs [2023/12/27 21:33:52] I:GraphicUtility: LoadingIFS finish @Thread: ver06/result_battle_ko.ifs [2023/12/27 21:33:52] M:GraphicUtility: LoadingIFS start @Thread: ver06/arena_rankup_window.ifs [2023/12/27 21:33:53] I:GraphicUtility: LoadingIFS finish @Thread: ver06/arena_rankup_window.ifs [2023/12/27 21:33:53] M:GraphicUtility: LoadingIFS start @Thread: ver06/arena_rankup_window_ja.ifs [2023/12/27 21:33:53] I:GraphicUtility: LoadingIFS finish @Thread: ver06/arena_rankup_window_ja.ifs [2023/12/27 21:33:53] M:GraphicUtility: LoadingIFS start @Thread: ver06/result.ifs [2023/12/27 21:33:53] I:GraphicUtility: LoadingIFS finish @Thread: ver06/result.ifs [2023/12/27 21:33:53] M:GraphicUtility: LoadingIFS start @Thread: ver06/result_ko.ifs [2023/12/27 21:33:53] I:GraphicUtility: LoadingIFS finish @Thread: ver06/result_ko.ifs [2023/12/27 21:33:53] M:GraphicUtility: LoadingIFS start @Thread: ver06/gauge.ifs [2023/12/27 21:33:53] I:GraphicUtility: LoadingIFS finish @Thread: ver06/gauge.ifs [2023/12/27 21:33:53] M:GraphicUtility: LoadingIFS start @Thread: ver06/force.ifs [2023/12/27 21:33:53] I:GraphicUtility: LoadingIFS finish @Thread: ver06/force.ifs [2023/12/27 21:33:53] M:GraphicUtility: LoadingIFS start @Thread: ver06/force_ko.ifs [2023/12/27 21:33:53] I:GraphicUtility: LoadingIFS finish @Thread: ver06/force_ko.ifs [2023/12/27 21:33:53] M:GraphicUtility: LoadingIFS start @Thread: ver06/ms_sel.ifs [2023/12/27 21:33:53] I:GraphicUtility: LoadingIFS finish @Thread: ver06/ms_sel.ifs [2023/12/27 21:33:53] M:GraphicUtility: LoadingIFS start @Thread: ver06/ms_sel_ko.ifs [2023/12/27 21:33:53] I:GraphicUtility: LoadingIFS finish @Thread: ver06/ms_sel_ko.ifs [2023/12/27 21:33:53] M:GraphicUtility: LoadingIFS start @Thread: ver06/connect.ifs [2023/12/27 21:33:53] I:GraphicUtility: LoadingIFS finish @Thread: ver06/connect.ifs [2023/12/27 21:33:53] M:GraphicUtility: LoadingIFS start @Thread: ver06/connect_ja.ifs [2023/12/27 21:33:53] I:GraphicUtility: LoadingIFS finish @Thread: ver06/connect_ja.ifs [2023/12/27 21:33:53] I:CPJOBaseScene: LoadThread end. [2023/12/28 12:33:50] W:signal: exception raised: EXCEPTION_ILLEGAL_INSTRUCTION [2023/12/28 12:33:50] I:signal: printing callstack [2023/12/28 12:33:50] I:stackwalker: 000001B6CDDA2423 (soundvoltex): (unknown): (unknown) [2023/12/28 12:33:50] I:stackwalker: 000001B6CE0DB068 (soundvoltex): (unknown): dll_entry_main [2023/12/28 12:33:50] I:stackwalker: 000001B6CE0DAB10 (soundvoltex): (unknown): dll_entry_main [2023/12/28 12:33:50] I:stackwalker: 000001B6CE20D5D1 (soundvoltex): (unknown): dll_entry_main [2023/12/28 12:33:50] I:stackwalker: 000001B6CE2103AF (soundvoltex): (unknown): dll_entry_main [2023/12/28 12:33:50] I:stackwalker: 000001B6CE20E5AA (soundvoltex): (unknown): dll_entry_main [2023/12/28 12:33:50] I:stackwalker: 000001B6CE192AA1 (soundvoltex): (unknown): dll_entry_main [2023/12/28 12:33:50] I:stackwalker: 000001B6CE192034 (soundvoltex): (unknown): dll_entry_main [2023/12/28 12:33:50] I:stackwalker: 000001B6CDF900C0 (soundvoltex): (unknown): dll_entry_main [2023/12/28 12:33:50] I:stackwalker: 000001B6CDF9005D (soundvoltex): (unknown): dll_entry_main [2023/12/28 12:33:50] I:stackwalker: 000001B6CDF8FF65 (soundvoltex): (unknown): dll_entry_main [2023/12/28 12:33:50] I:stackwalker: 00007FF78A479F7A (spice64): (unknown): (unknown) [2023/12/28 12:33:50] I:stackwalker: 00007FF78A4313B1 (spice64): (unknown): (unknown) [2023/12/28 12:33:50] I:stackwalker: 00007FF78A4314E6 (spice64): (unknown): (unknown) [2023/12/28 12:33:50] I:stackwalker: 00007FF8DD7E257D (KERNEL32): (unknown): BaseThreadInitThunk [2023/12/28 12:33:50] I:stackwalker: 00007FF8DE52AA58 (ntdll): (unknown): RtlUserThreadStart [2023/12/28 12:33:50] F:signal: end [2023/12/28 12:33:50] I:launcher: stopping subsystems [2023/12/28 12:33:50] I:logger: stop [2023/12/28 12:33:50] M:audio::wasapi: WrappedIAudioClient::Stop [2023/12/28 12:33:51] I:rawinput: disposing devices [2023/12/28 12:33:51] I:nvapi: unloading NVAPI Lien vers le commentaire Partager sur d’autres sites More sharing options...
bicarus Posté(e) le 28 décembre 2023 Partager Posté(e) le 28 décembre 2023 5 minutes ago, ICUS said: how can i fix this error? it crashed in single match result loading screen using [2023/12/27 21:33:52] I:Detach: in ALTERNATIVE_GAME_SCENE [2023/12/27 21:33:52] I:Detach: out ALTERNATIVE_GAME_SCENE [2023/12/27 21:33:52] I:Attach: in RESULT_SCENE [2023/12/27 21:33:52] I:Attach: out RESULT_SCENE [2023/12/27 21:33:52] I:CPJOBaseScene: LoadThread start. [2023/12/27 21:33:52] M:GraphicUtility: LoadingIFS start @Thread: ver06/result_battle.ifs [2023/12/27 21:33:52] I:GraphicUtility: LoadingIFS finish @Thread: ver06/result_battle.ifs [2023/12/27 21:33:52] M:GraphicUtility: LoadingIFS start @Thread: ver06/result_battle_ko.ifs [2023/12/27 21:33:52] I:GraphicUtility: LoadingIFS finish @Thread: ver06/result_battle_ko.ifs [2023/12/27 21:33:52] M:GraphicUtility: LoadingIFS start @Thread: ver06/arena_rankup_window.ifs [2023/12/27 21:33:53] I:GraphicUtility: LoadingIFS finish @Thread: ver06/arena_rankup_window.ifs [2023/12/27 21:33:53] M:GraphicUtility: LoadingIFS start @Thread: ver06/arena_rankup_window_ja.ifs [2023/12/27 21:33:53] I:GraphicUtility: LoadingIFS finish @Thread: ver06/arena_rankup_window_ja.ifs [2023/12/27 21:33:53] M:GraphicUtility: LoadingIFS start @Thread: ver06/result.ifs [2023/12/27 21:33:53] I:GraphicUtility: LoadingIFS finish @Thread: ver06/result.ifs [2023/12/27 21:33:53] M:GraphicUtility: LoadingIFS start @Thread: ver06/result_ko.ifs [2023/12/27 21:33:53] I:GraphicUtility: LoadingIFS finish @Thread: ver06/result_ko.ifs [2023/12/27 21:33:53] M:GraphicUtility: LoadingIFS start @Thread: ver06/gauge.ifs [2023/12/27 21:33:53] I:GraphicUtility: LoadingIFS finish @Thread: ver06/gauge.ifs [2023/12/27 21:33:53] M:GraphicUtility: LoadingIFS start @Thread: ver06/force.ifs [2023/12/27 21:33:53] I:GraphicUtility: LoadingIFS finish @Thread: ver06/force.ifs [2023/12/27 21:33:53] M:GraphicUtility: LoadingIFS start @Thread: ver06/force_ko.ifs [2023/12/27 21:33:53] I:GraphicUtility: LoadingIFS finish @Thread: ver06/force_ko.ifs [2023/12/27 21:33:53] M:GraphicUtility: LoadingIFS start @Thread: ver06/ms_sel.ifs [2023/12/27 21:33:53] I:GraphicUtility: LoadingIFS finish @Thread: ver06/ms_sel.ifs [2023/12/27 21:33:53] M:GraphicUtility: LoadingIFS start @Thread: ver06/ms_sel_ko.ifs [2023/12/27 21:33:53] I:GraphicUtility: LoadingIFS finish @Thread: ver06/ms_sel_ko.ifs [2023/12/27 21:33:53] M:GraphicUtility: LoadingIFS start @Thread: ver06/connect.ifs [2023/12/27 21:33:53] I:GraphicUtility: LoadingIFS finish @Thread: ver06/connect.ifs [2023/12/27 21:33:53] M:GraphicUtility: LoadingIFS start @Thread: ver06/connect_ja.ifs [2023/12/27 21:33:53] I:GraphicUtility: LoadingIFS finish @Thread: ver06/connect_ja.ifs [2023/12/27 21:33:53] I:CPJOBaseScene: LoadThread end. [2023/12/28 12:33:50] W:signal: exception raised: EXCEPTION_ILLEGAL_INSTRUCTION [2023/12/28 12:33:50] I:signal: printing callstack [2023/12/28 12:33:50] I:stackwalker: 000001B6CDDA2423 (soundvoltex): (unknown): (unknown) [2023/12/28 12:33:50] I:stackwalker: 000001B6CE0DB068 (soundvoltex): (unknown): dll_entry_main [2023/12/28 12:33:50] I:stackwalker: 000001B6CE0DAB10 (soundvoltex): (unknown): dll_entry_main [2023/12/28 12:33:50] I:stackwalker: 000001B6CE20D5D1 (soundvoltex): (unknown): dll_entry_main [2023/12/28 12:33:50] I:stackwalker: 000001B6CE2103AF (soundvoltex): (unknown): dll_entry_main [2023/12/28 12:33:50] I:stackwalker: 000001B6CE20E5AA (soundvoltex): (unknown): dll_entry_main [2023/12/28 12:33:50] I:stackwalker: 000001B6CE192AA1 (soundvoltex): (unknown): dll_entry_main [2023/12/28 12:33:50] I:stackwalker: 000001B6CE192034 (soundvoltex): (unknown): dll_entry_main [2023/12/28 12:33:50] I:stackwalker: 000001B6CDF900C0 (soundvoltex): (unknown): dll_entry_main [2023/12/28 12:33:50] I:stackwalker: 000001B6CDF9005D (soundvoltex): (unknown): dll_entry_main [2023/12/28 12:33:50] I:stackwalker: 000001B6CDF8FF65 (soundvoltex): (unknown): dll_entry_main [2023/12/28 12:33:50] I:stackwalker: 00007FF78A479F7A (spice64): (unknown): (unknown) [2023/12/28 12:33:50] I:stackwalker: 00007FF78A4313B1 (spice64): (unknown): (unknown) [2023/12/28 12:33:50] I:stackwalker: 00007FF78A4314E6 (spice64): (unknown): (unknown) [2023/12/28 12:33:50] I:stackwalker: 00007FF8DD7E257D (KERNEL32): (unknown): BaseThreadInitThunk [2023/12/28 12:33:50] I:stackwalker: 00007FF8DE52AA58 (ntdll): (unknown): RtlUserThreadStart [2023/12/28 12:33:50] F:signal: end [2023/12/28 12:33:50] I:launcher: stopping subsystems [2023/12/28 12:33:50] I:logger: stop [2023/12/28 12:33:50] M:audio::wasapi: WrappedIAudioClient::Stop [2023/12/28 12:33:51] I:rawinput: disposing devices [2023/12/28 12:33:51] I:nvapi: unloading NVAPI You should always post the whole log. No one can decode the call stack by just looking at it without knowing the base address and what version. Based on what you said, if the crash happens after a song, then it's almost always a server issue. Lien vers le commentaire Partager sur d’autres sites More sharing options...
ICUS Posté(e) le 28 décembre 2023 Partager Posté(e) le 28 décembre 2023 Il y a 3 heures, bicarus a dit : 항상 전체 로그를 게시해야 합니다. 기본 주소와 버전을 알지 못한 채 호출 스택을 보는 것만으로는 누구도 해독할 수 없습니다. 말씀하신 내용에 따르면 노래가 끝난 후 충돌이 발생하면 거의 항상 서버 문제입니다. Sorry I forgot to upload log file here is my log file and I use server computer(192.168.0.37:8083) with docker asphyxia container log.txt Lien vers le commentaire Partager sur d’autres sites More sharing options...
bicarus Posté(e) le 28 décembre 2023 Partager Posté(e) le 28 décembre 2023 18 minutes ago, ICUS said: Sorry I forgot to upload log file here is my log file and I use server computer(192.168.0.37:8083) with docker asphyxia container log.txt 541.91 kB · 0 downloads I didn't notice before, but you crashed, with EXCEPTION_ILLEGAL_INSTRUCTION. I would strongly suspect bad patch (hex edit) or a corrupt DLL file. Lien vers le commentaire Partager sur d’autres sites More sharing options...
mikaelr Posté(e) le 28 décembre 2023 Partager Posté(e) le 28 décembre 2023 2 hours ago, ICUS said: Sorry I forgot to upload log file here is my log file and I use server computer(192.168.0.37:8083) with docker asphyxia container log.txt 541.91 kB · 2 downloads What version of plugin you're using right now? Lien vers le commentaire Partager sur d’autres sites More sharing options...
ICUS Posté(e) le 28 décembre 2023 Partager Posté(e) le 28 décembre 2023 6분 전 mikaelr님이 이렇게 말했습니다: 지금 사용하고 있는 플러그인 버전은 무엇입니까? CORE v1.50c and plugin v6.1.2 2시간 전, bicarus가 말했습니다: 전에는 몰랐는데 EXCEPTION_ILLEGAL_INSTRUCTION으로 인해 충돌이 발생했습니다. 잘못된 패치(16진수 편집) 또는 손상된 DLL 파일이 의심됩니다. reinstall and just disable sub screen patch doesn't work Lien vers le commentaire Partager sur d’autres sites More sharing options...
bicarus Posté(e) le 28 décembre 2023 Partager Posté(e) le 28 décembre 2023 24 minutes ago, ICUS said: CORE v1.50c and plugin v6.1.2 reinstall and just disable sub screen patch doesn't work Not sure what you mean, but you don't need disable subscreen patch, you can just use "only use one monitor" option in spicecfg. Lien vers le commentaire Partager sur d’autres sites More sharing options...
mikaelr Posté(e) le 28 décembre 2023 Partager Posté(e) le 28 décembre 2023 59 minutes ago, ICUS said: CORE v1.50c and plugin v6.1.2 reinstall and just disable sub screen patch doesn't work don't patch your data first, give it a run and see if it works with the default settings. Try to use this plugin https://github.com/22vv0/asphyxia_plugins/releases/tag/fork-6.0.2.6 And latest spice2x https://spice2x.github.io/ 1 Lien vers le commentaire Partager sur d’autres sites More sharing options...
ruisu39 Posté(e) le 28 décembre 2023 Partager Posté(e) le 28 décembre 2023 On 12/25/2023 at 3:31 AM, 573agent said: the effect is available for me even outside of hexa diver, he's using the wrong DLL maybe? Yep, didnt update my soundvoltex.dll. Thanks for pointing out! Lien vers le commentaire Partager sur d’autres sites More sharing options...
573agent Posté(e) le 29 décembre 2023 Partager Posté(e) le 29 décembre 2023 9 hours ago, ruisu39 said: Yep, didnt update my soundvoltex.dll. Thanks for pointing out! Glad to see you found the issue. I tested the game with this plugin so everything should be fine if you use it. https://github.com/22vv0/asphyxia_plugins/releases/tag/fork-6.0.2.6 Lien vers le commentaire Partager sur d’autres sites More sharing options...
ICUS Posté(e) le 29 décembre 2023 Partager Posté(e) le 29 décembre 2023 2023년 12월 28일 오후 8시 55분, mikaelr는 다음과 같이 말했습니다. 먼저 데이터를 패치하지 말고 실행해 보고 기본 설정으로 작동하는지 확인하세요. 이 플러그인을 사용해보십시오 https://github.com/22vv0/asphyxia_plugins/releases/tag/fork-6.0.2.6 그리고 최신 spice2x https://spice2x.github.io/ It works!! thank you so much! Lien vers le commentaire Partager sur d’autres sites More sharing options...
beebop Posté(e) le 29 décembre 2023 Partager Posté(e) le 29 décembre 2023 (modifié) My game is struggling to stay at 120fps after applying the latest update. It worked perfectly fine even with live2D before I applied things. My fps jumps between 116 and 120 and the notes are generally very late. Any fixes? Modifié le 29 décembre 2023 par beebop Lien vers le commentaire Partager sur d’autres sites More sharing options...
mikaelr Posté(e) le 29 décembre 2023 Partager Posté(e) le 29 décembre 2023 4 hours ago, ICUS said: It works!! thank you so much! You're welcome. Enjoy 4 hours ago, beebop said: My game is struggling to stay at 120fps after applying the latest update. It worked perfectly fine even with live2D before I applied things. My fps varies between 110 and 119 and the notes are generally very off. Any fixes? What date code you're running right now? The frame drops have been a known issue since 1206 update but I'm not sure the exact way to fix that at the moment. You can try setting the process affinity to realtime first and see how it goes. 1 Lien vers le commentaire Partager sur d’autres sites More sharing options...
beebop Posté(e) le 29 décembre 2023 Partager Posté(e) le 29 décembre 2023 (modifié) Right now I'm running 1206 and am wanting to fix this problem first before I do the next update. How do I change process affinity to realtime? I see the option in spicecfg but I don't know what to input there edit: i did this from task manager and it made no difference Modifié le 29 décembre 2023 par beebop Lien vers le commentaire Partager sur d’autres sites More sharing options...
bicarus Posté(e) le 29 décembre 2023 Partager Posté(e) le 29 décembre 2023 (modifié) 3 hours ago, beebop said: Right now I'm running 1206 and am wanting to fix this problem first before I do the next update. How do I change process affinity to realtime? I see the option in spicecfg but I don't know what to input there edit: i did this from task manager and it made no difference It's Process Priority, not Process Affinity. Regardless, raising the priority is not going to help all that much. You can follow https://github.com/spice2x/spice2x.github.io/wiki/PC-optimization . Modifié le 29 décembre 2023 par bicarus Lien vers le commentaire Partager sur d’autres sites More sharing options...
Jhongerkong Posté(e) le 31 décembre 2023 Partager Posté(e) le 31 décembre 2023 On 12/27/2023 at 6:30 AM, sa1am said: 1219 patcher https://patch.573.gay/sdvx6 No power change and hide bottom text options? Lien vers le commentaire Partager sur d’autres sites More sharing options...
mikaelr Posté(e) le 31 décembre 2023 Partager Posté(e) le 31 décembre 2023 14 hours ago, Jhongerkong said: No power change and hide bottom text options? You don't really need those anymore with the newer spice2x 2 Lien vers le commentaire Partager sur d’autres sites More sharing options...
dchoi44 Posté(e) le 1 janvier Partager Posté(e) le 1 janvier On 12/30/2023 at 8:43 AM, bicarus said: It's Process Priority, not Process Affinity. Regardless, raising the priority is not going to help all that much. You can follow https://github.com/spice2x/spice2x.github.io/wiki/PC-optimization . It mentions something about a clean, and arcade-like OS image. Does this mean it's beneficial to run the game on virtualbox or something similar? Lien vers le commentaire Partager sur d’autres sites More sharing options...
bicarus Posté(e) le 1 janvier Partager Posté(e) le 1 janvier 1 minute ago, dchoi44 said: It mentions something about a clean, and arcade-like OS image. Does this mean it's beneficial to run the game on virtualbox or something similar? No, they're talking about using a dedicated PC. 1 Lien vers le commentaire Partager sur d’autres sites More sharing options...
Vinkamor Posté(e) le 3 janvier Partager Posté(e) le 3 janvier Hi guys. I'm wondering if you could teach me how to properly patch 2023042500. I've downloaded Nyaa's KFC-2021083100, and it works well. Then, I tried to patch KFC-2021083100 to KFC-2023042500, with a package I found in this thread. The dll in the modules folder was copied to the root "contents/" directory. But the game crushed after I clicked the spice64. I've tried to solve the problem with latest spicetool, replace "plugins/" folder with features.js. Unfortunately, all these methods doesn't work. Please see attached log for details. Thanks for your time in advance! log.txt Lien vers le commentaire Partager sur d’autres sites More sharing options...
bicarus Posté(e) le 3 janvier Partager Posté(e) le 3 janvier 1 hour ago, Vinkamor said: Hi guys. I'm wondering if you could teach me how to properly patch 2023042500. I've downloaded Nyaa's KFC-2021083100, and it works well. Then, I tried to patch KFC-2021083100 to KFC-2023042500, with a package I found in this thread. The dll in the modules folder was copied to the root "contents/" directory. But the game crushed after I clicked the spice64. I've tried to solve the problem with latest spicetool, replace "plugins/" folder with features.js. Unfortunately, all these methods doesn't work. Please see attached log for details. Thanks for your time in advance! log.txt 88.15 kB · 1 download for patch order, follow https://www.emuline.org/topic/3577-setting-up-sound-voltex-exceed-gear-data for the crash, your copy of spicetools is extremely old (it's from 2021), download the latest spice2x. Lien vers le commentaire Partager sur d’autres sites More sharing options...
Vinkamor Posté(e) le 4 janvier Partager Posté(e) le 4 janvier 20 hours ago, bicarus said: for patch order, follow https://www.emuline.org/topic/3577-setting-up-sound-voltex-exceed-gear-data for the crash, your copy of spicetools is extremely old (it's from 2021), download the latest spice2x. Hi Bicarus, thank you so much for your help! it works well for me. By the way, I can't use asphyxia services since last night. There is an error "ただいま回線が混雑しています。再度お試しください" in the game. I am wondering if you noticed the same issue? If this is the server maintenance, does it happen a lot? I appreciate all your help again. Lien vers le commentaire Partager sur d’autres sites More sharing options...
bicarus Posté(e) le 4 janvier Partager Posté(e) le 4 janvier 32 minutes ago, Vinkamor said: Hi Bicarus, thank you so much for your help! it works well for me. By the way, I can't use asphyxia services since last night. There is an error "ただいま回線が混雑しています。再度お試しください" in the game. I am wondering if you noticed the same issue? If this is the server maintenance, does it happen a lot? I appreciate all your help again. no, asphyxia runs on your computer, it should never be under maintenance. it means you set something up wrong. Lien vers le commentaire Partager sur d’autres sites More sharing options...
xxyke Posté(e) le 6 janvier Partager Posté(e) le 6 janvier Hi guys. I updated the 2023121900 file, but the songs after September 2023 are not displayed. Can someone help me solve this problem? Lien vers le commentaire Partager sur d’autres sites More sharing options...
endl3ss1217 Posté(e) le 8 janvier Partager Posté(e) le 8 janvier (modifié) Never mind I got the libavs-win64.dll issue fix, everything working now. Modifié le 8 janvier par endl3ss1217 Issue fixed Lien vers le commentaire Partager sur d’autres sites More sharing options...
MXDrako Posté(e) le 13 janvier Partager Posté(e) le 13 janvier On 1/6/2024 at 5:56 AM, xxyke said: Hi guys. I updated the 2023121900 file, but the songs after September 2023 are not displayed. Can someone help me solve this problem? Are You using asphyxia? Lien vers le commentaire Partager sur d’autres sites More sharing options...
xxyke Posté(e) le 13 janvier Partager Posté(e) le 13 janvier (modifié) 7 hours ago, MXDrako said: Are You using asphyxia? Yes, it suddenly shows up again now, it's strange Modifié le 13 janvier par xxyke Lien vers le commentaire Partager sur d’autres sites More sharing options...
sori213 Posté(e) le 13 janvier Partager Posté(e) le 13 janvier Is there an option to change the speed of the knob? When using the old version of spice2x, the knob speed was fast, but since using the latest version of spice2x, the knob speed has become slower. Also, I can't control the speed of the notes using the knob. Lien vers le commentaire Partager sur d’autres sites More sharing options...
bicarus Posté(e) le 13 janvier Partager Posté(e) le 13 janvier (modifié) 1 hour ago, sori213 said: Is there an option to change the speed of the knob? When using the old version of spice2x, the knob speed was fast, but since using the latest version of spice2x, the knob speed has become slower. Also, I can't control the speed of the notes using the knob. yes, look in spicecfg Analog tab and adjust sensitivity EDIT: if you are using a keyboard, then you can go to Advanced tab and use SDVX Digital Knob Sensitivity. Modifié le 13 janvier par bicarus 1 Lien vers le commentaire Partager sur d’autres sites More sharing options...
beebop Posté(e) le 14 janvier Partager Posté(e) le 14 janvier Is unplayable latency dependent on pc to pc or does it have to do with fps/refresh rate or other system confirgurations? Tried a lot of things so far but still getting -100 offset on every chart no matter the draw/judge settings Lien vers le commentaire Partager sur d’autres sites More sharing options...
Messages recommandés
Veuillez vous connecter pour commenter
Vous pourrez laisser un commentaire après vous êtes connecté.
Connectez-vous maintenant