All Activity

View File N131KJ Hot Start Challenger 650 This is a livery for the Hot Start Challenger 650. To install, extract the zip file into the "liveries" folder. You can supply your own registration, N131KJ is not printed on the cowlings. If you enjoy my work, consider supporting me on Patreon to cover some of the horrendous Adobe-costs ;). You can find 8K versions of the liveries there. Submitter pilotdeviation Submitted 09/18/2025 Category Hot Start Challenger 650  

I do my best with computer issues. I know more than I used to know, but that isn't saying much. I recently got a new desktop to fly X-Plane. I tried to copy the CL650 from my old NVMe. Of course that didn't work, it left out plugins. So I went to the X site, found my purchases and it showed unlimited downloads. I downloaded the installer, and it wanted my email. I put that in and selected "Next". Then I got an error message that said I hadn't included a "value". Huh? The only thing there to fill in was the e-mail. There was nothing about any "value". So I am stuck. What did I leave out and how can I fix it? What value are they talking about?

Can you screenshot that- I’m not finding “DCA Fail” in the QRH.

The manual is correct. Track error referring to the track, not just the final. So when I’m “right downwind” just past the landing zone with a visual approach loaded, I’m not on a track at that moment. When I select Direct RX(runway number), then Nav, then VNAV, then dial the altitude selector to zero, my newly defined track is from my point to the RX fix- without error, so the airplane turns right and the Vnav snowflake appears. At this point, if I’m above the snowflake, I can select VS (appears as VVS on the scoreboard) and command down (pitch works too), and this is the beautiful thing with PL21- you can “dive to intercept a vnav profile”.

OY-CVW Airfoillabs KingAir 350 1.0.0 View File This is a livery for the Airfoillabs KingAir 350. To install, extract the zip file into the "liveries" folder. If you enjoy my work, consider supporting me on Patreon to cover some of the horrendous Adobe-costs ;). You can find 8K versions of most of the liveries there. Submitter pilotdeviation Submitted 09/17/2025 Category General Aviation  

Early in the Morning at UHPP.

I hear what you are saying- I’m quite familiar with these. I have one persistent scenario saved- in holding at SKOTT intersection near KGPI, 13,000’ (200knots, 0*c). If I launch this state regularly it will open with everything working. If I open it after a few weeks, then it’s likely to be unstable. This instability manifests itself as the aforementioned Temp probe yellow dashes (and I’ve tried QRH 2 guidance, turning switches off for a time, ect), sometimes all 4 screens are black (but work when they are popped out), or more recently I noticed the oscillating pitch that was previously mentioned. I am certainly not upset, just trying to share user observations for your information. This is why my go-to is always start in the non persistent state. This is much more realistic from a pilots point of view, reinforces checklist discipline and to my knowledge I have never experienced glitches when starting this way. If you like, I’m happy to share more info the next time I see something weird.?

I can assure the only reason this shows is because the probes are still hot. Possibly because from the last flight you're restoring, they were already overheated and the simulation doesn't cool them off between reloads of the saved state. So if they were very hot before, you reload the flight, they'll still be hot (all of this gets saved into the state file). If you switch off the probe heats and wait about 5-10 minutes, they will come back, rest assured. It just takes them some time to cool off. Testing, the TAT probe hit about 114°C with no wind to cool it off (~386.5 Kelvin in the dataref display there). From there, switching the probes off, it took around 7 minutes to cool off below 60°C, when the indications on the PFD returned.

Thank you for the test case here. I've been able to identify the source of the problem. (It has relatively little to do with SEC FPLN, but that's besides the point.) Before I commit to a fix, I need to map out some of the real avionics behaviors some more, which you might be able to help me with: When exactly does the VPATH intercept happen? Can it happen while you are flying the base leg, or do you have to be pretty well aligned with the final leg before it can capture? Reason I'm asking is that the FMS manual on page 18-21 seems to imply that VPATH will NOT be captured if track angle error exceeds 30°, which would obviously be the case on the base leg (see screenshot). So if you tell me that you can capture VPATH even on base, then we're dealing with yet another case of the manual lying (or missing important details) about what the avionics actually does.

Re: Yellow dashed out TAT indications. I am aware of all that as I fly this plane in real life. XP CL650 temps only yellow dashed out for me when I load a saved scenario. It could be one that starts on the ground or in flight. Right from the get go, they are dashed out and cannot be restored- even if the probe heats are in the off position on the ground. I’ve tried introducing failures and clearing them- all to no avail. This is why I prefer starting from a standalone cold dark airplane- never seem to have issues with that.

