Material traders filter not working correctly ?

mpfj

mpfj
Before I raise a bug, can someone let me know if I'm doing this right ?

If I want to find material traders, I can use the filter option in the Galaxy Map.

AFAIK it will only show up traders you've been to, correct ?

If so, then look at the following screenshot:-

ZpMqloz.png
You can see that I've visited Arine and I've even done a couple of material trades at Wescott Terminal in Arine.

So why isn't Arine shown with a blue circle (indicating the presence of a Manufactured Trader) ?
 

Wasp0

Wasp0
Forget The in game searching, just use INARA......Simples and not limited to any distance, so you can plan to visit a trader on your way to an Engineer!

Good job FD don't design//make 2018 Sat Navs :eek:

Input a destination only to be told by the Sat Nav that as you have not visited that destination we can't find it!!
 
Last edited:

Cmdr DRAGONHEART

C
I had same problem yesterday...
Material trader did not work in galaxy map.
Sirius system has a mad trader but wen select on galaxy map
It was not showing it.
 

XW_Ziggy

XW_Ziggy
Third party tools exist because the tools FDev put in the game are terrible. That 40LY restriction is just spiteful and pointless.

Don't even try and bash your head against the stupidity of FDev's in-game tools, just paste your Inara or EDDB result into the game and be done with it.
 
Last edited:

Ian Doncaster

Ian Doncaster
Interesting thing I discovered about the 40 LY restriction - it will pick up traders (or black markets, or IF) that you have been within 40 LY of since you logged in, not just ones within 40 LY of where you are now.

So, if there's a trader at A 20 LY from you, and then you jump to B which is 60 LY from A, the trader at A will still show up on your map. If you then log out to the menu and log back in, the trader at A will no longer be on your map.

That does make me wonder if there's some efficiency thing going on where the internal data structures just aren't set up for querying "does any station in this system have facility X", so it limits it to 40 LY at a time so that it can get the data without slowing down the map / generating too many server requests at once.

If that is the case, it would still be really frustrating, but "technical limitations" would be a more understandable explanation than "we thought it would be fun" ... and might mean that, just as route plotting went from manual to 100 LY to 1000 LY to 20000 LY, the range gets increased in later releases.
 
You must log in or register to reply here.
Back
Top Bottom