I've had the same issue for a few days but I read in another post that someone had fixed this by deleting the Dynamic.Hogg file in your Star trek Online/Live/Piggs folder , worked for me .
I don't think I've had this problem. I have gotten a Fatal error that booted me from the game a few times but aside from a few things like that I've been able to get my exploration dailies done. I hope you get whatever it is sorted out.
Having the same problem, each attempt I have to shut down the game, and start my character in a safe zone. Reported multiple times, and no response from Cryptic.
Cryptic's last official response on this issue was that it was user error, a problem with peoples' firewalls, and as such, it's doubtful they'll ever bother to fix it.
Oddly enough, the people who have deleted the dynamic.hogg file have had few to no reported problems since doing so.
Where did that dynamic.hogg file come from?
Oh right ... user error. firewalls. not a cryptic support issue at all.
Dynamic.hogg has to be on your computer. I just renamed mine to something else and it fixed the problem I was having with this and the client created a new dyanmic.hogg file.
Cryptic's last official response on this issue was that it was user error, a problem with peoples' firewalls, and as such, it's doubtful they'll ever bother to fix it.
Oddly enough, the people who have deleted the dynamic.hogg file have had few to no reported problems since doing so.
Where did that dynamic.hogg file come from?
Oh right ... user error. firewalls. not a cryptic support issue at all.
:(:eek:
Funny you say that. Several days back, the game was running fine. During a gaming session, things were great. I got a new exploration mission and attempted to zone into the mission. Game ended up booting me to the login citing it couldn't get the server address.
At no point was a firewall involved except at my router and it's never cared one way or another about STO. Game has never given me this issue before.
I deleted the dynamic.hogg file and voila! The game works again and I can zone in. Interestingly, the more missions I go into, the LARGER dynamic.hogg gets. I'll bet it got some corrupted data inserted into it and when I tried to zone into an exploration mission, the client read the bad data and crapped out.
Besides, even telling the router's firewall to allow all traffic regardless of source for my laptop (where I play STO) made no difference. Even a naked direct connection made no difference. AV was fully disabled too when I was testing those 'suggestions'.
Yet deleting a client generated file that apparently grows the more missions you do worked flawlessly with all my normal security measures in place.
/sarcasm on
Yep, that certainly means it's a user's firewall or AV. Certainly can't be an intermittent bug in the client putting bad data in a file...
/sarcasm off
Comments
Oddly enough, the people who have deleted the dynamic.hogg file have had few to no reported problems since doing so.
Where did that dynamic.hogg file come from?
Oh right ... user error. firewalls. not a cryptic support issue at all.
:(:eek:
zone into clusters....
So, what is the next fix I should try?
Look in the: Star trek Online/Live/Piggs folder
Funny you say that. Several days back, the game was running fine. During a gaming session, things were great. I got a new exploration mission and attempted to zone into the mission. Game ended up booting me to the login citing it couldn't get the server address.
At no point was a firewall involved except at my router and it's never cared one way or another about STO. Game has never given me this issue before.
I deleted the dynamic.hogg file and voila! The game works again and I can zone in. Interestingly, the more missions I go into, the LARGER dynamic.hogg gets. I'll bet it got some corrupted data inserted into it and when I tried to zone into an exploration mission, the client read the bad data and crapped out.
Besides, even telling the router's firewall to allow all traffic regardless of source for my laptop (where I play STO) made no difference. Even a naked direct connection made no difference. AV was fully disabled too when I was testing those 'suggestions'.
Yet deleting a client generated file that apparently grows the more missions you do worked flawlessly with all my normal security measures in place.
/sarcasm on
Yep, that certainly means it's a user's firewall or AV. Certainly can't be an intermittent bug in the client putting bad data in a file...
/sarcasm off