OK NPC Ramming OUT-OF-CONTROL At This Point, anybody home at FDev?

It has - collisions happen when you're speeding.

NPCs flying dangerously close needs tweak, but it is not 'falling skimmers' type of issue.

No, it hasn't.
It can happen in a Res site, too. Quite often since 2.4, as a matter of fact. And you don't have to go particularly fast. Not to mention that "speeding" has no meaning whatsoever there.
 

Deleted member 110222

D
Like, don't speed.

Stop defending this. I don't speed, just so trolls can't get me killed through their sucidewinders.

This wasn't happening, now it is. My piloting hasn't changed. It's the NPCs. If you want to kid yourself that nothing fishy is happening, go ahead. I really don't care.
 

Deleted member 110222

D
It has - collisions happen when you're speeding.

NPCs flying dangerously close needs tweak, but it is not 'falling skimmers' type of issue.

Collisions also happen when you don't speed. Just because it hasn't happened to you...

FYI, I was never hit by the falling skimmers. You didn't see me denying it though, or calling other players ill.

In fact, I made more noise campaigning for it to be fixed than most people who actually died to it.
 
I honestly feel that this is something SJA has done intentionally. Devious? Perhaps. Underhanded? Maybe. Malicious? Doubtful.
 
Like, don't speed.

I don't think you understand what the actual problem is, speeding has nothing to do with it, at all. NPC's are flying directly at players when performing scans, you can be sitting completely motionless and it will still happen. This isn't a rare or once and awhile occurence, since 2.4 it happens with ALL NPC ships when scanning a player ship. Sometimes they will fortunately perform a super close flyby, but usually they will hit you unless you take evasive maneuvers.
 

Deleted member 110222

D
Competent but flawed? Yes, she's a human.

She fixed it once. Now it's back. This isn't the first time this bug, and yes, it is a bug, has cropped up. She's had her chance to learn. This shouldn't be happening.

And yeah, damn right am I angry. The time this has been left to rot really makes me wonder how much FD cares about the customer experience.
 
This NPC ramming stuff is getting out of control now. I know alot of players are getting rammed near the station by System Authority Vipers but I nearly lost a brand new Anaconda due to this crap when I landed in the Low Res to test the fit when a wanted NPC Viper with System Authority vessels on its tail rammed into me and exploded. Now suddenly I am wanted and all the System Authority guns are firing at me. I don't know how I got away in one piece but, I mean seriously, is it just me or does it seem like FDev went on vacation and left the interns in charge???

I've never ever had a single problem with any npc ever.
 
She fixed it once. Now it's back. This isn't the first time this bug, and yes, it is a bug, has cropped up. She's had her chance to learn. This shouldn't be happening.

And yeah, damn right am I angry. The time this has been left to rot really makes me wonder how much FD cares about the customer experience.

Bug fixing does not work that way really, especially if you have complex code which can work in very different ways.

What she did is fixed thruster control, AI is now correctly using it. However, it exposed issue in other part of the code.

As for 'why it takes so much time to fix', first, it is behaviour change, not a bug in a code. So it means change something in *configuration* part of code, not *processing* part of the code. That means basically changing it for all NPC AI in the game. Now, that's quite a huge change to be done without extensive testing. It can be done as part of minor release, but it also might be delayed, especially if slowing down as advised mitigates issue somehow.

TLDR you can be angry, but to call devs incompetent I will ask for clarification and on what basis you make that assumption.
 
Maybe FDev is working on it.
Normally I don't get scanned and rammed in solo, except twice last week both times in open...
Once was when my ping creeped over 500ms the other time I was boost speeding into the station. Got nailed right before the mail slot. It was unexpected and I am glad I had a rebuy.

something to consider...

[video=youtube;mR00P5x8_WQ]https://www.youtube.com/watch?v=mR00P5x8_WQ[/video]
 

Deleted member 110222

D
Bug fixing does not work that way really, especially if you have complex code which can work in very different ways.

What she did is fixed thruster control, AI is now correctly using it. However, it exposed issue in other part of the code.

As for 'why it takes so much time to fix', first, it is behaviour change, not a bug in a code. So it means change something in *configuration* part of code, not *processing* part of the code. That means basically changing it for all NPC AI in the game. Now, that's quite a huge change to be done without extensive testing. It can be done as part of minor release, but it also might be delayed, especially if slowing down as advised mitigates issue somehow.

TLDR you can be angry, but to call devs incompetent I will ask for clarification and on what basis you make that assumption.

Then they should tell us what the hell they are doing to try and fix it.
 
Fdev don't care.

This bug can cost you time and money. So unlike something that makes you money this will never be properly fixed.

Remember, this is Elite. Game breaking bugs are 100% perfectly acceptable, while anything that makes you decent bank is fixed within days or even hours.
 
Bug fixing does not work that way really, especially if you have complex code which can work in very different ways.

What she did is fixed thruster control, AI is now correctly using it. However, it exposed issue in other part of the code.

As for 'why it takes so much time to fix', first, it is behaviour change, not a bug in a code. So it means change something in *configuration* part of code, not *processing* part of the code. That means basically changing it for all NPC AI in the game. Now, that's quite a huge change to be done without extensive testing. It can be done as part of minor release, but it also might be delayed, especially if slowing down as advised mitigates issue somehow.

TLDR you can be angry, but to call devs incompetent I will ask for clarification and on what basis you make that assumption.

Might I ask for clarification and on what basis you are making such authoritative statements about the NPC AI implementation? The bug missed regression testing - again. Paint it how you like but I think most of us that earn a living from coding would have our competence questioned if we let the same high visibility bug get into a live system more than once.
 
Might I ask for clarification and on what basis you are making such authoritative statements about the NPC AI implementation? The bug missed regression testing - again. Paint it how you like but I think most of us that earn a living from coding would have our competence questioned if we let the same high visibility bug get into a live system more than once.

This. Even when unrelated bugs creep in, we're put under the spotlight. When an old bug that was fixed reappears, (which is alarmingly common in ED), it's pretty much inexcusable. Really, how does that keep happening?
 
Back
Top Bottom