View Single Post
Old 11-02-05, 02:03 AM   #6
JScones
Navy Seal
 
Join Date: Apr 2005
Posts: 5,501
Downloads: 19
Uploads: 0
Default

Quote:
Originally Posted by Georg_Unterberg
I found out something:

If I choose an upgrade (for some days) right before launching the patrol, the date won't get messed up:

I reloaded on 14/Jan/1941. Now I choose a different emblem for 14 days - counter jumps to 28/Jan/1941. I start patrol: bang! - 28/Jan/1941!
next try I reloaded and choose a different flak (for 2 days) - bang! - I'm at 16/Jan/1941!

Changing torps does not work, because you don't spend a day on those.
Now I get the picture - on every other patrol I chose an upgrade of some kind before starting the next - except patrol#2 where I spend renown for qualified crew.
So if I advance the day counter before another patrol, I can prevent the date messup.

Does this help in some way?
Yes. Thanks for the analysis. This helps confirm a few theories of mine. I'm not sure that there is any workaround that I can build into SH3Cmdr to trap this scenario, as these dates are what SH3 writes to the career files: SH3Cmdr can only assume that they are right. Problem is, and I won't call this an SH3 bug because quite simply the SH3 Devs weren't thinking of SH3Cmdr when they developed SH3, but sometimes the wrong date gets written to the career files. It's fixed up/corrected the next time you run SH3, but SH3Cmdr has no way of knowing that it is wrong at the time. I have worked out some known instances when the date will be wrong, but I'm sure they are only a small few instances. Anyway, a wrong current career date is only distracting, as both SH3 and SH3Cmdr work off the last patrol end date.

What you have done, however, is raise something that *may* be considered an SH3 bug and is an extension to what I have found, and that is that even though you increased the days in base by 28 days prior to exiting the career, SH3 didn't recognise this the next time you loaded the Career. That, I think, is something different altogether, especially when it obviously *did* write the correct date to the career files (as demonstrated by the displayed date in SH3Cmdr). There may be a valid answer for this, but it's late, I've just finished work, so I'll think about it more over the weekend. Anyway, it seems that there is at least an interim solution to this problem.

I must admit that I have noticed a few date anomalies over the past week or so...

Quote:
Originally Posted by marhkimov
Will this recent discovery delay the release of SH3 Commander?
Nup, for reasons stated above. Release 2.3 will be available this weekend, pending teh results of testing of all of the new features.
JScones is offline   Reply With Quote