Spawning without shields after every (frequent) disconnect from matchmaker etc is driving me insane!

In addition to the indignity of having your screen go black in the middle of jumping or dropping out of SC or anything else,

we are now supposed to sit around for 10 minutes every time before I can continue what we were doing?

Priority fix?



And please stop resetting our jump route preference to "most economical" what the hack...
 
Last edited:
Yeah I had that happen to me today when I was jumping into Pancienses. I was happy to be there, but not happy to be there without shields.

It was odd, but then it only happened to me once. More than that and it would definitely creep up to irksome and then annoying.
 
Yeah I had that happen to me today when I was jumping into Pancienses. I was happy to be there, but not happy to be there without shields.

It was odd, but then it only happened to me once. More than that and it would definitely creep up to irksome and then annoying.

It happens to me almost every time. I think twice out of all disconnects / match maker errors since 1.3 did I log back in to find my shields as they were.
 
I got 4 disconnects since 1.3 (been on a 10 days hiatus), on 2 of them I lose shield. Once when I'm docked, the other one on a nav beacon. Not cool FD, not with your new long-charge shield mechanics.
 
Last edited:
i've been getting this too. i'm not willing to carry on my journey and risk getting interdicted without shields, so i have to sit there for several minutes while they come back online.

even at the main menu, i go to make coffee and come back to find Start is greyed out. so i Save and Quit - and the process is hung, the window doesn't close.

less than happy about the whole thing.
 
Same, even with a 6B shielded python its a pain in the backside, can't even imagine what it must be like for Conda owners..
 
I got 4 disconnects since 1.3 (been on a 10 days hiatus), on 2 of them I lose shield. Once when I'm docked, the other one on a nav beacon. Not cool FD, not with your new long-charge shield mechanics.

Which is even more hysterical when NPCs get insta charge shields. I was fighting some pirates that jumped me in SC, and took out the shields on the Cobra. Tore about half his hull away when he started boosting to get some distance. All of a sudden, his shield recharge indicator starts racing in circles like it's the last few laps at Daytona, and the shields are back up in about 3 seconds. I've had it happen with several different ships over the last couple of days, but it's unpredictably random, and so fast that by the time I hit the record key, the shields are back up.

Fun times...
 
The disconnects are annoyoing - there's definitely more of them since 1.3 was released.

I've had 3-4 disconnects since 1.3, but I haven't had a shield loss yet... maybe I got yours? :D

I have had some severe rubber-banding (I think I nearly died when an Anaconda super-rubber-banded past me at well over 500-600m/sec - it missed me but I sure had that "DIVE! DIVE! DIVE!" moment! - not sure if hull collision is handled locally or by FD's server; if it was local I almost met the rebuy screen).
 
In addition to the indignity of having your screen go black in the middle of jumping or dropping out of SC or anything else,

we are now supposed to sit around for 10 minutes every time before I can continue what we were doing?

Priority fix?



And please stop resetting our jump route preference to "most economical" what the hack...

I have these problems too, since yesterday and posted about -> https://forums.frontier.co.uk/showthread.php?t=158573

Maybe it's worth to open an issue/ticket/bugreport or whatever it's called at FD.
 
Back
Top Bottom