bobterri

I believe it does.

True

Well, I am not complaining, because the developers have done a fantastic job. I am very grateful for their efforts and what they have done. I was just wondering.

Does the A32NX have RNAV landing capability yet?

Have a look at this:

Does anyone know what happened to this virtual airline? I came back from vacation and “poof,” it’s gone. I can’t log into their website (just a blank page), and I can’t log into their Smartcars.

Thanks Alvega.

Ok, I might be a little dense, but you're saying it's the small o, not the capital O.

Thanks for this. One question. Is that a capital O, and if so, do you have to Shift - O, or set Caps Lock?

My Nvidia driver is 533.36. Those of you who are not having any problems with the Windows 11 update, what is your driver?

I installed it and immediately noticed a stutter when turning while taxiing. I rolled back to the previous version and the stuttering went away.

Thank you for this refreshing and encouraging perspective. It's much appreciated.

Is this tool finally working with the Fenix A320?

I had a similar problem on a new computer. http://www.avsim.com/topic/483993-newcomputer-fsx-se-windows10-stutters/page-1 I tried everything but finally went to p3D v3.1 and it is running very well.

I, too, had a very similar problem with FSX-SE on a new computer running Windows 10, as you can see from the thread I started: http://www.avsim.com/topic/483993-newcomputer-fsx-se-windows10-stutters/page-7#entry3388333 In the end, I never solved it with FSX-SE, however, I installed P3D and have not had stutters. I know that doesn't solve your problem, but that's how I solved mine.

Because of another issue, I decided to reinstall FSX-SE. I had the same issue. It's as if FSX-SE either can't see the .BGL files or won't read them in /Addon Scenery/scenery, though it sees them in /Addon Scenery. Again, this is my main gaming computer and it is a Windows 10 computer. I have a laptop running Windows 7 on which I installed FSX-SE and it has no problems seeing .BGL files in the /Addon Scenery/scenery folder.

Mike, Ran GPU-Z and the card is running at x16 as it should.

All, Thanks. Mike, I have GPU-Z installed so I'll give it a look, however, my textures don't load slowly. Texture loading is great. Also, as I stated on the other thread, I downloaded and installed the X-plane demo, and with just about everything on the highest setting I'm getting a very fluid, stable simming experience. If my problem was a hardware problem I would think that X-plane would be unstable also. Anyway, I don't want to hi-jack my own thread and recreate the same kind of thread I already started previously...just some thoughts.

I started a conversation on the MS FSX | FSX-SE Forum entitled "NewComputer +FSX-SE + Windows10 + stutters." To make a long story short, I have been plagued by stutters on a new computer running FSX-SE and after running all the suggested tweaks, etc., nothing has really solved it. I was wondering if Steve's Fixer could help with stutters? I'm not looking for guarantees, just others who have installed Fixer and seen improvements with stutters. Anyone?

I do have FSDreamTeam's KLAX and KDFW installed, but at KDTW it's just Ray Smith's. And by the way, you're right, it was the jetways not gates. The tarmac from the default scenery was also bleeding through. I agree I'm just putting a bandaid on a problem. I just don't know what else to do. Somehow, apparently, FSX is recognizing the KDTW_OBJ.BGL file in /scenery/global/scenery but not KDTW_RS.BGL and KDTW_CVX.bgl in /Addon Scenery/scenery. I still suspect it's because FSX-SE is installed on Windows 10. I never had this problem before when FSX was installed on Windows XP and Windows 7. Oh, and it was doing it before I had any payware scenery installed.

Doggone it, I wish I had taken a picture! Let me describe an example. I installed Ray Smith's KDTW scenery just as he said to. KDTW_RS.BGL and KDTW_CVX.bgl in /Addon Scenery/scenery. KDTW_OBJ.BGL file in the /scenery/global/scenery. What I had after doing so, after loading up KDTW in FSX-SE parked at D8 at the new D-terminal was the new terminal from Ray Smith's Scenery but the gates and tarmac bleeding through from the default scenery. The old terminal was gone, but as I said, the gates were still there.

I'd like to post some pictures, but as I stated above I've found a way to deal with it. So far the method I related in my second post is working and I am getting zero bleed through. It's certainly not the way the authors of these sceneries intended but it's working.

Interesting development! I decided to try to install a freeware airport a little differently than per the instructions. I had tried Ray Smith's KDTW scenery and had the bleedthrough on a prior installation. I created a KDTW folder and placed it directly in the addon scenery folder. I created a scenery folder within the newly created KDTW folder and put KDTW_RS.BGL and KDTW_CVX.bgl folders in that folder. I put the KDTW_OBJ.BGL file in the /scenery/global/scenery folder per his normal installation instructions. I then activated the KDTW scenery after starting up FSX-SE and bingo! No bleed through. I tried it on KCMH scenery I had created in ADE which had bled through before and this time it too, using this new approach, had no bleed through. It sounds to me like it's a permission's issue, which I need to research and try to change. It may be a Windows 10 scenario. I'm not sure.

Recently I purchased a new computer to replace my old-faithful (I7 950) because of motherboard failure. The new one came with Windows 10 installed. I installed FSX-SE (had to run it in Windows 8 compatibility mode), configured Nvidia Inspector. It runs great, but then I began to install some freeware airport addons, mainly Ray Smith's. I noticed that some of the default scenery is bleeding through. I tried to change my texture resolutions to 30 cm, 60 cm, etc. None of the changes makes a difference. I have about a dozen payware airports installed and have not noticed any bleed-through on them. Any help? The new rig: 17-4790k, GTX 970, 8 gigs of ram.

Very helpful. Thanks.