Well got the mods up and running again (I think) having some issues with some maps and or Ship pack, Also im finding my Screen locks up when flying with lots of flack and other things in the mod pack was wondering if somone could help me sort yhis out,
Thanx Ranger
The Tin Man
Post a replyMODS HELP
5 posts
For the maps, be sure that you, or the installer, added entries into the ALL.ini file in your \IL-2 Sturmovik 1946\MODS\MapMods\Maps directory or IL2 won't find the new maps. Also, I saved my MOD posts from the old site. Here's my experiences with loading ShipPack 2.0:
In my quest to load Dixiecapt's VMF-213 Hell Hawks Campaign for The Slot, I started adding the numerous necessary mods, one after the other. Big mistake. At the end of it all, I had the dreaded 70% CTD (crash to desktop) and no idea which mod broke my game. Killed the MOD and files folders, reinstalled the Unified Installer, confirmed I was back up and running, then crawled off to lick my wounds...
I decided to try again, installing one mod at a time and checking to see if the game broke. First up was the biggest one, ShipPack2.0. The campaign calls for ShipPack1.0 but that has been supeceded. Installed the pack, promptly got the 70%CTD. Started working through the problem discussion thread.
- per fly_zo, change technics.properties to technics_ru.properties in Mods\STD\i18n ... nope, still 70% CTD
- Found this from Graf on page 4 of the thread "For anyone with the Static_AC Mod...you must change your stationary and technics .ini files in that folder to get the ShipPack to work." Static_AC is part of the Unified Installer, so I used WinMerge (freeware) to compare stationary.ini and technics.ini in MODS\Static_AC\com\maddox\il2\objects with those included in the ShipPack. Copied relevant lines from ShipPack ini files to Static_AC ini files, then deleted from MODS\STD\com\maddox\il2\objects so the only instance is in Static_AC
BINGO! Operational IL2 with new ships
In my quest to load Dixiecapt's VMF-213 Hell Hawks Campaign for The Slot, I started adding the numerous necessary mods, one after the other. Big mistake. At the end of it all, I had the dreaded 70% CTD (crash to desktop) and no idea which mod broke my game. Killed the MOD and files folders, reinstalled the Unified Installer, confirmed I was back up and running, then crawled off to lick my wounds...
I decided to try again, installing one mod at a time and checking to see if the game broke. First up was the biggest one, ShipPack2.0. The campaign calls for ShipPack1.0 but that has been supeceded. Installed the pack, promptly got the 70%CTD. Started working through the problem discussion thread.
- per fly_zo, change technics.properties to technics_ru.properties in Mods\STD\i18n ... nope, still 70% CTD
- Found this from Graf on page 4 of the thread "For anyone with the Static_AC Mod...you must change your stationary and technics .ini files in that folder to get the ShipPack to work." Static_AC is part of the Unified Installer, so I used WinMerge (freeware) to compare stationary.ini and technics.ini in MODS\Static_AC\com\maddox\il2\objects with those included in the ShipPack. Copied relevant lines from ShipPack ini files to Static_AC ini files, then deleted from MODS\STD\com\maddox\il2\objects so the only instance is in Static_AC
BINGO! Operational IL2 with new ships
Ok this is greek to me id like to get on comms with either bosti or Lobo On monday sometime to sort this out, I dont wana miss another mission night due to my mods being FUBAR.. so shoot me an email when ya want me on comms on monday night,,, Ill be home about 2200 Hrs EST. I gotta teach a late leadership lab class tomarrow for one of my Fellow officers who is on leave