Quote:
Originally Posted by h.sie
Phew. Thanks for the responses. What is 32 Point? Is it N, NW, NNW, NO, NNO and so on? Good idea, but not easy to program.
My first thougt was (easiest solution of all - I'm tired):
Bearing: 10 Degrees steps:
0, 10, 20, .... 350, 360.
Range: 1 instead of 2 significant digits and rest zeroes:
100, 200, 300, ... , 800, 900, 1000, 2000, 3000, 4000....
Using text instead of numbers (NNO, NNW, Long range, and so on) is easy to do in C++ or similar, but not in assembler (for me). But worth to try.
Who is Elanaiba? One of the programmers? Nice idea. He will surely be pleased. Maybe it's a better idea to directly contact the UBI customer service with some questions regarding programming details.
@LGN1: Thanks for the CO2-research. I'll use that information in the next days/weeks.
h.sie |
That is really great h.sie...the possibility to have inacurated WO readings!
So, here my 2 cents:
1. The bearing could stay untouched, they had very precise optical equipament and probably the readings were very precise too. Or perhaps just a bit of uncertanty, let´s say, one to five degress of error (in RL this tiny error is probably determinated by the sea state). But, obviously, if in the end, you have the necessary time, then for the first "Ship spotted", just an estimated direction is the better: N, NNW, NW, etc.
2. But the estimated distance is another history...it must be estimated only...so perhaps in steps of 500m, even 100m is already good. Much better than the always dead precise as in the stock game.
And to finish: check if these new estimated values (bearing and distace) will not mess with the weapons office solution in game. Also think about the dialogue and the lipsync. Just reminders to you think about if this or that aproach is better than another, etc.
And Dan already helped a lot of modders here: ask to Der Teddy Barr, Privateer, ref, etc. Der Teddy Bar even had access to some mathematic formulas used by the game engine and so on (all them given by Dan)