djhackersdev / bemanitools

Runs recent Konami arcade games and emulates various arcade hardware.
The Unlicense
84 stars 16 forks source link

IIDX GOLD does not connect to Arcana network #88

Closed icex2 closed 1 year ago

icex2 commented 3 years ago

In GitLab by @furu311 on Aug 27, 2021, 19:46

Please teach me how to fix it. I tried to connect IIDX GOLD to the Arcana network, but I get "NETWORK : SERVICES" and cannot connect.

I used "bemanitools v5.35" and placed the files in the GLD / 2007022101 folder. When I edited "iidxhook-14.conf" and started the game, the following error occurred.

eamuse.server=http://xrpc.arcana.nu ->5-2002-1013 error.

eamuse.server=http://xrpc.arcana.nu:80 ->5-2002-2400 error.

What you have done so far. -Router port:80 open. -I own an Arcana account and use the "PCBID" I created. -Disable other network adapters left one. -Disable firewall. -Other statuses indicate "OK" and will boot normally offline.

Hardware specs OS : Windows 10 Home CPU: Core i7 2600 3.40ghz GPU: GTX980 RAM: 16GB

icex2 commented 3 years ago

Please upload your full iidxdhook-14.conf file as well as a full log output. Make sure to search (ctrl+f) for your PCBID and replace it with [REDACTED] in the config and log files.

icex2 commented 2 years ago

In GitLab by @Stikam on Sep 23, 2021, 13:11

Actually, it's not a problem with GOLD, it's a problem for every game that uses 14-17 hook. I can confirm that 16 and 17 has the same issue (can't say anything about 15 since I can't boot it but that's another topic UPD: well, despite that I can't boot into 15, it gives SERVICES in network check, so 14-17 hook has an issue with network). Other IIDX with the same PCBID and service URL work fine (tested in 9-13)

icex2 commented 2 years ago

I assume the IIDX 15 problem might be related to this "I cannot figure this damn thing out" issue which has been bugging me now for a long time (and many other people also).

The network part however is still news to me and I would treat it as a separate issue at least in its current state (until further evidence).

So far, @furu311 didn't come back with error logs and a full dump of the config file and commands to execute used. Maybe you can help me out here.

icex2 commented 2 years ago

In GitLab by @Stikam on Sep 23, 2021, 19:27

iidxhook-15.conflog15.txt

Well, unfortunately I don't have access to my main setup right now, I'll post it logs later but at least here is my log and config file from my home PC for DJ TROOPERS (and yes, it crashes, but before that it fully completes all checks and gives NETWORK SERVICES). UPD: Forgot to mension - I'm using v.5.35

PC:

OS: Windows 10 Pro Version: 20H2 Build: 19042.1237

CPU: Intel(R) Core(TM) i7-4770K CPU

GPU: GTX 970

RAM: 24 GB DDR3

icex2 commented 2 years ago

In GitLab by @Stikam on Sep 24, 2021, 14:59

Ok, I've got to my main setup here are logs with bootable games that give SERVICE error. I was closing them when I reached network error. iidxhook-14.conflog14.txtiidxhook-16.conflog16.txtiidxhook-17.conflog17.txt

Here is a DJ Troopers log that can't be booted to the game but gives SERVICE in checks

iidxhook-15.conflog15.txt

And here are examples of successful boots with other old hooks These are from iidxhook1 (9th style) iidxhook-09.conflog09.txt And iidxhook2 (13 DistorteD) iidxhook-13.conflog13.txt I closed these games after they reached title screen

Specs: Using specific iidxio for C02 board Bemanitools v5.35 OS: Windows 10 Pro N, Version: 20H2, OS build: 19042.1237 CPU: Intel Core i5-3550 GPU: GTX 465 RAM: 8 GB

icex2 commented 2 years ago

Dumb question but are you using "clean" data, i.e. data that is unmodified from a original HDD and does not contain any hex edits or already swapped out DLLs?

Can you show me the contents of the directory H:\OLD IIDX\15 DJ TROOPERS (NOT WORKING)\HDD\2008031100\, H:\OLD IIDX\16 EMPRESS\I00\2009072200 and the other dirs that contain the bm2dx.exe?

icex2 commented 2 years ago

In GitLab by @Stikam on Sep 24, 2021, 20:38

I can't show contents of my folders right now but the data itself is definetly clean. Here are all permalinks that I snatched (they are freeleech, so it's not a big deal to redownload and test these games again): 14 gold - https://bemaniso.ws/torrents.php?torrentid=8191 15 dj troopers - https://bemaniso.ws/torrents.php?torrentid=19214 16 empress - https://bemaniso.ws/torrents.php?torrentid=19647 17 sirius - https://bemaniso.ws/torrents.php?torrentid=19647

icex2 commented 2 years ago

In GitLab by @Stikam on Sep 26, 2021, 08:58

Ok, I've managed to redownload gold (14) just to make sure that everything is right. Here is a folder without any modifications initial After that I placed all bemanitools files and started to boot the game. After first boot it looks like this after_first_boot Here is a log (I closed the windows game, and then the cmd output after getting network error) log.txt iidxhook-14.conf It was done on my home pc setup, so the paths are a little bit different but I get exactly the same error as in other setup.

icex2 commented 2 years ago

In GitLab by @Stikam on Sep 27, 2021, 08:14

I think I found solution for this problem. In order to fix this you need to set both PCBID AND EAMID to the one that you created in arcana. I only tested it in dj troopers using kactools-a14, so I need to confirm that this actually works on latest v5.35 as well as other games.

P.S. Despite that I can't boot dj troopers with v5.35, the network error is actually gone

UPD: Tested on my main setup with C02 and now 14-17 are working with arcana

icex2 commented 2 years ago

Awesome ideas and drive to try out stuff.

I revisited the relevant parts and did some testing. Since my setup is fully automated regarding deploying any bemanitool changes, this never occured to me because I set the EAMID always to the same value as the PCBID.

The iidxhook3 docs were already stating to set them to the same ID. However, considering that the other games do not require you to do this, I think this deserves additional emphasis with reasoning.

Was able to reproduce this locally with a local server test instance.

Thanks for digging into this on your own. This is already a great contribution and definitely reduced the workload and effort on my end to get down to the "root cause" of this issue.