N330CT

Scratch that....DataRef Tool conflict was causing crash to desktop.

I do not. Currently I cannot load the 1.7 version in xplane 12 as it crashes to desktop. It was working fine a few weeks ago and now will not load. I suspect it was an xplane update that broke it.

I have spent a fair amount of time with this as every time I have to add oil I have to shut off the two side monitors to do so. I have played with multiple aspect ratios in xplane to try to fix it but changing aspect ratio of the monitors does not seem to have any effect even though it seems that the view is compressed in the horizontal. On my end the items affected are oil replenishment, checklist hints, hand signals, and cell phone. I also have some issues (depending on the position of my head with trackir) with click spots. I wonder if it is connected to this issue. At one point I was concerned that it had something to do with xcamera but after more tinkering I am unable to fix so..... I have every confidence that Pils and Toto can fix it. Waiting patiently.......I will just go do some flying in the meantime.

This is true. You need the graphics card to support this configuration because it does eat the frame rate. I just know after I set the offsets I was able to correct for the bezel easily and no more issues with a stretched view or not being able to click on the secondary monitors. Never hurts to try especially with a new graphics card on board....Good luck!

The way op describes their setup seems similar to setting up nvidia surround which I have always struggled with getting to work the way I wanted. It was suppose to be gentle on the frame hits but I found myself having to transition in and out of it because I hated how the desktop setup worked with it. I have had good success with what Pils describes using the built in monitor offsets in xplane. It works a lot better than a stretched view. Its worth a try.

This is a really interesting topic.......the ability to evaluate how safely/smoothly you got the plane from point a to point b. For me currently I know I can get to point b in one piece....but in the real world how well did I do it? It would be really cool to get a report of....you left your landing lights on (Toto) or you violated the altitude/speed restriction on your SID.

So looking at this again.....I think you set to/ga thrust during the "in range check list". What you are describing sounds like you are in the Go Around checklist not the before landing checklist. Pils is right....video or some screen shots may help here.

This. You are hitting TOGA instead of setting go around thrust. Go back to your performance page and select the top left selection of "TO" thrust. It will turn magenta (I think....damn maybe its green i can't remember) and it will be set.

Pretty sure I was getting that after an update and I had not checked to update the AIRAC cycle in the aircraft FMS. I was using a Simbrief flight plan saved under a much newer cycle then the aircraft. I had updated with Navigraph but had not cycled the nav data base in the FMS. As soon as I updated the database in the FMS the error cleared.

There is a bind file (.ini) floating around somewhere on this forum already I am pretty sure....https://forums.x-pilot.com/applications/core/interface/file/attachment.php?id=34623 .....this is what you are looking for. I used it as a base and the rest was just tune to your liking. CommandMapping.ini

Had this same occurrence yesterday. Restart fixed it, I didn't save a log.txt but can in the future if it happens again. Just wanted whoever needs to know to be aware it is not isolated.

If it is any help for some reason I had to re calibrate my rudder pedals and toe brakes after the update. I had the opposite problem, brakes were released but still showing activated on the calibration screen. Not sure why but a quick look at the calibration screen showed that something had changed and they need to be fixed. Quick re calibration and I was up and running.

Maybe it is a more complex issue to fix then we understand? Not really sure but its just a pain to disable monitors and then reset them just to get oil in the plane. I would really like to read all of the startup checks/sequence instructions also, someone spent a lot of time and effort building those menus. It seems like there would be more talk of this because since there are a lot of multi-monitor setups out there. Trying to be patient (they obviously did a TON of work when you look at the update list) but I really would like to see this moved up in priority. Maybe we are the only ones with this issue?

Frustrated to see now three updates later this still has not been addressed. While I would never claim to know what it takes to fix or program anything on this amazing plane it is hard to understand why “implementing GPS jamming simulation” is more important then customers with more then one monitor not being able to read the menus. I can’t even put oil in the plane without turning off my other monitors so the menus and click spots work. This was logged in January.

10-4. Thanks for that. I know you all are busy and the plane is amazing!

Does anyone know if this is still on the radar? It makes it impossible to fill the oil without switching off the other monitors.

It was x-camera. To be able to click on stuff outside the plane with xcamera enabled you have to uncheck "exterior camera" on the associated xcamera view.

Yep. And I have been up to date since then as well which has me stumped as to what changed on my end since I could click last week with x camera and then this week I can’t. It really sucks switching back and forth, I can’t stand walking around with keys. Guess I will just pull the covers and pins once and then never use them again. Sucks but better then jacking with changing x camera every flight.

I have been using x camera with walk mode disabled since release. I have had no problems placing and removing covers and now I can't. Why would they take this functionality away?

In an effort to help anyone else that has a similar issue..... I followed Pils directions and updated x plane scenery. Of note was that other planes in x-plane were still functioning and pulling nav data correctly. I had previously installed a runway enhancement package that replaced runway textures so when I have previously performed updates on x-plane I had told x-plane to not overwrite these files. That seems to be the source of the issue as I allowed overwrite on this go around and it immediately fixed the problem. What I still don't know is what broke it because it was working fine since the challenger release with the added runway textures. I was always getting a message that the scenery may have not loaded correctly but the nav data worked fine. That message is now gone and everything is back to working. Thanks for the help Pils!

Will do.

I have current AIRAC data loaded and the FMS gives me a "Bad Route Parse" upon trying to load a flightplan. I tried to just punch in a Departure and Arrival airport and it says they are not in the database. So far I have: Restarted, Reinstalled nav data, New airframe, and reinstalled the Challenger. No solution as of yet. Log.txt attached. Log.txt

Outstanding. I searched long and hard but that is not where I was looking. Really appreciate the help.

I have searched but am unable to figure out where to set the approach minimums to get a call out. Normally there is a field for DH/MDA but I am not finding it or it is called something else in the Challenger. I watched Toto's video and saw that it worked but I am missing where he punched it in at. Thanks in advance.

Yep that's it.