Multiskins?

Hi Jel,
I notice that there are some multiskin folders in the Planes_ETO folder,
but the Pdir.set file points to the (Example: P47D_def folder as opposed to
the P47D_01 folder which is multiskin.) def skin.
If I edit the Pdir.set to point to the P47D_01 folder, I get a 162 error.
Will the multiskins end up working?
Thanks,

AO

Checking

I just loaded ETO "Planeset2" in the Planeset Maker with the default P47-D skin, and made a new "Planeset6" folder.
Then I edited the P47-D skin slot to use the "P47D_01" (multiskin) folder that you tried, and saved the "PDir.set" and "FMDir.set" files in the "Planeset6" folder.

I selected ETO with Planeset6 and flew a P47-D:



Seems OK here

Seems a shame not to have access to all of the squadrons that were skinned. The ability to have individual unique skins was a tremendous addition to EAW. It definately adds to the imersion of the sim.

Just my own opinion...

For EAW 1.28 and 1.29 people have access via your pages at Sandbagger's, but the problems lie in their ability to set them up for use.
The skin folders need to be put in an appropriate "Planes" folder, then referenced in a "PDir.set" file in a "Planeset" folder.
I would be happy to give a link to the tools they need to do this, and make a tutorial, however, it is not my intention to download them all and make multiple "Planeset" folders. People must make their own choices.

Did you ever try the 140 conversion software I wrote?
I have an updated version which I used on Ray's Mediterranean skins.

Yeah, man, jump in the pool.

Takes a bit to wrap your head around planesets but worth the effort, IMO.

That said, I have no idea how to set up multi-skin folders for 1.4.

Here is one- a conversion of its 1.28 predecessor:

As you can see from Jel's pic, it's alot of work to change all the
3dz and tpc file names to work in 1.40.
As in the B17 files shown above, as an example, the file that was called
Pbb1701a.3dz, is now called Plane01a.3dz. All the files in the skinfolder
have been renamed to 'plane.'
In the example above, this B17 multiskin folder is named 'B17F_01'
This folder is placed (located) in the Planes_ETO/Plane_Skin/Allies/B17/B17F_01
Then your Pdir.set file (located in your ETO140/Planeset folder) points to this
folder.
Example: Pdir.set file says
Planes_ETO\PLANE_SKIN\Allies\B17\B17_01

Anyway, if I could get Jels conversion tool, I wouldn't mind spending a little time
converting IM's multiskins for 1.40. His multiskins truly helped the immersion in EAW
for me. (Along with my engine sounds! lol!)

IM, through the years, I mainly downloaded your 8-bit multiskins. On my computer, I
never really saw a big difference between the 8 and the 24, so I would work on those
first.
Jel, I still only have a StrEdit128C, but it still works fine on dir.set files.
Just need the conversion tool.

AO

Well, if you go by the accusations on the other thread, you'll never get 'em.

Sorry, one last bit of sarcasm.

I'll shut up now.

Never shut up Ray. Your honesty is refreshing.

Skin conversion folder set-up:



The "ToBeConverted" folder has a number of IM's desert multiskins which I just downloaded from Sandbagger's and unzipped:


They have the old 1.2 filenames:


Running the program and double clicking on the "ToBeConverted" folder:


Clicking "2. Click HERE...":


Selecting the first folder shows the 1.28 3dz planecodes. Click on any that is correct ("PHURR" in this case) and the whole folder will be converted:

Some skin folders may have an "ORD*.3dz" which would be listed before any "P*.3dz" files so the first one is not necessarily the correct one. That is why this selection step is needed.


When a folder is converted the next one is automatically selected, and all you need do is click on the 1.28 planecode to convert it:


It took about 1 minute to do the lot:


The files have been re-named in 140 format:


Make sure you keep the originals and only convert a copy of them.
Sometimes I do two batches, one with the "Include Default Skins" checkbox checked, and the other without.
That checkbox is there because some old skin files are incomplete and rely of some files from the "3D.CDF" being used.


Here is the link to the download page of the editing tools:

http://1drv.ms/1TQo0lD

Download "129-140 Skin Convert2016" (7-zip) and run it. It will create a "129-140 Skin Convert2016" containing the program, the "DefSkins" folder and an empty "ToBeConverted" folder.

Googly moogly! Thats quick! Didn't know you could do a whole batch like that!
Great tool Jel! IM, you could do them yourself in a matter of minutes!
Zheesh....and I thought I was gonna help....lol!

AO

ps: Jel, let me know where I can get it...I can at least do my own. Wouldn't mind
throwing my 352nd multiskin folder in ETO.
Thanks!

There is a link you missed in my previous post in this thread- just above the Download "129-140 Skin Conver2016" line

Hey! Watch your language. We have rules.

Seriously, this is a perfect example of Jel's dedication to the game and to the community.

The 8 bit skins lack the true colors used in the skinning for one thing. And second, the markings aren't as sharp as the 24's. I am lucky in that my video card and drivers run D3D better than glide. The skins are really nice. I guess I need to post a few new screenies to illustrate the differences.

I'm working over 60 hours a week now and don't spend much time at skinning.Right now I am just now building the 63rd FS P-47D 1944-45.





They were painted last July, so, I'm a bit behind. I have a back log of unfinished sets.

I ramble...

Jel,
having a problem with the converter.
It works great on all the file names, but it does not
change the pointers in the file.

In examining an already existing converted multiskin, I see
that the file pointers also have been changed to 'plane.'

So do the converted files pointers need to be manually edited?

AO

I will check the files I did yesterday. Previous converters renamed the pointers.

You are correct. I do not know how it happened.
I have replaced the download file at OneDrive
I will download it and test just to be sure.

Edit: I downloaded the new version and tested it. The pointers are now named correctly

Roger........got it and it works great!
Thanks!

AO