New ETO 1.0 and 1.2 installation guide

[hairyspin]

This is certainly one of the oddest, not say unusual problems I've heard of, but as Tailwind says, the My Documents folder and subfolders are not created until the game runs for the first time. The error message you report is usually because ETO has not been installed to the Program Files (x86) set of folders in 64-bit Windows.

That being the case, there won't be anything to delete in My Documents, wherever it is located. If you haven't already, get the ETO Installation Guide and follow its instructions: installing in 64-bit systems is covered in depth because you can't install to the default locations, you must specify the correct installation path for 64-bit systems. Then there are files to edit before running ETO for the first time.

Good luck!

[Human Drone]

So all, you are really emphasizing that I have to start with a vanilla CFS3 installation in C:\Program Files (x86). This is what I get for being a hard head - and not realizing or reading the guide before-hand.

I was hoping to keep things neat and install all my sims in C:\FlightSims because in other places I've read that it gets around some permission issues inherent in the Win 7 directories. So I have a "vanilla" CFS3 in C:\Flightsims\CFS3; then I copied that to C:\Flightsims\CFS3ETO, ran MultiCFS3 and verified both installs were independent, and then started the ETO install guide when I realized that there was this requirement for C:\Program Files (x86)\CFS3. But I didn't get too far - when MultiCFS3 failed I quit.

So can I just delete the folder that the ETO 1.0 package installed under my C:\FlightSims folder, re-install a vanilla CFS3 into C:\Program Files (x86), and get on iwth it, or should I do as Grizzly50 recommended in http://www.sim-outhouse.com/sohforum...d=1#post656287 and clean out all the registry entries and what-not?

Any chance that in the future y'all could work with CFS3 wherever it may be found? (I know you guys do this in your <ahem> spare time and I appreciate it, just sayin'...)

Thanks,

Tom

[grizzly50]

So all, you are really emphasizing that I have to start with a vanilla CFS3 installation in C:\Program Files (x86). This is what I get for being a hard head - and not realizing or reading the guide before-hand.

I was hoping to keep things neat and install all my sims in C:\FlightSims because in other places I've read that it gets around some permission issues inherent in the Win 7 directories. So I have a "vanilla" CFS3 in C:\Flightsims\CFS3; then I copied that to C:\Flightsims\CFS3ETO, ran MultiCFS3 and verified both installs were independent, and then started the ETO install guide when I realized that there was this requirement for C:\Program Files (x86)\CFS3. But I didn't get too far - when MultiCFS3 failed I quit.

So can I just delete the folder that the ETO 1.0 package installed under my C:\FlightSims folder, re-install a vanilla CFS3 into C:\Program Files (x86), and get on iwth it, or should I do as Grizzly50 recommended in http://www.sim-outhouse.com/sohforum...d=1#post656287 and clean out all the registry entries and what-not?

Any chance that in the future y'all could work with CFS3 wherever it may be found? (I know you guys do this in your <ahem> spare time and I appreciate it, just sayin'...)

Thanks,

Tom

Human Drone,

I would just clean it all out, to be on the safe side, and reinstall. Then follow the Installation Guide.

[Human Drone]

Successfully installed up to the 1.40 Hotfix! Everything seems to be working okay... I've never been shot down or crashed in such beautiful scenery!

HOWEVER... I noticed when running the spawn swapper batch file that there are a lot of "File not found" messages screaming by. I shoved a pause into the 01_____.bat (forgot the dull name) and the first feww lines were doing what they were supposed to, so I left well enough alone. Is this normal?

Also, I'm not entirely sure the BDL zapper is working as it should. I don't play online (yet) so maybe that doesn't matter, but, I'll try it again when I can to see if it's doing what it's supposed to. It's in the proper directory (CFS3 ETO Expansion) and set to open in that directory, so...

And, speaking of scenery, I take it you guys have included the nice scenery available here, either Winding man or jbscenery? So I don't have to horse with anything else for now? Cause I have to do some work on the car for the next day or so, & I'll get all out of the groove!

Thanks so much,

Tom

[grizzly50]

Successfully installed up to the 1.40 Hotfix! Everything seems to be working okay... I've never been shot down or crashed in such beautiful scenery!

HOWEVER... I noticed when running the spawn swapper batch file that there are a lot of "File not found" messages screaming by. I shoved a pause into the 01_____.bat (forgot the dull name) and the first feww lines were doing what they were supposed to, so I left well enough alone. Is this normal?

