As a result of a comment by Iron Mike in the "Multiskins" topic I offered to make a tutorial about making planesets for EAW140. This is the first post.

There are two types of "planes" folders, and users need to understand the differences.

1. The "Planes_ETO" folder is the evolution of Ralf's original which contained more than 300 skin folders from OAW_unified.
Because there were so many he broke them up into aircraft type subfolders:



Note the pathname: "Planes_ETO\Plane_Skin\Axis\FW190".
This folder contains 11 skin folders for selection by the planeset making utility.
A similar set-up has the FM folders in it such as "Planes_ETO\Plane_FM\Axis\FW190".

2. The others for limited theatres such as "Malta140_Planes".
They have two subfolders, "FMs" and "Skins" containing the individual folders.


Because there are two types of folder structure there are two different planeset making utilities, and the correct one needs to be used.

End of part one

As this is a response to Iron Mike's request to get his multiskins used I will start with the tool for the "Planes_ETO" folder, with the objective of replacing a default B17 skin referenced in the "ETO140\Planeset2\PDir.set" file.

For convenience I have copied the utility I need to use (Planes_ETO PSM2016.exe) and pasted it into the EAW folder which contains the "Planes_ETO" folder:



Opening screen. The planes folder (Planes_ETO) needs to be located and double clicked:


The double clicking produces this:


We want to modify an existing file, so we need to see the load/save panel:


Navigating to the "ETP140/Planeset2" folder lists the FMDir.set and PDir.set files,


Click on both of them to put the data in the grid:


Now we just hide the load/save panel by clicking on it:

We are now ready to edit

End of part 2

The skin folder we want to change is on line 6 in the right hand column. It is for a B-17G:



.... so the B17 in the Allied Skins column is selected.
Doing so displays the "Work frame" where you select the folder you want from the B17 set:


Clicking on the last of the three choices selects the "B17G_01", hides the "Work frame", and replaces the path to the skin folder on line 6:

Now that the "Work frame" is invisible you can see the "B17" that I clicked on in the Allied Skins list.
To save it we need to show the load/save panel again, and click "Save the PDir and FMDir.set files" button:

Please note that as this routine saves both files then both need to be loaded before you do any editing (as in part 2). You cannot just load the "PDir.set" and leave the FM column blank.

So I flew a B17 bombing mission in ETO140 using planeset 2. Everything is working fine



End of part three

I have just uploaded an installer to OneDrive:

http://1drv.ms/1Qp3WS4


This is a 7-zip self installer which creates a folder called "Package" when you run it.
Inside the "Package" folder there is a "setup.exe" that you need to run.
It installs the program and the runtime files. Note where the program is stored so that you can copy it and past the copy in the EAW folder where you need to actually use it.

Excellent Jel.....

AO

You might as well be posting in Dutch!

Bring back the old slots and naming system!

Nope, this is the way to go.

It took some work on my part to figure out the quirks and there are quirks but the flexibility it offers is worth the trouble.

Still, good to hear from you.

Oh dear
It is good to see you posting John, but disappointing to see what you posted.

This thread is a tutorial about how to use a piece of software to make planesets.
I was hoping that it might become a sticky.

It is part of a response to Iron Mike's comment wishing that more of his multiskins are used. Your post took up unnecessary space, and provoked further responses (including this one) which take up even more.
We have been using planesets since they were included for ETO in the 1.28e release six years ago. The "PDir.set" and "FMDir.set" files needed were not made manually, but by people using tools similar to this one.



They never went away. That system is still in use by readers of this forum, including myself, when they use 1.2, 1.28, 1.28a/b/c/d/e/f, 1.29 or the FXExe.
Nobody is making skin files using the 1.40 naming system. There is no need, because these files can be converted as shown in the "Multiskins" thread.

Jel,
when I go to open the work frame, it opens and shows me the skin folders,
but it gives me a runtime error 76.
Thanks,

AO

Error 76 is a "path not found" error so try this test.
Make sure you select "Planes_ETO" as the planes folder. The other editor is needed for the single theatre planes folders such as "SPAWPlanes".


The opening screen must look similar to this after selecting "Planes_ETO":

You should see "Planes_ETO" selected in the directory list, and the Allied/Axis FM and skin folders listed.

Click on "Typh_Temp" in the Allied FMs column:

The work frame should appear with the choice of two FMs.

Select the first one, the entry is made in the table and the work frame disappears:


If this produces the error 76 then let me know exactly at which point

Hi Jel,
when I click Typh-Temp in the FM column, the work frame opens
with 2 FM choices.......as soon as my mouse curser touches a
choice, I get the error.
Thanks,

AO

It did not in my case. I will try using a different o/s

Roger that.......
I'm using XP.

AO

I cannot get it to crash so I need you to do a test.
In the folder at OneDrive where you got the editors from there is a 7-zip self installer named "Test folder"
When run it creates a "Test folder" containing three things:
A "Planes_ETO" folder
A "Planes_ETO PSM2016.exe" program
A "Planes_ETO PSM2016NoPic.exe" program

To explain where I am coming from
1. You got the CTD when the mouse was over the folder name.
2. What is supposed to happen is that if the folder contains a picture then it is shown when the mouse is over the folder name. This may help the user choose a skin folder in particular. It does happen on my PC.
3. I have disabled this routine in the "Planes_ETO PSM2016NoPic.exe" version, so nothing happens when the mouse is over the folder name.

So try both in the test folder and see if you get the CTD.
If you do not with either then try them in the folder you have been using.

Both work for me in this test folder, and with the original I see the picture:


Normally the pic is in the skin folder as there is little point in putting one in the FM folder. However, while I was testing I copied one into the FM folder just in case having a pic in the FM folder caused the problem. So for this tempest there is one in both.

Interesting.......
the no-pic works fine.
The Planes_ETO PSM2016.exe works,.....
but only works on the planes_ETO folder you sent.
Not on MY planes_ETO 1.40 install.

Can you send me the link again for the 1.40 Multiplayer install?
Thanks,

AO

ps: The 'no-pic' exe works fine on all.

PM sent:)

Jel,
found out the reason it gives the error is because the
Planes_ETO PSM2016.exe has to be in the same folder as the
Planes_ETO folder.

AO

ps: Got the download and so far, all is working fine!

From the second post in this tutorial

For convenience I have copied the utility I need to use (Planes_ETO PSM2016.exe) and pasted it into the EAW folder which contains the "Planes_ETO" folder:


LOL

Yea, I had to go back and re-read it then
slap myself in the head. lol!

AO

Just look at the pictures lol