Gw & Sh3 Comander Problems

[Jmack]

Installed both to lates versions ... now on my type VIIB when i choose flank speed it the U-boat stops ... on the type IXB flank speed its no more than 13 knots .
this was the ones i tried ... any ideas ?

[vinceor]

Had this problem. The bandage fix, you have to go back in saved games till the problem isn't there. I got to the point when the game would come up, the first thing I would do was 'Flank speed.' If it worked great, if not then I would reload a previous saved game. I thought it might be part of a sabatage or mechanical breakdown mod.

But I have reloaded SH3 + GW + Unchange_Adding recently. I felt destructive one Saturday morning.

[Jmack]

i have no saved games ... im starting new .

[cobalt]

its an sh3 commander random malfunction

[enaceo]

That's probably sabotage/wear-and-tear/malfunction system added in the new sh3cmdr.It's pretty neat actually now you have to make sea-trials to see crash-dive depth,engine speed,condition of the periscope...Some people said crash-dive took them to 120 m because of sabotage

[JScones]

From the SH3Cmdr readme file (it's always a good idea to first read the documentation that comes with programmes that you install as they tend to sometimes provide some handy info about the product )...

Simulated equipment malfunctions plus (optional) damage caused by sabotage - by Hemisent.
Simulates the effect of equipment malfunctions plus damage caused by sabotage by randomly reducing default equipment specifications. Editable through 'Randomised events.cfg' and the seven 'Randomised events_19**.cfg' files located in your SH3 Commander\Cfg folder. By default, only malfunctions are simulated. However, deleting or renaming the seven 'Randomised events_19**.cfg' files will leave the 'Randomised events.cfg' file active, which includes both malfunctions plus damage caused by sabotage overlayed.

Hehe, no need though to delete patrols to get rid of the feature if for some reason you don't want it. Just delete FROM the first MALFUNCTION entry to the end in each of the SH3 Commander\Cfg\Randomised events *.cfg files.

[mr chris]

Originally Posted by enaceo

That's probably sabotage/wear-and-tear/malfunction system added in the new sh3cmdr.It's pretty neat actually now you have to make sea-trials to see crash-dive depth,engine speed,condition of the periscope...Some people said crash-dive took them to 120 m because of sabotage

Yes i had to crash dive on my lastest patrol and the boat did not stop going down untill i noticed we were at 190m! In future i will be testing crash dives!

[Jmack]

im not shure i like that feature ... can we disable it ?

[CWorth]

Originally Posted by Jmack

im not shure i like that feature ... can we disable it ?

Look 2 posts above yours.

Originally Posted by JScones

Hehe, no need though to delete patrols to get rid of the feature if for some reason you don't want it. Just delete FROM the first MALFUNCTION entry to the end in each of the SH3 Commander\Cfg\Randomised events *.cfg files.

What you will be looking for are entries that start like this...

MALFUNCTION SETTINGS
[Mal0:data\Library\GUNS_SUB.sim]
;Flak guns taking additional time to reload or being unable to reload at all..Simulates guns affected by long exposure to sea water, battle damage etc. Poor quality ammunition also causes jamming.
;Reload time in seconds
;1939 8% randomization
ApplyToPeriod=19390901|19391231
ChooseFrom=62

You will need to delete everything after the MALFUNCTION SETTINGS line in all 8 randomised_events.cfg files.You can find these in the C:\SH3 Commander\Cfg folder.

[Jmack]

did i mentioned that i hate to edit stuff ?

so if i start sh3 normally withouy sh3 commander will it run normaly ? or must i unninstall sh3 commander ?

thanks

[zzsteven]

Originally Posted by Jmack

did i mentioned that i hate to edit stuff ?

so if i start sh3 normally withouy sh3 commander will it run normaly ? or must i unninstall sh3 commander ?

thanks

If you start SH3 normally you won't have malfunctions. But you will miss out on the other good things in Commander.

I like the malfunctions mod, it adds some uncertainty to a patrol. Sort of like real life.

zz

[JScones]

If you don't feel comfortable editing the "Randomised events *.cfg" files, just delete them. You'll lose the randomised lost contact time and thermal layers, but you'll still have the other benefits of SH3Cmdr.

However, it's not real hard to open a file, look for one line, and delete everything after it.

[CWorth]

I saved you the trouble of editing the files yourself..

Just stick these in the SH3 Commander\Cfg folder

Randomized files<---click here for files

[Jmack]

i would agree with the randomized malfunction as long as i had a "randomized" repair during mission the problem would get worse or it would improove( taking on consideration the crew experience of course and other factors ) ... no fun in going flank speed and the thing doenst go more than 13 knots , and i found this right in the exiting of the harbor, i agree that sh3 commander its a really nice complement to the game but imagine this i go on patrol i notice some malfunction , i go back and loose one patrol ... ok not too bad , but on the next patrol i leave harbor and detect same problem.

anyway i looked at the files and for what i understand i have to delete everything on 8 files ( RANDOMISED EVENTS ) below this line
;-----------------------------------------------------MALFUNCTION SETTINGS

if someone is willing to post a detailed instrucion of what to do i will try it but editing always brings more problems to me ... or i can try and live with it despite the fact that i think the randomized malfunctions is exagerated cause in 4 missions i always had the same problem or similar .

[Jmack]

LOL ... nevermind some parts of the las post

thanks ill keep the files and i promisse il try to play it with sh3 commander