Route planning bug?

I've noticed that when plotting a long route while in VR performance inexplicably falls off a cliff on my PC. FPS drops to ~7FPS from 90FPS but none of my hardware is being challenged. My GPU use almost becomes nil and my CPU is using less way than <40%. RAM use stays at the same ~5.6 gig / 8 gig as it was before. It is almost as if when I click 'plot route' ED stops using my GPU for rendering and switches to the intel integrated GPU. It also takes forever to plot the route (like >5 mins this time).

Anyone else having this problem / is it a known issue?

To clarify, before I plot a route my system is being worked reasonably hard and I get 90FPS but when the route is being plotted I get very low FPS but my PC stops being worked to the point it is almost idle.

System specs:

Oculus Rift CV1
8 GB RAM
i5 4670K
MSI 970GTX gaming
Windows 10 (up to date)
Up to date game ready drivers.
 
I assume you are aware that 1000 ly is max you can route and that the more dense the star systems the longer it takes to plot. In populated space it is usually 1000 ly. At the galactic core it is around 30 ly. Where I am about 8000 ly from Sag A it is about 250 ly otherwise the plotter churns on for far to long. If as I assumed you know this then perhaps there is corruption in your ED install. Perhaps a fresh install of ED would resolve. Just guessing.
 
I assume you are aware that 1000 ly is max you can route and that the more dense the star systems the longer it takes to plot. In populated space it is usually 1000 ly. At the galactic core it is around 30 ly. Where I am about 8000 ly from Sag A it is about 250 ly otherwise the plotter churns on for far to long. If as I assumed you know this then perhaps there is corruption in your ED install. Perhaps a fresh install of ED would resolve. Just guessing.

Thanks for the reply Dogbite. I know of the 1000 ly plot limit but didn't know that it it was more of a variable than a constant. I'm near the core on my way back from colonia and in the very dense area still. I've now tried plotting shorter routes (instead of selecting the bookmarks I created to get there) and it pretty much gets rid of the problem. I experienced a similar problem before I got VR but it wasn't as game breaking on a monitor so didn't look into the effects on my PC.

I'd love to know what is actually the cause of the dramatic impact on performance. It seems to me that it must be that the calculation is being done server side and the client PC starts responding to events on the server so is demonstrably slower. It sounds like a bug but there might be a technological barrier. If the plot limit is variable they should create some sort of algorithm to take that into account, even if it as basic as *it has taken >60 seconds to plot this route, ask client if they want to stop*.
 
I assume you are aware that 1000 ly is max you can route and that the more dense the star systems the longer it takes to plot. In populated space it is usually 1000 ly. At the galactic core it is around 30 ly. Where I am about 8000 ly from Sag A it is about 250 ly otherwise the plotter churns on for far to long. If as I assumed you know this then perhaps there is corruption in your ED install. Perhaps a fresh install of ED would resolve. Just guessing.
It has something to do with your jump range. Divide max plot route by jump range and see how many jumps you can make. Round the number down and multiply by jump range and you'll get the optimal route distance.

My ship
Range 32LY
max route: 1000LY

1000/32=31.25 =I can in theory make 31 jumps
number of jumps x jump range= 31 x 32 = 992LY optimal route.

But since stars are not evenly spaced in 32LY intervals I had to bring the max route down to around 980LY. If I stick to that distance my route plots instantly every time.
 
Thanks for the reply Dogbite. I know of the 1000 ly plot limit but didn't know that it it was more of a variable than a constant. I'm near the core on my way back from colonia and in the very dense area still. I've now tried plotting shorter routes (instead of selecting the bookmarks I created to get there) and it pretty much gets rid of the problem. I experienced a similar problem before I got VR but it wasn't as game breaking on a monitor so didn't look into the effects on my PC.

I'd love to know what is actually the cause of the dramatic impact on performance. It seems to me that it must be that the calculation is being done server side and the client PC starts responding to events on the server so is demonstrably slower. It sounds like a bug but there might be a technological barrier. If the plot limit is variable they should create some sort of algorithm to take that into account, even if it as basic as *it has taken >60 seconds to plot this route, ask client if they want to stop*.

Well there ya go. Being so close to the core the density is killing your plotting. ED had mentioned they are looking at longer route plotting but with so many systems to consider in a route I can't see the situation improving dramatically. I am about 18000 ly from home and plotting about 250 to 300 ly now. If the plot takes more than a minute I just shorten the route some. As I am on the way back so the plots will increase now. Happy travels.
 
Back
Top Bottom