Carrier Jumping Without Me...

[Carpe Noctem 0311]

1. I dock with my carrier.
2. I lower ship below main deck of carrier.
3. I enter carrier services, and navigate my way to the galaxy map through carrier services.
4. I choose a location.
5. I see that the normal countdown process begins.
6. I wait through the countdown.
7. According to the carrier, we (the carrier and my personal ship docked on the carrier) HAVE jumped together.
8. I examine the galaxy map through my left panel on my personal ship, and it shows my personal ship still in the last system, as if it had never jumped.
9. Upon examination of the carrier services navigation/galaxy map screen, the carrier shows itself as having jumped, and now being in the expected destination system.
10. I undock/launch form my carrier in my personal ship, to check if there is some sort of bug.
11. I check personal ship, & carrier services galaxy maps, and again the carrier shows in the destination system, and my personal ship shows in previous system.
12. While checking the galaxy map, my personal ship is not shown in the previous system via the icon for a ship that I own being there, but all locations where the current location of my ship is posted states the previous system I was in prior to jumping, or trying to jump with carrier.
13. Carrier does show the Carrier icon in the chosen destination system.
14. If I plot a course in my personal ship, it plots a course form the previous system I wanted to jump from, to the system my carrier shows in, and confirms the game reads me as in the previous system.
15. Even while my carrier is in the destination system i jumped it to, AND my personal ship is read as in the previous system, when i undock/launch form my carrier, it shows as sitting directly in front of me, and I am able to re-dock with it, and fly around or into (ya, i tested its' physical presence by bumping into it...i'm a glutton for punishment).
16. If I log out, and then back in, the game then normally rectifies at least some of the incorrect information, though it doesn't always cause my personal ship icon indicating which system it is in to appear.
17. Upon re-logging, i am normally then sitting in the previous system, in normal space (vs supercruise, etc.) where my carrier was, and my carrier is now physically/visually gone...seemingly finally read as completely in the destination system. This is NOT always the case though, and sometimes when I log back in, the situation has NOT changed, and my carrier is still observable in the previous system, where my personal ship was left, though it is still appearing on galaxy map as having jumped to the destination system. It's kind of random what the re-log fixes, or doesn't fix.
18. I have attempted to jump approximately 5 times, while docked on my carrier, to various locations, and have had only 1 successful completion of a jump that didn't leave me behind.
19. I took a video of this scenario, though I haven't posted it anywhere yet.
20. This issue just began for me today. This is not an issue of router ports (i'm currently not running through a router), and i've made no system changes should have caused this issue.
I'm at a loss on this one, except I consider the new expansion implementation, if they are implementing anything, or altering anything behind the scenes in preparation, might have caused this issue for me...but that was just a passing thought I had while considering possibilities.

 

[Feldspar]

Have you tried jumping, then immediately logging completely out of the game without confirming where you are?

If this was a widespread problem then other people would be reporting it, which would suggest (but not confirm) it was something to do with your set-up. Are you seeing increase (normal) jump and transition times?

 

[Carpe Noctem 0311]

Have you tried jumping, then immediately logging completely out of the game without confirming where you are?

If this was a widespread problem then other people would be reporting it, which would suggest (but not confirm) it was something to do with your set-up. Are you seeing increase (normal) jump and transition times?

I'm not seeing any increase in jump transition times. All I know is that i've changed nothing. The settings on the game are the same for me as they have been for a long time, i've not changed anything on my system anytime recently, and i've not experienced this issue prior to now (yesterday). I''m no network engineer, nor a hardware tech, but I have been setting up my own networks, and building my own rigs for a long time, and i've gone through all checks, troubleshooting, etc., I can come up with right now to test for issues on my end, including network related, hardware, software, etc., though i'm sure i've not tested ever single possibility known to man. I haven't specifically tried "jumping, then immediately logging completely out of the game" in that specific & exact set of order of steps as you state, but i'll do that next, and see what the end result is, thanks for the suggestion. I'm planning on investigating/troubleshooting this more today. Appreciate your time.
Edited to add: P.S. I'm in NO WAY discounting possible issue on my end, as i've learned long ago to never do such with pc/network. I'm just wanting to solve an issue that came out of nowhere, without obvious/known cause, nor anything I can identify as being on my end...it certainly could be on my end. I just want to fix the issue, wherever the cause lies.

 

[Carpe Noctem 0311]

UPDATE: I just tested a jump. I also switched to my FedVette from my Cutter. The jump was successful, I was not left behind. The only change I made between reporting this issue here, and it now working was 1. I hit the rac & slept. 2. I switched to my Vette from Cutter. So, unless the Cutter was causing the issue, OR I managed to Sleep-Fix this issue, it has resolved itself, which leads me to believe it was an issue either between myself & the Server, or it was at the server. It also leads me to belief it probably wasn't on my end, though, as I said...never discount possibility. Bottom line: Issue seems self-resolved. Thanks.
UPDATE: Now receiving "Unrecoverable error on the transaction server" then disconnects...

 

[Carpe Noctem 0311]

Since the self-correction of the FC issue as reported, I am now receiving numerous errors:
1. "Unrecoverable Error on Transaction Server" - Happened while trying to drop from supercruise at a station in Robigo.
2. "Could not connect to the adjudication server; Error Code: BLue Cobra" - Happened while in Galaxy Map plotting course to Sirius Atmospherics to complete passenger missions.
I am not believing either of these is on my end. I'll keep updating here, and hoping these issues will also resolve themselves, as my FC jumping issue has apparently done.

 

[STRONTIUM DOG]

test data flow isn't being bottlenecked at amazon ec2 server relays
by switching to a vpn which should carry your data packit traffic a diff route

 

[Carpe Noctem 0311]

test data flow isn't being bottlenecked at amazon ec2 server relays
by switching to a vpn which should carry your data packit traffic a diff route

Will do, thanks.
Edited to add: I forgot to add, i've been playing since the last 2 errors as reported, and with the exception of some noticeable, small hiccups, i've not been kicked. I've also done some quick traceroutes to see if I could see any discernible issues of ping/packet, etc., but didn't see anything. If the errors arise again, i'll definitely try the vpn circumvent as you mentioned. Like I said, i'm not claiming to know everything, but i'm testing for what I can (isp, hops, ping, packet loss, etc.). Thanks again. If I figure something out, or encounter more issues, i'll post. Otherwise, i'll let it die, hopefully as my issues die out as well.

 

[Stabby_Dave]

I always find that if I don't get the "jump warning" messages, it's going to go wrong. In that case, I simply relog without leaving the carrier and it's all ok.

 

[Carpe Noctem 0311]

I always find that if I don't get the "jump warning" messages, it's going to go wrong. In that case, I simply relog without leaving the carrier and it's all ok.

Good point, and one I neglected to mention I had noticed. Good catch. Absolutely true. I noticed the lack of the notifications or "warnings" coincided, most of the time, with a failure. So, you "relog" prior to the jump, and log back in, to find yourself still docked, and then the jump proceeds as normal (just to clarify my understanding)? I do sometimes not have those warnings, but still have no issues, but I agree that the majority of time if there isn't a "warning" then there's an issue coming. For instance, I jumped a while ago, got non "horn" blowing by the carrier, nor a pop-up, but the jump proceeded as planned, and both I, and my carrier, reached the expected destination.

 

[Stabby_Dave]

Relog after the jump - when the jump countdown timer has reached 0. I never take the chance. No warnings = relog after jump.

 

[Carpe Noctem 0311]

I tried the relog AFTER the jump, and my result was me sitting there, looking at a physical carrier, that wasn't ACTUALLY there. The carrier showed itself in the galaxy map as reaching the destination, my ship showed itself as being in the origin location, not the destination location, and yet I could both target, and dock on the carrier. It was as if I had created a rip in time-space, and due to some sort of "spooky action at a distance" or some other such concept I don't fully keep up with, my carrier did in-fact exist in 2 places at the same time, though I could ONLY test it at the origin location due my ship (Cutter) being stuck there. I had to bring my FC back to the origin location to try again. If I SC'd away from the carrier, then it would no longer be there, but if I stayed there where it was prior to telling it to jump, I could interact with it, docking, etc., though it showed itself at the jump destination on gal map. In the end, after pinching myself to ensure I actually still existed in normal space-time, I finally went to bed. Then when I tried again the next day, today, the issue seemed to resolve itself, though I then began having some other issues (mentioned above) though they too eventually self-resolved. Personally, I think I transcended our known Universe, and I plan to write a book about it next summer, titled: "what just happened in ED?" I'm just glad it's back to normal...I was starting to question my own existence.

 

[oblivionmanman 2476]

happend to me why worry call it back problem solved

 

[Carpe Noctem 0311]

happend to me why worry call it back problem solved

Calling it back did NOT "fix" the issue. It continued to jump without me for the remainder of the evening, and all attempts. I think you mistake "worry" for troubleshooting of an unexplained issue, that could not be solved, and affected gameplay. If you can't figure out the trigger, you can never hope to prevent the next one. The problem was not "solved" by calling it back, since the issue continued. The solution actually had nothing to do with me...it simply resolved itself overnight while I slept, apparently.
Edited to add: Although I do agree with the main point..it was eventually solved somehow.

 

[oblivionmanman 2476]

Calling it back did NOT "fix" the issue. It continued to jump without me for the remainder of the evening, and all attempts. I think you mistake "worry" for troubleshooting of an unexplained issue, that could not be solved, and affected gameplay. If you can't figure out the trigger, you can never hope to prevent the next one. The problem was not "solved" by calling it back, since the issue continued. The solution actually had nothing to do with me...it simply resolved itself overnight while I slept, apparently.

ooww never known that o well it resolved good luck

 

[varonica]

Since the self-correction of the FC issue as reported, I am now receiving numerous errors:
1. "Unrecoverable Error on Transaction Server" - Happened while trying to drop from supercruise at a station in Robigo.
2. "Could not connect to the adjudication server; Error Code: BLue Cobra" - Happened while in Galaxy Map plotting course to Sirius Atmospherics to complete passenger missions.
I am not believing either of these is on my end. I'll keep updating here, and hoping these issues will also resolve themselves, as my FC jumping issue has apparently done.

It's a network issue, the location of the carrier isn't updating for all network clients, there are 3 networks and many thousands of players and the new location of the Carrier has to propagate across the entire network. Due to player requests the jump time has been reduced as much as FDEV can do without causing major issues, but there are still issues when there is slowdown or congestion on the internet, it's not magic, just how things work.

As suggested by another player, you can force an update of FC location by performing an action that requires the data to be updated so your PC makes a special request update, such as logging in and out, maybe changing ships even, but because the time to update the entire network has been pushed to the limit there will be occasions when this happens to people. It has only ever happened to me once, but I am assuming that players in other areas where the network may not be updating as fast will have more issues.

From the sounds of it from your new issues your connection with the internet may be dropping packets so no it's not an issue on your end, maybe some node between you the transaction server may be having problems or even your ISP.

 

[Carpe Noctem 0311]

It's a network issue, the location of the carrier isn't updating for all network clients, there are 3 networks and many thousands of players and the new location of the Carrier has to propagate across the entire network. Due to player requests the jump time has been reduced as much as FDEV can do without causing major issues, but there are still issues when there is slowdown or congestion on the internet, it's not magic, just how things work.

As suggested by another player, you can force an update of FC location by performing an action that requires the data to be updated so your PC makes a special request update, such as logging in and out, maybe changing ships even, but because the time to update the entire network has been pushed to the limit there will be occasions when this happens to people. It has only ever happened to me once, but I am assuming that players in other areas where the network may not be updating as fast will have more issues.

From the sounds of it from your new issues your connection with the internet may be dropping packets so no it's not an issue on your end, maybe some node between you the transaction server may be having problems or even your ISP.

My attempt to trigger an update, or special request, was ship changing, relogging, & etc., but it had no affect. I also checked every hop I could find between myself and server, etc., and saw nothing resembling lost packets, or higher than normal latency (I stated in previous comment about tracing, & etc.). My ISP was showing correct speeds, and no lost packets also. I came to the conclusion that whatever it was, I could not see it, without going crazy, and embarking on some intense digging attempt I had no desire to mess with. Like many other issues, I find that if I can't identify me as the issue...i'll give it a rest, and see what might be disclosed later. I slept. I woke. I played. I jumped. Problem resolved itself, as did the connection errors that were present for a very short time. It's done, but mainly I was curious, if others were experiencing the same issues, around the same time, as that might have led to discovery of something. Bottom line...I can jump today. We'll see what happens tomorrow, but until then..problem solved, self-resolved.

 

[Carpe Noctem 0311]

P.S. Looking to buy used pair of space legs for planetary exploration. Willing to take gimped ones until I can find new ones. PM. Thanks...