Also, I'm not entirely sure the BDL zapper is working as it should. I don't play online (yet) so maybe that doesn't matter, but, I'll try it again when I can to see if it's doing what it's supposed to. It's in the proper directory (CFS3 ETO Expansion) and set to open in that directory, so...

And, speaking of scenery, I take it you guys have included the nice scenery available here, either Winding man or jbscenery? So I don't have to horse with anything else for now? Cause I have to do some work on the car for the next day or so, & I'll get all out of the groove!

Thanks so much,

Tom

Human Drone,

I think your spawns are corrupted.

NOTE: RULE #1 FOR ETO INSTALLATION AND INSTALLING ANYTHING INTO ETO:
1. Start ETO in Era 1, Fly, and then Exit.
2. Set the ETO Spawn Selector to 1, Stock Spawn Mode.

Here's what to do to fix: Look in the CFS3 ETO Expansion main game folder for a folder named CFS3 ETO Expansion READMEs. Look in this folder for a document named ERA Files Restore Rev 1.40.rtf.

Follow the instructions found therein EXACTLY.

If you have installed ETO to a location other than C:\Program Files\Microsoft Games, make sure you do Step 1 first: "Step 1. First copy and paste your Era swapper program files to a location outside of CFS3 ETO Expansion.

The 3 files are: CFS3 ETO Expansion\MASTERETOSTARTUP.bat, CFS3 ETO Expansion\ETOEraSwapper.bat, and CFS3 ETO Expansion\global_layer\ETOGLSwapper.bat,". You only need backup these three files named.


Once you have done all of the instructed steps, run the CFS3 ETO Expansion ORIFs Re-Install Cumulative Rev 1.40.exe.


This should straighten up everything just fine.


One more prventative measure: After installating ORIFs, make sure ETO has been run in Era 1 and exited, then make sure the ETP Spawn Selector is set to 1, Stock Spawn Mode. After making sure, find the ETO Backup icon and run it. This will make a BACKUP folder for the files and folders you just replaced with the ORIFs Re-Installer to a location outside of the main game folder.

If these kinda of problems happen again, all you will have to do is use the document to delete what is necessary, and replace the items manually from the BACKUP folder.


Also, when installing new missions into ETO, just place copies of the missions and spawns into the proper places in this BACKUP folder. Post-ETO release new missions won't be in the ORIFs Re-Installer, but they will now be in the BACKUP folder, once you have placed copies of them there.

As to the BDP Zapper, ZX Zapper, and ETO BACKUP, they have all been replaced since the ETO 1.20 release. All you will see when you run the BDP Zapper and/or the ZX Zapper is a slight flash. Trust me...they're working just fine. Go into the main game folder and see if you can find any *.BDP files.

[Human Drone]

Gee, Thanks for all that help... I didn't think I'd screwed it up that bad... I did set the spawns to 1, era to 1936 1940, and flew once between each... Must've bungled something!

Anyhow, will do. Sorry to have caused you all that, I was being careful.

Best,

Tom

[Human Drone]

My dear sir:

After some examination, I'm not so sure that I have a problem at all. It's just the QC spawns that I want to stop. Are these controlled by your spawn files?

I opened all of them, and nothing really seems amiss - like, the air.noair has a single entry in it, and, while I have yet to lean the details of such things, I suspect that the probabilities specified mean that it will never happen. As well, the batch files appear to be doing their job... clever enough.

So I'm looking around, I'll be darned if I can remember how I stopped them before... Maybe when I get home I'll see something obvious, I don't have it on my machine.

Thanks again,

Tom

[FireStorm II]

Human Drone,

"It's just the QC spawns that I want to stop"

This just rang a bell, do you mean in QC, after you shoot 'em all down, they all come back ? If so there is a small mod to do in a file, one sec let me check....


Yes, it would be the AppData folder. Win7 standard would be C:\Users\NAME\AppData\Roaming\Microsoft\CFS3 ETO Expansion_________\uisel

Open this file and look for:
<EnemyAircraft>
<Aircraft type="string" val="3GR Fw 190D-9"/>
<Model type="string" val="3gr_fw_190d_9"/>
<Quantity type="uint" val="2"/>
<Respawn type="bool" val="y"/>
</EnemyAircraft>

Change Respawn type from "y" to "n"
Now you can land in peace after clearing the skies!

[Human Drone]

YOU DA MAN! That's it! See, folks like you & grizzly are why I threw $20 in the kitty this AM... Thanks for all , + the ETO and PTO!