[#2512]Timelines Graph 5- Battle Of Omicron Lyrae - BUG

[nick75]

At a certain point my ship becomes uncontrollable.
In a couple of seconds I travel 4000+ km away from the mission area.

Since this is not issued ingame by any means, like someone saying "stay away from something" or "be warned about their devices kicking you off 4000+ km", then I guess this has nothing to do with anything that I could in any way be aware of and try to avoid.
Ergo: it's a bug.

Since this mission is time based, I let you guess how much time it's needed to get back from 4000+ km away at the speed of 3468 m/s.

Please correct. Thank you.

[LameFox]

Sounds familiar. What was your objective at the time?

With me it happened when it wanted me to fly away from the Kha'ak ship prior to ramming it. I started to fly toward the objective marker (I might have boosted, I forget), and then got catapulted to extreme speed my ship could not recover from. I fixed it by getting out of the seat so I didn't go quite as far, but it probably would have if I'd remained at the controls.

[Exidrial]

The same thing keeps happening to me as well. It only seems to happen when you're close to the Kha'ak capital ship. I have not been able to finish that mission because of the bug yet though I'm just biting the bullet and manually flyng back to the engagement area now rather than restarting each time it happens.
https://youtu.be/noUoKeaRf2Q

In case this is important information: I have auto roll and collision avoidance both turned off

[nick75]

Sounds familiar. What was your objective at the time?

With me it happened when it wanted me to fly away from the Kha'ak ship prior to ramming it. I started to fly toward the objective marker (I might have boosted, I forget), and then got catapulted to extreme speed my ship could not recover from. I fixed it by getting out of the seat so I didn't go quite as far, but it probably would have if I'd remained at the controls.

To me it always happens after the fist stop of 10 seconds close to the Kha'ak mostruosity.
Last time I tried the mission (5th try now), it happened again but this time I was kicked off 7000+ km. *facepalm*

[Imperial Good]

Ran into the same bug. When at the stage to fly into the Obliterator I engaged travel mode to fly away and get some distance and travel thrust with the intent of flight assist turning back towards the Obliterator so I can ram it at full speed.

Instead I started to accelerate at over 2 km/sec^2 away from the Obliterator. By the time I regained control, a few seconds later, I was over 500 km away from the obliterator. Only mission I ran into this issue with, and it seems a lot of people are as well.

Two possible causes would either be some scripted logic affecting the player ship with the intent of helping them fly fast into the Obliterator, or there are physics gremlins with the Obliterator. Physics gremlins with the Obliterator might be related to local gravity fields and animated sections of the ship.

[Calgor Grim]

Two possible causes would either be some scripted logic affecting the player ship with the intent of helping them fly fast into the Obliterator, or there are physics gremlins with the Obliterator. Physics gremlins with the Obliterator might be related to local gravity fields and animated sections of the ship.

To add to this, the mission dialog directly following that mentions some sort of "Repelling forcefield", it's what makes it irritating to get into position a second time around for the teleportation attempt as it marginally pushes you away from the weak spot. It almost seems like that forcefield has way too much elasticity. It also seems to be focused around that rear sphere of the ship facing outwards towards the generators. I wonder if those spots are where perhaps multiple pushing effects overlap and amplify an effect or something?

I did managed to get past this mission thanks to the exceptional advice from Lamefox of getting out of your seat when the catapulting starts. It still launches you but the ship slows down a whole lot quicker, it only managed to launch me 600km away instead of 4000km away but with how irritating that bug is and to get to this point, I never want to see this mission again and yet it should have been a bit of a standout moment.