|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Xaen
Caldari Caritas.
|
Posted - 2008.04.16 16:12:00 -
[1]
Manually converting au to km is a pretty crappy and labor intensive way to use the system scanner. EVE measures interplanetary distances in AU, why doesn't the system scanner?
Also, is there a reason for the range limitation other than 1111111111111111111111111111111 in binary equating to 2147483647 in decimal? (That was rhetorical)
Is there some reason you guys can't use a float so we can scan the whole system? The existing probe mechanics still prevent people from being precisely pinpointed across a 200au system, so I don't see the need for the limitation on the directional scanner other than developer convenience. - Support fixing the UI|Suggest Jita fixes|Compact logs |
Xaen
Caldari Caritas.
|
Posted - 2008.04.16 17:30:00 -
[2]
Originally by: Tarminic
Originally by: Alski
Originally by: Garat Mant I support this change.
Could we also have the directional scanner show on the solarsystem f10 map view? It would be helpful to see the "searchlight" from your scanner sweeping the system...
Better yet, can we have the searchlight display on the solar system map, and have an option for making the transition between ship view and system map instant?
That would rock.
Seconded. Guessing whether a celestial body is in my scan cone or not is not very accurate. |
Xaen
Caldari Caritas.
|
Posted - 2008.04.16 17:37:00 -
[3]
Originally by: Fifth Horseman
Originally by: Alski Better yet, can we have the searchlight display on the solar system map, and have an option for making the transition between ship view and system map instant?
There is a transition speed option. F10- Starmap Tab. Animation Sub-tab. Select "Instant"
"Instant" isn't. - Support fixing the UI|Suggest Jita fixes|Compact logs |
Xaen
Caldari Caritas.
|
Posted - 2008.04.16 17:42:00 -
[4]
Originally by: Frug It really makes no sense for it to be a random number of km, that doesn't even fit into the size of the input box they provided.
Either make it in AU, or make it a slider, or ditch it.
It's not random. It's the largest integer that can be represented within the confines of 32 bits in binary.
Whatever the solution, what we currently have is consistent with the rest of the UI. It's crap.
Here's the idea I like: Radio button to select km/au Text field to enter km/au and a radio button that selects 5/10/20/40au (the scan probe sizes).
Selecting this button "greys out" the text field. Clicking on the text field "greys out" the au selector radio buttons. - Support fixing the UI|Suggest Jita fixes|Compact logs |
Xaen
Caldari Caritas.
|
Posted - 2008.04.16 19:18:00 -
[5]
Originally by: Alski
Originally by: Xaen
Originally by: Fifth Horseman
Originally by: Alski Better yet, can we have the searchlight display on the solar system map, and have an option for making the transition between ship view and system map instant?
There is a transition speed option. F10- Starmap Tab. Animation Sub-tab. Select "Instant"
"Instant" isn't.
I was gonna QFT this, but i just checked ingame and i think it is "more instant" than it once was considering how usefull it would be to be able to allign your scanner from that map, i'd call what delay there is acceptable.
"More instant" isn't. - Support fixing the UI|Suggest Jita fixes|Compact logs |
Xaen
Caldari Caritas.
|
Posted - 2008.04.16 19:25:00 -
[6]
Originally by: Allwix range slider with both displayed
No. Not unless accompanied by a text field/radio buttons.
Sliders with over two billion possible positions are unworkable. - Support fixing the UI|Suggest Jita fixes|Compact logs |
Xaen
Caldari Caritas.
|
Posted - 2008.04.16 19:47:00 -
[7]
Originally by: HostageTaker wow, just wow!
Who here actually remembers when scanning down ships in safes was an art? (Before scan probes)
CCP have already dumbed down the scanning/probing enough where any clueless Joe can launch a probe and push a button and yet there are still some people that find this hard... unreal
Please unplug your keyboard before you hurt yourself on the internetS.
Reading comprehension fail.
Grammar fail.
Brainal plexus fail.
Who should unplug whose keyboard again? - Support fixing the UI|Suggest Jita fixes|Compact logs |
Xaen
Caldari Caritas.
|
Posted - 2008.04.17 15:39:00 -
[8]
Originally by: Bimjo
Originally by: Hoshi The range limit is the is the max number a normal unsigned Int can have.
0 to 65536 is an unsigned Integer number(if Int is 2 bytes) -2147483648 to 2147483647 is a signed Long number,if long is 4 bytes. pedantic lesson over
So you've learned C/++ eh?
Well I'm talking about the mathematical concept of an integer, not a particular flavor based on a particular language and platform. |
|
|
|