open All Channels
seplocked Issues, Workarounds & Localization
blankseplocked Autopilot Gone, Double Ships, Star Map Crashes
This thread is older than 90 days and has been locked due to inactivity.

Author Topic

Cat Molina
Posted - 2011.09.05 01:18:00 - [1]

Edited by: Cat Molina on 05/09/2011 01:43:01
Some problems I've encountered since the last update:

Display of systems to be traveled does not appear upon setting an autopilot route. The route is being set... as selecting it again outputs the message 'cannot set route to same place twice'... but the data does not appear on the screen. The next stargate in route is also not highlighted in yellow. Had to use Ombey's maps to get from Metropolis to Sing Liason today. Very old-school. (EDIT: Further testing shows autopilot completely broken. Attempting to autopilot results in "Autopilot disabled - No waypoints set" even though Dodixie (only 2 billion jumps away according to my client) is still set.

Possibly related: any system I set an autopilot to or that I have assets in (via the assets window) is listed as being 2,147,483,647 jumps away. Looks like it's gonna be a long trip... I should probably pack some snacks.

Opening the Star Map causes immediate lockup. Only CTRL-ALT-DELETE and closing Eve gets me out.

Double ships appear in my hangar. Sadly, they are not really doubled... just the icons.

My drones have lost their damn minds. I believe they've gone crazy from the jet black background which surrounds them on their icon (i.e., the nebula background on drone icons does not appear).

At periodic intervals, while traveling in space, all nebula completely disappear leaving me in a dark universe. At which point my computer begins to 'stutter and chug' as if attempting to render something huge.

Clearing cache does not fix any of these problems.

Any advice?

Rina Asanari
Posted - 2011.09.05 07:09:00 - [2]

Two things.

First, check your autopilot settings regarding security status preference and system avoidance. Maybe you've placed some systems on your avoidance list or checked "avoid systems where pod killing occured". These settings may be the cause why there's no course plotted to the target system, just because there is no path to the destination meeting the given requirements.

Your graphics issue seems to be totally unrelated and I'd advise you to check the "usual suspects" first: Drivers, thermal issues, background programs/system load ... that sort of things.

Cat Molina
Posted - 2011.09.05 08:20:00 - [3]

Thank you Rina.

Changing the autopilot settings was difficult. As I mentioned, every time I open the starmap it locks up. On the fourth try I found that if no autopilot is selected and the map is opened up in a station, it won't freeze up immediately... just get sluggish.

As you suspected, autopilot settings had been changed to 'avoid pod kills'. Odd that value would reset, I'm an Empire brat and hadn't changed them in years. Changing that gave me my autopilot back (for the present... I trust nothing anymore Wink).

Thanks again.


This thread is older than 90 days and has been locked due to inactivity.


The new forums are live

Please adjust your bookmarks to

These forums are archived and read-only