what kind of an error? screenshot?
what system do you run?

Well
At night, at 4500 meters, I make surface attacks with no problem. I have even done this at a bit over 2000 meters. One of the comments on a startup screen has a u-boat captain commenting on being invisible at night at 1000 meters because of the angle and so forth, making the conning tower invisible to the watch on a ship.
A periscope would have to be fully extended with the moon behind it at least.
What do you think?

Ahoy unterwasserduden
I would say no, this is not natural. Daytime perhaps but not night.
Are you using IRAI or any other mods that effect the AI's ability to attack and so forth. If you are, this might be the reason for the extra superman vision of the enemy. I'm assuming you mean meters, if it was Km you wouldn't even know there was an enemy there.
So, you might want to list your mods. This may be adjusted depending on which mods you have loaded up.
D40 :up:

that was pretty much what I was trying to say. It is still possible, depending on how loud you are, what speed are you going (possibly creating a massive wake?), moonlight, ambient light..

I'm not saying that it's impossible to get very very close, I'm just saying that it is possible to spot a uboat from 4500 meters :)

Though, perescope is slightly different subject.

I think what UnderWaterDude is talking about are the "periscope spotted" messages that NewUIs is generating when a ship is around us.

Those messages emulate enemy ships spotting us, and our radio man intercepting their comming our presence. Afaik, they are just random messages, and have nothing to do with our U-boat being actually detected.

IIRC they can be disabled through option editor :up:

hmm, I don't think that is exactly like that, gap.

If you look closely, it comes in in red colloring when it does apply to you (it even works on friendly ships).

And I noticed generally if you are hunting for enemy ships and they spot you and you get that message - they do act as they spotted you. I think it is an actual spot, which TDW made into a radio message from this ships that you MIGHT have a chance of intercept.

The greyed-background messages of subs spotted are indeed random though.

I can be wrong, indeed. :hmm2:
But going by this post by Rongel, I am not the only one thinking so... and indeed, they are not completely random: you have to be within a certain distance from any ship for them to be generated.

Not exactly: those are static messages, but they are not random. They get dispatched to you based on current date/time. :know:

PD 3.2ghz
3 gigs of RAM
1 GIG VC, Nvidia GeForce GT 430
Windows XP SP3

Game runs fine, just having issues with the this latest version. I have
ran previous versions in the past. Just getting back to the game.
This is when I am accessing the Options File-Editor Viewer.

The pic is not as clear as I wanted it.

http://imageshack.us/a/img832/4355/errordj.jpg

try manually downloading and installing .Net ver4 from Microsoft website.

(I think its this link: http://www.microsoft.com/net/download)

Thanks :yep:

Edit: Just updated to the lasted version and it is doing the same thing.

Oh Wow!
Sorry, I forgot about those. Yeah, the periscope sighted messages in gray...
Sorry underwaterdude, my bad.:D Yeah these we don't even worry about. Although the ones from a distance show the positions of merchants and warships.
So, If you get one, take a look on your nav-map and you might see a red ship marker where the periscope or submarine sighted position is. From there, if it is close enough to your course, you can intercept the ship if it hasn't made any course changes by the time you should meet it. I use the periscope sighted messages to locate merchants anyway.
By the way, RDP, about the netframewrk error. This sounds familiar to me like I've read of someone having this or a similar issue with the new UI before.
I'll see if I can locate what this was and if it could help here.
D40 :salute:

Not sure we can help you w/o TDW around, but we try...

Can you open the "Details" and copy/paste them here? (you can see the details button in your screenshot above)

Yep. I think it was with .exe patcher though. Also trying to locate the info.

I'll post them a bit later, thanks for the help.

@ dogfish40, thanks.

@ reallydedpoet

Hi! :salute:

I have the same system - WinXP SP3 and also I have installed - .Net Framework - v1.1, v2.0,v3.0, v3.5, v4.0
I haven't such issues as you have..
TDW said that he wrote his Apps in .Net Framework v2.0
Maybe you need to install v2.0 also?
Hopefully it can help..

Thanks, it's strange really. It's worked for me in the past with no issues. And the game with other mods is running smoothly.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.FileNotFoundException: Could not load file or assembly 'System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified.
File name: 'System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
at TheDarkWraith.SilentHunter5.OptionsFileEditorViewe r.ReadCfgFile()
at TheDarkWraith.SilentHunter5.OptionsFileEditorViewe r.OptionsFileEditorViewer_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Mes sage& m)
at System.Windows.Forms.ContainerControl.WndProc(Mess age& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.O nMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].



************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
OptionsFileEditorViewer
Assembly Version: 1.0.28.0
Win32 Version: 1.0.28.0
CodeBase: file:///C:/Ubisoft/Silent%20Hunter%205/MODS/NewUIs_TDC_7_1_0_ByTheDarkWraith/data/Applications/OptionsFileEditorViewer/OptionsFileEditorViewer.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.