[fabianfred]

(a)... The original unchanged il2..... the files.sfs directs the game to look for

planes/objects/maps etc. in the appropriate sfs files section

(b)... The modded game using the old system...... the new files.sfs directed the game to look in

the new 'Files' folder ....as directed by the filelist..... and for anything not changed it carries on to

look in the default location

©... The new mod system with a wrapper......tells the game to look in the new MODS

folder......if not found there...then look in the filelist and 'Files' folder....or in the default location

So when we made a new map in (b).........when asked to load the map in the FMB or in play by

the mission file........ it looked in the filelist first....if it found it there....it went to the

Files/maps/maps_all.ini which directed it to the correct map name folder for details......... if not in

the filelist it went to the default location

A new map in ©........ it looks in the MODS folder...in the maps folder (if there is one) and then

into the correct map folder as directed by the maps_all.ini in the maps folder............otherwise in

the old filelist and Files folder (if we haven't yet transferred it to the new MODS folder)........or in

the default location

[Bee]

I'm not sure :wink:

I kind of knew where I was with the old system. The new wrapper seems much less versatile and hands-on. More for playing mods than making them. I'm not sure if I like it yet. :?

[Phillip]

Guys, give me a few hours and I will make a "How-to" so hopefully every one can understand. I find it alot easier to use than the old system. Loads up faster, and if I have problems with one mod, I can simply delete its folder without searching for the right files or maybe deleting the too many files!

Stay Tuned !!

Phillip

[Bee]

Thanks Phillip, standing by.....

[Guest]

the new wrapper is better !
is does away with the need for a filelist.txt

it now uses a folder called MODS
you simply place your mod into there but you give it a folder name like 'Tiger Moth' then place your 3do folder into that & then of course your cockpit folder goes into the 3do folder ect

any of your previous mods will also work in the usual place but there is no longer a need for filelist.txt

[FA_Cheech]

Yeah, I hear you, but I personally am not loading any new mods until this gets sorted out.

Have already had to reload the mod as a result of the P-51 dive mod issues, and this new wrapper.dll needs some massaging. At least from a "how-to", new file structure for mods discussion, etc.

Jolly, recommend the new wrapper.dll post in the Mod Downloads section be beefed up with additional info on what it is, how it works, etc.

[Phillip]

New Wrapper MOD install "How-to"

This is a guide to take you through the various ways to install the Mods with Qtim's new wrapper.

First time install:

1. Download and install the Sound Mod in a temp folder(or the "new" mod activator or sound mod soon to be availible).

2. Download and install the new wrapper into the same temp folder (overwrite old wrapper).

3. Delete the filelist.txt, Filelist-Fixer.bat, flc.exe, and any readme's. These are no longer needed.

4. Make a new folder called "MODS" in the temp folder.

5. Rename the "Files" folder into "Basic" or what ever you like. Note, this folder should ALWAYS be the first folder in the new "MODS" folder.

6. Drag and drop the renamed "files" folder over into the "MODS" folder. Then you should have four items in the temp folder;

MODS (folder)
files.SFS
il2fb.exe
wrapper.dll

7. Drag and drop these 4 items into the root directory of your IL2 46 game, i.e. C:\Ubisoft\IL-2 Sturmovik1946

8. Finished

9. Have fun!

Install with old Sound Mod system

1. Download and install the new wrapper.dll into your root directory (overwrite).

2. Or, download and install the L2D Tabby mod. Overwrite the wrapper .dll

3. Delete the filelist.txt, Filelist-Fixer.bat, flc.exe, and any readme's. These are no longer needed.

4. If you did step 1, then make a new folder called "MODS" in your root directory. Step 2 user must not do this, the Tabby Mod makes a "MODS" folder automaticly.

5. Rename the old "Files" folder to "Basic" or what ever you like. Again, this should be the first folder in the new "MODS" folder.

6. Drag and drop the renamed files folder into the "MODS" folder.

7. Done !

8. Have fun !

Install older planes and other Mods into the new "MODS" folder.

This part is simple. Unzip the mod you want into a temp folder. Rename the files folder into what the mod is i.e. Avalas_Planeshine_Mod , etc. Drag and drop this new folder into the "MODS" folder that is in the root directory of the game. This can be done for all planes and mods. It is a good idea to give each folder a new name so you can tell what mods are installed.

Note:

As QTim said, this wrapper loads faster and better than the old filelist system. One thing is that if 2 or more mods use the same files, it will load the files from the first folder found.

I have all the planes and the skin packs(vp_media and Avalas), and the maps and after about 10 hours of testing, I have had found only 1 problem. That the original sound mod has a Bf110C-4B in it, even with the new mod (110C-4B), I get no rear gunner. I fixed that by copying the files from the new 110 mod into my basic sound mod folder. Then everything worked perfectly.

With this system you can delete any old or unwanted mods without having to try and find the files it uses. Just delete the folder or rename the folder with a -(dash) before the name, i.e. -BF110C4B


I hope this will clear up any questions. Feel free to PM me if there are any I have not answered.

As always, the German translation will follow shortly (as soon as my daughter comes home from work!)


Phillip

[Vpmedia]

First I put the wrapper.dll there and renamed filelist.txt to _filelist.txt,
then I made the MODS\GUI,SKINMOD,SOUNDMOD,MAPSDEFAULT,MAPSCUSTOM folders and copied the files there from the 'files' folder. Everythin works as before.
I only got trouble to sort out the lot of files named like "002A5F5489D39E2E" etc. I gues I should delete them all and reinstall the flyables in the new structure.
In the long term to use the new dll will be much better because people will get less install/uninstall problems.

[Username]

Phillip - many thanks for the guide. A couple of questions:

Why is it necessary to rename the 'files' folder before putting it into the MODS folder? And once this is done, are you saying the new wrapper can still read it without a filelist.txt in the main directory?

Is it absolutely essential to extract from every old mod the relevant files folder for inclusion in the new MODS folder under an appropriate name? If so - that's a fair bit of work as I have 75 mods installed. :wink:

Re the hash files (eg 4CCYT56453HJJ13K), mods such as the 6DOF mod use nothing else. Do they have to go into a separate folder within the MODS folder?

[Phillip]

@username, no you do not have to install all the Mods again. You do not have to rename the files folder if you don't want to. But remember, the wrapper reads and loads the files in order as they are in the MODS folder. I rename mine so it is the first one in the MODS folder.

If you have the sound mod already installed you just have to follow the steps under "Install with old Sound Mod system". With the new mods, they will be installed automatic in the right folders.


Phillip

[Username]

OK, thanks Phillip - time to give it a whirl. I think I'll call my files folder 'AAA' :wink: