Plotter problems

[Tomx]

I'm currently in the confluence on the far side of the core.

I'm finding even with the filter on to drastically reduce the numbers of stars (neutrons only) the plotter is next to useless.

I'm having to manually plot each jump (even with an obivous path on a 52ly ship a 5ly distance is "route plotting failled)

I've also found that having to manually plot each jump is causing me to hit the neutron stars every now and again - I'm not sure if this is a but and it's just the 30km/s rate creeping into the exclusion zone or if I'm accidentally moving the throttel when I log out but I've lost 3% hull.

So I've developed the following patern.

During jump - throttle to zero, entering system throttle to zero again.
Scan star and honk system.
Point nose away from star (recently introduced
Pull up galaxy map (takes a while)
Try plotter (might get lucky...)
Single plot next star.
Exit
Charge FSD (off alignment or not full throttle)
Pull up system map (incase things to scan)
Exit
Throttle up and align


Anyone have a better plan?
Anyone know how to get around this - I'm about 400ly from where I was aiming for - it's going to be slow/frustrating with this method (not to mention the slowly cumulating hull damage)

Tom X

 

[Evyl Minkey]

When you have the stars filtered do you have the last option on the list checked? I can't remember what it says but I think it is something to do with excluding stars from your route. I only mention it because when I select that it causes my route plotting to fail.

 

[goemon]

after taking my 48 ly jumprange conda to the core, and not being able to reach the great annihilator because plotting, i have sworn myself not to take anything beyond 33 ly jumprange agin into the core.

high star density and high jumprange are too much for the plotter.

i went 1000 below sag a* - there it kicked it. so basically: plot twenty jumps manually up or down.

 

[Tomx]

Could be that - I thought by filtering out most of the stars (reducing the number of options the computer has, it should be faster but who knows....
Really would have thought falcon de lacey would have managed a better plotter by 3303! It really would be nice to have the option to restrict the plotting timer (versus optimisation)...

I worked out what was happening with the collisions - if you go to the galaxy map and plot for a while your ship can fly into the NS EZ. This is because you drop out much closer than other stars etc. and so the 30 km/s is significant.

Pointing away works well (But is a bit annoying!) Ah well!

Ah welll.....