Battle Kat I understand what you are saying but not convinced the porting over of maps will be a smooth process because with the addition of new terrain types the coding between the old and new tiles may change. In fact it has to doesn't it?
Also I accept the new coding for org files and that there will be no backwards compatibility between the old and new. But as a scenario designer like myself you have to remember the most tedious things about building a scenario is the time needed for making the map and then next editing/introducing/building the forces into the scenario, the write up and reinforcement entry.
Sure you can copy and paste the write up probably but the reinforcements have no direct connection to the org file structure.
By that I mean you can see in the reinforcement dialogue that on turn 4 a platoon of Panther tanks comes in and where but it doesn't tell you what division, regiment or battalion it came from in the org file. Sure if you have a single battalion of Panthers then you have a pretty good idea but if you have 4, 5 or 6 battalions like in some of the mega scenarios you have to do that by memory and quite frankly mine is not getting any better. One has to be careful with that or the historical entry of forces in a particular scenario could be fouled up.
In fact to make an old scenario into a new one at the very least one would need 2 screens or another computer. One running EFII and the other running EFIII. So you can look at what you did and what your building anew.The larger you go with a scenario the more work and time involved. No easy task by any stretch of the imagination.
One thing is for sure, any way you slice it there will be some work involved in rewriting some of the old great EFII scenarios into the new EFIII.
Ivan the Big
Archived Forums
Help
Calendar
Member List
Search
){kind=link}
