Request - workaround on 'getting stuck on roid' (DONE)

gumby1 · Post by **gumby1** » Tue Jan 29, 2008 3:15 am

Did I read somewhere that you claimed/stated that the program could prevent getting "stuck on a roid"?

How so?

I saw it get stuck tonight and it didn't get "free" from the roid for about 10 minutes, until I got tired of watching as it sat there "warping".

Post by **VanGoghGaming** » Tue Jan 29, 2008 9:32 am

Try to set the orbit distance to a decent value like 2500-3000m as it says in the tutorial. That helps a lot.

gumby1 · Post by **gumby1** » Tue Jan 29, 2008 2:06 pm

VanGoghGaming wrote:Try to set the orbit distance to a decent value like 2500-3000m as it says in the tutorial. That helps a lot.

Sure -- it was set at 2500m (I have now changed that to 3000m) but as near as I can tell it got "stuck" on a completely different roid.

I'm wondering if it is a bigger issue in lower security systems (where the rocks are bigger). You mentioned you mostly tested in 0.9 - 1.0?

The fact that my SB was running prevented any rat dmg but I worry about detection if an AFK miner gets stuck on a roid for 2 hours w/ an SB running?

I was wondering if you might start a "feature request" section, as I can see this type of thing occurring somewhat regularly?

While I'm far from the programmer you are I would think it would be "possible" to detect and correct this something like --

Warp activated and command sent greater than XX seconds ago and still not docked
Start workaround roid routine
Ctrl-space
Select top line of overview
click orbit
wait 30 sec
send Warp command again?

Post by **VanGoghGaming** » Wed Jan 30, 2008 11:58 am

Moved this topic to "Pilot's Lounge" since feature requests belong here. The workaround you suggested has been implemented in v1.30. Please try it out and report back if anything is wrong.