Anyone else dumped off a fleet carrier while offline?

I'd decided to return to the bubble, as ED is on the back burner a bit, and massacre missions to fund the FC are easier to find there.

So I parked up on the Kapisi, in Kinesi, called my other four ships to the carrier, and logged off.

The carrier was due to arrive on the 3rd, so today I logged in, expecting to still be in the Kapisi's shipyard, but instead I was looking down on Kinesi 1, and as I had to align myself with the escape trajectory before going anywhere, it was clearly assumed I had crashed into the planet.

My other ships are all in Ijo, the carrier's destination, and the Jon Altriani Sleeper Service from Tir leaves at 2200 today, so no worries, but a bit weird. Update glitch?
 
Was it YOUR carrier or anothers players..
FC owners can turn landing permission OFF... This will eject alll Players from FC...
So if the FC goes Friends or squad or None... every body gets kicked out at what ever location the change is made
For your equipment to get booted they have to disable ship yard and outfitting... which then boots the items/ships to nearest station...
 
Last edited:
Was it YOUR carrier or anothers players..
FC owners can turn landing permission OFF... This will eject alll Players from FC...
So if the FC goes Friends or squad or None... every body gets kicked out at what ever location the change is made
For your equipment to get booted they have to disable ship yard and outfitting... which then boots the items/ships to nearest station...

This was a Fleet Carrier Owners Club Discord thang, so (much as I hate disagreeing with people), that seems unlikely.

If the owner did do it, for whatever reason, it's interesting that my other ships stayed on. I guess that would be the shipyard, though.
 
I had an issue a while back where I'd just touched down on my Carrier that was about to jump. I'd touched down and got the usual "clonk" and the menu popped up briefly, allowing me to interact. Then, before I'd touched anything, I was rudely ejected from the Carrier and it started the jump sequence, so I could not dock...even though I had just been docked. I assumed it was some weird sync issue, where I'd docked successfully client-side (aka my PC) but the servers thought I'd not touched down yet. I've seen weird sync (I assume) issues like this in the past too. For example, I've just successfully exited SC at the station instance, then I'm suddenly being interdicted as if I'd not left SC. Or how about the classic "loop of shame" resulting from the countdown going 10...9...8...7.4321 suddenly, despite being at 50% throttle the entire time.

Anyway, these example are all when the sync is perhaps just slightly out. I've never landed before, logged off, and been (or not been as in your case) somewhere else entirely... that I remember at least.

Is it possible the Carrier was full, and then the Carrier owner decided to dock so some ships got kicked? Is the 40 ship limit actually enforced in that regard?
 
I had an issue a while back where I'd just touched down on my Carrier that was about to jump. I'd touched down and got the usual "clonk" and the menu popped up briefly, allowing me to interact. Then, before I'd touched anything, I was rudely ejected from the Carrier and it started the jump sequence, so I could not dock...even though I had just been docked.

You can't enter a carrier while it's in lockdown, 5 minutes before jump, that's when all the retractable landing pads get pulled in and the landing pad covers slide over to secure the carrier. So you weren't docked, you were just sitting on the outside of it, I would have thought it should refuse you landing permission, but apparantly that's not exactly how it works.
 
You can't enter a carrier while it's in lockdown, 5 minutes before jump, that's when all the retractable landing pads get pulled in and the landing pad covers slide over to secure the carrier. So you weren't docked, you were just sitting on the outside of it, I would have thought it should refuse you landing permission, but apparantly that's not exactly how it works.

I knew my timing was tight before I'd be locked out. But I appeared to touch-down and the menu popped up briefly before I was ejected.

Btw: I know I said "Started the jump sequence" but I meant the start of the lock-down period, not the actual opening of the warp tunnel animation. I've docked on my Carrier when it's preparing to jump numerous times previously, but never quite so last-minute as this time. Still, I had touched down, but game suddenly changed its mind. Can't explain it, other that some weird sync issue where I'd docked successfully, but the Server didn't get the message until after the lock-down had kicked in.
 
