No problems here with rudder control except when it's iced up!

Has anyone with the most recent patch been able to use the rotary dial in altitude hold on the autopilot to change altitude on the PFD? I just completed a flight from KAEG to KPHX and the only way I was able to definitively change the altitude during autopilot was via the VS hold rotary.

 

-Damien

There has been some reports of losing click spots. F1 trying to get as much info as they can on it. I seen it once  from a seemingly loss of focus.

How is everyone liking the King Air so far? 

 

I got it a week ago, and I love it! Fabulous plane, in all aspects really - after I got the landing procedure memorized and set the landing flaps at a low enough speed so that I didn't get ballooned up into the flight levels again :-) The G1000 implementation rocks, and I have to say - the idea to have the keypad as an Android app is brilliant! That's what makes the G1000 finally usable in a Sim, for me at least.

 

In fairness though, I had to fiddle around with my FSX settings because the Flight1 G1000 gauge caused me to overrun the FSX memory limits after 20 minutes or so of flight - both in the B200 and the T182T. Also, it's taking a toll on the framerates, most noticeable when panning around quickly with TrackIR. Having said that, I'm simply back at LOD=4.5 now, Autogen maxed or one below max depending on the area I'm flying in, so it's not all that bad really

Yeah you really got to be at LOD 4.5 with the KA if flying into any other payware scenery.

 

The best thing to do is create custom cfg with the settings you want. I've got LOD 4.5 / 5.5 / 6.5 all with different autogen scenery settings so I can set my sim accordingly.

 

Anytime it's Orbx I have to go 4.5. With UTX/GEX and payware planes I can do 5.5 and with stock planes I'll go 6.5.

Hello all,

 

I asked this question in the Flight 1 forum, but thought I'd take a shot and see if anyone else had this and fixed it.

 

When I start a flight, the sim is freezing for a couple seconds, every couple seconds. There is a long lag when pushing any buttons on the yoke, throttle quad.  If I turn the battery switch off, it goes away and all is normal.  But I switch the battery back on, and the freezing returns.  This is only inside the cockpit, the spot view doesn't have this issue.  I tried a fresh install of the plane and it still happens.  Someone mentioned over-zooming can cause it, but I am at .60 in the virtual cockpit.  I am in DX10 mode.  Not sure what changed as I didn't always have this.  I'm thinking I changed a setting somewhere, but don't know what. ??

 

Thanks,

 

Don

I suspect DX 10 is your problem. I think in another post they addressed that issue saying the aircraft isn't made for DX 10.

There's nothing wrong with DX10 and the King. It works like a champ. Been flying it for weeks.

 

I do recommend anyone running FSX under DX10 to purchase the DX10 Fixer app.

 

 

I'm thinking I changed a setting somewhere, but don't know what. ??

 

Hope your not suggesting we tell you what setting you changed?

Running DX10 (Steve's fixer) here with the B200, no problem.

Running DX10 (Steve's fixer) here with the B200, no problem.

+1

 

 

I am in DX10 mode. Not sure what changed as I didn't always have this. I'm thinking I changed a setting somewhere, but don't know what. ??

 

DX10 mode is exactly the same as DX9 mode except that you have higher quality graphics from your graphics card.  It's better technology.  The only issue you would have would be with some graphic anomalies that have been pretty much fixed by Steve's DX10 Fixer.  Your problem sounds like a memory problem, most likely caused by a tweak like Bufferpools or AffinityMask or another bad tweak setting.  Your system does not require any tweaks except that you might want to change LOD_Radius from the default 4.5 to 6.5 and the Texture_Max_Load setting from 1024 to 2048 (and no higher).  You can simply check this out by rebuilding your Fsx.cfg (save before you delete the config).  This will wipe out any bad tweaks and bring your settings back to the default.  Change your resolution but leave the sliders alone.  Now run the Duke and see if the problem still exists.  If that does not fix the problem then you have a bad overclock or bad memory configurations.  With a system like yours, I was able to overclock to 4.8GHz for a short period of time before I started seeing a lot of problems with FSX.  I lowered it to 4.4GHz and the problems went away.  More information about setting up FSX can be found in the AVSIM FSX Configuration Guide (see link in my signature).

 

Best regards,

Jim,

 

Thanks for the suggestion...I tried deleting the .cfg file and it did not help the issue.  I have flown this plane several times without issue, and this just started happening a couple days ago so maybe I am having a hardware problem.  I'll try flying some other more complex planes and see if I have problems.  Lately I've just been flying the Realair B60 v2 and Turbine Duke and they've worked perfectly.

 

I was not trying to imply it was a DX10 issue, I just mentioned that as often times people ask when trying to diagnose a problem.  I was hoping someone else had this same issue.  On the Flight1 forum, someone did complain of the exact same problem, but they said it was because they were zoomed too close in the VC, and that isn't my situation.

 

Thanks,

 

Don

Try to declutter the MFD by 1. In areas with lots of roads and obstacles it can cause stuttering. I had the same issue and just found a declutter by 1 resolved the situation.

Try to declutter the MFD by 1. In areas with lots of roads and obstacles it can cause stuttering. I had the same issue and just found a declutter by 1 resolved the situation.

Try to declutter the MFD by 1. In areas with lots of roads and obstacles it can cause stuttering. I had the same issue and just found a declutter by 1 resolved the situation.

I believe Sean says to declutter the MFD by 1 and there is an echo in here, in here, in here. :biggrin: