will the patch be game save compatible? i really hate starting over and
over between patches and mods. thanks!
over between patches and mods. thanks!
Preset theatres work for historical situations. The problem comes when there is an ahistorical situation...
building and testing a patch installer (assuming it works first up) is a day long process so 5 small patches is 4 man days of time lost that could be fixing stuff.
Also King, I don't know if you guys have worked on this yet, but please let AI programmers know that AI should avoid certain amount of stacking penalty as a matter of being hardcoded. Right now it suffers too much from stacking ridiculous amount of divisions on small province that the combat effectiveness of the units in there are completely lost, and with poor theatre commander, most units never see fight while end up retreat/surrendering. I'm seeing this happening too many times in 1944 scenario as Germany, fighting against USSR.
I believe one of the 1.4 threads indicates that the "superstack" issue is already being looked at.
You're saying you know 1.4 isn't betatested yet?IIRC, it was said by one of the devs that it's already been addressed and/or completely fixed for 1.4.
If it's not fixed already, then it should be by the time the RC for 1.4 is ready for beta testing.
You're saying you know 1.4 isn't betatested yet?
I believe one of the 1.4 threads indicates that the "superstack" issue is already being looked at.
This issue could be different. I was following the process of channel island superstack fix so I knew that, but here I am talking about AI stacking 15 ~ 20 divisions on the front because it ran out of provinces that share border with its enemy. This stacking that I'm currently refering to is not fatal to the AI, but it reduces its efficiency when it could have had the upper hand.
This issue could be different. I was following the process of channel island superstack fix so I knew that, but here I am talking about AI stacking 15 ~ 20 divisions on the front because it ran out of provinces that share border with its enemy. This stacking that I'm currently refering to is not fatal to the AI, but it reduces its efficiency when it could have had the upper hand.
Well now we have some more infromation about the flag troubles I can have another look at them.
So the balancing factor is the amount of time it takes to test the patch installer?
Hell, I would take that and get small bits of fixes here and there even if it takes 4 months to fix most of the stuff than wait 3 months for same amount while having nothing in between.
Edit: Also on preset theatres, I've been thinking, I see absolutely no problem with preset theatres and ahistorical war. As I suggested, if the theatres pop up after you occupy a territory that belongs in the theatre, what would be wrong with it? Would the AI eat up too much resources trying to reorganize everytime it conquers and get new theatre?
Also King, I don't know if you guys have worked on this yet, but please let AI programmers know that AI should avoid certain amount of stacking penalty as a matter of being hardcoded. Right now it suffers too much from stacking ridiculous amount of divisions on small province that the combat effectiveness of the units in there are completely lost, and with poor theatre commander, most units never see fight while end up retreat/surrendering. I'm seeing this happening too many times in 1944 scenario as Germany, fighting against USSR.
You're saying you know 1.4 isn't betatested yet?
It could be different, but if I remember the post right, it was stated that they were fixing "the problem of superstacking WITHOUT just fixing the overly obvious Channel Islands specific occurrance of it"
While I agree that time should be spent on bugfixing and not creating installers, I think you can be more couragous with releasing beta patches to the community (in a simple .rar archive).
The last beta patch for 1.3 was downloaded less than 1000 times, those are just the forum readers. Generally, most people on this board like downloading new versions, they like to see stuff happening.
And you don't have to bother submitting installers for all those patches to the different retailers.
Of course I know you would be flooded with feedback the likes of "Could you fix problem A....", "Why is a fix for B not included, ....", "Feature Z should be in", "Unit XY is to strong", "Game still slow in 1942", and so on. (and I know this can be very discouraging)
But still, you would also get a lot of desired feedback much faster than your internal testing can possibly deliver.
We have finite budgets for patching, that's the way things are. So time taken to make installers is time subtracted from making patches, reducing the ammount of things we can do with the patching process.
The supetstack issue is being looked at.
While I agree that time should be spent on bugfixing and not creating installers, I think you can be more couragous with releasing beta patches to the community (in a simple .rar archive)....