I knew my timing was tight before I'd be locked out. But I appeared to touch-down and the menu popped up briefly before I was ejected.
I've had that....
Was in close race with the carrier jumping
Got permission to land, gear out... just touched the pad and boof
Lockdown.. no more docking.
Then my carrier jumped 500 ly and I spent 30 mins catching up with it in a python with a class 3 scoop and a 30ly jump range

Bill
 
FC owners can turn landing permission OFF... This will eject alll Players from FC...
So if the FC goes Friends or squad or None... every body gets kicked out at what ever location the change is made
Are you sure about that? You seem certain, but I think I checked how that works with my alt Epic account and as far as I remember (it was long time ago though) it did not work like that. If I remember correctly, it doesn't change anything for someone who is already docked, so it doesn't kick anyone out - you just can't dock back once you leave.
Maybe I got this wrong, but if it works how you describe it, then I'm kind of shocked - first of all it would mean I was assuming something wrong for a long time, and secondly it would be great tool for griefers, so I'm surprised we don't hear about people stranded in the middle of nowhere, when they were promised trip to Colonia f.ex.
 
I knew my timing was tight before I'd be locked out. But I appeared to touch-down and the menu popped up briefly before I was ejected.

Btw: I know I said "Started the jump sequence" but I meant the start of the lock-down period, not the actual opening of the warp tunnel animation. I've docked on my Carrier when it's preparing to jump numerous times previously, but never quite so last-minute as this time. Still, I had touched down, but game suddenly changed its mind. Can't explain it, other that some weird sync issue where I'd docked successfully, but the Server didn't get the message until after the lock-down had kicked in.

Well, .001 of a second late is .001 of a second late. I'm not sure how fine they do the timings but pushing it close can mean that close and not being able to dock, I try not to let it get that close myself (y)
 
Well, .001 of a second late is .001 of a second late. I'm not sure how fine they do the timings but pushing it close can mean that close and not being able to dock, I try not to let it get that close myself (y)

But I wasn't late, things were close (not part of the plan lol) but I had docked and the Carrier menu popped up briefly. The timings were tight, very tight, but I had docked and the menu had popped up for a couple of seconds before I was ejected. This is why I think it's a weird sync thing. Or, do you HAVE to be in the hangar and not still on a pad once the lock-down starts? Could still being sat on the pad be the issue?

I had another sync issue last night, one I've had before. I was in SC heading for a station, I got the safe exit message and did just that. The usual leaving SC screen effect came up then, a second or so into this effect, I was interdicted. So, from my (client) perspective I was already at the station, waiting for the station instance to load. During that "loading screen" I got interdicted. After I destroyed my attacker - wimpy attacking ship, me with no cargo or bounty sigh - I saw I'd been teleported over 10x the distance away from the station vs. where I was. Not a problem, but equally not quite right either.

So, events must somehow be getting out of sync with the server "correcting" things as it sees fit. It's the only explanation I can think of - other than the on the pad rather than in the hangar one. I still cannot quite understand what happened in the OP's case though, as it wasn't an issue of tight timing at all. I'd expect just a random gremlin...they happen in ED....from time to time lol.
 
I've had that....
Was in close race with the carrier jumping
Got permission to land, gear out... just touched the pad and boof
Lockdown.. no more docking.
Then my carrier jumped 500 ly and I spent 30 mins catching up with it in a python with a class 3 scoop and a 30ly jump range

Bill

I had something quite similar to that. It was a while ago now, so the details are a little hazy, except for possibly the one small detail of my ship blowing up...

Anyone else noticed that when you've been scanning some planets before the jump, and rushing back because you took a chance on getting one more planet, that as you come out of SC and select auto-docking, the screen tells you that you're already doing so, so you have to either leave it, or cancel docking and do it again manually, just to be sure?

I'd love to think Frontier put in some code to help stragglers SC-ing to the carrier, but so far I've never taken the chance, and at least once, found myself locked out, because I cancelled.
 
Back
Top Bottom