forked from Hay1tsme/segatools
WACCA Reverse (SDFE) 3.07.01 - Error 4103-0 in Mercury and Code 1201 in amdaemon #5
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Issue
When launching WACCA Reverse, the following issues occur:
ARTEMiS seems to have received the game requests and ALL.NET auth, despite that the ALL.NET icon remains gray (disconnected)
System/game info
a8bd98706f)Extra question
It would be appreaciated if you could clear up this question for me:
Logs
(If you want the logs to be put in a bin instead of this issue to not make the issue long, please let me know at the replies)
Screenshots
Hello!
Well written issue, it was very easy to read and everything for debugging was provided!
This sounds like a dump issue to me or maybe you missed an update. WACCA Reverse 3.07.01 requires the following updates/version:
3.00.00 -> 3.01.00 -> 3.02.00 -> 3.03.00 -> 3.04.00 -> 3.05.00 -> 3.06.00 -> 3.07.00 -> 3.07.01
Make sure to delete everything and start extracting it in the correct order and overwrite everything.
ICF1 and ICF2 are the identical files and are only used for upgrading the version number on an original ALLS. For typical use ICF1 is the only one you really need.
Those issues you are getting also seems to be connected to a bad dump or missing files. So my recommendation is still the same.
I hope that actually is the issue and it helps :)
Hi, thanks for replying to my issue:
3.00.01? I'm assuming you mean 3.07.01. I believe I've extracted the dump in this order (replacing any existing file from lowest to newest), I have all the SDFE version dumps:
I see, thank you for clarifying this
Another thing interesting to note, 4103-0 occurs even on version 3.10.0, which is the offline patch. Do you think it's a issue with my system or just some bad dump?
Edit:
Same issue on 3.00.00
Edit 2:
I would like to try anything that I can possibly do to fix the issue before assuming the dump is bad. If you want, I can record the installation process and upload the video to Google Drive if you would like
Edit 3:
Installation process
https://drive.google.com/file/d/1aZ1BdG3iWi2wqPj1L6_LDE_R0WS2Fjf2/view?usp=sharing
I would try a different source for the game dumps as it still shows the same errors...
It could be that your 3.00.00 dump might be bad. Just in case, because I have not other idea where that issue could come from to be honest.
I see, I'll see if I can find another source for the dumps then
By any chance, it is possible for you to share a method to extract a
.appfile to a vhd? Or are all the methods just private?This is not related to segatools and I sadly cannot help you with that. Let me know if another dump will work, I will keep the issue open.
Cheers 🎉
I haven't changed my dump (I've found a new source, but it will take a while to download it all in), after reading through the configuration files I tried a particular setting and this allowed the game to boot in.
I did notice the ALL.NET icon remained in a disconnected state, but regardless of that online functions still work fine... Wonder what's up with that
Also, the LED check still fails
Please dont tell me you set
bEnableErrorWatcher=falsein DefaultHardware.ini because that just ignores all errors and will result in an always gray ALL.Net logo, please ust get a proper dump at this point.Yeah,
I've tried a completely different dump, same 4103 error occurs with the same errors.
Some possible reasons I've figured out is either:
Another thing I've noticed, every first time you run the game, amdaemon always gives out a
setAppRootPatherror (see logs for more details)amdaemon errors
Mercury errors
Not impossible but could indeed happen.
I highly doubt it as long as its Win 10, it would work.
It's UE4 with c++ so i also doubt that is the issue, the only issue is the OpenSSL issue on Intel 10th gen or higher,
Maybe but youc an just grab the working compield segtaools from the Releases tab.
This should only happen on teh first launch in fact and never again.
I also encountered this problem
I think it’s not a problem with the system version
Previously, I encountered 4103-0 errors when running
under Windows 11 23H2.
The same error appears under Windows 10 LTSC 21H2
I tried disabling amdaemon or bEnableErrorWatcher and found that both methods can make the game run, but the ALL.Net logo is not connected to the Internet.
Alright, I'll try that.
(I was not aware there was a pre-compiled binary - most segatools repo doesn't include any pre-compiled binary so my assumption was to always compile it myself)
Edit:
The amdaemon error has changed:
Following error persists:
At this point, I'm somewhat sure that this is my issue and isn't a tooling issue, I will close this issue eventually.
@Dniel97 It looks like the
amGfetcherInit()error code also happens when I try to run Initial D: THE ARCADE Season 2, with the following error:Notably, it doesn't happen with CHUNITHM Sun Plus or CHUNITHM Paradise Lost
Check out the FAQ for common SEGA error codes:
https://gitea.tendokyu.moe/Dniel97/SEGAguide/wiki/FAQ#amgfetcherinit-errcode--1. Also keep in mind that the amdaemon.exe from Initial D THE ARCADE is HtPec packed and cannot be used with segatools by default. Make sure to unpack amdaemon.exe.
Also having this issue with 4103-0 error in Wacca and 1201 error in amdaemon. Tried multiple different segatool builds and multiple dumps on multiple computers, all with the same issue. I'm pretty sure this is an error with a missing dll and I was able to fix it by doing the following:
CDM-v2.12.36.4-WHQL-Certified/amd64/ftd2xx64.dllintoWindowsNoEditor/Mercury/Binaries/Win64ftd2xx64.dlltoftd2xx.dllThe installation information menu still shows unknown application data for some reason; probably an unrelated issue.
NO WAY! Good catch! I already had that driver installed for other programming related tools so I haven't noticed that. After removing it, I was able to confirm the exact same behavior.
So that is an easy fix if you know that it is the issue. Thanks! I will close the issue now.