are there any sites that offer freeware sceneries of airstrips there? it would be nice to have these airstrips there in x-plane 12

Really? If any feature warranted deploying an update, this would be it.

thankyou. new pc trying to set up and forgot 50% of how to do it.

The nosewheel steering system needs the wheel to actually be centered or nearly so for the actuators to engage. If I had to guess (since guessing is all I can do), your nosewheel was turned one direction or the other, preventing the system from clicking into place. If you taxied forward a bit, or got a tow from a tug, it should have straightened out which would allow it to engage.

I have noticed this too. As mentioned in a previous post- saved scenarios (in-flight) often breed weird behavior like this. Especially if it’s been a few days since you launched the scenario. Oft problems like this include: FMS loses all Perf Init and Flight Plans PFDs and MFDs all black (but you can pop them out and this work fine) TAT on PFDs is dashed out yellow Oscillations in pitch that an dynamically unstable- often unrecoverable. All VNAV becomes unusable. I use three machines/ three copies of XP12 and CL650: I7 9700K, 4070 Ti Super homebuilt ASUS I9/ 4070 Super gaming laptop MacBook Pro M4 On a positive note- starting from cold dark airplane seems to always work fine. This is exactly like the real airplane, so I’m not bothered by it.

Thank you, Coop! I'm a big fan of TorqueSim aircraft models.

OK this came clear don't know how but its working

Can you elaborate? In what way is it "stupid?" It should be exactly where you left it. You can also always just save a cold & dark state and reload it every time you want a clean jet set up the way you want it. That's cause you turned on the probe heats while on the ground with no airflow over the (non-aspirated) TAT probe housing. The TAT probe goes "--" once the temperature it reads hits about 70°C. This is behavior reproduced from the real jet. This is also why Bombardier tell you not to rely on the temperature indications on the PFD for PERF INIT and use ATIS or METAR data instead.

the nose wheel inop shows with the switch on if steering switch is off inop warrening goes away but still no controll of the tiller.

Open these files and change GLOBAL_specular to 0.5 file is located at X-Plane 12\Aircraft\X-Aviation\RSG DA40NG\objects

how do i correct DCA fail

Re: Altimeter- the sim tends to get a bit stupid after a few visits in persistent mode- I prefer to sets cold dark each time to avoid that. On a positive note, I’m real good at tweaking all my prefs though- lol. *also- lots of times in persistent mode, the temperature indicators in the PFD are yellow dashed out…

Thanks for quick reply. I’ve done it in the real airplane at KAFW (34R) and KGPI (20). KGPI, setup ILS 02, SKOTT transition. Keep it in Nav/Vnav until a few miles from HOTRU. Sec flight plan: Setup Visual to runway 02, modify it to give a 3 mile final. Put PLAN screen on MFD 2 and leave FMS 2 displaying Sec flight plan. (You should see the Activate button on lower right corner. Do not activate it yet. Fixes are RX02 (twice) and RW02. Now you are looking at ILS02 on MFD/ FMS 1, and the Visual to 20 on MFD/FMS 2. Approaching HOTRU, select APPR to arm the approach and set 4500’. Airplane switches to green needles and starts down on the ILS. You should be gear down, flaps 30, 150knots. Once decent is established, switch to HDG/ VS and switch NAV source to magenta/ long range nav. Airplane will capture 4500’ (pattern altitude on a clear day). Turn HDG left about 20 degrees and head toward downwind. On FMS 2, Activate the Visual approach/ Sec flight plan. (For good SA, I have previously put a 3nm fix off of RW20- dashed blue circle). When almost abeam and about 2.5nm from RX20, select NAV, VNAV, Alt selector to Zero. Airplane turns to the fix and SHOULD display magenta VNAV reference with snowflake (in the sim, instead of making a Sec flight plan, if I replace the ILS with the visual, I get the reference/ snowflake, when swapping flight plans, I do not). If you are high, VS down to intercept the VPATH. She flies a picture perfect visual. So. Replacing the ILS when on the downwind works, but swapping flight plans provides no vertical reference, only lateral. Swapping the flight plans is preferred as it’s fewer button presses in the pattern plus the first flight plans (ILS 02) now becomes Sec so if you need that for the miss, you can simply activate it. I go to KGPI all the time and circle to 20 about half the time, this is really helpful. Gotta make it 3nm to keep you away from the rocks. Works left or right downwind.