dlrk

I understand that the FMS generates real-time performance data in-flight. But how can I determine if an airport I'm planning a flight to can handle the Challenger without actually flying there and putting it in the FMS?

What is the functionality where RWY appears above the VSI and a path is drawn on the PFD SYN VIS? I'm guessing it's displaying 3-degree glide path?

Solved on discord, the OAT needs to be entered on the TEMP COMP page on page 2 of the index

No, look at the manual you posted "This message is cleared when the temperature compensation is turned off...or when a valid temperature for the airport is entered"

Disregard this post, I pulled the landing gear emergency extension instead of the parking brake

After starting up per the expanded normal checklist, I receive a NOSE DOOR OPEN warning

But I did enter a valid temperature

What does "CHECK APT OAT" mean on the FMS? I've entered the OAT in the takeoff and perf pages.

What is the procedure for a go-around?

Not sure if this is a bug or supposed to be a reflection

How should the FMS be set up for a traffic pattern training flight?

What does this system do? Can't seem to find an explanation of this

What value should be set for go-around N1 TGT? It looks like the TO value isn't displayed in flight, and and the checklists indicate this must be manually set.

I've tried Vulkan, I've tried lowering antialising, and texture quality. Seems like no matter what I do, when there are thick and/or overlapping clouds, I can't maintain even 30 FPS

I should add, this is without volumetric clouds

I'm still having some pretty significant FPS issues, despite a fairly strong system (8Gb RTX 2070, i9-10850K CPU). X-Plane continues to indicate that the CPU is the limiting factor, and looking at VRAM, there doesn't seem to be any correlation to VRAM usage (it'll drop below 20 FPS with less than 70% VRAM in use). This problem seems to worsen when pointing my view "upwards"

The X1000 does model track offsets, I've done it using this airplane.

I'm also having this issue (not as bad as in the OP though). When I disconnect the autopilot to correct, it winds up pitching up rapidly due to apparently being out of trim. With regard to the throttle setting, this does seem more likely to occur in the 2 minute phase of cruise where power is set at full

Perfect, that's exactly what i was looking for!

First, let me say this is one of, if not the best, add-on airplanes I've purchased. The detailed engine model is amazing, and a lot of fun to learn how to handle. That said, there are a couple features that I would really love to see added if possible in a future version: 1.Avionics integration with xPilot (the VATSIM client) for radio on/off status and transponder on/off/alt. The squawk code goes over fine now, though. Just the mode C and radios don't seem to be integrated. 2. A more full in-sim maintenance system, like that in the HotStart TBM or the various REP planes. Finally, there are some typos in the before start G1000 checklist where "power lever" is sometimes written as "power level". Thanks for a great model!

I went for the G1000 because with the Entegra the approach waypoints don't display right unless you use the RXP GPS, and the RXP GPS cannot be updated, and RXP has a history of abandoning their products

Thanks for that information, that helps. I was under the impression that VRAM is only limiting if it's all used, that clarifies. That said, I still think their may be some sort of issue with SMP, since it's resolved by reloading SMP graphics

I still get very low FPS that is relieved by forcing a graphics refresh from Skymaxx. I don't think it's related to VRAM usage, since it's not really correlated with VRAM usage. It's CPU thats the limiting factor, according to X Plane

Just to clarify though, wouldn't the GPU normally switch to RAM once running out of onboard VRAM, rather than CTD?

Okay. Perhaps I'll upgrade once the great GPU shortage has ended.