Dave_YVR

Almost 28 years now in ATC, I guess I've been doing it wrong this whole time. 🙄

Say what? ATC is responsible for terrain separation when issuing ANY altitudes or vectors when on an IFR clearance. In the sim however, not so much.

No, of course not but it had nothing to do with the 7900 altitude assignment, or any other non even thousand altitude. I wouldn't and couldn't expect either the default or payware ATC to know every minimum IFR altitude including MRVA's. The default ATC has never known much about mountains and terrain clearance. The point was more the fact that your comment about "Never in the history of aviation has an aircraft been asked to climb to or descend to some random altitude like 7,800. Never. " is a wrong assumption. How do you know it's random? I'm not arguing the fact that it was too low, thats clearly obvious but odd altitude clearances are issued all day every day worldwide, they just have adequate IFR terrain separation.

Not true at all. It all depends on the minimum IFR altitude applicable for where the aircraft is. MRVA's for instance are rarely at even altitudes as are most other Min IFR alts.

In the brief time I ran 4k, I just used the Windows display scaling and set a custom % to get the zoom that worked best for me.

Chrome actually has approx 69% of the worldwide non-mobile browser market up to June of this year. Safari and Firefox both have about 8.75 and Edge has just under 4%.

It all depends on the conditions, if the snow is heavy it'll melt and if dry it will blow away from the jetblast.

It's only 8 million more pixels being refreshed 30, 60 or more times per second. It's going to have some effect on performance. 🤔

Also try not to let installers install full products into the Documents folder, create a specific folder of your choosing. I have a few hundred addon's in both my v4 and also v5 and the Documents folder is still under 50mb for each sim.

Even if you do have to update or uninstall/reinstall P3d, the uninstaller only removes P3d files and not those that were installed by other products. It's not really a big deal.

You are the operator, compliance is all up to you! 😉

There was a pretty massive model update today, you should have been prompted to update.

I added T2g VHHH v2 manually to the scenery.cfg. Took about a minute and is super simple to do. I still prefer it myself over the xml addon, at least I know where everything is.

Not anymore, I did have to correct the airport elevation as it was showing a foot too low. Added in some excludes for certain landmarks that are much nicer than default and it's good! It's not up to date (it was in 2016), but it's a million times better than what an ADE fixup will do for it.

That's ok, you don't need to open the stock airport file at all. Using the FTXG CYTZ as your working ADE, I removed the Downtown city objects and let sim use the default ones or you can keep the ones included in the CYTZ Objects file and create excludes to remove the default duplicate buildings. The process of loading the Stock data is only to remove the default airport objects from showing up as well as the ones in the CYTZ ade. It seems it worked! Again, not the FTXG CYTZ, but Canadasim CYTZ in V5.

Those will be in the FTXG CTYZ Objects file. You can merge the objects file with the ADE and then select what you want and don't want to keep.

You can easily remove those with ADE. Getting the default objects to not show up is easy as well, but it's often more than just adding an exclude over the airport as in the video above. From Tools, select Load Stock data, and select Taxi Signs and Scenery Objects, once done under Lists, select Scenery objects and Filter by True. Next Select ALL and delete those newly imported default scenery objects, ADE will leave behind micro excludes that it added for each object. Do the same with the taxi signs, save and compile. I've converted probably over a hundred ade's using this method so far including many of the ORBX FTXG airports. Some end up with elevation issues, most do not. It just comes down to trial and error. With the ORBX FTXG CYTZ you will probably find some elevation issues, but thats independent of getting rid of the default scenery objects coming though and I haven't worked on fixing that as I'm working on getting the CanadaSim CYTZ to work instead.

Fair enough I guess, but you shouldn't be.

That right there is 100% your answer. TG has 3 flights a day to the older OPRN and none to OPFA. You really should really do yourself a massive favour and try out AIG's freeware, it has hundreds flights a day to OPIS and also some action at OPFA (it's just a slow airport irl with approx only 20 airline movements /day). You will also be stunned to see what you have been missing at in the US as well traffic wise.

Set your ORBX Library insertion points. As always, Airports and regions get set below your bottom most addon airport, then LC gets set below airports and regions.

As the name implies, it's in the scenery folder that houses your ORBX KSAN. To be specific the filename is KSAN_V2_ADEX_ADE.

Sure you can, you just need to have configured AI Companion to limit AI elsewhere.

He could configure the sim to make it look more like it would with a $500 video card and get more FPS, but he doesn't. Nothing wrong with a smooth 24fps.

Try running the FlightBeam Manager for starters, it has a built in troubleshooter that will fix most problems.

Afaik, the only A35K AI model available is the payware one from FSPXAI. While you can add it yourself to FLAi, there's a very slim chance you'll see a free one pop up anytime soon.