Could maybe check whether there is a packet loss on the connection. Or unusually high latency.
Crew behaviour relative to opponent skill.
- Thread starter Scoob
- Start date
Mine's usually pretty good; she gets sent in first to take all the heat, while I cut through shields as the target is distracted. It usually works well - occasionally losing an SLF - but I'm not as analytical as @Scoob. I just wish she wouldn't fly through my beams and then blame me.
Prosaically, I'm guessing that there are several RND factors working against each other and there will be times when they combine against your best interests.
Prosaically, I'm guessing that there are several RND factors working against each other and there will be times when they combine against your best interests.
How can I test that? I've done the usual speed tests - see picture earlier -and connection seems solid.
Yeah, same. If I send her in alone against a wing of other ships and they all gang up on her, she's likely toast. However, as soon as I start shooting, they'll be gunning for me so she'll not get hassled. Sending her against lone ships would usually see her win too. Often I'd send her after one ship, while I take on another for example. I used her a lot when I was in pretty tough ships myself.
When I first started using her this time - I'm in a Keelback remember - she was cutting through the low-level ships with ease, it was silly. That first session with her, I basically doubled my money, then did so again next time out. Fun. Then she just stopped being any good, regularly dying within moments of an encounter starting, or not obeying that initial attack order, or not freely engaging. Generally other ships appeared to be behaving as they should, it's just her that went dumb.
It's one thing having the odd "surprised she died to that" moment, vs. her consistently dying to REALLY low-level ships. Sorta fancied a bit of "easy" Res combat, but I've lost interest now. I'm doing this "restart" as role-play, I have lots of well-equipped, Engineered ships back at the Fleet Carrier. Was just trying to capture that starting again feeling... except Crew did not exist when I started back in 2014.
Basically, at best, she's acting like a total rookie, at worst she's bugged out when she fails to obey orders. If each order, change of target etc. needs something server-side to confirm it, perhaps that's why she's slow. However, as I'm solo, I thought the instance would be basically self-contained on my client.
I don't know. I used to run Wireshark a couple times. You get an overview of connections. There is likely a less unconvenient and easier way. You'd probably analyse a connection with some network monitor app. A ping does deliver basically your analysis, but you need an address to ping. And I have no clue how to find connected IPs without a dedicated app for that.
I'd suggest putting in a ticket to support. They're usually quite good.
Never used that. Just the regular speed test. I chose a server in Cambridge as that's where FDev is based, not a clue where my "local" server would be, but Cambridge isn't that far. With everything else Internet-related working so well, I don't think it's a me problem here, but I'd of course be open to other suggestions. I had some particularly bad experiences - was (trying to) Fight Thargoids at the time - in the couple of days after U16, but stuff did settle down mostly. Moving on to do something else - sorta burnt out a bit, with all the glitches I was getting, also had my forth ever death in game - once again BUG related like the prior three. Really put me off.
I cannot provide any evidence of my experiences, I don't record my play sessions. They're surely want something to back it up?
Maybe I should make a post of the PC sub-forum, the issues I experience do seem "networky" but I do genuinely have a really good Internet connection and PC in general. ED is pretty lightweight when it comes to CPU, GPU, RAM and bandwidth use - certainly if you're just buzzing around in a space ship.
FDev is running their servers in the AWS (Amazon hosting services)
It can be possible there are issues between your location and the AWS node you are connecting to and not something general, else everyone would be on the forums complaining
In the past i used with great success a tool called PingPlotter - iirc they still have a free version (or a trial)
IIRC in the past you could see the IP for the server you're connected, but if this info is no longer visible in the launcher or in the main menu, you should be able to find it in the net log
So get the server's IP and run a pingplotter to that destination - you will get detailed route and ping/packet loss for each node along the way
ED uses AWS, an Amazon service, Cambridge has nothing to do with it in terms of connection, unless your local cluster of Amazon serves is at Cambridge, too.
That's basically it. Now you can get the IP. Then you send a ping and get the results. Check again to see if IP stays consistent and that's how you check your leg of the connection.
In the "What happened to limpets" there is talk about servers affecting the limpet behaviour negatively.
They affect the Refinery behaviour too
I was once at a mountain cabin with lousy 3G signal - at times i could barely mine, due to connection issues i had fragments stuck in the refinery, not getting processed due to the really crappy internet connection
At mountain cabin you play ED? What about fishing in ice cold lake? Have sex with wife at candlelight? Go hiking (and bring bow and rifle)?
Yes, I've been playing RDR2 a lot lately
Yes, I've been playing RDR2 a lot lately
There is time for everything. For hiking, for sex, for barbecue, for dining... and for elite too...
Not having tv or anyone else nearby and with a really lousy internet that wasn't suited not even for social media not to mention any streaming services - there is a surprisingly amount of time to do a lot of stuff
Fuu... man, imagine that juicy mountain lake fish you could have caught. Damn, that's almost better than Kumo burgers.
Thanks guys, I'll dig a little deeper when I next get some time.
It's funny, it used to surprise me how little bandwidth ED needed. For years (the dark years!) I was on a terrible end-of-line ADSL connection, 1.6km from the box. The BEST I got was 2.5mbps down and 1.0mbps up. The only good part was my Ping was relatively low for ADSL. ED Played great and I'd regularly team up with a buddy. In fact the only times we've had issues playing together were i) When he had to run off a poor Wifi connection for a while, and ii) if someone else with a poor connection / lower-end hardware (we assume) joined us in an instance. That'd basically break the instance right away, with lots of rubber banding, hits not dealing damage etc. We'd just re-instance in the PG.
Heh, I dreamed of a solid 3G connection in the dark years, but we're in a mobile black-spot too - literally, it's marked as black (no coverage) on the map. I do get a slight signal these days, but only upstairs on the Westerly-facing side of the house. Cabin does sound nice, but poor internet is a deal breaker lol. Don't get me wrong, being outside, hiking, cycling etc. etc. is great, however, I still need solid internet to chill out after all that. Been spoilt the last couple of years with FTTP, would struggle going back...
It's funny, it used to surprise me how little bandwidth ED needed. For years (the dark years!) I was on a terrible end-of-line ADSL connection, 1.6km from the box. The BEST I got was 2.5mbps down and 1.0mbps up. The only good part was my Ping was relatively low for ADSL. ED Played great and I'd regularly team up with a buddy. In fact the only times we've had issues playing together were i) When he had to run off a poor Wifi connection for a while, and ii) if someone else with a poor connection / lower-end hardware (we assume) joined us in an instance. That'd basically break the instance right away, with lots of rubber banding, hits not dealing damage etc. We'd just re-instance in the PG.
Heh, I dreamed of a solid 3G connection in the dark years, but we're in a mobile black-spot too - literally, it's marked as black (no coverage) on the map. I do get a slight signal these days, but only upstairs on the Westerly-facing side of the house. Cabin does sound nice, but poor internet is a deal breaker lol. Don't get me wrong, being outside, hiking, cycling etc. etc. is great, however, I still need solid internet to chill out after all that. Been spoilt the last couple of years with FTTP, would struggle going back...
To help with diagnosis logs may be useful, but when I've had instancing issues they've usually taken my word for it if I give enough description to give some clue what's happening. Especially if it's repeatable.
Ok, might look at doing that then. Not sure when I'll next get in-game though, might have a moment later, but not sure yet.
I'll be trying this solution by Kyle Stryker for odd SLF behaviour later today:
forums.frontier.co.uk
SLF stuck on "maintain formation"
This is a new one for me. SLF no longer responds to commands. I can launch and recall, but the game defaults to "maintain formation" and there is nothing I can do about it. Even if I try to pilot the SLF, hardpoints and I are locked (in formation). Tried recalling. Rebooting the game...