That's if they teleport you back to the correct station. My friend got randomly teleported to a system he's never been before 200 ly away (without his ship).
Hopefully your friend did open a support ticket...
That's if they teleport you back to the correct station. My friend got randomly teleported to a system he's never been before 200 ly away (without his ship).
Yesterday my game crashed while disembarking from my ship after landing at a CZ (stuck black screen with infinite footsteps). Fearing the worst, I logged back in... and found myself in the CZ, disembarked, ready to go. Not sure why I didn't get booted, maybe because I hadn't picked a side yet?Especially great when the game crashes.
I haven't done any ground CZs yet (can't wait to experience this changeWell, ugh. I do not like this change.
Also, before the latest update, I was getting around 50fps in GCZs, now I'm getting around 30fps. Anyone else's performance drop with this update?
I agree. The dude didn't understand the issue at all.An "intended change" that can transport you across the galaxy without a ship, just for closing the game? I think the support rep didn't fully understand the question they were answering.
Holy Crap. That is beyond words.This change makes absolutely no sense. For example:
- Fly to Colonia from the Bubble.
- Go straight to a ground CZ without docking anywhere.
- Relog, either intentionally (exit to menu) or unintentionally (game crash).
- Log back in to find yourself back in the bubble with your ship still in Colonia.
Another example for fdev (short form for failed developement). Seriously, if FDevs intention is, having only braindead people, who think it is fun staring at the screen for 10 minutes, watching a poor coded AI, chauffeur you to a CZ, or unemployed people, who have the time to do so and dont care about how stupid it is, yes... if thats their intention, they made a perfect job.I've actually beenabusing this intended mechanic by last docking at a station owned by a faction that will go hostile with me after some more hostile actions and then relogging at a foot CZ to get back teleported there after I've done my many crimes so I can turn in a small amount of bonds/bounties to get away from hostile reputation.
You forgot the part where you have to waste 5 minutes running to your ship before taking off.Take off, hit supercruise, bank around and land, kill them all over again.
Nah, just park a srv close but out of the line of fire. Unless you like running, then by all means, you do you.You forgot the part where you have to waste 5 minutes running to your ship before taking off.
If relogging was an exploit, then no-one would get engineer updates.Why not? Relogging is an exploit isn't it?
It absolutely is an exploit. But I agree with your condition (if... then). If relogging never was an option in the first place maybe some effort had been made to make engineering more accessible for the common person that doesn't play the game for 16 hours per day.If relogging was an exploit, then no-one would get engineer updates.
It absolutely is an exploit. But I agree with your condition (if... then). If relogging never was an option in the first place maybe some effort had been made to make engineering more accessible for the common person that doesn't play the game for 16 hours per day.
If it was per design they could've just added a 'reset instance'-button to our cockpits.It's got nothing to do with accessibility, you literally have to log out and in again to get your engineer updates, (specifically Kit Fowler, Yarden Bond, Wellington Beck, Oden Geiger). As designed by the game developers. Relogging is a function of gameplay.
They could also have given us a cockpit button to request docking, but they chose not to.If it was per design they could've just added a 'reset instance'-button to our cockpits.
And, of course, no-one is in their cockpit when they need to relog, and none of the Odyssey interface is in any way compatible with the previous UI.They could also have given us a cockpit button to request docking, but they chose not to.
The issue could not be loaded.