Hazard color coding not correct on 3DO scans

[GoogleCodeExporter]

Right now, the weather, temp and techtronics are color coded based on the 
hazard level.

On the capture, you can see a planet (Alpha Giclas IV) where we have weather 3 
and techtronics 6.

Both are red. Which implies that both are heavy threat.
But the weather really isn't that bad.

I'd like to see this coding:
0 - 2 = green
3 - 4 = orange
5 - 8 = red

The idea is that the player will know you can only go to red ones with the 
appropriate shield, and green one requires no shield. But the orange ones are 
still *possible* with some risk taking, without shield.

Oldlaptop, I am assigning you on this, since you were the one who made these 
modifications, I think?

Original issue reported on code.google.com by Awakened...@gmail.com on 28 Dec 2012 at 8:32

Attachments:

• Hazard_Color_Coding.jpg

[GoogleCodeExporter]

Any weather value above 2 is always red at the moment, because it will 
*unavoidably* kill crew (unlike earthquakes which can be evaded with 
some good driving).

Original comment by oldlapto...@gmail.com on 28 Dec 2012 at 11:18

[GoogleCodeExporter]

If I may respectfully, OldLaptop, I have many many time used my lander without 
a weather shield at weather 3 and sometimes even 4 to get a risky but paying 
mineral.
Weather 3 really isn't that dangerous because it just doesn't happen that often.

Earthquakes, frankly, can't really be avoided much more.. in my experience I 
lost just about the same amount of crew from say, weather 3 and earthquakes 3 
without shields.
I suggest we let the player decide how red it is, and keep the color code at 
something uniform for all hazards; with at least SOME orange in between... 
otherwise, as a player, my reflex is "well, that shouldn't be red.

Here is another way to see it:
If it's red at 3 and then it's also red at 8, that could lead me to think that 
weather 3 is as dangerous as weather 8 (or that weather 8 is as not-dangerous 
as weather 3)...

Original comment by Awakened...@gmail.com on 28 Dec 2012 at 11:37

[GoogleCodeExporter]

I have mostly based the codes on this: http://wiki.uqm.stack.nl/Lander_Hints , 
since that's intended for new players. Perhaps it's different for HD mod since 
earthquakes aren't quite as easy to see. Any other opinions? dczanik? Jaako?

Original comment by oldlapto...@gmail.com on 29 Dec 2012 at 12:40

[GoogleCodeExporter]

I'm with AwakenedEyes on this one. Red color for weather value > 2 is too 
strict. 
What actually happens with the "will always kill crew" is that as lightnings 
are generated, there is a 10% chance that a "killer lightning" is generated 
which kills always one crew.

Now, with weather value 3, lightnings are generated pretty seldom. Taken 10% of 
that, killer lightings appear rarely. Thus, weather 3-4 should indeed be yellow 
or orange, and 5-8 red.

Original comment by Jaakko.M...@gmail.com on 29 Dec 2012 at 11:42

[GoogleCodeExporter]

Done in r847.

Original comment by oldlapto...@gmail.com on 29 Dec 2012 at 4:21

• Changed state: Fixed

[GoogleCodeExporter]

The weather is still showing red at weather 4 on my test at Alpha Giclas VII

Original comment by Awakened...@gmail.com on 29 Dec 2012 at 9:46

• Changed state: Accepted

[GoogleCodeExporter]

Hm. It's yellow here, are you sure you're using a build made after r847?

Original comment by oldlapto...@gmail.com on 29 Dec 2012 at 10:08

[GoogleCodeExporter]

yes it's revision 853 I am currently using

Original comment by Awakened...@gmail.com on 29 Dec 2012 at 10:14

[GoogleCodeExporter]

I can't reproduce the issue with that very executable (running in WINE):

http://plantmonster.homeip.net/~oldlaptop/images/uqm-hd-issue122-a.png

Original comment by oldlapto...@gmail.com on 29 Dec 2012 at 10:37

[GoogleCodeExporter]

It's not WINE. It's the 3DO version.
For some reason the <4> in 3D0 shows in red, even though the text version shows 
in yellow.
Jaakko, Damon, is it related to the code or to the 3DO icons?

Original comment by Awakened...@gmail.com on 29 Dec 2012 at 10:45

• Changed title: Hazard color coding not correct on 3DO scans

[GoogleCodeExporter]

Ahh, I forgot to update the 3DO coarse scan as well as the PC one (even things 
that are common between them are rendered in different functions). Corrected in 
r861.

Original comment by oldlapto...@gmail.com on 29 Dec 2012 at 10:52

• Changed state: Fixed

[GoogleCodeExporter]

Verified fix.

Original comment by Jaakko.M...@gmail.com on 30 Dec 2012 at 5:52

• Changed state: Verified