Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Delta7]

I notice a reoccurring glitch where I will occasionally not start at full burn when perusing a fleeing enemy fleet. At first I thought it might be a feature to discourage the pursuit of enemy fleets under certain circumstances (enemy fleet being significantly smaller perhaps?) but I can find no pattern in when the error occurs and when it does not. Additionally, all of my allied ships start in full burn, while my flagship does not.

Obviously this is intended to happen when you are joining a pursuit led by an allied fleet, but I sometimes find it happening to my flagship even when I'm the only fleet pursuing the enemy.

I am using a few mods, but the only ones that I could think of that might affect this are Dynasector and Nexerlian, and even those seem unlikely to impact this. Dynasector does make core gameplay changes, but mostly to economics. Nexerlian does make some balance changes, but is primarily focused on large scale faction conflict rather than changing individual battles.

Edit
whoops, meant to post this on the bug report forum...
any chance a moderator could move it there?

[Alex]

(Moved.)

Hmm - full burn will cut out if there's something in your path, such as an allied ship, a ship hulk, or a particularly large asteroid. Is it possible that this might be happening here?

(For allied ships, it'll also consider their velocity, i.e. a second rank of ships shouldn't stop just because there are also full-burning ships in front of them.)

[AxleMC131]

I'm afraid I have nothing sensible to add to this discussion, but I just wanted to say that the misspelling of pursue as peruse (meaning to "read or examine in a careful or thoughtful way") in the title gave me a right laugh. 

[00lewnor]

I've had this happen sometimes as well with just me and my escort frigate burning in so it isn't necessarily allied ships, I assumed it was a big asteroid and didn't pay much attention to it. I cant really add anything bit will try to remember to look for the cause next time it happens.

[Alex]

Alright, cool - I'll just assume it's an asteroid until informed otherwise