I have the same issue. The game can't load or is having issues with the "Crd_Ds9_Ground.Zone" file. Claiming it dosn't exist or is the wrong version when the launcher has verified 100%
Same issues. If I load a character not on DS9 everything is fine and as soon as they beam over to ds9 poof the game disapears and only the error message about the crd_DS9_Ground.Zone is left and 2 of my characters are trapped on ds9
why is there no official reply ... same problem with crd_DS9_Ground.Zone ffs... i don't want to reinstall my entire game, i don't have such a good internet connection, and it's limited.
I found a thread on reddit, that was saying "You need to delete the data.hogg and bins.hogg files for the Launcher to redownload those two files which will allow you access to DS9 again", but sadly I can't find those data.hogg and bins so i can delete them. Anyway, sad there is so poor reply on forum.
if you can't force verify another player said make sure having BOTH "on-demand patching" UNTICKED, AND force verify TICKED. (edited 25/10 for clarification to avoid a mislead)
And then (save and restart launcher if needed - unsure) LET it force verify as it wants.
I am unsure this is your issue but it's one of the solution to some crash types.
(Disclaimer - verification after 1st crash/1st time slow load+time out on server, or mismatch version on the AoD launch day, worked for me, but I probably had "on demand patching" disabled anyway from before and that's why it worked "auto", then. OTHER player suggested to TICK froce verify+UNTICK on-demand patching (and let it force verify) and it works for others with some but not all issues. There were other issues such as windows 10's October update effect causing issues.)
if you can't force verify another player said make sure BOTH "on-demand patching" AND force verify are checked.
@rndflactuation got it half correct. The difference is you need to make sure "On-demand patching" is UN-checked. This is what forces the game to patch the missing/crc-failed maps.
Later in the same post, rndflactuation also got it right:
Yes, to clarify, it was seemingly a VERY unfortunate accidental omitting mistake of one word - UNTICK, in one place.
I really apologize, didn't mean to mislead. I will edit the post (with a clear edit in this regard)
P.S.
Sorry, you were probably the poster whom in his posts I saw this solution initially (though I though it was another player named speedy something, it looks like it was you) but forgot your name then
Comments
It's suspicious the devs have been so quiet over all the bugs that came with AoD and the critique.
And then (save and restart launcher if needed - unsure) LET it force verify as it wants.
I am unsure this is your issue but it's one of the solution to some crash types.
(Disclaimer - verification after 1st crash/1st time slow load+time out on server, or mismatch version on the AoD launch day, worked for me, but I probably had "on demand patching" disabled anyway from before and that's why it worked "auto", then. OTHER player suggested to TICK froce verify+UNTICK on-demand patching (and let it force verify) and it works for others with some but not all issues. There were other issues such as windows 10's October update effect causing issues.)
https://www.arcgames.com/en/forums/startrekonline#/discussion/1244067/age-of-discovery-won-t-launch
Short summary: You need to turn ON "Force verify" AND turn OFF "On-demand patching".
@rndflactuation got it half correct. The difference is you need to make sure "On-demand patching" is UN-checked. This is what forces the game to patch the missing/crc-failed maps.
Later in the same post, rndflactuation also got it right:
I hope this helps you as it has several other players.
I really apologize, didn't mean to mislead. I will edit the post (with a clear edit in this regard)
P.S.
Sorry, you were probably the poster whom in his posts I saw this solution initially (though I though it was another player named speedy something, it looks like it was you) but forgot your name then