TarJak
08-07-06, 05:29 PM
Last night I noticed a bug that I'm not sure can be fixed. If there is a way of fixing it I'd like to know.
What happened was I had a saved career (3 Patrols late 1942 in base at La Spezia 29th Flot), then I installed some lite ships mods, (great work Anvart!). To test these I created a new career starting a different name, year and flotilla (1939 Wilhemlshaven 2nd Flot), to see some of the lit ships I'd set up there in my SCR campaign. All good so far, the lit ships are there and I'm a happy camper.
Went back to my original career and set of on my next patrol. I then get a message saying "The base has changed to Lorient" and when I have a look around I'm in the middle of the ocean with no harbour. Checked my map and lo ang behold I'm at 0 degrees long and lat. i.e.; on Greenwich Meridian at the Eqauator!
Killed the patrol and had a look at the save games. From when I created the new career with a DIFFERENT name etc, my flotilla had changed to the 2nd. Workaround went to the save before the change (Luckily in base), and all is fine again. Anyone else seen this sort of behaviour?
What happened was I had a saved career (3 Patrols late 1942 in base at La Spezia 29th Flot), then I installed some lite ships mods, (great work Anvart!). To test these I created a new career starting a different name, year and flotilla (1939 Wilhemlshaven 2nd Flot), to see some of the lit ships I'd set up there in my SCR campaign. All good so far, the lit ships are there and I'm a happy camper.
Went back to my original career and set of on my next patrol. I then get a message saying "The base has changed to Lorient" and when I have a look around I'm in the middle of the ocean with no harbour. Checked my map and lo ang behold I'm at 0 degrees long and lat. i.e.; on Greenwich Meridian at the Eqauator!
Killed the patrol and had a look at the save games. From when I created the new career with a DIFFERENT name etc, my flotilla had changed to the 2nd. Workaround went to the save before the change (Luckily in base), and all is fine again. Anyone else seen this sort of behaviour?