Rastuasi

Still doing tests, but it looks like it's tied to the state of Colorado. I can load in to other states, but KDEN, KCOS, KTEX, and a few on the west side all get door jams. However, KLWC, KGLD, 46CA (california), KBFI, and so on are all okay. Tried with a stock plugin folder and I do not have any scenery for Colorado outside ortho4xp. Uploaded more logs CL650_Logs_No Plugins.zip

I was testing having 1 airframe for FSE, 1 airframe for non-FSE but persistent location, then 1 airframe for freedom of location, but persistent with the airframe. Steps To Reproduce: Create an airframe in career mode. Fly that airframe somewhere. Close simulator and reopen (simulate a second date of flight). Upon loading into the sim, choose a different airport. Start flight and get into the Hotstart menu, I clicked on career mode Selected the same airframe and unchecked "Restore Previous Position". Clicked Enter FBO and loaded in. All was well.. it will load the new location but not all is well, at least when I went to the plane. I went to the plane, clicked on the door handle to pop open the square and nothing but the sound happened. Clicked it a few more times, nothing. I hit Shift + 4 which took me inside the plane, stood up and walked to the door. I could pull on the small handle in the center, but the big handle on the side was not working. Video Showing the Issue: Apologies for the fan in background, new headset and hadn't realized it was doing that. CL650_Logs.zip

Better yet, call out the AC cart, plug it in and activate ground power while APU is on, then when you shut down apu, there's still power and FO finishes his reading. I then hand signal to remove the cart and everything shuts off.

Oooh okay, so I was not going completely insane trying all these datarefs I'm seeing as output, good to know. Okay, well display wise, I can work around that, the commands then are what I will want to figure out so that I can set the alt, hdg, vs, speed, etc. Easier than finding the mouse and setting those in the sim.

Nothing appears to be forcing it off and I do not have the saitek multipanel, so there is no battery switch for me to have to disable on that. I use the Saitek AP and Radio panels with a Saitek X55 Hotas. The only way I have gotten the AP and Radio panels to light up is to assign a battery_master to one of the toggles on the X55. The radios, lit or not, will actually manipulate the radios. So they are connecting there just fine. However, the AP panel will light up and show 00000 FT, but when I go to rotate the alt, it just zeros back out. When I set the ALT inside the plane, using the dash, it does not adjust the AP panel's number. Edit: Yes the datareftool is how I have been trying to figure this out.

I can get it turned on if I map a battery master switch, but not if I use the internal battery switch on the center top panel in the plane. So it's not a USB power issue as they're on their own power supply. They also work on every other plane, so it's just a matter of figuring out the datarefs. Also the autopilot panel doesn't adjust altitude and light up neither. However, I'm still working on the radio panel, so haven't gotten to looking into those datarefs yet.

Was on the following flight plan: KJST JENER4.JENER KOZAR.FOREY2 KARB Due to the star dropping me off at SWETY, I added a waypoint between SWETY and YACNU (start of the RNAV 06). The point I was adding was BROZZ, would've given me enough space to do a wide turn into the approach. Log.txt CL650_Log.txt

Thank you, I recalled having this done on my first flight, but for some reason, forgot that I did since then and so just had to manually confirm the checklist. Now I know what I had forgotten.

Sweet deal, okay, so I shall have to plan a flight for this evening.. would do it now, but work is a thing.

Interesting, thanks @JC_YYZ I shall have to test that on my next flight. I know my other planes will not do that, you have to either set VS or FLC to get them to start, so that TOD beep is purely informational. However, it should be noted, they also don't start immediately if VNAV is on, they wait for the VNAV lock to kick in (pink circle that comes down from side)

By stating "all simulators", the indication is thusly, all versions of that simulator. Do not say "all" unless "all" is truly verifiable. Also, as the subject of this thread is specifically for XSaitekPanels and not SPAD, I'm sure your suggestion about SPAD is truly an agenda to derail the thread and breaks forum rules.

Point remains, SPAD will never work on anything but Windows, so you cannot accurately state "all simulators and systems". You're the one with the agenda, so get out unless you're willing to help with the dataref mapping on the CL650's panel and why that is not recognized.

As a side note, I did try to set up the descent early, but the moment I set VNAV, FLC, and alt, she starts descending. I'm not sure how or if it is allowed, one can set up the descent and let the system start it at the actual TOD.

It does not work and will not work as that developer refuses to be OS agnostic. So think again before spouting off that it works for everyone. Which regardless, doesn't change what that dev did in the codebase, which I have looked through and it's making dangerous system calls. Also, looking on the Xplane forums I see countless people saying SPAD is failing, causing sim crashes or other bugs and that Xsaitekpanels just worked for them.

My issue is I cannot get it to see the cl650 battery switch, it sees battery master if I assign that to a joystick, but it will not see the value of that panel switch.

I won't touch SPAD with a 2000 mile pole, mostly cause it won't work, but also because it's a system risk if you look at the underlying code base.

@Pils I downloaded your saitek ini and powered on the plane, but the radio panel and AP panel still refuse to turn on. I already looked and you set it to just battery power on, so not sure what's up. I did confirm, the log.txt shows it being found and picked up.

0:03:37.622 E/FMOD: /jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. Getting the same

When I hear the gong for TOD, usually 1 minute out, I simply activate VNAV, FLC, and set the Altitude to the base of the descent (where the approach alt starts). Once you do that, then if ATS is on and profile is setup for approach, it will throttle back to M.72 (default) and start the descent.

Did you actually enter and exc the approach in the FMS? I had that show up last night, I merely went back in to the DEP/ARR page and redid it and it magically worked. Also, you do not want to really be hitting that APPR button till you're on the last bit right before the approach starts.

That save function saved me when I took off and realized I forgot to start FSE. Hit that button and was back entering runway.

I wouldn't say it's a risk, but a boot in tush that I'd see as "go get that upgrade".

I will check that next time. I believe it was listed there and it was act but not sure why it wouldn't recapture it.

Climbing up, got near 38000, aiming for 39000 when suddenly ATS goes black. I then tried hitting both ATS disconnect buttons behind throttles, re-engaging the ATS on front and it never lights back up. SAT is -65 C, so it is not hitting the -70 C bug another person mentioned. Failures menu does not show anything.

FYI, there is a sticky on this. The dev reasoning is that the pilot would not defuel, only people that would are maintenance and only for maintenance reasons.