In fact the cockpit doesn't look as good as I have seen in YouTubes.

 

That's likely between your computer and your eyes (graphics card settings). I see that you have an nVidia card - try these:

http://forum.avsim.net/topic/324786-nvidia-configuration-guide-inspector-2xxxx-drivers-version-20-explanations-of-all-settings/

That's likely between your computer and your eyes (graphics card settings). I see that you have an nVidia card - try these:

http://forum.avsim.net/topic/324786-nvidia-configuration-guide-inspector-2xxxx-drivers-version-20-explanations-of-all-settings/

I will double check but I know Nick and I set up my PC exactly per his specs.  NV Inspector was set up per his guide but I'll look now and compare notes.

 

 

However, I looked at my FSX.cfg and noticed that TML is still 9.

 

Hold on!

 

Remember there is a difference between "TextureMaxLoad=" and the one we're supposed to be talking about here, which is "TEXTURE_MAX_LOAD=".  It appears that you changed "TextureMaxLoad=" from it's default value of 9 to 4096 (or the value you put in there). 

 

Please go back and put "9" in there, and change "TEXTURE_MAX_LOAD=".  That should do the trick my friend!

 

 

Dave

AA Flags - None

AA Mode - Override

AA Setting - 8xs[Combined 1x2 SS +4x MS]

AA Filtering Mode - User Defined/Off

AA Filtering Setting - 16x

Neg LOD Bias - Clamp

Texture Filtering Quality - High Quality

Single diaplay

Prefer max performance

I do not use the NV Frame Rate Limiter

I have Vertical Sync Tear Control to Standard

Vertical Sync 1/2 Refresh Rate

Hold on!

 

Remember there is a difference between "TextureMaxLoad=" and the one we're supposed to be talking about here, which is "TEXTURE_MAX_LOAD=".  It appears that you changed "TextureMaxLoad=" from it's default value of 9 to 4096 (or the value you put in there). 

 

Please go back and put "9" in there, and change "TEXTURE_MAX_LOAD=".  That should do the trick my friend!

 

 

Dave

Hi Dave, bingo, that's what I did.  Set it back to 9, then looked at TEXTURE_MAX_LOAD= and it was 1024.  So I set it to 4096.  Rebooted the sim and still don't really see any difference.  

Before I changed it to the correct settings I was changing planes to look at the different typos at Fly Tampa's KBOS and FSX crashed on me.

​Anyway, I have it to 4096 now as per your post, thanks.

I'm still unsure about what it may do however.  I have two Flightbeam airports, KSFO and KIAD but I did NOT tell it to load the 4096 textures.  So hopefully it won't give me OOM crashes.

One thing that DID give me OOM's every single time was a long flight in Flight1's B200 or their Mustang from KBOS to JFK and flying over Aerosoft's VFR Manhattan I would hear the OOM chimes and then FSX would crash on landing.

So I disabled Manhattan in the scenery library.

I also read that OOM's can be caused by too much AI traffic and I use UT2.  I dialed it back to 60% airline and 10% GA.

 

 

Remember there is a difference between "TextureMaxLoad=" and the one we're supposed to be talking about here, which is "TEXTURE_MAX_LOAD=".  It appears that you changed "TextureMaxLoad=" from it's default value of 9 to 4096 (or the value you put in there). 
 
Please go back and put "9" in there, and change "TEXTURE_MAX_LOAD=".  That should do the trick my friend!

 

Good catch! Totally missed that.

 

Oh Microsoft...

 

 

 

Then again, we also have the FAA with its own various definitions of "night."

 

 

I do not use the NV Frame Rate Limiter

 

If you're using a frame rate limiter at all, it should be the nVidia one (at least in my experience).

So another perhaps stupid question, a friend sent me a YT on this planes by some guy named Nick and he makes training videos, I think the name of the company is Angle Of Attack and his plane has a window with glass in the upper right side and it was greenish and you could see out of it.  Do any of the models have this?  I think I have loaded them all and I can't see this.  Or was that just a demo of the NGX before it was released?

I have a LOT to learn yet!

Good catch! Totally missed that.

 

Oh Microsoft...

 

 

 

Then again, we also have the FAA with its own various definitions of "night."

 

 

 

If you're using a frame rate limiter at all, it should be the nVidia one (at least in my experience).

Can you give me a reason why?  I would like to learn this.  Why is there a difference between FSX's and NV's?  Like I said, I don't know one millionth as you guys but I'm trying to learn.  Some things seem easy but others I don't have a knowledge base you guys have.

 

 

Do any of the models have this?

 

