sweetmusic

Very long time no post... FS2020 has brought me back! So the grass bends in the wind? If you think about it, what's the real difference between rendering grass and trees? Are the trees and grass too high? In some parts of the video, I feel like Antman flying over the rainforest! Can't wait for "bicycle" mode. Great scenery everywhere.

So how secure and hardened are our major air traffic control centers? The unintended no fly zone around Chicago due the outage was dramatic and big.

Looks like EZCA has OCD when in AUS !

Yikes, that's beautiful scenery! So OK... but just one more addon. :rolleyes:

I never delete files that I can't recover if something goes terribly wrong. I rename them instead, usually by appending an "x" to their file name extension. I do the same for an entire directory of unwanted files. After a reasonable time period that assures me that the "missing" files have no adverse effects on FSX, I may then delete them if I need the space. By not deleting them, restoration simply involves removing the "x". Hope you can find a solution.

See this thread: http://forum.avsim.net/topic/413464-using-fs9-ai-traffic-in-fsx/

I bet Florida airports get some pretty good night lightning!

[WHENPIGSFLY] show_source_code=1 law_suit=0

This has been a fun thread to read. Let's keep it going... IF the code owners would be willing to reveal some "new" FSX parameters or secret code that could be tweaked or hooked into, what would you like to see revealed? A great question, perhaps, for Pete Dowson and his FSUIPC product.

Agreed, but that's because he's using the same website product (IP.Board).

If you do decide to use AIFP V2, here's what worked for me: 1. After installing AIFP, be sure to right-click the executable program AIFP2.exe and select "(run as administrator)". 2. Once running, select "Convert FS9 Traffic Files to FSX" from the Files menu. 3. You will be asked to select the FS9 traffic files you want to convert to FSX from a file tree menu. Navigate to where your FS9 traffic files are located. 4. At the bottom of the screen, be sure to check the box "Add _FSX suffix to FSX traffic files. Also, DO NOT check the "Delete FS9 files after conversion" since you still need these for FS9. 5. After pressing "Convert", you'll be asked to browse to your FSX traffic file destination folder. For me, this was "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Scenery\World\Scenery". 6. Hit "OK" and the files will be converted. The program will display a CONVERSION REPORT that you can print out if you wish. That's it! As always, proceed at your own risk. Good luck. By the way, if you don't convert the FS9 traffic files before using them in FSX, NONE of your FSX AI traffic (including MS standard AI traffic) will be visible.

You can also add a comment at the end of a normal line of code. Everything after the double forward slash is ignored: RUNWAY_LIGHTS_APPROACH_SCALAR=1.6 // this scales the approach light bars

Try this link: http://www.fsdeveloper.com/wiki/index.php?title=Sound_Cones_in_FSX

The Ivibe website says: "FSUIPC is an interface for Microsoft Flight Sim that will provide the TFS3 Control Panel with the game telemetry needed to support intellVIBE." This fact alone makes the product sound very interesting!

Weren't trees, houses, and buildings intentionally oversized by Microsoft to cut down on the sheer number of polygons required to render city and urban neighborhoods? Cars always look too small compared to trees and other autogen objects. It would be nice if a scaling factor could be set in some appropriate config file to control their size.

I bought a pair of wireless eDimension 3D glasses years ago. The experience was very good, especially in-cockpit. But the stock FSX runway lights at night were not rendered properly (they floated above the ground). I imagine the 3D glasses and drivers have gotten better since then, but the FSX runway lights are probably still a problem. Maybe Orbx and their custom scenery has overcome this. If so, that would be great!

A very nice choice... Can you suggest a high-wing GA aircraft of similar quality? I like a full view of the ground.

I seem to recall a possible cause related to landing gear and runway tire screech sounds that load into memory just before touchdown. Could a terribly fragmented disk cause a temporary freeze while these sounds are loading? Maybe others can comment further.

Thanks! I feel better now. :rolleyes:

All those buttons to the right of the co-pilot's seat look like an accident waiting to happen... especially if the plane suddenly banks hard right! Oops!

That fix works great for highway traffic, but doesn't affect airport vehicle traffic.

Thanks. I'll give some a try! As far as the Nvidia control panel, I really like the Digital Vibrance control (mine is set at +70%). It boosts the color saturation to a nice level.

This is a long (and interesting) thread. Makes me think, though. Whether it's through SweetFX, ENB, FXAA, graphics card settings, or monitor settings (in any combination), what is atmospheric reality? Except for trying to achieve the "clearest day on earth", for me atmospheric reality always includes humidity, haze, and fog that mute colors and textures to some degree. Doesn't that undo much of the finer settings these tools bring to the table? That said, I'm happy with the FSX visibility slider and the Nvidia saturation, brightness and contrast controls. What am I really missing?

Good point, especially since most monitors are cold fluorescent backlit LCDs. I'm sure dynamic “local dimming” LED monitors do a better job with night time flying. (Need to be careful. This is starting to sound like a hardware post!).

It makes the picture color richer, brighter and cleaner. Used with other settings, colors are retained while adjusting for a darker image overall. Officially, NVIDIA says: Digital Vibrance: Color Separation and intensity; helps to compensate for lighting conditions in the workspace. Gamma: The brightness of mid-tones without affecting shadows and highlights. Contrast: The difference between the lightest and darkest parts of the desktop. Brightness: The lightness or darkness of your display. Hue: Adjusts the overall color of the image. In use, I always leave the Color channel setting to "All channels" and I never touch the Hue (leave at +0%). The best way to get the settings "right" is to EXPERIMENT. Put FSX in a large window (alt-enter) so you can see the NVIDIA Control Panel. The effects are immediate. No need to "Apply" the settings unless you want them to be saved. You can jot the settings down and may find different favorite settings for day, night, dawn, and dusk. There are so many combinations (and easy to change) that I haven't found a need for the other shader packages like ENB or SweetFSX. One thing though, NVIDIA Control Panel doesn't sharpen the image. Sharpening has always puzzled me as something that counteracts anti-aliasing and weather visibility. Maybe someone can comment further. One final thought. You can't achieve a convincing dark night while sitting in a well lit room. Ambient light ruins the effect. If you can't darken the room, wait until dark and turn off the lights.