Re: SHIII Commander – weird message
 

Delete/rename \SH3 Commander\Cfg\Miscellaneous.cfg and see what happens. I'm hoping that it is the cause, otherwise I have no idea. :hmm:

Re: SHIII Commander – weird message
 

:oops: gee I though that file was under game/data directory...

(correction to my previous post: IXB instead of IXA)

Anyway, I've saw your reference and I've renamed this file from miscellaneous.cfg to miscellaneous_cfg.

1st attempt

Launch SH3 from its original startup link (not through commander) then load my save (coz I'm in the middle of my 21st mission) and got "CE: sonar destroyed sir".

2nd attempt

Launch SH3 from SH3commander, then I load the same saved game, and got "CE: sonar destroyed sir"

sorry, not good news :( might be something else that is affecting or the saves are already compromised with the issue.


Cheers

I'm running GW and I just did another patrol with the same message. This was without SH3 Commander 2.5. FYI

Thanks for the response Jason!

Well, I'm closing this off at this stage. I am not convinced there is a problem with SH3Cmdr: only three, maybe four, people have raised this issue out of literally 100's of users; it still happens when the only two new R2.5 gameplay changes are removed from SH3Cmdr; and it happens when SH3Cmdr is not even running.

My guess is that it is mod-conflict related - a lot of new mods have been released lately. Perhaps there is a common thread amongst those with the problem. If we can crack that, it will help.

Anyway, if someone can conclusively pinpoint it to an SH3Cmdr file, I'll revisit. Unfortunately, no matter what I do, I cannot replicate the problem and I'm running SH3 with GW.

Hi,

I don't know if this helps but i never had this problem with SH3CMDR2.5 and GW so i think that might be why you can't recreate it - the issue only started on my install when i installed NYGM tonnage mod and the unified campaign file over GW. i think that it might have something to do withe NYGM tonnage or the unified campaign not CMDR

Kaleun

On my game, the only thing that changed was installing SH3Commander 2.5 on top of GW.

I don't have anyother mod installed, either have manually changed files.

Anyway I've just removed SH3Commander from my system after rolling back its files. I want to see what happens once I start my 22nd mission without SH3C.

FYI

Nothing destroyed when I started my 22nd mission.

(SH3Commander 2.5 not installed)

What atmosphere mod are you guys running? I've just found some dodgy entries in at least one of GW's Sensors.dat files, which are part of the Atmosphere inclusions. Sensors.dat could be a prime suspect with the kind of errors you guys are getting.

Kpt Lehmann: for reference check at least the default installed Sensors.dat, BalkonGerat_type21 entries, which are mostly in scientific notation. I haven't checked the others yet.

16km range env ( :oops: Im not certain if is this that you are looking for)

I've now installed SH3C2.5 on top of GW again to see if the damage issue ocurr again... I'll get back to this post in next few minutes to report (once the game starts)

Light or dark?

Actually, it doesn't matter. They all have the same (strange) values. Maybe Kpt Lehmann can shed some light?

My theory being, in the absence of anything else, that these values are interfering with only certain pieces of equipment (ie an upgrade perhaps), hence why some people are getting the problem and others aren't.

I've reninstalled SH3C2.5 on top of GW again

Started SH3C2.5 then launched SH3 from it, followed by loading the save-game (in the base before the mission)

I noticed two things:

1) My 22nd mission (without SH3C) started at 11/April/43. With SH3C the same 22nd mission started at 8/May/43.

2) Once I put my feet in the sub, I received as 1st message "CE: Sonar is destroyed, sir"

:(

The GW additional atmosphere mod that I'm using is "Atmosphere mod V2 16km Light"

I had the sonar destroyed message on stock game.

This was with the IX sub on France pens.

Yeah, I'm sure I've read about the issue before, even recently, but definitely last year. There's definitely a combination of events causing it, and the seed is in one of the default (or updated) game files.

:hmm: So thyro, you are running stock SH3 just with GW, right? Just like me.

So, pls zip up the entire affected career folder (including save games) and, size permitting, email it to me. I'll have a look on my machine.