And actually it wont matter if your sub's position is off a little on the map !
As long as all measurements are applied to the same mark.... it dont matter if you draw it on a piece of paper totally unrelated to the sim.

275 deg. of your position, is 275 deg. of your mark,,, no matter WHERE the mark is !
So....
1400 meters out, on brg. 275 will be the same no matter where you draw it.

You can plot without being Exact on the map..... and still get an accurate solution.

Make Sense ?
:)

Target ship would be 275 deg, 1400 m from my sub and not my mark but maybe u are right should be same target course/speed calculated just a bit differently positioned on map...:hmmm:

after you get visual with target it does not matter... and if you use 4 bearing method ... even you make some misteakes because of the navigator erors when you move between berings you can corect them when you get visual with the target

If you plot correctly, and are accurate with your measurements....
They will be true to your MARK.... Thats what matters... the plot.
If your Real-Nav mark is off 200 meters on the map, then all you measurements will be off by the same... making them correct to your MARK.

If you plan to take your shot a 350 deg. and his speed his 10 knots, and his range is 2000 meters, and you have his AOB from plotting...
It all shakes out the same as long as you use the MARK as a constant.
And as was said..... once/if you can get a visual.... then its all Good.
But you could just as well take the shot "Heads Down" without looking as long as your Plotting was correct.

The plot is the plot...... no matter where you put it on the map.
The math works the same as long as you use the MARK as a constant, and you are not moving.

Just sayin...........
:cool:

Yes.... I only ask for a celestrel positional fix at sun rise and sun set. And only if i can see the sun. Between these times I plot a line in the direction of travel and estimate using time and speed where I am.

When i find a contact..... I just place and X (pencil mark) anywhere on the map and then take all marks from this place.

Sure I get errors.... but I feel this is realistic.... As sometimes uboats had no idea where they were due to cloudy days and storms.

This is the whole Idea of using a Real Nav mod.

:salute:

Re-downloading and re-installing the mod did not fix my problem. I am still unable to open SOAN. it's showing properly, can be moved around, ship types can be changed, but a doubleclick does exactly ... nothing.

Any other ideas?

You do not doubleclick - just one will do and it should open.
Ensure you click on the cover and not any writing etc

I will test when I am at home! It is actually possible that this might be the reason, because I installed a SSD a few days ago and everything is so freakin' fast that I actually might have opened and instantly closed it again (although it sounds a bit unlikely). I'll let you know!

EDIT: No. The cursor does become yellow, indicating that there is some kind of action behind a click, but it does not do anything. SOAN stays closed.

EDIT 2: Reinstalled again... now it opens. Don't know what went wrong the first time... Now the X button and movecontrol of SOAN is out of reach (out of screen to the right). I red something about reseting positions, I'll try to find that again...

EDIT 3: Found it. Deleted the draggables.TDW file and that worked. Tested it again and immediatly rendered the SOAN to be unmoveable again (opened it up to far to the right and controls were out of reach again. Am I missing something here? (Sorry if this was already answered!)

--> Could the SOAN be also moved by clicking to an additional "moving-knob" at the left? So that I can get it back if it jumps out of reach?

OR: If it would just expand to the left direction, the problem would also be solved!

Python Error
 

Hi TDW!

I'm getting following python errors when I want to select a historical mission!
The crew won't show on the bridge now!

With 'Real Nav' activated when I ask to Navigator Officer to calculate my position on map when it show my position is this the exact position or it have an error percentage ?

(I'm sorry for my English !!!! :O::cry:)

Have an error... you go in option.py and asearch there... the game pick a random number... by default the max is 8 km if i am remember well... you can increse there the min and the max that the error can be in game

Ok, thanks !!!! I've found it :yeah:
I did not know if it was introduced a calculation error but it is.
I asket to a real submariner if this value could be corrected


Is this section :

######################################### Real Navigation ############################################
# the error (expressed as decimal) for the Navigator's calculation of current position (fix) using celestial navigation (used in real navigation only). This is the max error in meters. It will be used as the -min value and max value of a random function
# below is an float value only! (in meters)
NavCelestialMaxCalcFixError = 5000.0

# the minimum time it takes the Navigator to calculate the current position (fix)
# below is in seconds
NavCelestialCalcFixMinTime = 900.0

# the maximum time it takes the Navigator to calculate the current position (fix)
# below is in seconds
NavCelestialCalcFixMaxTime = 2700.0

# does navigator show position on the maps after he calculates current position (plots a new navigation fix)?
# change below to either True or False
NavShowPositionOnMapsAfterCalc = True

# if NavShowPositionOnMapsAfterCalc enabled, how long does the navigator show the calculated position on the map?
# below in seconds
NavShowPositionOnMapsAfterCalcTime = 20.0

# the max error (expressed as %) a dead-reckoning fix occurs based on distance between fixes (used in real navigation only). This value is fed into a random function as a -min value and max value:
NavDeadReckoningMaxCalcFixError = 15

# minimum time it takes Navigator to plot position based on dead-reckoning
# below is a float value only! (in seconds)
NavDeadReckoningMinCalcTime = 15.0

# maximum time it takes Navigator to plot position based on dead-reckoning
# below is a float value only! (in seconds)
NavDeadReckoningMaxCalcTime = 60.0

So, what did he reply? :hmmm:

I'm waiting for a reply :03:
Initially I don't know if was possible to have an error on the report (position of U-boot) of Navigation Officer.

in my opinion is verry realistic... errors is human... so in real life you can do error when you try to calculate your position celestial... starting from this error after you mouve is logical that you are all the time in error if you are making calculation from dead recoign ... so until next celestial fix you keep doing errors:)