JesC

Just finally picked this one up. After a couple of short flights it seems like a really satisfying simulation. Really enjoy my Carenado Hangar!! Just wondering if there was ever a solution for disabling the Airspace Alerts on the MFD and a means of defaulting the start up to HDG Up mode... ...or, is it just the same drill as the PA46T? Thanks,

I don't have either of those GPS units and I don't recall ever trying to enter coordinates in any FSX GPS units. But shouldn't you be entering those as 58N20W or 59N30W. If so, then perhaps the values greater than 100 would be accepted. Just a thought.

Sometime in the next few days I will probably give the newly released 344.11 driver a try. I have always been successful running every new release but, at this point I have gone all the way back to 335.23 to maintain system stability. Anything above that version showed great performance promise but was causing regular system crashes. Its a roll of the dice!!

According to the Facebook page the service pack has been released.

Congratulations!! Well Done!! Point Plan-G to the Scenery.cfg file specifically, not just the FSX folder. In other words C;\ProgramData\Microsoft\FSX\Scenery.cfg.Then I think you will have it. So I assume Gate 21 is gone now? BLUE SKIES Jesse

I don't think you had mentioned this before or perhaps I misunderstood. Do you mean that you actually uninstalled KMCO 2.0 and removed the KMCO 2.0 BGL files from any FSX folders?

Yes. There is a Gate 21 in the default file. The file you referenced for KMCO has no Gate 21. I don't think I know what "Airprt Editor" you are referring to; but, I am opening the BGL files in Airport Design Editor (ADEX 1.61 Professional).

Looking at the KMCO file you referenced there doesn't seem to be any "Gate" 21; only Cargo Parking 21. So that would seem to be why FSX doesn't recognize Gate 21. Not sure why Plan-G is seeing Gate 21 but it would certainly seem that it is falling back to the Default file for the original Gate 21. It may have something to do with the way Plan-G was updated.

Are you totally certain you don't have any other KMCO files installed?

You might also want to search both the Forum and Google for the kernelbase.dll CTD. There is some interesting reading that may be pertinent to your situation. In fact you may want to try posting in the Avsim CTD Forum. Some very helpful and knowledgeable folks there.

Well... I'm very sorry to hear that. I was really hopeful for you. Also sorry for any wasted effort. Perhaps someone else will have a better idea.

Should be fine. Let us know how it works out.

The 335.23 has worked nicely for me. But, you might want to try a few flights with the 331.82 and see if that has eliminated your problems before moving to the 335.23.

That is among the messages and errors I experienced with the Nvidia drivers later than 335.23. With the 337.50, 337.88 and the 340.23 drivers I was getting promising performance but also random CTD's and BSOD's. Since reverting to 335.23 the issues have ceased. That may be something worth trying.

What Driver are you using. I had problems with CTD's and BSOD's on anything later than 335.23. Since rolling back to 335.23 all seems stable now. Might be worth a try anyway.

Tried it in FSX and performance seemed good but I kept getting CTD's and BSOD's. Have uninstalled and reverted all the way back to 335.23 for now and all seems very stable once again. For now I will probably wait for next release before trying again.

It might help if you add the "DisablePreLoad" tweek in the fsx.cfg under the MAIN section. Like this: [MAIN] DisablePreLoad=1 That should keep the scenery in your default flight from loading.

I don't have the TBM and don't really know anything about the problem but thought you might find some helpful ideas in this recent thread: http://forum.avsim.net/topic/441623-missing-plane-textures/ Good Luck with resolving this!! Jesse

That effect only works on doors and other openings that have been coded by the aircraft model as door openings. There are very few aircraft that have the windows coded that way. But, any doors should work fine I have never found any aircraft it doesn't work with and I have a ton (including many, many Carenado). In addition, each aircraft can have each of the effects adjusted specifically to that model through a simple menu. It really is one of the best bargains in the FSX payware world. Simple to install, simple to use and very effective. .

