Aller au contenu

[Arcade PC] Beatmania IIDX 28 BISTROVER (BEMANI)


Omar2
Go to solution Solved by Omar2,

Messages recommandés

1 hour ago, NekomineTheNeko said:

Hello again. I brought 5 logs with different situations. I think something will work out with this variety. 1.Default, SEE patch. 2.Wasapi-asio. SSE patch. 3.asio-asio,SSE patch. 4. No patch SIZE, default. 5.No patch,Asio and wasapi,starting without sound. If I didn't add something, it means it was already in the logs with other variations. The Shared Mode patch is enabled. My gigabyte ga-ma770-ud3 v2.0 motherboard is old, I know, but Sound Voltex 4 works stably and without bugs with sound and start. Those logs that are torn off, there the games fly out. Like everything. If something is unclear, speak up and offer. I'll read it and try. (I am writing through a translator.) My configuration pc. 6gb Ram,1tb HDD, rx 550 2gb, amd athlon x2 2 cores, 1,7ghz.

log.txt 73.04 kB · 0 downloads log.txt1 80.85 kB · 0 downloads log.txt5 107.13 kB · 0 downloads log.txt4 86.85 kB · 0 downloads log.txt3 74.48 kB · 0 downloads log.txt2 78.81 kB · 0 downloads

 

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.

 

Modifié par bicarus
Lien vers le commentaire
Partager sur d’autres sites

I've tired many fixes, but my IIDX keeps crashing before the start-up menu, and one warning I consistently get is the: W:signal: exception raised: EXCEPTION_ACCESS_VIOLATION before F:signal: end.
I'm wondering if this is the main issue or if any of you guys also get this error but are able to run it fine.
Attached is what I see when trying to run it.
I've attached some of my logs before, in above posts.

image_2023-05-13_153723320.png

Lien vers le commentaire
Partager sur d’autres sites

3 hours ago, sillytrew said:

I've tired many fixes, but my IIDX keeps crashing before the start-up menu, and one warning I consistently get is the: W:signal: exception raised: EXCEPTION_ACCESS_VIOLATION before F:signal: end.
I'm wondering if this is the main issue or if any of you guys also get this error but are able to run it fine.
Attached is what I see when trying to run it.
I've attached some of my logs before, in above posts.

image_2023-05-13_153723320.png

 

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

 

Modifié par bicarus
Lien vers le commentaire
Partager sur d’autres sites

Thanks for your reply. I tried to use Flex Asio, but I didn't figure out how to configure and enable it. And it also turns out that I need to include the SE patch or

it won't help, because a newer version is required? And where to put it? U mon.im or turksigara? And if possible, help with explanations. I have never encountered such a problem. (Preferably in stages, what to do.)

Thank you in advance.

8 hours ago, bicarus said:

 

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.

 

Thanks for your reply. I tried to use Flex Asio, but I didn't figure out how to configure and enable it. And it also turns out that I need to include the SE patch or
it won't help, because a newer version is required? And where to put it? U mon.im or turksigara? And if possible, help with explanations. I have never encountered such a problem. (Preferably in stages, what to do.)
Thank you in advance.

1.Mon.im. 2.Turksigara. 

IMG_20230514_124821.jpg

IMG_20230514_124853.jpg

Lien vers le commentaire
Partager sur d’autres sites

4 hours ago, NekomineTheNeko said:

Thanks for your reply. I tried to use Flex Asio, but I didn't figure out how to configure and enable it. And it also turns out that I need to include the SE patch or

it won't help, because a newer version is required? And where to put it? U mon.im or turksigara? And if possible, help with explanations. I have never encountered such a problem. (Preferably in stages, what to do.)

Thank you in advance.

Thanks for your reply. I tried to use Flex Asio, but I didn't figure out how to configure and enable it. And it also turns out that I need to include the SE patch or
it won't help, because a newer version is required? And where to put it? U mon.im or turksigara? And if possible, help with explanations. I have never encountered such a problem. (Preferably in stages, what to do.)
Thank you in advance.

1.Mon.im. 2.Turksigara. 

 

 

 

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.

 

Lien vers le commentaire
Partager sur d’autres sites

2 hours ago, bicarus said:

 

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.

 

