TTools

[sailor]

How can I get TTools to work with GW? It seems to get confused with FS9 and won't focus just on GW.

[Joao Paz]

Maybe if you rename ....

... your [Flight Simulator 9] folder to [Flight Simulator 9 backup] ... and then your [FSGW3] to [Flight Simulator 9]

Then do your traffic stuff, and rename back both names

[Admin]

Open Traffic Tools, click on file and choose User Defined for source and traffic

[sailor]

Renaming the files seems to work ok. Tried your suggestion Tom, but things got too confused after a while as it would change back on its own.

[dca1322]

While we are talking about TTools, I've noticed, in my "method A" install, that vintage AI aircraft are trying to fly routes WAY above their maximum ceilings. I've got Waco's trying to get to 29,000 ft.!

This is obviously a problem with any traffic changes I have made to my original FS9 install...which do not work with GW. I am trying to find a quick and dirty way to fix this. I have several "traffic" .bgl's in my World scenery folder but I'm not sure if GW added one or what I should delete? I could post the list but it is 14 files and I'm thinking that there must be a default? Or should I just extract the original FS9 traffic (traffic.bgl??) and put it in and go from there?

Suggestions on how to handle this are really appreciated, gang.

Vic

[Bill Lyons]

If you would care to edit the 20,000 thousand flights in the traffic bgl to make the old planes fly at the correct altitudes we would be much appreciative.

[Admin]

Golden Wings installed a modified basic traffic file. There is no quick & dirty way to change it or it would have been done. I might point out that everything looks pretty good under 5000 feet and If you don't go to 29000 ft you won't see any Wacos up there. Also the only way to run ATC in GW is off. Just as it was...

[dca1322]

I have been running with ATC off. I would, however, rather have all these AI aircraft not flying at 300FL They should be in their normal altitude range.

Yes, I understand the problems in altering 20,000 plus AI flight plans...it's basically undoable by any normal human...and I'm one of those (OK...the "normal" part has been debated enough! ).

I'm thinking, however, that if a database of all of the GW modified AI flight plans was made, it would be much easier to make "general" changes. For instance, sort the DB by aircraft #, find the GW AI aircrafts max ceiling (from the aircraft.cfg), then do a "change all" for all flightplans, for that particular aircraft, which are above max (change all "200" to "085", all "300" to "135" for example). The original FP altitude would give you the direction...they could all be changed to "VFR", which they should be, anyway, and 500 ft. could be added to the FP altitude when doing the "change all".

Unless I'm missing something it should not require the individual changing of all 20,000+ flight plans, one at a time.

I'm no computer whiz, but I'm going to give it a try, for my own benefit. I've already done a "change all" from IFR to VFR...but that won't, in itself, add the 500 ft. to the altitude. That will have to be done in another step.

What, exactly, were the traffic files called that came with GW? I need that info to continue.

Thanks.

Vic

[Admin]

The only file you need to be concerned with is traffic030528.bgl

I estimate it will take you upwards of 300 hours to accomplish your goal. That is upwards of 300 hours that you will not be enjoying FSGW, but it is your choice. Also be aware that when you alter those flightplan parameters, you will be totally confusing the entire traffic schedule since you will be altering arrival times on every flight that you modify the cruise level. Basically, you will have a mess instead of a traffic file. For your purposes, it might be better just to delete that file annd then build your own basic traffic file just the way you want it

[dca1322]

Hmmm...hadn't thought of the affect of altitude on flight times (and, so being, on arrival times). But, not to be detered, I think if I change every flights altitude by a certain percent (using the highest, reducing it to get it below the AC's ceiling, and applying that percentage, rounded of to the nearest 500 ft. level) it will be interesting to see what happens.

What the heck, I can't stand a Waco at 30,000 ft. I want my AI down here with me, where they belong. Heck, I'm seeing open cockpit and non-pressurized GW aircraft with outrageous ceilings in their aircraft.cfg's of almost 20,000 ft! That will take more research as that is not to be believed.

But, anywho, I'm getting the feeling I have worn out my welcome with my GW questions and will move along forthwith.

Thanks for all the help, Tom. Best to you.

Vic

[Admin]

Since you have deleted your account I suppose you won't see this, but nevertheless...
What needs to be changed in the following example is marked in red.

AC#45,N64440,2%,4Hr,IFR,01:42:17,02:48:05,320,F,0498,KBUR,03:42:15,04:48:03,330,F,0497,KTUS

Assuming you can change one flight per minute, I make that between 300 - 350 hours. Perhaps you can devise a way to batch change. Anyway... I don't have time to mess with it so have fun. And since you've deleted your membership, I'll lock this thread.