160 users need the new versions which can be downloaded from this link: TransLinks

Run the "TransLinks.exe" (7-zip self installer) in your 160 folder(s).

Some exes read the two files from the root folder and others from the EAWTM2 folder, so the installer will put the latest versions of "TextMap1.str" and "TextMap2.str" in both the root and the EAWTM2 folder.

The reason for this download is that over time we have added additional 3dz file-types to the exe. Some need a transparency link so that the transparency file is loaded when the referenced texture file is loaded. As a result I have added the additional links to the "TextMap1.str" and "TextMap2.str" files.

Jel

I can report that this fixed the transparency problems for both the B-26 and the ME410 multiskin squadrons that I'm setting up so a big "thumbs up" for fixing it.

However, it did not fix the wingview problem. The game only sees the primary plane wingview no matter which plane you sit in.

This is only for multiengine planes that use the Y/YTR pcx files and the Y.3dz.

Single engine planes use the U.pcx and the U.3dz are fine.

Also, were you able to see the B-17G's blink back and forth between silver and green when viewed at a distance?

I think that the two unresolved problems have been there from day1, but we did not notice them until we had different coloured multiskins.
I do not think that It is a transparency problem.

I agree that it isn't a transparency problem with these two issues.

I can fix the silver/green flashing problem by setting the view distances back a bit in the plane.dat file. It's a bug but a surmountable one.

However, the fact that the game recognizes the multiskin file system for the files other the "Y" is a puzzle. And I'm not talking about the Y/YTR linkage, I'm talking about the fact that the game doesn't recognize PLANE01YX.pcx. through PLANE15YX.pcx.

I found a clue and have contacted Aldo

Still not out of the woods.

I'm working on converting Mike's HE111 mutliskins with updated 3dz's and making them 1.6 compatible. The G.3dz points to the MEX/MRA because it needs to have clear cockpit glass.

That link is not working but if I change it to PEX/PRA is does work.

Also, whether or not on purpose, it the secondary planes use the texture file as assigned. However, they don't use the linked transparency file but rather the primary one.

So for example, plane #2, the first secondary plane, uses PLANE01PX.pcx but it uses PLANEPRA.pcx, not PLANE01PRA.pcx

This is good for two reasons:

1 - It reduces the number of necessary files in the folder.
2 - It does away with the problem of the difference size file names.

This is the problem area for the cockpit wingviews
The code is Aldo's and mine and not original EAW source code so I am not breaking any rules

To explain the context:
The U.3dz has both wing views for a single engined fighter and the port wing view of a two- or four-engined bomber.
The Y.3dz has the starboard wing view of a two- or four-engined bomber.

Aldo's original code loaded the pilot's view using the U.3dz for the original plane and then multiskin planes 01-15
It was designed for single engined fighters.

In an experiment I disabled the loading of the Y.3dz
Running the exe and flying one of Mikes multiskin B-17s I saw the port wing but no starboard wing (as expected). Jumping from plane to plane I saw the correct port wing every time.

In the code snippet I have changed the "u" to "y" in two critical places. When I ran the compiled exe and flew the B-17 I saw the correct starboard wing and no port wing
So the code works with either a "u" or a "y"

What I cannot yet achieve is having two sets of this code, one to load the port wing using "u" and one to load the starboard wing using "y".
I get the correct wing for whichever comes first; and the default version of the one that comes second.

Jel

It's getting complicated, that's for sure.

One thing.

The B-17 is a rarity in that it uses BOTH the U and the Y. There might be others but I can't think of one.

Most multi's use only the Y but that's not working either.

If I had to choose, I'd skip the B-17 because, as we've agreed, the playability for the level bombers is minimal unlike the attack planes like the B-25, B-26, Mosquito and many, many more.

So, in my opinion if you can get the Y issue fixed let's consider it a win.





BTW, on the MEX/MRA problem I put a HE111 file set named He111 KG 55(multi).zip in your GEN folder.

The first two secondary planes point to PEX and the rest point to MEX so you can see what I'm talking about.

Bingo!

Now I just want to make sure that the single engined planes work correctly

Gentlemen. FYI, the He-111 was modded to allow a non mirrored skin. On the original the wings and fuselage are drawn from the tex only. I went in and changed the right hand side of the skin to a new texture panel and painted it. Then added a trans panel for the new side. PEX + PRA. But the skins 01 - 15 drawn from the mex.tpc. I took liberties when making my non mirrored skins and changed/added a new right side on several types.

As reported -

Here is a link to the latest exes which have the B17 wingview colour problem fixed
December 10th 160 exes

Jel

have you tried this with the B-26's?

from the cockpit I'm seeing 4 engines on Plane01
Do you have more files for the B26 multiskin, maybe with coloured wings for a clearer test? Three planes would be enough.

I will do more tomorrow. At least when you get something displaying then there's a good chance you can stop it from displaying by making the display conditional.

Hmmm, a 4 engine B-26? Could be a great "What if" plane.

But I digress.

I'll put together a new package of B-26's later today and get it up to the GEN.

I'm back.

You aren't seeing a four engine bomber wing on those B-26's. You're seeing the B-26 wing twice.

What is on the U and Y 3dzs?
In the B17 fix both were loaded because the starboard wing view was on the Y and the port on the U.

This is what I'm seeing.

B-26 plane #4, or planeset PLANE03* has a green skin as opposed to the first three planes which have silver skins.

The first three have correct silver wingviews, although there are two sets showing. This one should have a green wingwiew and you can see that indeed one set is green.






As to your question -

The B-26 only uses the Y.3dz with one engine on either side of the cockpit as do almost all twin engine planes.

I went back and checked the four engine planes and it turns out they do use both the U and the Y, so it's not just the B-17 that uses this configuration. Sorry for the misinformation.

In that little set you gave me there was a U.3dz which had no PCX file referenced in the header.

Yes, that's a left over from the old days when we needed an empty U.3dz when placing a twin engine plane in a single engine slot and vice versa. If it's not there you get the "bi-plane effect" as it was called back in the day.

I'm not sure if it's still needed with the slotless system but it is in many, many aircraft 3dz sets.