I will look into the display issue.
Starting in April would really screw that up. When you first start the game your timescale counter is at 0. Its going to change years in 12 turns. If you start in April, you will have the year changing in summer instead of winter and it would screw up a couple of counters.
Ok that is strange, it does the same thing to me.
It also changes the year every 12 turns after that, so the year on the overview panel changes in July, the year on the main campaign script changes in January like it is supposed to.
If I set the start date to summer in descr_strat and change the year to July, it swaps them around. The date on the main campaign screen changes in July, and the date in the overview panel changes in Jan.
As of now I havent come up with a way to synch them up. My best guess is that the game was hardcoded in one area to a limit of 6 turns per year (RTW code) and when they added the timescale they didnt get it all removed.
I did some testing with the Date condition for events, and it seems like that condition reads the date on the campaign map, not the date on the overview panel.
If you change your descr_strat to summer and set the date to July as I did, then change it to show turns per year, then you will never see the discrepency, and the date on the overview panel will change in Jan. But then you run into the problem of the Date condition reading the date from the timescale which doesnt match the overview panel. So if you set a date of 1450 for an event, it may actually fire in 1451 depending on the summer/winter setting for the event. Irritating.
If anyone else has any ideas on this I would be glad to hear them.
I would never have caught this because I rarely if ever look at that screen. Thanks and + rep.
EDIT: I will do some testing with the 4 and 6 tpy scripts and this weekend and see if they do the same thing.





Reply With Quote












































