| Pages: [1] :: one page |
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Tkarro Ta'Lon
   |
Posted - 2007.05.11 15:43:00 -
[1]
I have noted, that the auto maping of a path from certain places to others will always go through Jita even though there are other routes. I suggest adding logic to the starmap section that gives you the option of avoiding those locations that are severely loaded such as Jita, or make it default that you do not fly through them unless they are bookmarked as a waypoint or going around is significant in the addition of jumps.
I for one, note that if I fly around Jita, it saves me several minutes because I don't have the added resolution time of joining the Jita Node.
Just a thought, I hope it helps.
|
Gor Kraon
Minmatar
Red Alliance
|
Posted - 2007.05.11 20:35:00 -
[2]
If autopilot could do that it would give you the ability to avoid a large camp/blob/fleet in 0.0 as well. Say the limit is 200 pilots and it diverts you, autopilot would tell you that a fleet is there... Course they could simply make it only work in empire.
|
Vincent Almasy
Gallente
The Underground
|
Posted - 2007.05.11 21:50:00 -
[3]
personally set to avoide systems with: 50,100,200,300,400,500+ people in system. a little for everyone.
|
Goumindong
Amarr
Merch Industrial
We Are Nice Guys
|
Posted - 2007.05.11 22:26:00 -
[4]
 Originally by: Gor Kraon
If autopilot could do that it would give you the ability to avoid a large camp/blob/fleet in 0.0 as well. Say the limit is 200 pilots and it diverts you, autopilot would tell you that a fleet is there... Course they could simply make it only work in empire.
Or they could tag certian problem systems[jita/rens etc] and give them a standard aversion value[like the prefer safer bar]
If other systems become an issue, it shouldt be difficult to add or remove problem systems.
----------------------------------------
Thou Shalt "Pew Pew" |
Nyana
|
Posted - 2007.05.12 11:44:00 -
[5]
Originally by: Gor Kraon
If autopilot could do that it would give you the ability to avoid a large camp/blob/fleet in 0.0 as well. Say the limit is 200 pilots and it diverts you, autopilot would tell you that a fleet is there... Course they could simply make it only work in empire.
The map already has a "pilots in space" view, if the autopilot could simply use that to avoid blobbed systems, nothing would change since the pilots have been able to access that information for 4 years anyway.
|
Aleranie
|
Posted - 2007.05.12 15:12:00 -
[6]
The problem is: once you start weighting points like that, the computational complexity starts to scale upwards very quickly.
|
Zeonos
Amarr
Fairtrade Syndicate
|
Posted - 2007.05.12 15:35:00 -
[7]
or you could simple be able to right click on a waypoint and say "Avoid this location/node", then it would find the shortest way around.
Latest evemon |
Nyana
|
Posted - 2007.05.12 15:41:00 -
[8]
Originally by: Aleranie
The problem is: once you start weighting points like that, the computational complexity starts to scale upwards very quickly.
True, but the "avoid podkill zones" isn't that slow, and the number of podkill zones are *FAR* greater than the number of Jita-like systems. 
|
Dal Thrax
Caldari
Multiverse Corporation
The Core Collective
|
Posted - 2007.05.12 15:55:00 -
[9]
Originally by: Gor Kraon
If autopilot could do that it would give you the ability to avoid a large camp/blob/fleet in 0.0 as well. Say the limit is 200 pilots and it diverts you, autopilot would tell you that a fleet is there... Course they could simply make it only work in empire.
So does the map.
Dal
Originally by: CCP Sharkbait
we are screwed. delaying startup again. soon as i have time i will fill you in on the details
|
TheEasterBunny
|
Posted - 2007.05.12 17:59:00 -
[10]
Originally by: Aleranie
The problem is: once you start weighting points like that, the computational complexity starts to scale upwards very quickly.
Not necessarily, if you have a checkbox to avoid busy systems you could treat it as avoiding low sec systems, and just subtract from the system sec status based on how many people.
i.e. Jita is .9, for every three hundred people you subtract .4 from the effective sec status used in the autopilot calculations. So that if you get the good old 700 person jita, your autopilot will avoid it at all costs, but if there's only a few hundred (very occasionally in jita) it will be just like every other high sec system.
Of course that is an example and having the number of pilots and the effective sec status loss change for tweaks or for how much node saturation there is. Perhaps an easier way to do it is to tell the autopilot to avoid the traffic messages which already show on the map, just having a checkbox to avoid them (since they're based on % server usage, it would be a good way to stay away from full nodes regardless).
But by modifying something already used in the calculation, you minimize the added complexity for a new autopilot computation.
|
| |
|
| Pages: [1] :: one page |
| First page | Previous page | Next page | Last page |