Notice Fleet Carrier Update - Known Issues

Does anyone knows if it's possible for a save file to actually be corrupted on the Frontier server? For eksempel something happens like buying a FC, and it fails so many times so you end crashing your save...
 
Does anyone knows if it's possible for a save file to actually be corrupted on the Frontier server? For eksempel something happens like buying a FC, and it fails so many times so you end crashing your save...
@Za1zeR
This happened to me during beta...the fix was log out of the launcher, and log back in.
See if that helps.

Clicker
 
I also participated in beta 2 and am experiencing black adder whenever I attempt to purchase.

This persisted when I attempted to purchase in a system that only had 3-5 other carriers present, so it does not appear as if it is being caused an excess of other carriers in system, in my case at the very least.
 
One issue I noticed when my FC failed to purchase is that it had the same fixed name as it did in Beta 2. I then looked in my log file and found this. Which leads me to think that those having the crash are the ones who participated in Beta 2.

{23:30:26GMT 4396.067s} Webserver request failed: code 403, details 'eeKfoiscZZPAod8DhHyfxicliHpN22JX8iAJGv2wbh3xsQIksUQxOCXmETUnM6b2L0qPIXyjlYcAL+gvdX7J3SwXwxke3AOFnB+8PcFBnlyoG9qzxdzTxDmKaVU6EkkX+S+6HoR6pP/VDM0WndwqdXrHGD6Jkqd5xZY7yIIi'
{23:30:26GMT 4396.067s} Webserver request: https://api.orerve.net:443/2.0/elit...46Am0Z8R+g6JEOi0D6bC6e2eoIs3KMktnIYFVb8gFSxU4...
Plaintext error response: {"status":403,"message":"Helper\\FleetCarrier::spawnCarrier Failed to spawn Fleet Carrier 1600684 because we are already spawned"}
If this is the true cause of this bug its the last time I logged in any beta for ED... EVER
 
As it’s now approaching midnight in Frontier local time, the development team are getting some well-earned rest along with the community team as well! We’ll be back in the morning to continue investigating these issues and updating you on fixes for them as soon as we can.
Get some shuteye all y'all. We can wait until morning.

iu
 
One issue I noticed when my FC failed to purchase is that it had the same fixed name as it did in Beta 2. I then looked in my log file and found this. Which leads me to think that those having the crash are the ones who participated in Beta 2.

{23:30:26GMT 4396.067s} Webserver request failed: code 403, details 'eeKfoiscZZPAod8DhHyfxicliHpN22JX8iAJGv2wbh3xsQIksUQxOCXmETUnM6b2L0qPIXyjlYcAL+gvdX7J3SwXwxke3AOFnB+8PcFBnlyoG9qzxdzTxDmKaVU6EkkX+S+6HoR6pP/VDM0WndwqdXrHGD6Jkqd5xZY7yIIi'
{23:30:26GMT 4396.067s} Webserver request: https://api.orerve.net:443/2.0/elit...46Am0Z8R+g6JEOi0D6bC6e2eoIs3KMktnIYFVb8gFSxU4...
Plaintext error response: {"status":403,"message":"Helper\\FleetCarrier::spawnCarrier Failed to spawn Fleet Carrier 1600684 because we are already spawned"}


I bought a Carrier in beta 1... not in beta 2 .. but did join beta 2 for about 30 min to check on hotspots

maybe its both
 
I just plotted a route from an orbital station. While sitting in the station in my ship I can see the next jump yellow system ring as if I was outside
 
Back
Top Bottom