SH5: Bugs, glitches, and issues thread

[Cyborg322]

Originally Posted by Silent Steel

Servus finchOu
This sounds like a lack of RAM.
Check if you have some background programs running.

Viel Glück am Jagd
/Silent Steel

Hmm... 16GB should be plenty enough Xbox Live Geforce Experience can cause stuttering. A background process as you say is most suspect some Antivirus can really hog resources


Simon

[finchOU]

Originally Posted by Silent Steel

Servus finchOu
This sounds like a lack of RAM.
Check if you have some background programs running.

Viel Glück am Jagd
/Silent Steel

Originally Posted by Cyborg322

Hmm... 16GB should be plenty enough Xbox Live Geforce Experience can cause stuttering. A background process as you say is most suspect some Antivirus can really hog resources


Simon

Yeah definitely not a Ram Issue. What do you guys do to shutdown back ground processes? I also have stuttering when looking through the binoculars at a large convoy....like a rapidly vibrating screen...then back to normal. I've never figured that one out.

[Ashikaga]

Quick question.

My navigator for a while now refuses to do celestial fixes.
I click on it and three hours later, realtime, still no fix.

Anyone know what could be wrong ?

[THEBERBSTER]

Hi A
Does he have any Morale?
Peter

[Ashikaga]

Hey Peter, oh yes he does ! Full morale.

I ordered him to do a celestial and this time he did it in about half an hour.

Might have had something to do with the automated scripts.


On another note, not really a glitch but an issue that bothers me, whenever I use the binoculars on deck (not the UZO, my own) I get a darker image, daytime as well as nighttime.

This causes a problem because I all of a sudden cannot see stars anymore at night (or not as many as I should be seeing), and during daytime the darkened lens severely hampers viewing. Is there any way, other than to start editing the .dds file to change this ?

I want clear binoculars (Kriegsmarine U-boat personnel also kept their binoculars quite clear)

[THEBERBSTER]

Hi A
Check this out.
Binoculars With Bearings By Torpedo V1 > Enable JSGME
Binoculars Without Bearings V3 by Torpedo > Enable JSGME

TWOS compatible.
Peter

[Ashikaga]

Thank you Peter, will check those out, though I do not need bearing in my personal binoculars, I need a clear view and not a sudden darkening of the screen as if someone smeared engine grease all over my lens


Now I came across a very annoying problem just now.

It is 23-1-1940 and I received a BdU message dated 05-10-1939 at

When trying to decode it, following all steps, but the number coming up is 312 with Triton. However, the envelope (1940) stays in Hydra and refuses to change code names when I click on it. It also will not change years (if at all possible). Therefore this message cannot be decoded.

It was a message for U,** so probably not even worth decoding.



So is my Enigma defective ? Or just the program/present mission I am doing (Western Approaches).

Would love some explanation/help here.

[vdr1981]

Originally Posted by Ashikaga

Thank you Peter, will check those out, though I do not need bearing in my personal binoculars, I need a clear view and not a sudden darkening of the screen as if someone smeared engine grease all over my lens


Now I came across a very annoying problem just now.

It is 23-1-1940 and I received a BdU message dated 05-10-1939 at

When trying to decode it, following all steps, but the number coming up is 312 with Triton. However, the envelope (1940) stays in Hydra and refuses to change code names when I click on it. It also will not change years (if at all possible). Therefore this message cannot be decoded.

It was a message for U,** so probably not even worth decoding.



So is my Enigma defective ? Or just the program/present mission I am doing (Western Approaches).

The message is for you... "**" is just a starting designation ( I had to use something, but I can't know what Uboat number will game assign to you).
Use OFEV to enter any number you like ...

Would love some explanation/help here.

How about to check some TWoS documentation for a start ? Sometimes I really wonder how many times I have said this...

[Ashikaga]

I have read all there is about this problem.

It does not fix it. I also have watched and followed all tutorials about the enigma to the letter. I keep getting jibberish.

If a message is dated the fifth of Oktober 1939 and arriving the twentythird of januari 1940, I should be okay with the word Strom and not Mundung, does not matter that the message was sent in Oktober 1939. Tried that and failed.

When I then follow (to the letter) all instructions in video as well as documentation, and when I open the assigned envelope, it will NOT give any other codeword than Hydra, nor any other year than 1940.

I tried several things. Change the month to oktober (1940) not working
Januari 1940 with the fifth day (bdu message day 1939) not working
Januari 1940 with the day message received (23-1) not working.

So you can tell me to read documentation all you like. It does not work, period.

Step A: open kennwort envelope : Januari 1940 = STROM
Step B: Code given is :
RN
CT
EC
SW

Step C: Look up CES (Gives 312)
Step D: Look up 312 (gives TRITON)
Step E: Envelope Schlussel M [Refuses to change to Triton, keeps at Hydra. Month can change]
Step F: Day key (jan. 23 1940 = Beta A, VIII H, III M, VI S.
Step G: plugs : 22/8, 18/21, 24/3, 5/20, 4/10, 17/6, 16/11, 2/9, 1/15, UIDZ
Step H: Type in NTCW, get GSNH
Step I: Put GSNH on rotors.

Start decoding the message and...

GET GIBBERISH AND NONSENSE YET AGAIN.





I am deleting the message and BdU can go stick it where the sun dont shine.



.

[vdr1981]

Originally Posted by Ashikaga

So you can tell me to read documentation all you like. It does not work, period.

Did you try this?

[Ashikaga]

DANG !!!!!!!!!!!!!!

I did not find that out until now ? GEEZ !!!!!

That worked. However when exporting the message to the ship's log it refused to send the message. It showed just the txt Enigma MSG and no message.

But I wrote it down so still have it.

(Might have to do with me deleting it from the radio message stack)

Thank you anyway ! (Silly that it was just a tiny thing namely changing the year that I did not know how to).

[vdr1981]

Originally Posted by Ashikaga

DANG !!!!!!!!!!!!!!

I did not find that out until now ? GEEZ !!!!!

That worked. However when exporting the message to the ship's log it refused to send the message. It showed just the txt Enigma MSG and no message.

But I wrote it down so still have it.

(Might have to do with me deleting it from the radio message stack)

Thank you anyway ! (Silly that it was just a tiny thing namely changing the year that I did not know how to).

type the message manually in the right empty box and then send it to the ships log...

[Ashikaga]

THANK YOU !!!





Quick question:

Any way to get the storm sounds to go away when submerged in bad weather? I keep hearing them at 20 meters depth....

[Ashikaga]

I have seen that the "send weather report" in the radio operator's bar is not working/defunct. Is it possible to make it operational since during WWII many U boats reported the local weather to BdU so since I play full realism, I would like to do that too at regular intervals.

[CrabKey]

I have just updated Wolves of Steel to v2.2.1 and when starting a new career received these warnings when first entering the bunker...

Campaign Advance problem detected Return to main menu, etc.

This problem was addressed in this thread once before but I do not understand the cause or the solution which was determined.

The game is installed from DVD
Updated to 1.2
I've tried Uplay on, Uplay off
Administrator rights is correct

If anyone remembers this glitch that would be great, otherwise I shall reinstall.

Thanks!