Good afternoon,
I let Kurt know about the busted link (it looked like he uploaded the picture, not the aircraft) and deleted it for the time being. As soon as it is re-uploaded, I will place it in the library.
Done and done.
-
Please see the most recent updates in the "Where did the .com name go?" thread. Posts number 16 and 17.
-
IMPORTANT DOWNLOADING INFORMATION - ALL MEMBERS PLEASE READ
Please see this thread for updates. Update Thread
SOH ADMINISTRATION
Thirteen new FDG2 P-51B/C upgrade packages uploaded
- Thread starter Captain Kurt
- Start date
Done and done.
AI FDG2 P-51B
A new entry has been added to Add-Ons Library, category CFS 2 Aircraft - American
Description: AI FDG2 P-51B
Ground attack version of Upgrade package for the 354th FG in WWII campaign by Captain Kurt
Flown by an unknown pilot, 355th Fighter Squadron at Lashenden, England, April 1944
I chose this model as the best P-51B/C Malcomb Hood CFS2 model for use in the 354th Fighter Group in WWII campaign. With Gramps' permission I have added a number of improvements to upgrade the flight model, increase AI combat performance, added correct drop tanks, improved cockpit panel, and three new skins for 354th FG pilots.
To check it out, rate it or add comments, visit AI FDG2 P-51B
The comments you make there will appear in the posts below.
A new entry has been added to Add-Ons Library, category CFS 2 Aircraft - American
Description: AI FDG2 P-51B
Ground attack version of Upgrade package for the 354th FG in WWII campaign by Captain Kurt
Flown by an unknown pilot, 355th Fighter Squadron at Lashenden, England, April 1944
I chose this model as the best P-51B/C Malcomb Hood CFS2 model for use in the 354th Fighter Group in WWII campaign. With Gramps' permission I have added a number of improvements to upgrade the flight model, increase AI combat performance, added correct drop tanks, improved cockpit panel, and three new skins for 354th FG pilots.
To check it out, rate it or add comments, visit AI FDG2 P-51B
The comments you make there will appear in the posts below.
Capt Kurt,
Do you mind if I take the Tuskegee Airmen skins that SopwithC created for the original FDG2 P-51B/C and put on one of your new flight models and on one of your AI models?
Do you mind if I take the Tuskegee Airmen skins that SopwithC created for the original FDG2 P-51B/C and put on one of your new flight models and on one of your AI models?
kelticheart
Charter Member
Splendid materials indeed, Capt Kurt! Thank you! :salute:
There's only one thing I do not understand, and it's why all of them were uploaded as 13 standalone packages, each one of them with soundpacks, individual files and 2d panels. The average size of each one of them is about 8.5 Mb, times 13, makes it a total of about 110.5 Mb.
Both Alpha's P-51D and FDG2's P-51B/C could have been uploaded as a single pack with one soundset, panel, airfile, dp, model and cfg files and with all the different repaints in their separate folders. Even better: common texture files, like vc's, pilots, props, wheels, and whatever other common details, can be grouped in just one folder, with separate folders only for fuselage, wings and tailplane textures.
One upload organised like that for Alpha's P-51D and FDG2's P-51B/C, as I saw many other members do with multi-skin uploads. A much smaller upload size, which I routinely do when I group original uploads together for my archives on CD/DVD.
Using this tecnique not only helps some of us who still do not have easy access to wide-band connections, it also helps SOH with keeping storage space on the servers low with ever-increasing Internet costs.
This is not meant to be a criticism, just a suggestion from which both downloaders and SOH may benefit a lot. It's also a suggestion for each one of us who like to upload what we can produce with our skills, as I saw this habit of uploading the same files over and over, creating a huge mass of duplicates, many other times.
And now I am off to make one package each for your beautiful, strictly historical repaints.....
Cheers!
KH :ernae:
There's only one thing I do not understand, and it's why all of them were uploaded as 13 standalone packages, each one of them with soundpacks, individual files and 2d panels. The average size of each one of them is about 8.5 Mb, times 13, makes it a total of about 110.5 Mb.
Both Alpha's P-51D and FDG2's P-51B/C could have been uploaded as a single pack with one soundset, panel, airfile, dp, model and cfg files and with all the different repaints in their separate folders. Even better: common texture files, like vc's, pilots, props, wheels, and whatever other common details, can be grouped in just one folder, with separate folders only for fuselage, wings and tailplane textures.
One upload organised like that for Alpha's P-51D and FDG2's P-51B/C, as I saw many other members do with multi-skin uploads. A much smaller upload size, which I routinely do when I group original uploads together for my archives on CD/DVD.
Using this tecnique not only helps some of us who still do not have easy access to wide-band connections, it also helps SOH with keeping storage space on the servers low with ever-increasing Internet costs.
This is not meant to be a criticism, just a suggestion from which both downloaders and SOH may benefit a lot. It's also a suggestion for each one of us who like to upload what we can produce with our skills, as I saw this habit of uploading the same files over and over, creating a huge mass of duplicates, many other times.
And now I am off to make one package each for your beautiful, strictly historical repaints.....
Cheers!
KH :ernae:
tonybones2112
Charter Member
Kurt, you've done a monumental task. Bravo:salute:
Tony
Tony
Back in town again so I can respond.
Thanks all for the compliments.
SPman - yes the campaign will require a new CFS2 ETO install unless you have already created an ETO install using Rami's guide. If so you can just drop in the campaign files. aircraft and a few other things and it will work.
Devildog - please do, you don't need any special permission. But thank you for aking anyway.
Kelti - I understand what you are saying and for the campaign installer I will use something like that. Each plane will have its own folder but the panel and sound will each have a single folder and all of the aircraft will be aliased to those. I also tried to alias the model file but it did not work consistently, sometimes yes, sometimes no.
For the stand alone planes just submitted, I thought about what you suggest, but I decided on separate complete uploads for several reasons. One is that some guys will only want a few, but not all of the planes. Given the different hits shown on the downloads, that seems to be true. Two is that it would be hard to illustrate all of the skins in some of the thumbnails so you could see what was available. Three is that uploading the skins separately means over time, they could become separated from the model and are in separate download sections anyway. Maybe the wrong choice? But that's the reasoning behind it.
Cheers all.
Thanks all for the compliments.
SPman - yes the campaign will require a new CFS2 ETO install unless you have already created an ETO install using Rami's guide. If so you can just drop in the campaign files. aircraft and a few other things and it will work.
Devildog - please do, you don't need any special permission. But thank you for aking anyway.
Kelti - I understand what you are saying and for the campaign installer I will use something like that. Each plane will have its own folder but the panel and sound will each have a single folder and all of the aircraft will be aliased to those. I also tried to alias the model file but it did not work consistently, sometimes yes, sometimes no.
For the stand alone planes just submitted, I thought about what you suggest, but I decided on separate complete uploads for several reasons. One is that some guys will only want a few, but not all of the planes. Given the different hits shown on the downloads, that seems to be true. Two is that it would be hard to illustrate all of the skins in some of the thumbnails so you could see what was available. Three is that uploading the skins separately means over time, they could become separated from the model and are in separate download sections anyway. Maybe the wrong choice? But that's the reasoning behind it.
Cheers all.