Cannot run SH3 Commander 2 - can anybody help?

Hauptman · 10-07-05, 07:37 AM

One more thing I just noticed. I tried to run SH3 and there was written "loaded with SH3 Commander..." Also the carreer I set up was there. So I loaded game, got out of harbour and then returned back and docked back in harbour (i.e., finished one patrol). It seems that even if it did not let me through when I tried to set-up the carreer in SH3 Comm screen, SH3 Comm in fact generated the carreer I requested.

Now SH3 Commander recognizes this patrol. I can see it in the SH3 Com screen, I can do crew management etc. I still only have problems with setting-up a new carreer (stil the same error message when I click on the setting-up a new carreer line and year/month buttons).

On the other side, it must be something with the flotillas.cfg. I tried to remove the file - SH3 Comm worked fine - no error, but I had not flotillas and subs at all (which is obviously logical). So there is probably flotilla.cfg accessibility error.

Thread Tools
Show Printable Version Email this Page
Display Modes
Switch to Linear Mode Hybrid Mode Switch to Threaded Mode

10-07-05, 07:37 AM	#1
Hauptman Swabbie Join Date: Oct 2005 Location: Prague, the Czech Republic Posts: 6 Downloads: 0 Uploads: 0	One more thing I just noticed. I tried to run SH3 and there was written "loaded with SH3 Commander..." Also the carreer I set up was there. So I loaded game, got out of harbour and then returned back and docked back in harbour (i.e., finished one patrol). It seems that even if it did not let me through when I tried to set-up the carreer in SH3 Comm screen, SH3 Comm in fact generated the carreer I requested. Now SH3 Commander recognizes this patrol. I can see it in the SH3 Com screen, I can do crew management etc. I still only have problems with setting-up a new carreer (stil the same error message when I click on the setting-up a new carreer line and year/month buttons). On the other side, it must be something with the flotillas.cfg. I tried to remove the file - SH3 Comm worked fine - no error, but I had not flotillas and subs at all (which is obviously logical). So there is probably flotilla.cfg accessibility error.