No. That I know about, and have always used. @hobanagerik is saying you can continue to use Lock, but with the blue highlighting turned off.
I have likewise always used Legacy and I MIGHT consider using Lock if I could turn off the garish blue and yellow highlighting. But I have looked through the different settings again just now and I still cannot see anything that looks like it can do that.
Hoping I have overlooked/missed something?
Others have reported the same thing in this thread.
Yes, I also have the “doubled” landing lights.
Additionally, there seems to be a bug with the linternal lights, which seem to be coupled to the external NAV lights.
I wonder, who, if anyone at all, is testing these planes. All it would take is to load up the plane in night time, and turn on the lights.
On a postive side, the detail of the 3D modelling of the virtual cockpit, but also externally, the clarity of the textures, and the bump mapping, are second to none. Engine sounds as throaty as I would imagine it to do.
As for the loss of rudder authority on take off: I have noticed this during taxi and take off on several planes, not only the Carenado 210. This rather looks like a MSFS bug to me (SU3 beta) with the rudder and/or front wheel steering freezing.
Apart from that, this armchair pilot thinks, that it flies really well, + the turbo is simulated correctly too (looking at you, 207…).
P.S.: Is there a chance, that Carenado would consider to add the fantastic freeware KLN90B to the Avionics options?
Yes, I see that too.
Is there a POH available?
Google is your friend!
http://www.aeroelectric.com/Reference_Docs/Cessna/cessna-poh/Cessna_210_T210N-1982-POH_scanned.pdf
I’ve clearly remembered this wrong. I believe it was an addon for 2020 that required manipulating the contents of the “Interactions.xml” file. There used to be a mod on flightsim.to, but that file is no longer available.
https://flightsim.to/file/43157/blue-highlight-removal
I managed to find another copy of this addon, but suspect its from 2020 only. I’m not sure which bit was altered though to even attempt a 2024 version of it.
It’s either this section:
<HighlightNodeId>__NO_HIGHLIGHT__</HighlightNodeId>
Or this:
<Switch>
<Case Valid="NO_HIGHLIGHT_NODE_ID">
<!-- Skip the highlight for this MouseRect (can be used to prevent breaking material using a dynamic texture such as touch screens) -->
<HIGHLIGHT_NODE_ID>__NO_HIGHLIGHT__</HIGHLIGHT_NODE_ID>
</Case>
<Case NotEmpty="HIGHLIGHT_NODE_ID">
<!-- Skip the highlight for this MouseRect (can be used to prevent breaking material using a dynamic texture such as touch screens) -->
<HIGHLIGHT_NODE_ID>__NO_HIGHLIGHT__</HIGHLIGHT_NODE_ID>
</Case>
<Default>
<HIGHLIGHT_NODE_ID/>
</Default>
</Switch>
No idea what the 2024 equivalent would be but I would imagine it’s similar. Might also want to take any follow ups to this to another thread, and not this one.
I got exactly the same FPS in these two planes in SU2. 12700, 3060Ti, 64 GB, Quest 3 on Airlink with Virtual Desktop.
ok thanks, this plane is not for me then. I need my FPS and stock 208b is not so good optimized.
Hi,
When programming the cowl flaps to my HC Bravo using a switch to open and close them, I have noted that only on the C210 the cowl flaps move opposite from all other aircraft with cowl flaps. I.e. when putting the switch to the OPEN position the cowl flaps close and vice versa.
I think the cowl flaps are bugged - if you close them the CHT temps decrease whilst in reality they increase… have mentioned this above. The mechanism and the animation are wrong.
The engine sound in VR is far too directional. When you turn you head, the ear furthest from the engine can hardly hear the engine. This is off-putting and spoils the otherwise great experience. I hope a fix can be done!
Has anyone noticed the turn coordinator behaving strangely? The ball reacts unpredictably when you yaw. Sometimes it moves the wrong way, sometimes the right way, sometimes neither. The p-factor seems off too.
I flew this for the first time last night. I really wanted to like it, but there are too many distracting, glaring, critical issues.
Like most folks I noticed that the weathervaning effect is way overpowering. But it’s not consistently so and it doesn’t make sense to my pilot brain. Taxing off with a 7 knot left crosswind needed a lot of right rudder - my right foot was to the stop and I was still drifting, until all of a sudden I wasn’t. Okay, I thought, it’s trying to simulate increased efficacy of the rudder at higher airflow. But it really wasn’t - it just kind of “kicked in” all of a sudden. Then, I did a(n intentional) 180 on the runway and tried to take off the other way. Now I needed a boot full of left rudder to maintain centerline, even at high torque. Something is very wrong here. Like others, I suspect it’s a combination of the nose gear contact/friction and rudder efficacy.
Then, like @FarFutureFox pointed out, the inclinometer (ball) behavior is all wrong. It’s not predictably so, but in many cases, adding rudder toward (stepping on) the ball made it diverge - the ball went the opposite direction expected. Additionally, I noticed rudder trim did not produce expected behavior. Either way, that’s going to “kill” someone in IMC, or even those trying to remain coordinated at the left end of the V-G diagram. In the sim we don’t have a butt-o-meter to feel out whether we’re coordinated; we have to rely on the ball.
Other things I noticed:
- Pitot heat switch is always on. Click spot can toggle the parking brake, but not the switch.
- HSI has no calibration functionality - no free/slave remote switch, no ability to push the heading knob in to manually rotate the card to align to the mag compass (even though it’s marked as such)
- Question: why a redundant turn and slip indicator when we already have a turn coordinator?
- Stall horn audio fades when on the edge of stall. In my experience with piezo-electric stall horns, the horn is either on or off, it doesn’t fade. When tickling the edge of a stall, it can “flutter” where it’s rapidly oscillating between on and off, but it doesn’t fade. If it’s supposed to be a Reed-type warning (like you’d find in a 172), then the sound itself is wrong.
- Engine start sound is really loud, then the engine is really quiet.
- Stereo panning of the engine when I move my head is funky. Look extreme right and the sound disappears. Look extreme left and it’s still there. Almost as if both audio channels are panned to one side, or the “source” location is simply misplaced
- Checklist is all over the place - lots of things out of logical order, missing elements, etc
With all the flight model and system issues, the rest of the flight was just a quick checkout. I did a couple touch and go’s, slow flight, and stalls. I don’t have real-world experience in a 210, so the observations that follow are shared in hopes that folks with rw experience can provide insight as to whether this is normal behavior:
- Major wing drop in the power-off stalls, like pretty much an incipient spin. Again, hard to know if I was coordinated because of the weird rudder/inclinometer behavior. But trying hard to remain coordinated, I got it to drop both left and right in subsequent tries, never remained wings-level through the break. Don’t know if that much wing drop is accurate to reality.
- Landing - coming in on short final at 75 knots, 3° glidepath, fully configured, I had to be so nose high that I couldn’t see the runway. It was like landing a taildragger, using the Lindbergh reference. I even tried “sitting up” higher and still was crazy nose-high enough that I couldn’t see. I noticed really high deck angles during slow flight as well (which is how slow flight generally is) but don’t really know for sure how realistic this behavior is compared to reality. Might just need to experiment with eye height a little more. Coming in at 85 knots provided a much more reasonable point of view, but that’s awfully fast.
Bottom line, I really want to like this Carenado stuff - their aircraft are generally beautifully rendered and they are classic, ubiquitous aircraft that sit in a good market spot. But the QA is so hit and miss - and not in a way that makes me think “oh that’s annoying,” but in a way that makes them “dangerous” to fly, instilling all sorts of workarounds and bad habits just to hand fly what should be fairly simple aircraft. By comparison, the Dakota is a breeze to fly (yet suffers from more minor QA issues).
Ok I have some good things to say about this, and some bad things.
The good things:
This is actually a very nice aircraft by Carenado. Visuals are just superb, sound is very good in quality, not sure how realistic but it sounds great. Systems are there, you have a nice choice of avionics, things work. The aircraft is a joy to hand-fly and is probably the easiest aircraft to land I’ve ever encountered. Hope some T210 pilot can chime in and tell me it that is how it works irl because this plane lands like a feather.
I didn’t find any weathervaning problems in my flights, rudder authority is quite good and always enough to compensate for crosswinds.
Probably one of the nicest aircraft by Carenado and certainly something that can be enjoyed for GA flights. It looks really beautiful.
Now a negative rant:
If Carenado is capable of doing this, then they are intentionally botching the commissioned work they get for MSFS, the Dakota for example could have a tablet or a choice of avionics but it doesn’t. I hope this trend of making the payware aircraft good and the commissioned aircraft a toned down version does not continue, because once we get the toned down version we are never going to get the aircraft as it could be and that is a real shame. Maybe Microsoft has something to review here about how this works.
It almost seems like it is designed this way. MS/Asobo get their stock aircraft for a good development price and 3rd party guys are ensured folk drift to their websites to buy because almost nothing in the base sim is study level or completely functional.
That aside, I also had a good flight in this plane but did not test the intricacies as well as CharlieFox00
It could very easily be the case that Carenado is doing exactly what they’ve been commissioned for and no less. When you buy a car yourself, you want it to have certain bells and whistles. When your company buys a car as a fleet vehicle? Maybe you get power windows
You described the issues much better than I could. I’ve reported the coordination and sound issues to Carenado support, but the more people who inform them the better. This aircraft has so much potential, but is seriously let down by some critical flaws.