[crazydog]

sorry i forgot to add that i had fisrt put in sas mod activator, and then run the two uni's. do i need to add all new ac lines manualy?

yes you must add all new lines manually
and you must reinstall the sas mod activator, cause the UI1.1 also have the Il2fb.exe, files.SFS and wrapper.dll files, if you install the sas mod activator first, they are overwrited by the UI's old files

[Dietz]

Please my head hurts too...I am loaded with mods from here & SAS all presently working fine ...so far....but I have some questions re 1.2 that no one has aswered clearly anywhere.
1.) If I do a virgin install,do I need to manually reinstall everything (planes, maps,objects,effectsand respective STD notations) or can I simply bring them all back from a copied modded version, by dragging them over to virgin game?
2.) I have been using mostly SAS install lately & SAS "buttons",I assume the 1.2 will change that somewhat,right?Should I reinstall SAS installer & newest buttons,when they become available?
3.) Will 4.09M work without alot of fiddling or will it work with game switcher ( I have this but never tried to use it for two differnt versions of the game...does it require two versions on Crive? BTW I tried to install it directly over a copy of my copy modded Il-2 & got it to go to 95% istall before it stopped working. I have been told to first use the games standard 4.09bm config file & eliminate all the dll.s before installing 4.09m over modded game , but I didn't do this & obviously it doesn't work...no painits a copy...
4.) Will all future mods depend on 1.2 being installed or will a yet to be offered plane installer version allow us to continue to install new aircraft ( like the brand new betas of the F-86 & Mig 15 that now require 1.2 to work,) or will new SAS" Buttons " probably allow me to do the same? If so I will have to decide to bite the bullet.
5.) Should I just wait a while til the bugs are ironed out...if I dare call them bugs? I have plenty to play with now ( tho I miss the chance to look over the SM79 in the 4.09 release...
The fact of the matter is I'm no computer whiz..I have done a couple of dozen virgin reinsatlls since joining the merry crew here at AAA & SAS & frankly I'd like to avoid all that time of doing it again...but I don't want to be out in the cold when the Lancaster or Blackwidow or Meteor comes along.Can someone clearly address all of these concerns? I'd like to enjpy the play experience as much as the "collecting/installing " experience... :wink:

[Bearcat]

I just switched to 4.08.. (Dont know if that was necessary or not) and I installed 4.09m to a seperate folder on my desktop. Then I took the SFS & exe files from 4.09m on my desktop and dropped them into my 4.09 Mods OFF (Original) folder that is located in :C:\Program Files\Ubisoft\IL-2 Sturmovik 1946\_Game Switchers. That enabled me to get to the stock 4.09m with no mods from hitting 4.09b1 Standard on my switcher. Then I took the files from :C:\Program Files\Ubisoft\IL-2 Sturmovik 1946\_Game Switchers\4.09 Mods 6DOF ON and dropped them into the C:\Program Files\Ubisoft\IL-2 Sturmovik 1946\_Game Switchers\4.09 Mods ON (NO 6DOF) folder.. That enabled me to switch to 4.09b1mM by hitting 4.09b1 Mod on my switcher. Then lastly I took the SFS files from the folder on my desktop that I installed 4.09m into and dropped it into the folder C:\Program Files\Ubisoft\IL-2 Sturmovik 1946\_Game Switchers\4.09 Mods 6DOF ON and I then took the 4,09 files and copied them into my main 46 folder. I ionstalled the UI 1.2 over this and so far everything seems to work fine except that I get Russioa text only in the rank drop down menu in a campaign. But the mission brief etc is in English..

When I hit 4.09b1 Standard on my switcher I get stock 4.09m. When I hit 4.09b1 Mod I get 4.09b1 w 6DoF, and when I hit 4.09b1 Mod w 6DoF I get 4.09mM w 6DoF. I elimin ated the option all together for any version without 6DoF since I have TIR and will never use anything w/O 6Dof..

Eventually I will eliminate the 4.09b1mM option as things settle down and probably wind up with a 4.09m/4.09mM until the next patch comes out. But so far everything works fine.

[Salty54]

Dietz,

I have created two distinct configurations, one for AAA UI 1.2 and another for SAS with 2.3 Button. The answer to your question is yes, you have to manually add all your mods into your configuration. I tried to shortcut adding mods and it froze at 60% loading. Nothing I did resolved it so I had to start over. In betweeen each mod addition I started up the game and verified that it worked. It took a long time.

For the AAA UI 1.2:
1. Download all the 1.2 files and use Winrar to verify that no corrupted files exist. Do this before proceeding to overload onto UI 1.1 (1.2 requires 1.1 to work).
2. You need to have a clean, fresh, un-modded 1.1 to load over. I stress it must be a totally non-modded configuration. I started with a fresh install of 4.07 from the DVD, then added the 4.08 patch, then UI1.0, UI 1.1 ect.
3. Add whatever mods you desire. This is the long tedious part. If you approach this cautiously and verify each addition, it will work. Note: Mods for cockpit makeovers, special effects and such can be copied and pasted right into your Mods folder. Aircraft additions require changes to your air.ini, plane.ru and weapons.ru files. Before you drop the new aircraft into the MODS folder, make sure that you have added the new information correctly into these files. Map additions require that you update the all.ini file to add the map load.ini information. If you have add the QMB Plus or Pro mod then you need to update the config.ini to show the new map, plus add the template mission sets required for the new map to be used in quick missions. Some maps require the static.ini file to be updated to display ground objects correctly. This is critical that the information is added correctly or your game will crash. This was a problem I had with Cannon's BoB map. It requires three other mods which have their own additions to the static.ini files to work.

For SAS:

1. Download the latest Button file 2.3. This has been updated to support PeterD's F86 and Mig15.
2. Make a clean 4.07 install from your DVD, then update it to 4.08 and finally 4.09. Make sure that in between updates the game starts up and runs correctly.
3. Download the latest SASMODACT and extract the six items, Dgen folder, FILES folder, MODS folder, Files SFS, il2fb.exe and the wrapper.dll. Copy and paste these into your root 4.09 configuration.
4. Copy and paste the Button 2.3 file into MODS/STD/gui/Game folder and replace the button file there. You are now ready to put mods into your game.
5. Use the SAS default sound patch so you can hear sounds in your game. The patch comes with a excel spreadsheet showing which PRS file links to a particular aircraft in the game. Use this matrix to change your preferred sounds accordingly. The PRS files are loacted in the game root directory FILES/Presets/Sounds folder. You will have to create a new folder called Samples and add it to your FILES folder. The sound .wav files go in this folder. You can open up the PRS file with Notepad in order to read its contents. The PRS file tells the game which .wav file to use. This was a long process for me, so depending on how much you want to change, it will take some time.
6. SAS requirtes that all mods be added manually. Do not use the F86 or Mig15 auto installer at all! It will mess up your game. Open these up with Winrar and extract contents to another folder not in the game. From the folder, copy and paste the aircraft MOD folder into your MODS folder. Usually a readme file is included that tells you what information needs to be added to the air.ini, plane.ru and weapons.ru file.
7. Refer to No. 3 above for adding your other mods to the SAS configuration. It works the same.

From your comments, it looks like you already know a lot about adding mods so if this is old stuff disregard. The bottom line is that there is no quick easy way or shortcut. UI 1.2 makes adding a lot of mods at one time easier but you get a lot of mods you may not neccessarily use and it makes the loading time long. SAS requires more work but you get only the mods that interest you and its leaner and faster loading.

Good luck!

BTW, I really like your art work. You are very skilled and talented.

[Dietz]

Dietz,

I have created two distinct configurations, one for AAA UI 1.2 and another for SAS with 2.3 Button. The answer to your question is yes, you have to manually add all your mods into your configuration. I tried to shortcut adding mods and it froze at 60% loading. Nothing I did resolved it so I had to start over. In betweeen each mod addition I started up the game and verified that it worked. It took a long time.

For the AAA UI 1.2:
1. Download all the 1.2 files and use Winrar to verify that no corrupted files exist. Do this before proceeding to overload onto UI 1.1 (1.2 requires 1.1 to work).
2. You need to have a clean, fresh, un-modded 1.1 to load over. I stress it must be a totally non-modded configuration. I started with a fresh install of 4.07 from the DVD, then added the 4.08 patch, then UI1.0, UI 1.1 ect.
3. Add whatever mods you desire. This is the long tedious part. If you approach this cautiously and verify each addition, it will work. Note: Mods for cockpit makeovers, special effects and such can be copied and pasted right into your Mods folder. Aircraft additions require changes to your air.ini, plane.ru and weapons.ru files. Before you drop the new aircraft into the MODS folder, make sure that you have added the new information correctly into these files. Map additions require that you update the all.ini file to add the map load.ini information. If you have add the QMB Plus or Pro mod then you need to update the config.ini to show the new map, plus add the template mission sets required for the new map to be used in quick missions. Some maps require the static.ini file to be updated to display ground objects correctly. This is critical that the information is added correctly or your game will crash. This was a problem I had with Cannon's BoB map. It requires three other mods which have their own additions to the static.ini files to work.

For SAS:

1. Download the latest Button file 2.3. This has been updated to support PeterD's F86 and Mig15.
2. Make a clean 4.07 install from your DVD, then update it to 4.08 and finally 4.09. Make sure that in between updates the game starts up and runs correctly.
3. Download the latest SASMODACT and extract the six items, Dgen folder, FILES folder, MODS folder, Files SFS, il2fb.exe and the wrapper.dll. Copy and paste these into your root 4.09 configuration.
4. Copy and paste the Button 2.3 file into MODS/STD/gui/Game folder and replace the button file there. You are now ready to put mods into your game.
5. Use the SAS default sound patch so you can hear sounds in your game. The patch comes with a excel spreadsheet showing which PRS file links to a particular aircraft in the game. Use this matrix to change your preferred sounds accordingly. The PRS files are loacted in the game root directory FILES/Presets/Sounds folder. You will have to create a new folder called Samples and add it to your FILES folder. The sound .wav files go in this folder. You can open up the PRS file with Notepad in order to read its contents. The PRS file tells the game which .wav file to use. This was a long process for me, so depending on how much you want to change, it will take some time.
6. SAS requirtes that all mods be added manually. Do not use the F86 or Mig15 auto installer at all! It will mess up your game. Open these up with Winrar and extract contents to another folder not in the game. From the folder, copy and paste the aircraft MOD folder into your MODS folder. Usually a readme file is included that tells you what information needs to be added to the air.ini, plane.ru and weapons.ru file.
7. Refer to No. 3 above for adding your other mods to the SAS configuration. It works the same.

From your comments, it looks like you already know a lot about adding mods so if this is old stuff disregard. The bottom line is that there is no quick easy way or shortcut. UI 1.2 makes adding a lot of mods at one time easier but you get a lot of mods you may not neccessarily use and it makes the loading time long. SAS requires more work but you get only the mods that interest you and its leaner and faster loading.

Good luck!

BTW, I really like your art work. You are very skilled and talented.

Well I am practiced at reinstalling ...so I'll give your suggestions a try...maybe I'll separate careeresfor each install? Thanks for the compliment..I shpuld go back to painting for a while!!! :?

[norm]

my last queston. (i hope) would it work if i just copied the info from sas Air.ini, plane_ru.properties and weapons_ru.properties in to the Uni ones, and put those in the place of the SAS mod activator ones?
also sence SAS is down, where can i get there laitest buttons?

[8FS_Bulau]

...I installed the UI 1.2 over this ...

When I hit 4.09b1 Standard on my switcher I get stock 4.09m.
When I hit 4.09b1 Mod I get 4.09b1 w 6DoF...

Sounds like you still have 4.09m and U.I. 1.2 (which is 4.09b1m) separate.
I thought you were saying you made them work together...in other words, can you do this:

Open up the new 3BG_KTO map in FMB (this comes with U.I. 1.2)
Try to place a SM.79 aircraft (this comes with 4.09m) onto that map.

[Bearcat]

Ahhh! Havent tried that yet!! I cant even find the SM79 ... It is in the stock 4.09m.. but with 4.09mM I cannot find it.. So there are indeed issues.. but I had no crashes..

[8FS_Bulau]

Ahhh! Havent tried that yet!! I cant even find the SM79 ... It is in the stock 4.09m.. but with 4.09mM I cannot find it.. So there are indeed issues.. but I had no crashes..

I don't think it is an "issue" so much as due to the fact that what you have done is still maintaining separate versions of 4.09 and 4.09b1m. The difference is in the files.SFS that is in use when you start the game.

I added the U.I. 1.1 content (MODS and Files folders, .exe and wrapper) to my 4.09m official, and I can get the SM.79 in that, along with all the 1.1 Mods, but I had to use the SAS buttons to make it work. What I would have to try now, is doing the same thing with my U.I. 1.2 content.

One problem will be that the AAA buttons that come with 1.2 might not included the 4.09m aircraft.

[Bearcat]

I don't think it is an "issue" so much as due to the fact that what you have done is still maintaining separate versions of 4.09 and 4.09b1m. The difference is in the files.SFS that is in use when you start the game.
I added the U.I. 1.1 content (MODS and Files folders, .exe and wrapper) to my 4.09m official, and I can get the SM.79 in that, along with all the 1.1 Mods, but I had to use the SAS buttons to make it work. What I would have to try now, is doing the same thing with my U.I. 1.2 content.
One problem will be that the AAA buttons that come with 1.2 might not included the 4.09m aircraft.

That was basically what I did as well..

So I wonder why when it loads up is says v4.09m on the lower right hand corner? .... That was why I thought it was running in 4.09m.. but when I tried what you sugested it didnt work.. and when I went to fly the SM79 it wasn't there.. Hmmm .. I am certain a fix is forthcoming..

[8FS_Bulau]

If it says 4.09m, then it is using the 4.09m files.SFS. Did you add the 4.09 aircraft to your air.ini? That must be done for your modded game to have those aircraft, but then they must be in whatever buttons your are using, too, or you will get a 60% CTD.

[Dietz]

Probably asked and answered somewhere but if I do a fresh install do I still need to add 4.08 or 4.09beta before the 4.09 new patch or are they covered by 4.09 :???: ?

[8FS_Bulau]

Probably asked and answered somewhere but if I do a fresh install do I still need to add 4.08 or 4.09beta before the 4.09 new patch or are they covered by 4.09 :???: ?

You need to patch to 4.08 before adding the 4.09 official patch. (4.09b1m is not required)

[8FS_Bulau]

Flying the SM.79 over the 3BG_KTO map!
4.09m Official and Unified Installer 1.2 combined.
It took the SAS buttons to make it work, though.

[norm]

i have gotten the 4.09 ac to appear in the list, but they do not appear during play and they are invisible in the arming screen. i am using sas buttons 2.21