The game starts only in one case. The Wasapi + asio4all bundle. But without sound. ((Device + Backend).In other cases, it either does not start, or it starts, but crashes, or it starts, works and there is no sound. If it's not difficult, can you throw off your config with asio from spice2x? I'll install it and try to run with it. Maybe I'm messing up somewhere...

Although damn, I'm confused. I continue to tick the patch on the CE, but do not install the enabled Wasapi? Is there 16 bit 44100 present in the sound settings? Do I need to enable Exclusive Mode in the playback device settings? Or turn it off? If you need to enable, do you need a priority mode for the application? It can be done in stages so that it is clear to me. Thank you in advance.

Lien vers le commentaire
Partager sur d’autres sites

Hello everyone. I'm desperate to ask you for help. When I start beatmania iidx 30 Resident,it fails to start and reports an error. It issues the message“avs-core: ignoring folder creation for '/dev/nvram': unsupported fs type”,it keeps looping until I close it. Is there any way to fix this?

[2023/05/14 17:50:58] I:hooks::lang: early initialization
[2023/05/14 17:50:58] I:avs-core: loading DLL
[2023/05/14 17:50:58] M:avs-core: version string: 2.17.3.0
[2023/05/14 17:50:58] I:avs-core: Found AVS2 core 2.17.3.0
[2023/05/14 17:50:58] M:avs-core: optional functions identified
[2023/05/14 17:50:58] I:avs-ea3: loading DLL
[2023/05/14 17:50:58] I:avs-ea3: Found AVS2 EA3 2.17.3.0
[2023/05/14 17:50:58] I:network: SpiceTools Network
[2023/05/14 17:50:58] I:network: Network preferences: 10.9.0.0
[2023/05/14 17:50:58] I:avs-core: booting
[2023/05/14 17:50:58] M:avs-core: ignoring folder creation for '/dev/nvram': unsupported fs type
[2023/05/14 17:50:58] M:avs-core: ignoring folder creation for '/dev/nvram': unsupported fs type
[2023/05/14 17:50:58] M:avs-core: ignoring folder creation for '/dev/nvram': unsupported fs type
[2023/05/14 17:50:58] M:avs-core: ignoring folder creation for '/dev/nvram': unsupported fs type
[2023/05/14 17:50:58] M:avs-core: ignoring folder creation for '/dev/nvram': unsupported fs type
[2023/05/14 17:50:58] M:avs-core: ignoring folder creation for '/dev/nvram': unsupported fs type
[2023/05/14 17:50:58] M:avs-core: ignoring folder creation for '/dev/nvram': unsupported fs type
[2023/05/14 17:50:58] M:avs-core: ignoring folder creation for '/dev/nvram': unsupported fs type
[2023/05/14 17:50:58] M:avs-core: ignoring folder creation for '/dev/nvram': unsupported fs type
[2023/05/14 17:50:58] M:avs-core: ignoring folder creation for '/dev/nvram': unsupported fs type
[2023/05/14 17:50:58] M:avs-core: ignoring folder creation for '/dev/nvram': unsupported fs type
[2023/05/14 17:50:58] M:avs-core: ignoring folder creation for '/dev/nvram': unsupported fs type
[2023/05/14 17:50:58] M:avs-core: ignoring folder creation for '/dev/nvram': unsupported fs type
[2023/05/14 17:50:58] M:avs-core: ignoring folder creation for '/dev/nvram': unsupported fs type
[2023/05/14 17:50:58] M:avs-core: ignoring folder creation for '/dev/nvram': unsupported fs type

 

Lien vers le commentaire
Partager sur d’autres sites

9 hours ago, NekomineTheNeko said:

The game starts only in one case. The Wasapi + asio4all bundle. But without sound. ((Device + Backend).In other cases, it either does not start, or it starts, but crashes, or it starts, works and there is no sound. If it's not difficult, can you throw off your config with asio from spice2x? I'll install it and try to run with it. Maybe I'm messing up somewhere...

Although damn, I'm confused. I continue to tick the patch on the CE, but do not install the enabled Wasapi? Is there 16 bit 44100 present in the sound settings? Do I need to enable Exclusive Mode in the playback device settings? Or turn it off? If you need to enable, do you need a priority mode for the application? It can be done in stages so that it is clear to me. Thank you in advance.

 

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?

 

6 hours ago, ayase said:

Hello everyone. I'm desperate to ask you for help. When I start beatmania iidx 30 Resident,it fails to start and reports an error. It issues the message“avs-core: ignoring folder creation for '/dev/nvram': unsupported fs type”,it keeps looping until I close it. Is there any way to fix this?

[2023/05/14 17:50:58] I:hooks::lang: early initialization
[2023/05/14 17:50:58] I:avs-core: loading DLL
[2023/05/14 17:50:58] M:avs-core: version string: 2.17.3.0
[2023/05/14 17:50:58] I:avs-core: Found AVS2 core 2.17.3.0
[2023/05/14 17:50:58] M:avs-core: optional functions identified
[2023/05/14 17:50:58] I:avs-ea3: loading DLL
[2023/05/14 17:50:58] I:avs-ea3: Found AVS2 EA3 2.17.3.0
[2023/05/14 17:50:58] I:network: SpiceTools Network
[2023/05/14 17:50:58] I:network: Network preferences: 10.9.0.0
[2023/05/14 17:50:58] I:avs-core: booting
[2023/05/14 17:50:58] M:avs-core: ignoring folder creation for '/dev/nvram': unsupported fs type
[2023/05/14 17:50:58] M:avs-core: ignoring folder creation for '/dev/nvram': unsupported fs type
[2023/05/14 17:50:58] M:avs-core: ignoring folder creation for '/dev/nvram': unsupported fs type
[2023/05/14 17:50:58] M:avs-core: ignoring folder creation for '/dev/nvram': unsupported fs type
[2023/05/14 17:50:58] M:avs-core: ignoring folder creation for '/dev/nvram': unsupported fs type
[2023/05/14 17:50:58] M:avs-core: ignoring folder creation for '/dev/nvram': unsupported fs type
[2023/05/14 17:50:58] M:avs-core: ignoring folder creation for '/dev/nvram': unsupported fs type
[2023/05/14 17:50:58] M:avs-core: ignoring folder creation for '/dev/nvram': unsupported fs type
[2023/05/14 17:50:58] M:avs-core: ignoring folder creation for '/dev/nvram': unsupported fs type
[2023/05/14 17:50:58] M:avs-core: ignoring folder creation for '/dev/nvram': unsupported fs type
[2023/05/14 17:50:58] M:avs-core: ignoring folder creation for '/dev/nvram': unsupported fs type
[2023/05/14 17:50:58] M:avs-core: ignoring folder creation for '/dev/nvram': unsupported fs type
[2023/05/14 17:50:58] M:avs-core: ignoring folder creation for '/dev/nvram': unsupported fs type
[2023/05/14 17:50:58] M:avs-core: ignoring folder creation for '/dev/nvram': unsupported fs type
[2023/05/14 17:50:58] M:avs-core: ignoring folder creation for '/dev/nvram': unsupported fs type

 

 

post the whole log.txt file, "M:" means it's not an error, just a misc message.

 

Modifié par bicarus
Lien vers le commentaire
Partager sur d’autres sites

4 hours ago, bicarus said:

 

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.

 

here is my full log

log.txt

Lien vers le commentaire
Partager sur d’autres sites

3 hours ago, isaactam617 said:

tried many fixes but same result,game will crash when selected a song to play

also tried asio and wasapi but same result

log.txt 144.28 kB · 2 downloads

 

seems like network error, are you using latest asphyxia plugin from this thread?

 

 

1 hour ago, ayase said:

 

[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

 

 

 

Modifié par bicarus
Lien vers le commentaire
Partager sur d’autres sites

54 minutes ago, bicarus said:

 

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

 

 

 

You are so helpful, thank you! I will try that when I back home.😃

Lien vers le commentaire
Partager sur d’autres sites

That's all I can convey. I started to go into another error when installing FlexASIO. My last attempt to understand why it doesn't work... If it doesn't work out, thank you anyway for trying to help. Here the pluses can be put as on 4PDA?bm2dx.dllbm2dx.dllbm2dx.dllbm2dx.dllbm2dx.dllbm2dx.dllbm2dx.dll

log.txt FlexASIO.toml spicetools.xml bm2dx.dll

Lien vers le commentaire
Partager sur d’autres sites

8 hours ago, NekomineTheNeko said:

That's all I can convey. I started to go into another error when installing FlexASIO. My last attempt to understand why it doesn't work... If it doesn't work out, thank you anyway for trying to help. Here the pluses can be put as on 4PDA?bm2dx.dllbm2dx.dllbm2dx.dllbm2dx.dllbm2dx.dllbm2dx.dllbm2dx.dll

log.txt 71.45 kB · 0 downloads FlexASIO.toml 180 B · 0 downloads spicetools.xml 114.95 kB · 0 downloads bm2dx.dll 18.55 MB · 0 downloads

 

[2023/05/15 16:25:25] W:signal: exception raised: EXCEPTION_ILLEGAL_INSTRUCTION
[2023/05/15 16:25:25] I:signal: printing callstack
[2023/05/15 09:25:27] M:ea3-pos: ea3_report_posev: "/coin/reset", 1
[2023/05/15 09:25:27] M:ea3-pos: ea3_posev_show_debug: slot[0]: coin 0, service 0, credit 0(0+0), from_coin 0, to_credit 0, player 0
[2023/05/15 09:25:27] M:ea3-pos: ea3_posev_show_debug: slot[1]: coin 0, service 0, credit 0(0+0), from_coin 1, to_credit 1, player 1
[2023/05/15 16:25:26] I:stackwalker: 0000000180205F29 (bm2dx): (unknown): (unknown)

 

seems like another illegal instruction error, I think it's because your processor does not support SSE4.1 (not just SSE4.2), I don't think there is any way to fix this to run on your 15 year old PC...sorry

 

Modifié par bicarus
Lien vers le commentaire
Partager sur d’autres sites

39 minutes ago, msdatada said:

image.png.d09a1ea53639a3dfc74a2e3b7277fdc9.png

What should I edit?

No editing is necessary.

 

If, however, you happened to encounter game crash after enabling the TDJ in spicecfg, first create a copy of ea3 file for backup (this is in case that editing that file causes to get corrupted), delete the first Japanese line and the whitespace in the second line.

Modifié par Funrto
Lien vers le commentaire
Partager sur d’autres sites

I'm looking for a way to battle play on the left turntable for both 1P and 2P.

I tried replacing the texture of gmframe, but the note array does not change.

Please tell me how to rewrite the note sequence.

 

I am using the translation function.

Sorry for the confusing words.

Lien vers le commentaire
Partager sur d’autres sites

17 hours ago, msdatada said:

log.txt 64.05 kB · 4 downloads

i got error.

how to clear this?

 

follow guide first - https://docs.google.com/document/d/1SFfRb9nQK-riCdKChFprocVr97TqUxYra63wSK2fplo/edit?usp=drivesdk

 

[2023/05/19 20:50:12] M:audio::wasapi: WrappedIAudioClient::Stop
[2023/05/19 20:50:12] M:audio::wasapi: WrappedIAudioClient::Reset
[2023/05/19 20:50:12] M:audio::wasapi: WrappedIAudioClient::Stop
[2023/05/19 20:50:12] M:audio::wasapi: WrappedIAudioClient::Reset
[2023/05/19 20:50:12] M:imgui_impl_spice: shutdown

 

Seems like the game is shutting down by itself (and then crashing), usually this is bad server configuration, or graphics issue (game window is closing by itself)

 

Using latest Asphyxia plugin? can you remove -smartea and -eamaint?

 

Can you try windowed mode?

 

Modifié par bicarus
Lien vers le commentaire
Partager sur d’autres sites

Thank you for your detailed instruction, I've follow the doc and download asphyxiaV1.40d and resident plugin 1.4d from the link attach in doc. Also, I check my audio smapling is set to 44100/16 bit.My laptop can run bistrover but failed when starting up resident, even quit in the terminal.

But when I run spice64, I got this problem. I have tried this on my two laptops, but still got the same. I also tried upgrate game from 2210 to 2212, with the step of replacing files with out bm2dx.dll, but same problem occured.

I searched the thread and found only one same case to me,  it seems problem of asphyxia server, but I used core from github latest release and plugin from the doc, even run with -ea, simulated by spicetool, same error occured.

I know this kind of problem can be difficult to troubleshoot and I would be very grateful if you could give me some information

[2023/05/20 17:08:39] W:signal: exception raised: EXCEPTION_ACCESS_VIOLATION
[2023/05/20 17:08:39] M:xrpc-module: module_add: 8: eacoin.opcheckout, verbose=1, text_xml=0, plain=0, esign=0, xrpc11=1
[2023/05/20 17:08:39] M:xrpc-module: module_add: 9: eacoin.getlog, verbose=1, text_xml=0, plain=0, esign=0, xrpc11=1
[2023/05/20 17:08:39] M:xrpc-module: module_add: 10: eacoin.getpricelist, verbose=1, text_xml=0, plain=0, esign=0, xrpc11=1
[2023/05/20 17:08:39] M:ea3-eacoin: ea3_eacoin_boot: work size for optbuf: 32768.
[2023/05/20 17:08:39] M:ea3-eacoin: ea3_eacoin_boot: work size for vstab: 32.
[2023/05/20 17:08:39] M:ea3-eacoin: ea3_eacoin_boot: work size for vslot: 816 x (2 + 2).
[2023/05/20 17:08:39] W:EXCEPTION: avs-printf-format-string.c:144
[2023/05/20 17:08:39] W:EXCEPTION: avs-printf-format-string.c:171
[2023/05/20 17:08:39] W:EXCEPTION: avs-printf-core.c:457
[2023/05/20 17:08:39] W:EXCEPTION: avs-printf-core.c:520
[2023/05/20 17:08:39] I:signal: printing callstack
[2023/05/20 17:08:39] W:EXCEPTION: logger-formatter-message-default.c:49
[2023/05/20 17:08:39] W:EXCEPTION: logger-api.c:191
[2023/05/20 17:08:39] W:EXCEPTION: logger-api.c:264
[2023/05/20 17:08:39] I:stackwalker: 00007FFA0425474C (KERNELBASE): (unknown): RaiseException
[2023/05/20 17:08:39] I:stackwalker: 00007FF99FB8953E (avs2-core): (unknown): XCgsqzn0000191
[2023/05/20 17:08:39] I:stackwalker: 00007FFA067A8386 (ntdll): (unknown): RtlCaptureContext2
[2023/05/20 17:08:39] I:stackwalker: 00007FF99FB2A445 (avs2-core): (unknown): XCgsqzn000017b
[2023/05/20 17:08:39] I:stackwalker: 00007FF9D15E9A59 (avs2-ea3): (unknown): XEmdwapa000017
[2023/05/20 17:08:39] I:stackwalker: 00007FF9D15F0D40 (avs2-ea3): (unknown): XEmdwapa000024
[2023/05/20 17:08:39] I:stackwalker: 00007FF7457675C6 (spice64): (unknown): (unknown)
[2023/05/20 17:08:39] I:stackwalker: 00007FF74567940E (spice64): (unknown): (unknown)
[2023/05/20 17:08:39] I:stackwalker: 00007FF7456313B1 (spice64): (unknown): (unknown)
[2023/05/20 17:08:39] I:stackwalker: 00007FF7456314E6 (spice64): (unknown): (unknown)
[2023/05/20 17:08:39] I:stackwalker: 00007FFA05C254E0 (KERNEL32): (unknown): BaseThreadInitThunk
[2023/05/20 17:08:39] I:stackwalker: 00007FFA0670485B (ntdll): (unknown): RtlUserThreadStart

 

log.txt

Lien vers le commentaire
Partager sur d’autres sites

11 hours ago, JhonLee said:

Thank you for your detailed instruction, I've follow the doc and download asphyxiaV1.40d and resident plugin 1.4d from the link attach in doc. Also, I check my audio smapling is set to 44100/16 bit.My laptop can run bistrover but failed when starting up resident, even quit in the terminal.

But when I run spice64, I got this problem. I have tried this on my two laptops, but still got the same. I also tried upgrate game from 2210 to 2212, with the step of replacing files with out bm2dx.dll, but same problem occured.

I searched the thread and found only one same case to me,  it seems problem of asphyxia server, but I used core from github latest release and plugin from the doc, even run with -ea, simulated by spicetool, same error occured.

I know this kind of problem can be difficult to troubleshoot and I would be very grateful if you could give me some information

[2023/05/20 17:08:39] W:signal: exception raised: EXCEPTION_ACCESS_VIOLATION
[2023/05/20 17:08:39] M:xrpc-module: module_add: 8: eacoin.opcheckout, verbose=1, text_xml=0, plain=0, esign=0, xrpc11=1
[2023/05/20 17:08:39] M:xrpc-module: module_add: 9: eacoin.getlog, verbose=1, text_xml=0, plain=0, esign=0, xrpc11=1
[2023/05/20 17:08:39] M:xrpc-module: module_add: 10: eacoin.getpricelist, verbose=1, text_xml=0, plain=0, esign=0, xrpc11=1
[2023/05/20 17:08:39] M:ea3-eacoin: ea3_eacoin_boot: work size for optbuf: 32768.
[2023/05/20 17:08:39] M:ea3-eacoin: ea3_eacoin_boot: work size for vstab: 32.
[2023/05/20 17:08:39] M:ea3-eacoin: ea3_eacoin_boot: work size for vslot: 816 x (2 + 2).
[2023/05/20 17:08:39] W:EXCEPTION: avs-printf-format-string.c:144
[2023/05/20 17:08:39] W:EXCEPTION: avs-printf-format-string.c:171
[2023/05/20 17:08:39] W:EXCEPTION: avs-printf-core.c:457
[2023/05/20 17:08:39] W:EXCEPTION: avs-printf-core.c:520
[2023/05/20 17:08:39] I:signal: printing callstack
[2023/05/20 17:08:39] W:EXCEPTION: logger-formatter-message-default.c:49
[2023/05/20 17:08:39] W:EXCEPTION: logger-api.c:191
[2023/05/20 17:08:39] W:EXCEPTION: logger-api.c:264
[2023/05/20 17:08:39] I:stackwalker: 00007FFA0425474C (KERNELBASE): (unknown): RaiseException
[2023/05/20 17:08:39] I:stackwalker: 00007FF99FB8953E (avs2-core): (unknown): XCgsqzn0000191
[2023/05/20 17:08:39] I:stackwalker: 00007FFA067A8386 (ntdll): (unknown): RtlCaptureContext2
[2023/05/20 17:08:39] I:stackwalker: 00007FF99FB2A445 (avs2-core): (unknown): XCgsqzn000017b
[2023/05/20 17:08:39] I:stackwalker: 00007FF9D15E9A59 (avs2-ea3): (unknown): XEmdwapa000017
[2023/05/20 17:08:39] I:stackwalker: 00007FF9D15F0D40 (avs2-ea3): (unknown): XEmdwapa000024
[2023/05/20 17:08:39] I:stackwalker: 00007FF7457675C6 (spice64): (unknown): (unknown)
[2023/05/20 17:08:39] I:stackwalker: 00007FF74567940E (spice64): (unknown): (unknown)
[2023/05/20 17:08:39] I:stackwalker: 00007FF7456313B1 (spice64): (unknown): (unknown)
[2023/05/20 17:08:39] I:stackwalker: 00007FF7456314E6 (spice64): (unknown): (unknown)
[2023/05/20 17:08:39] I:stackwalker: 00007FFA05C254E0 (KERNEL32): (unknown): BaseThreadInitThunk
[2023/05/20 17:08:39] I:stackwalker: 00007FFA0670485B (ntdll): (unknown): RtlUserThreadStart

 

log.txt43.68 kB · 1 download

 

You have:

W:mounttab: boot(/dev/nvram2,/dev/nvram) mount error(80070011)

 

Follow the guide again and see the section about the error above on how to fix, and try again

 

 

Lien vers le commentaire
Partager sur d’autres sites

  • 2 semaines après...
31 分前、Zen_B7 さんはこう言いました:

はい、ページ右上の検索を使用してください。答えはこのスレッドの 35 ページにあります。

Thanks for letting me know right away.

Lien vers le commentaire
Partager sur d’autres sites

11 hours ago, meru_golang said:

I tried downloading LDJ-003-2022103100 as per the available documentation, but TDJ is not functioning. I have applied all the necessary patches and steps, but it still doesn't work. Do you know how to resolve this issue?log.txt

 

[2023/06/05 00:52:42] I:graphics::d3d9: D3D9Ex fullscreen display mode for adapter 0: Width: 1920, Height: 1080, RefreshRate: 60, Format: D3DFMT_X8R8G8B8, ScanLineOrdering: 1

 

The game failed to launch at 1080p@120hz so you probably get a monitor error. Usually solved by setting GPU resolution scaling in NVIDIA control panel or similar

 

[----/--/-- --:--:--] W:mounttab: boot(/dev/nvram2,/dev/nvram) mount error(80070011)

you also have nvram mount error, see guide for how to fix

https://docs.google.com/document/d/1SFfRb9nQK-riCdKChFprocVr97TqUxYra63wSK2fplo/edit#heading=h.kq3q8goqednp

 

 

Modifié par bicarus
Lien vers le commentaire
Partager sur d’autres sites

Veuillez vous connecter pour commenter

Vous pourrez laisser un commentaire après vous êtes connecté.



Connectez-vous maintenant
×
×
  • Créer...