The additional $5.00 is for getting (as I recall) v.2 rather that the v1.x. Includes several enhancements. Check out their product descriptions and forum if you are unsure.

I've never seen any impact whatsoever. Never heard anyone else have any either. It's a great program and very inexpensive. Go get it!

To clear the Shader Cache just go to "User"/AppData/ Local/ Microsoft/FSX and remove the Shader folder. You may want to move it to a safe location in case you want to replace it later. When you start FSX next the folder will be rebuilt. I'm just thinking that the profile isn't properly applying one or more of those settings that I mentioned but then when you revert to the former driver it is once again properly recognized. It just sounds convincingly like what happens to me. Once I get that one or two settings replaced, all is well. Just next time you try; it might be worth your time to write down all of your settings (or do like I do and keep a screenshot of the settings) so you can check them. Once again, The Best of Luck to You!! Jesse

I don't think it's any problem to calibrate a "TV" monitor. A good quality TV seller will have done a calibration before you purchased, unfortunately, most retailers don't ever bother. Just keep in mind that the changes you make will be applied across the board and will effect the appearance of your other uses of the monitor(Watching TV?). I am not familiar with the PMDG settings and I don't think I have access to them since I am not a member of their forum. To clear the Shader Cache just go to "User"/AppData/ Local/ Microsoft/FSX and remove the Shader folder. You may want to move it to a safe location in case you want to replace it later. When you start FSX next the folder will be rebuilt. Hope this will help to resolve your issues. Good Luck!! Jesse

I'm using Windows 7 and 337.50 works beautifully for me. In fact I have never had trouble implementing SGSS on any of the Drivers. There must be something else going wrong. Sorry I'm not thinking of anything at the moment though. I do know there is one of the settings that always jumps up to bite me when I update the drivers. It may be "Nvidia Predefined FXAA Usage - Disallowed" or maybe "Antialiasing Behaviour Flags - None". Sorry I can't remember for sure which, but you may want to check all of your settings before trying again and see if it may be one of these more obscure settings that isn't carrying over. Like I said it always gets me. Are you using DX9 or DX10? Cleared the shader cache? Checked the fsx.cfg Display.Device entries? Hope you can get this puzzle solved. I think the later drivers and particularly the 337.50 Beta have made a big difference. Good Luck!!

My knowledge and understanding of this is limited but some of this may possibly be helpful to you. If it is too basic or simplistic I certainly apologize and if I make any errors hopefully someone more knowledgeable will chime in to add corrections. From my understanding, Inspector is not altering your simulator per se. It is a utility that applies your chosen settings to the graphics card whenever the selected program is running; in this case FSX. It has some settings and options that Nvidia Control Panel does not have available and it is generally more efficient at applying these settings. I think when you first installed and ran Nvidia Inspector, it reset the Nvidia Control Panel settings. This probably also reset your Display Color Settings which will need to be set. Before proceeding though, I would suggest that for best results this may be an excellent opportunity to recalibrate your monitor. There are a number of methods and utilities for accomplishing this but for this purpose I have found the windows utility quite adequate. To do this right click on the Desktop and select "Screen Resolution". Go to the "Advanced Settings" tab and select "Color Management" and again the "Advanced" tab and select "Calibrate Display". From there simply follow the instructions. After you have calibrated your monitor you can now open FSX and open Nvidia Control Panel to make your final adjustments. To do this, once again right click on the desktop and this time select "Nvidia Control Panel". In the Control Panel you only want to make adjustments in the "Display/Adjust Desktop Color Settings" section. Under "2. Choose How Color is Set", bullet in "Use Nvidia Settings". From here you can adjust Brightness, Contrast and Gamma settings for each Color Channel as well as adjusting Digital Vibrance and Hue. I hope this helps. It has really made a big difference in the appearance of my simulator. If you need additional help or clarification it may be helpful if you would verify whether you are using FSX in DX9 or DX10 mode, and include whatever Nvidia Inspector settings you are using as well as any changes you have made to the fsx.cfg. P.S. Don't forget to clear your shader cache as well.