Posted by: Steve Walmsley
« on: December 19, 2015, 05:23:42 AM »It will be 7.1. Some of the bug fixes will need a DB change. I hope to work on it over the weekend.
Q: Will the next patch be labeled 7.01 or 7.1 ?x.01 usually designates just an .exe change.
Q: Will the next patch be labeled 7.01 or 7.1 ?What does it matter? That said, the last two revisions after a major version have been x.10.
As usual, don't start any major campaigns for a week or two until any obvious problems are found and fixed.
Gonna wait for 7.01 through, With all the new stuff things have to be bugged somewhere.
As usual I forgot to reset window positions when creating a new patch
I'll sort it out for v7.01
...Work is a little mad at the moment so I will get to it in the next few days. Sounds like you should avoid using auto-detect for the moment and I suggest any major campaigns wait for v7.1.
Did you try the solution suggested at the beginning of this bugs thread?
John
I see what happened, the 5. 54 installer contains a zip file with the actual 5. 54 patch, all the missing folders and images are in that. Or you could just install the portable version.
I can't delete the example game. I get an error message instead. Error 3052 was generated by DAO. Recordset File sharing lock count exceeded. Increase MaxLocksPerFile registry entry.
This patch can only be applied to version 4. 2 or later. To apply the patch, unzip the patch file and copy the files as follow:
If i switch ON the "Generate NPR as non-TN" will they eventually advance to TN status or just stay low-tech forever ??Stay low-tech. NPR does not know how to advance from conventional start to TN status.