I am making this thread so that any issues can be reported and hopefully dealt with.


Russ
I am not quite clear as to what you did. Yesterday I transferred my "SPAW140" and "SPAWPlanes" folders from an earlier 140 set-up to the new one, and transferred all the "Not yet installed" files back to the main DirSets folder in readiness for testing.

I flew a couple of missions using the "SPAW140RO" dir.set and planeset 13, and had no problems.

I did have some in SAW and MME planeset1 due to a couple of missing tpc files that the converted 3dz files were still looking for and would have accessed from the 3d.cdf previously. I went back to the original 1.28c installations, got them and put them in the appropriate planeset folders.

What I will do is to download the scenarios from OneDrive one by one and check them out. I will start with SPAW

I had already uploaded "SAW140" and "NewIRAQ" patched with the rogue tpc files yesterday, so I just re-downloaded them and "SPAW140" to test.
I only flew one mission in each but had no trouble.

SPAW140RO: Plenest13 flying a Corsair from the Victorious.

SAW140V4: Planeset1 flyinga Rata

MME140: Planeset 1 flying a Hurricane

If anyone encounters a problem please give me enough detail so that I can try to reproduce it

Jel

Thanks Tony I'll try your procedure...I tried installing from the 7 zip file.Damn sure I'm not sure what happened.But I'm sure I buggered something by not paying attention'

OK SAW reports pic not found
p109 ets.tpc -1

One good note is I now using d3d windower and the graphics corruption I had is gone everything looks great!!!!!!

We have had visitors from abroad, and it was great to have a reunion of my two WW2 airmen's daughters, Marilynne from Australia who is my brother Bill's daughter (FAA 820 Squadron Avenger TAG), and my cousin Marian from the UK. Marian's father was my uncle Archie who flew as a mid-upper gunner with 625 squadron but did not survive the war.
As a result we have been very busy and I have not had a chance to respond to any problems with EAW until this morning.

CD Free 140 problems so far have been due to 3dz files referencing tpc files from the 3d.CDF which is no longer there.
I was foxed by one error message because in a check of the skin files I could not find a 3dz file referencing the missing TPC. However, widening my search I found that some of Moggy's TMod files in IRAQ reference the "PTYPHTEX.TPC" and this enabled me to solve the problem.

The upshot is that I have just uploaded "IRAQ140basic" and "SAW140basic" 7-zips to their appropriate folders at OneDrive.
Running them will generate the following folders:

MoggysMiddleEast
Planes_IRAQ
SAW140
SAW_Planes

Delete the previous versions of these folders before running the 7-zips.

A note re- Moggy's Middle East

It has five planesets:
1 references Planes_IRAQ
11, 16 and 18 reference Planes_ETO so this needs to be present if you select any of them
13 references SPAWPlanes so this needs to be present if you select it.

As far as I know the versions of ETO140, Planes_ETO, and the DAW140 folders can be copied from the "normal" EAW140 folder and pasted into the CDF free 140basic folder. I have not made CDF free versions of those as no problems have been reported.

Jel

Hi Jel,
I downloaded the 1.40Basic, Iraq140Basic and Saw140Basic.

I ran the 140Basic exe, then ran the Iraq and Saw inside the 1.40 Basic.
When I run the DirsetExe Manager and try to choose a dirset, I get a
'path not found' error....no matter which dirset I choose.
Am I doing something wrong?

Thanks,

AO

EDIT: OK, my mistake......other dirsets in the dirset folder were misleading.
Selected DefaultEAW, MME140, and SAW140v4 and all worked well.
I was looking for uniform names. (ETObasic instead of DefaultEAW)

Tony
Can't see either of those files on one drive.Just the two older ones modified on 9/6

Both are in there.

Moggy's Middle East and Spanish Air War.



AO

Was looking for IRAQ140basic" and "SAW140basic those two properties says modified on 9/6 I'll download the ones there

Fresh download and get SAW reports pic not found p109 ets.tpc -1 all my other installs 1.28 1,40 run well.Using planeset 1 which is the only choice

The files are here:



Russ please give me more details of what you had set up that generated the error.
A screenie like this is helpful:

That way I can try to repeat what you did so that I can figure out what happened and why.

This one launched with no problems:


I deliberately flew the plane in the 109E slot because of your error report.