Several do - to include the default PMDG livery (company options were discussed to in the intro manual - not sure how directly they referred to the HGS, though, as I haven't read it in a while). Regardless, I wouldn't compare anything to AoA unless you have a computer with their specs (which I'd argue is unlikely).

 

 

 

Can you give me a reason why?  I would like to learn this.  Why is there a difference between FSX's and NV's?  Like I said, I don't know one millionth as you guys but I'm trying to learn.  Some things seem easy but others I don't have a knowledge base you guys have.

 

There's some issue with the internal FSX frame rate limiter. I can't remember what the issue is and why an external limiter would work better, but there's a ton of discussion in the community if you'd like to have a look. To me, it's better to set things from a hardware perspective than a software one (nVidia inspector controls hardware while FSX is just software).

Several do - to include the default PMDG livery (company options were discussed to in the intro manual - not sure how directly they referred to the HGS, though, as I haven't read it in a while). Regardless, I wouldn't compare anything to AoA unless you have a computer with their specs (which I'd argue is unlikely).

 

 

 

 

There's some issue with the internal FSX frame rate limiter. I can't remember what the issue is and why an external limiter would work better, but there's a ton of discussion in the community if you'd like to have a look. To me, it's better to set things from a hardware perspective than a software one (nVidia inspector controls hardware while FSX is just software).

I see.  Yes, hardware versus FSX software.  That makes sense.  Ok, so I'll have to look at the different models.  I had FSX close on me after changing models too many times.  But that was before the TML was fixed.

 

 

I had FSX close on me after changing models too many times.  But that was before the TML was fixed.

 

This is bound to happen, actually, and doesn't have much to do with TML. The reasoning is actually in the intro manual, but the basics are that loading a complex aircraft and loading it again (even a different livery of the same aircraft is loading it again) will cause issues. If you're just having a look at various liveries, this is fine (though you'll have to put up with the inevitable error). If you're jumping between liveries before a flight, it could end poorly.

 

Off the top of my head, DAL, SWA and the PMDG liveries all have it. It can be added to any livery, however, and the steps on doing so are in the intro.

This is bound to happen, actually, and doesn't have much to do with TML. The reasoning is actually in the intro manual, but the basics are that loading a complex aircraft and loading it again (even a different livery of the same aircraft is loading it again) will cause issues. If you're just having a look at various liveries, this is fine (though you'll have to put up with the inevitable error). If you're jumping between liveries before a flight, it could end poorly.

 

Off the top of my head, DAL, SWA and the PMDG liveries all have it. It can be added to any livery, however, and the steps on doing so are in the intro.

Ok, so I'll look in the intro.  I have the DAL installed and do not see that darned window.  I was just messing with it.  Here's what just happened.  I quit the flight, went back to the select plane/location etc. menu and tried to load the PMDG 700NGX and I got this:

 

Invalid Hardware or Driver Detected.

This graphics card does not meet minimum requirements for shader support.  This product requires a geForce 3/Radeon8500 class or better graphics card.  Flight simulator will now exit.

What the heck?  I have a GTX980 and all the latest drivers and the PC is only two weeks old.

I don't understand this message.

 

 

I have the DAL installed and do not see that darned window.

 

While in the VC, pan up. It'll be there. In order to bring it down into view (because it's not always kept down), click on the left pillar, or assign a key command to bring it into view.

 

I'll suggest the following:

Re-read the intro manual.

Do the tutorial.

 

If you still have questions, come back and ask away. You'll seriously gain a lot more with the intro and tutorials with the expanded and pictorial explanations rather than what you're going to get here via text.

While in the VC, pan up. It'll be there. In order to bring it down into view (because it's not always kept down), click on the left pillar, or assign a key command to bring it into view.

 

I'll suggest the following:

Re-read the intro manual.

Do the tutorial.

 

If you still have questions, come back and ask away. You'll seriously gain a lot more with the intro and tutorials with the expanded and pictorial explanations rather than what you're going to get here via text.

I think we have our wires crossed.  I can bring down the HUD no problem, I'm talking about that training video where there is a clear window with a green tint in the upper right corner that you can see through.  I wonder if that's from them doing a demo before it came out or something I'm missing.  I'm reading the intro right now and then I'll go through the tutorial.  There's a lot to learn, in fact 3523 pages!  Zoinks!  That's a oot of pages.

 

 

I think we have our wires crossed.  I can bring down the HUD no problem, I'm talking about that training video where there is a clear window with a green tint in the upper right corner that you can see through.

 

Sounds like they have "eyebrow windows" selected. Another company option, though I forget who uses them...

 

It's an option that you can add to any livery, though.

 

 

 

I wonder if that's from them doing a demo before it came out or something I'm missing.  I'm reading the intro right now and then I'll go through the tutorial.  There's a lot to learn, in fact 3523 pages!  Zoinks!  That's a oot of pages.

 

You don't necessarily need to read the FCOMs and FCTM. The intro and tutorials will get you started just fine, and at much less of a time cost than the daunting 3000+ of the FCOM/FCTM.

Sounds like they have "eyebrow windows" selected. Another company option, though I forget who uses them...

 

It's an option that you can add to any livery, though.

 

 

 

 

You don't necessarily need to read the FCOMs and FCTM. The intro and tutorials will get you started just fine, and at much less of a time cost than the daunting 3000+ of the FCOM/FCTM.

Ok, good, so they do exist.  Is there an option somewhere that selects this?  It's really no big deal at all, just cosmetic, I'm still going through the introduction then on to the two tutorials.

I want to thank all of you guys for helping me.  I really appreciate it, you've been a big help.

Jack

Ok, good, so they do exist. Is there an option somewhere that selects this?

See page 60 of the Introduction Manual for eyebrow windows. Like Kyle said read the Introduction and do the Tutorials.