While you're happily demanding to remove core gameplay from ED, I'd like to add my request to remove engineers, which I consider an exploit, too.
It's time to consider the SLF an exploit in multi-player
- Thread starter Webgear
- Start date
This^ is the worst part of the problem.
The bug has been present since the April patch. Acknowledged by Frontier. Today is the 1st of August and guess what? Bug still present.
We are very unlucky that the bug in question doesn't give the owner of the SLF some extra credits, like 1000 Cr per week, as a side effect. It would have been fixed within 2 days if it had, sure as hell.
FTFY. It would still take them weeks to months to fix it
Outside of rebalancing reasons I'd rarely advocate something be outright removed, but this {Expletive removed} has gotta get sorted somehow because it massively impacts on a fair game.
Nothing about the NPCs themselves. I would guess the root cause is somewhere between those facts:
- The game uses UDP. LIke about any game out there. UDP has no handshake, doesn't uphold the connection, nothing like it. It's just messages sent without any acknowlegement, error correction, etc. The advantage is that it's faster than TCP. So most games use it, a message lost here and there doesn't matter.
- The game apparently doesn't have time tracking for the messages. Which means, they can arrive out of order.
- Without having analysed the network traffic in this described scenario (too lazy to do it at the moment as I am not getting paid for it ) i would expect that orders to the NPCs for whichever reasons were given higher priority and it messes up the IP stack. Purely one theory, there's plenty of other options what could go wrong, don't pin me down on this.
Exact reason for WHY the messages don't go out in correct order, apparently they do so. Which means that the recepient gets them in wrong order. And acts on them based on that. Any server based plausibility check would easily detect and prevent that. On a P2P network on the other hand... game over.
I consider anything but front mounted jousting poles an exploit.
Nice analysis, but this is a relatively new bug (compared to the life expectancy of many other bugs in ED, that is). It used to work just fine before the April update, P2P or not.
It's not an analysis. I didn't put any effort into actually testing things and figuring anything out. I just wrote that up as one plausible theory of what could be going wrong. On the question if thing were fine before April: no idea. It might also only have been discovered recently. We'd need be able to run older versions to crosscheck, which we obviously can't. And even if it is new: maybe for some reason somebody gave messages higher priority. Maybe some other bug was fixed, which prevented this from happening previously. I can't tell. As i didn't analyse anything, but am only guessing.
Is fighter bug fixed, does it matter it's 1vs1 or wings, just giving slf single order at start of fight is ok?
No, it isn't fixed, only the command spamming issue. But the fighter lag is still there.
Command spamming was never the issue. It exacerbated the underlying problem, but that problem was introduced a while back and never fixed. The 'fix" was based on Frontier's mistaken assessment of what was going on, so really didn't fix anything.
They did something similar with the module pane. Couldn't see what priority the modules were without cycling the list...so guess what their fix was? The list cycles itself back to top whenever you open the pane or repair/power cycle a module...which craps up repairs in combat almost as much as the original problem did.
They did something similar with the module pane. Couldn't see what priority the modules were without cycling the list...so guess what their fix was? The list cycles itself back to top whenever you open the pane or repair/power cycle a module...which craps up repairs in combat almost as much as the original problem did.
So this is odd, a request for ! Open Only.
They've been broken since the April update.
How? (If it's in this thread, just give me the post number)
The OP's first post of this thread and my own comments in post #17.
My CMDR has three Elite ranked crew on retainer and hasn't equipped a fighter hangar, except to see if this bug was still present (it is), in more than three months.
Rubbish netcode choice or not, SLF's used to work just fine (without the characteristic lag) before the April update.
It's a bug.
Last edited:
Hopefully FD will look deep into this one
and not only fix the NPC code resulting in the rubberbanding,
but also touch them becoming idle when at range from the mothership.
The AI behaviour is quite buggy.
and not only fix the NPC code resulting in the rubberbanding,
but also touch them becoming idle when at range from the mothership.
The AI behaviour is quite buggy.