While it's certainly not UT's responsibility to fix this for the devs, if he can identify the issue - assuming it is something exposed to modding - then this might help the devs. A fix would be welcome from whatever source, but I do agree a proper fix rolled into the 4.10 update would be preferred.Observe wrote:I don't see the point. Egosoft is well-aware of the problem and it's very easy to reproduce. I'm not looking for mods to correct the errant behavior, because the fix belongs in the core game.UniTrader wrote:Drop me a note if its certainly an oddity of the Arawn (or other specific Ships) only, i may look into its behavior in more detail then...
It's quite simple in principle: Order a ship to move to a location and it should respond accordingly. If it doesn't, the game is broken and needs fixing at the source - not by mod band-aids.
As an aside, the Arawn was the original "beast" ship I aspired to own as my flagship. So much detail has gone into it, from the nacelles that deploy for combat, to the various doors that open for Drones - and fighters if you mod. It even has internal defences, and was evidently designed to have Fighters originally. Seems odd that a vessel that had so much time spent on it for such details, can't even fly properly.
Edit: My Arawn seems to be navigating between Zones OK when it has no following ships...I'll continues flying around though to see if that remains consistent in 4.10.
Scoob.