xTalonFoxtrot42x

Thought this was a glitch. I believe its tied to the bloom effect. Turn off bloom in fsx and it should go away.

Newest nVidia drivers as of 344.48 WHQL I believe.

Fixed it, rolled back my drivers. I updated them prior to installing DX10.

Looks like it may not be DX10 causing the issue. I tried reverting everything back and I still get the stutters every 4 or 5 seconds. I have no idea what caused this. I also completely deleted my fsx.cfg and started fresh (no tweaks) and still got the same stutters at either JFK or LGA.

Steve: AI traffic has been turned off. I haven't tries uninstalling the libraries but I will do so. This is the same exact issue described by the poster above. Again, the only remedy is turning down the scenery complexity slider. So it has to be some airport building object chasing the stutter. Not lights, runway, water, or anything else.

Issue: I'm having the strangest issue since trying to switch over to DX10. Whenever I'm in NYC (KLGA, KJFK, etc) I get intermittent stutters which essentially pause the simulator for about 1-2 seconds. It repeats on a pattern of 5 seconds stable, 1-2 seconds pause, back to 5 seconds of stability. This eventually goes away if I'm far enough out from an airport such as directly over the city. Once I get close enough to a NYC (mainly KJFK and KLGA) the stutters return. What I've tried: 1) Every possible time of day 2) Every type of aircraft 3) Default and custom scenery 4) Inspector settings and FSX settings. What worked: The only solution I could find was to turn Scenery Complexity to Sparse. Leaving Autogen at sparse or extreme did not matter and can be ruled out. Thoughts: I believe, without a doubt, there's something at these NYC airports in terms of objects that are not compatible with DX10 and thus causing the stutters. I've tried to replicate this at numerous airports in dense populations and rural ones. I've also tried to replicate it at custom and default airports. The only "region" so far that gives me this issue is the NYC one. Are there any freeware mods or something that can replace the generated airport scenery specific to these airports that can be compatible with DX10? Any help would be appreciated.

Bump. I've read that a guy named Metzger did some updates to the .air and .cfg files a several default aircraft but his site, and links to the downloads, are all dead. Anyone have the updates backed up or know of them to be uploaded elsewhere? Edit: Found this link which updates the Cessna172 (http://flyawaysimulation.com/downloads/files/6344/fsx-panel-and-fde-for-default-cessna-172sp/). Would still like to know about Metzger's updates though...

Those were the unedited original files. In photoshop I made sure to completely "paint" the alpha white. Would you be able to test the actual file with me and see if you can get the lights to be toggled? I'm starting to feel like this isn't a alpha texture problem because the 747 model doesn't have an all white alpha but the lights are still toggled. Also with that model they aren't controlled by the landing lights but by a separate circuit just like the default fsx aircraft.

My only suggestion is to rethink the GPU. If you're going to splurge on a rig then the GPU is something you don't want to skimp out on. With Nvidia it a "goldilocks" problem. A 660ti is too cold (underpowered) and a 680 is too hot (overpowered) but 670 is just right. If money is no object, go 680. Otherwise you should start with a 670 and build from there. I also think any "super clocked" or "ftw" editions are garbage. You're paying a premium for something you could do for free yourself. Also the benefits to OC a GPU are generally small compared to OC a CPU. Lastly, you really don't need 3GB ram. It's a great way to eat more money from you. Most games these days don't even come close to being able to utilize that kind of video memory. So to summarize, grab a 2GB GTX 670 or 680 and build from there.

Weight and efficiency. Two engines produce less drag and weight thus leading to more fuel efficient flights. It saves money on maintenance costs as well.

Didn't seem to help. When I changed the alpha to all white it had a weird effect where the light could only be visible from certain odd angles. If it's all black then it's like the texture doesn't exist. There are no night effects. I'll attach one of the files in question. The image is too big to upload but use the links in my OP to view the file in question. Here's the main image (http://i.imgur.com/gYUdkv3.jpg) and here's the alpha (http://i.imgur.com/wfYzFO0.jpg). So when I make that alpha all white it does the weird light effect. Still no toggle though, landing lights or otherwise. Edit: I noticed that the toggle (with the landing lights) works when using the FS9 POSKY model in FSX. But then I lose the ability to add a VC to the model and it's not optomized for FSX. It seems something is lost in translation between the two models.

Hello, first post so I'm hoping someone can help me out. This is regarding FSX: On the default aircraft you are able to toggle both the cabin (window) lights as well as the tail logo lights using a key command (generally "L"). This will turn the light effect or texture on/off when selected. However, I've found with this POSKY 737-800 model (OSX738WE) the light texture is permanent depending on the actual day/night cycle of the sim. Other POSKY models, such as the 747-400F (OSX744FV4_CF6-80) DO allow the cabin/tail light textures to be toggled. I understand that these lights are not defined in the [LIGHTS] section of the aircraft.cfg but rather controlled by the night textures in the aircraft texture folder (Os738body_r_l and Os738body_l_l). My question is, how can I enable such an effect for the 737 as seen with the 747 or other default aircraft? I've reviewed various posts on the subject and have found two schools of thought; either modify the textures alpha or edit the model in material editor. Is this an issue with the model or an issue with my night textures? Thanks.