Jell
Nothing fancy just a simple single mission using plane set 1.....Going to try a fresh install
Fresh install just SAW added in same error in instant mission.Might try new download of 1.40 basic.
At least I got the 1.40 online setup working well and can fly with that'

Fresh install same problem I surrender and will fly what works..

On the basis that there is a problem with a file I need to be able to produce it on my PC so that I can fix it.
As it would appear to involve a 3dz file looking for a file named "p109 ets.tpc" I need to know which plane you were flying, which mission type, and which AIs were set (if any). That way I have some clues as to which skins were involved.

I cannot locate a "p109 ets.tpc" on any of my machines or external drives, and have never seen a file of that name.
Maybe it was "p109etes.tpc", or "p109etex.tpc"?

Has anybody else hit the problem that Russ describes?

Jel

I also added ETO140, DAW140, and the ETO_planes folder into this
no CDF folder. All are working well so far!

Regular ETO:


DAW:


SAW:


SPAW:


MME: (IRAQ)


AO

I have a utility which I have just used to check the headers of the 3dz files in the SAW_Planes\Skins folder



I have used it on every folder, and nowhere is a "P109e" file referenced.
There were a couple of rogues like the "P190BV.TPC" referenced by the "PlaneU.3dz" which have already resulted in my adding the "P190BV.TPC" to the "SAWBf109B-2" folder, and similar fixes applied to two other folders.



I have taken that quote and edited it so that the last line in in bold text. I am wondering if Russ has a mixed installation?

This is my "140basic" folder with everything in it plus a couple of recent 7-zips and the odd editor program:


That is how it should look.

Russ,
are you adding an old install (1.28) of SAW? Or an old favorite skin or something?
With a fresh download of SAW from ONEDRIVE, you should not be able to get that error.
The SAW_planes folder does not have any files with that name, unless there is one in there
by mistake, or you added your own skin to one of the folders.
Try to fly single mission instead of instant. If you get the same error, tell us what plane
you chose.

AO

OK no mixed install just the basic 1.40 and saw from the 140 site.....My old 1.40 install with the cdf's which is Jells 1.40 online works well.....Seems I got some gremlins there but thanks to Tony I can fly 1.40 with the cdf files works well for me....Thank you for the help.Tried single missions with a variety of planes same error

OK the exact file name is P109ETEs.tpc.Seems I'm the only one with this error..Fresh install with just SAW added in and flying default instant mission planeset 1 which is the only choice I have.My old 1.40 setup runs saw fine just have the basic EAW mainscreen but it loads and flys sweet.So what works I'll go with

Hi Russ, I don´t know if is related or not but i remember during an online test with tony, flying Saw, i needed a file for the 109 but i can´t remember why! Maybe the same problem maybe not, sorry not being very helpful. For sure Jel will help you.

Cheers

Russ

In the "Spanish Air War" folder at OneDrive there is now a "P109eTES.TPC" file from the original SAW set-up.
Download it and put it in the "Planeset1" folder and see if it fixes the problem.

If it does, and you have an instant mission working, please let me know which plane you were flying, and the other types of aircraft you see when you hit F9.

Can you please also confirm that there were no "SAW_Planes" and "SAW140" folders in the "140basic" folder before you ran the "SAW140basic.exe" in it.

Russ,
just to make sure your doing things correctly, please follow the
procedure below:

Download these 3 files from ONEDRIVE and place them in a NEW folder:


Run the 140basicNoCDF.exe. (Double-click) You will end up with a
1.40 basic folder:


Take the other 2 files (IRAQ140basic.exe and SAW140basic.exe) and
place them 'inside' the '1.40 basic' folder:


Run those 2 files from there and you will end up with this:


Be sure to place your own EAW.ini file in the 1.40 basic folder and
you are all set to go.
Double-click the DirsetExeManagerv5.exe, select the EXE, the
Dirset and the planeset, then click 'fly.'

If you follow this procedure, there is no way for you to get the
p109etes.tpc error....there are no files in this install with that
name. If there was, we would all get the error.

I think were getting confused with the 1.40 basic description. When
'you' say 1.40 basic, I get the impression you are talking about
the original 1.40 install which came with CDF's. When 'I' am
talking about 1.40 basic, it means the 'new' no-CDF version.
Hope this helps,

AO