Well I am amazed as normal, the P-40's are back and so are the Gladiators. Shame you had to cut out the other 190 V's...but hell, the V-18 was the ''Historical'' one and documented, thankyou for putting that in and keeping it there! I take it the V-18 is only for C.U.P?

Don't forget the French Postwar A5's and A8's, I was amazed to learn of these! They are just below the Kangaroo in the planelist.
Yep we test EVERYTHING, usually smashing the install in process, then keep what works! Sometimes we fix things ourselves, CUP has fixed countless items in 412.
I'm sorry about the duff test upload, the new link failed to overwrite the old properly. That's the thing with CUP, the Modular design allows us to prise it apart, break it and put it back together.
Each previous step is always backed up. That's why we do the restore point from time to time. Now we have all taken another step forward together.

Everything is working properly now! Every plane is there, checked some things out and... MAGNIFICENT!
Real nice job, SAS~Monty27.
Discovered just a very, tiny, small, weird thing in FMB. Object 2643 Vehicle Opel Blitz 6700A Medic W(inter) is looking weird... 
BTW, have some questions about these objects… Is it normal some of them are not usable? They are in the list, but cannot be seen. For instance, 1155 human 21 till 1175 human 41 is invisible. Some others, probably buildings, too. Something for the future?
Greetings,
Jenato
Hi Jenato
Yes this is weird but OK. We have so many more objects that I think its OK to overlook the odd tiny anomaly. However, we will fix them all in time.
The reason is that all CUP modules use the vast resource of the
SAS-Modular Map Expansion (SAS-MME). Often overlooked; SAS-MME makes almost every map ever made for Il2 available to the CUP Modules. However, each CUP Module also has different object lists, more modern vehicles in the Jet Age, more horses in Dawn of Flight.
Despite vastly different STD folders for each module the Static.INI for each set must contain common references in order for the maps to load. Any object or reference missing from any of the four Static.INI's, even a miss-spelling, may prevent a map from working and produce the 'Mission Save Bug'. So therefore we have to try and keep a large number of Static.INI references common across all eras, even though they access different material.
All the maps work, loading and saving missions properly, and putting those Static.INIs together took months of testing!
Occassionally I come across a vehicle with the wrong skin - which is what you saw - and its easy to skip past. There is plenty more in there.
Changing the Static.INI is a dangerous practice, and we do one object at time very carefully. However, it is possible to correct the strange skins and I have been doing so, slowly and carefully.
You could help us: During your travels through FMB, should you spot an anomaly, please note these details:
CUP Module: ie, #DOF/#JTW etc..
Object heading: ie, Objects/Stationary Armor etc...
Object Number: in the menu window.
There are very few anomalies left but they can be corrected in the Static.INI, with a bit of patience and testing. With all due respect we advise caution with editing your Static.INI. Of course, you are backed up from the last upgrade but if you pass on your observations to me, via PM, I would be most grateful and we can add them to the testing program.
eMeL, in particualr, went cross-eyed for months, loading maps, saving missions, noting mission save bug... , loading maps, saving missions, noting mission save bug... , loading maps, saving missions, noting mission save bug... , loading maps, saving missions, noting mission save bug...
With the success of CUP we are now lucky enough to actually have a few of the greatest Il2 map makers, like SAS~Farang65, working directly on the CUP SAS-MME. So we are getting some professional help at last and have a lot more to look forward too, including some wonderful new maps.
Again the Modular design helps us out here - new maps and improved Static.INIs will be added to all modules via the next SAS-MME upgrade. Future upgrades of individual modules will also contain the relevant improvements. From the user end - just throw it in!
Simon