KalahariRover

It's been pretty inconsistent for me. I've had very manageable taxi speed and on other flights it has been really fast.I almost hate to say this because it is such a generic response, but did you load the default C172 and then switch planes? I do that now by habit and haven't seen the galloping gazelle taxi behavior lately.Secondly, one thing that causes absolute rocket behavior sometimes is if you put the condition lever too far forward. I've seen this also in the default Caravan and the Aerosoft Twotter. Must be how FSX models turboprops. I creep that thing forward on start to get the engine to catch, and only advance it to full right before take off.In the default Caravan I've had the engine actually overpower the parking brake at idle if I started the engine with the condition lever too far forward.

I have both planes. The difference is in the amount of reverse thrust. I'm not at my FSX PC, but as I recall the Carenado Caravan is set to produce 15% reverse thrust and the Aerosoft Twotter 25%. You can check by looking at the mouseover text tag for the throttle when it is in full reverse.The 15% setting isn't enough to get the plane to roll backwards.There are some folks on here who fly Caravans for real and can comment on whether or not the reverse is just for shortening the landing or the Caravan can actually back up.

I can't speak for the default GNS 430; I swapped it immediately for the Reality XP version.That being said, in a real GNS 430 the 2nd "page" in the NAV "chapter" is the map; and it is selectable in the menu system as to whether track is up or North is up. It also has the option to have your DTK up. (These options are in the SETUP MAP accessed by pushing the MENU button while on the map page).The terrain map, however, only allows track up; as I recall it even shows "TRK" at the top of the terrain map to make sure you understand the orientation.Garmin has a full pilot's manual for the GNS 430 on their site. I used it as my training guide while learning how to operate the Reality XP. Since the RXP is based on the Garmin Trainer, the manual is a big helpAnyway, in the Carenado GNS 430 you might try going to the map page, then pushing MENU and then selecting SETUP MAP and look for an entry in the list called ORIENTATION. North should be an option if it is modeled.

Well, all the doors are working again for me - I have Acceleration. It is entirely possible I was next to a fuel station as I usually end my flights that way. I didn't know that was a recurring issue with FSX, thanks.

Recognizing this is a Speed and Temp issues thread, should there be a separate central thread where we aggregate up all the little things that need fixing?For example, I notice that the OBS knob text tag incorrectly reads the course setting from the HSI, rather than the actual OBS setting. All software releases with dozens of these small things, but over time they get fixed, assuming we let the developer team know about them.Another oddity - the sound seemed a bit anemic to me, so I peeked into the sound config file, and the prop sound sections reference sound files that don't actually exist in the sound folder.Also, many have noted that the Prop RPM gauge is off by 50 RPM.So where should we tally these up? I don't want it to seem like bashing, it isn't, small fixes are part of the standard development life cycle.

Here's what I did. This was my first installation ever, but it is working just fine for me. This was to replace the default GNS 430 with the GNS 430 from Reality XP. Anything more complicated you'll need professional help, which for sure ain't me.BTW, as always, make a backup of the original panel.cfg and save it under a different name, so you can go back if you get in trouble.1. Run the GNS WAAS Config X.exe utility (located in the Reality XP program folder) and select the Carenado C208B panel in the resulting menu.2. Select "Configure Aircraft" on the lower right.3. Check the box for "GNS Unit" and the radio button for GNS 430.4. Click "Apply" and "OK" then close out the list of aircraft panels which exits the configurator.5. Open Notepad and then open panel.cfg in the Program Files (x86)/Microsoft Games/FSX/SimObjects/Airplanes/Carenado 208. (If you don't see it make sure "All Files" is selected and not "Text Files")6. Verify that at the very top of the Panel.cfg file it says "Window05 - Reality XP GNS 430 WAAS" etc. - that means the config utility you ran earlier worked.7. Now, in two places in this file you will see something like "gauge00=Carenado430!GNS430_nc1" or something very much like that. You will replace this text with "rxpGNS!GNS430".8. The first place to do so is in the section called [Window00]. The final text for that line, after you make the replacement: gauge00=rxpGNS!GNS430, 0,0,500,2669. Repeat for section [Vcockpit03], with final text for the line: gauge05=rxpGNS!GNS430, 2,161,282,150Note you don't have to monkey with those numbers at the end, just leave them as they were.10. Save the file (using the same name of panel.cfg) and you're ready to go. 11. When you enter the sim and load the plane, hit Shift-3 and deselect "3D Knobs". Otherwise the old panel knobs poke out and look funny. You have to do this everytime you fly, unless one of the resident geniuses on here knows how to permanently disable them.All this looks pretty complicated when shown stepwise as it is above, but honestly it is just two quick replaces and you're done. Caveat: I am a complete rookie at this. But this did work perfectly for me.

Yes, thanks. I used notepad, opened the existing panel file, and then in the two places I saw "Carenado GNS xxx" I replaced that text with the Reality XP equivalent, which I found in the documentation. SInce the gauges are the same size it just dropped right in.

In my case it is very inconsistent. The doors used to work; now whenever I open a door, whether through the tool or just by clicking on the pilot door handle itself, it opens but then instantly shuts of its own accord. I have Acceleration.

Ah, I got it. Instructions that come with the package are pretty light. A product by experts for experts, I gather.

This really is a newbie question, but what the heck. I have purchased the GNS430 from Reality XP. How do I get it into the VC panel? I can currently only see it as a 2D pop down. Thanks!

I've been following the speed and temp tweaks discussion here on this forum and as Fede puts the file tweaks out, I've been incorporating. Didn't mean to imply someone has released a formal new FDE or a patch. I can't land for beans in FSX if I don't get a feel for a new airplane in slow flight, that's why I asked about the behavior. She'll do a very steady 80 KIAS at -500 fpm at around 500 torque, but it is really close to the point where she noses down hard. In the same full flap configuration and the same 80 KIAS it takes 850 torque to hold her in level flight. I usually come in at 85 knots to get some margin; that's where the 550 torque comes from. Too easy to overshoot on the power reduction otherwise; and anything below 500 torque and the nose drops rapidly and with some loss of control.

FYI, in the modified FDE 550 torque results in a 500fpm descent at 85 KIAS with full flaps. Close enough?

Thanks very much for this. I've never sat in a Caravan much less flown one so I really appreciate the real world insight. Makes it much more interesting to try to fly the airplane the right way.

Thanks a bunch for doing this. I really appreciate everyone's hard work here.

One other speed issue I've noticed was during slow flight.With full flaps, the airplane runs out of trim at 68 KIAS (with default full fuel and passengers/cargo, 2500 feet MSL).In other words, when the autopilot altitude hold is engaged and I reduce power to lower speed, once I've lowered power to the point where I see 68 KIAS the autopilot has advanced the trim wheel fully forward (19.5 deg) and any further reduction in power means the airplane will lose altitude.Makes the last moments in IFR approaches difficult and seems wrong. The stock Caravan certainly doesn't have this behavior - the autopilot can hold altitude at much lower speeds before it runs out of trim.I don't believe that has anything to do with engine power. I suspect drag, but more testing will be required. For example, it could be all the gauge calibrations are way off, or she flies like she's 2,000 pounds too heavy. Could be a lot of things.You all may want to fool around with some slow flight to check the airplane's behavior at that stage of flight. It sure doesn't feel right, but I'm not a pilot, so I'm just basing this on the way other FSX aircraft perform.