Cameron

You are incorrect. The behavior you see in the simulator is accurate. You asked about the camera on the nose. It was discussed for that reason.

@oxff Your latest post has been pared down to remove the nonsense you were asked to discontinue. While you want to attempt to school others on your knowledge and flex or look down on them, you're clearly missing the point being made in this topic. System V is irrelevant to the core fact the aircraft has been compiled and tested in Ubuntu 18.04 LTS, and successfully shipped to other users on that platform. While it may be giving an issue in 1.0.3 as shipped to you, it does not dismiss the fact other versions up and to this point worked, including that of the build internally tested for 1.0.3. Coop already stated to you he would investigate where wires got crossed to ship that wrongly compiled System V binary in 1.0.3. Your mere suggestions that the team was not doing their part to address any issue is what started this debacle in the first place. This is your one and only warning, because I've frankly had enough after seeing the arrogance in your last message I just removed 95% of. Knock it off or get suspended. No more. Thank you.

Hi @JJM, I'm not really sure what you mean? When I go to the liveries section I see thumbnails for every download: https://forums.x-pilot.com/files/category/17-liveries/

Also see here: https://hotstart.net/cl650/pins.html

I am not putting words into your mouth. You are putting words into ours. You literally said, "The fix for these errors were supposed to be in 1.0.2, then in 1.0.2b, and now we're at 1.0.3 with the same issue." That literally implies we took no action to this point, which is incorrect. You are the first person to report this since the release of 1.03. This is just really lame. I'm sorry, but it is. It's been supported since the day of release. The release was tested with Ubuntu 18.04 LTS, and it works out of the box with such. You are clearly not running that, but that doesn't mean we don't support Linux. That's also putting words in our mouth. I really, honestly, do not care to compare to another industry in any form. We are talking about a niche in a niche in a niche here. X-Plane itself is a small industry, then you have Linux, which is less than 2% of X-Plane users, and then you finally have you, a Linux user using a build of Linux other than the most popular variant available for which the product was compiled and tested on. Linux excels at servers. I don't dispute that in any form. We don't need to continue this longwinded drama, so please don't do so. @Coop will update here appropriately. Thank you for your patience.

No. FLIR is thermal based. This is quite a bit different.

If you look through the release notes, the following is present in 1.0.3: Disable obstacle database on Linux builds to prevent library loading issues To assert that the team just dismissed or could care less is incorrect, and I suggest you take a different tone here. I find Linux a sticky issue as it is. There are so many flavors of it, that it's almost at your own risk without using Ubuntu 18.04 LTS. The argument I commonly get amongst Linux users when we don't support the platform for products is that they understand there are inherent risks due to the many flavors and libraries. Then, when we bring back the opportunity to use our software on Linux, stuff like this happens and it creates a compounding headache all over again. Give @Coop the opportunity to help you best he can before throwing accusations around of not doing anything about this stuff. He means well. Thank you.

I am sorry you find it misleading. As RealSimGear is the developer of the product that also makes the hardware, it makes sense to me. I don't know about limitations. All I know is they create software on the other side for their hardware that allows for placement saving. From what I recall, X-Plane itself does not have a default behavior to save third party plugin panel positions, and will reset them in this manner.

As far as I'm aware, there's nothing in the SDK to allow us to prompt returning back to X-Plane's main menu.

This is not possible unless you own RealSimGear hardware. If you don't (which it sounds like you don't), you will need to drag across for each sim session.

As has been stated, what you are showing from Aerobask is NOT EVS. That is SVS. We have that in the 650, and it's also in the TBM 900. EVS is the topic here, and it's not possible to implement properly in XP 11.

The hope is to eventually bring it in with XP 12 if it allows, but we don't know if that's possible yet. As the EVS could be retrofitted after delivery, it wouldn't shock me if they shipped it on the panel, but I don't actually know if they do. I just know that we originally intended for it and couldn't make it work with X-Plane 11, so the controls were modeled. @Goran_M will know more about that.

Hi there, This error is a result of you not running the latest version of the Challenger 650. You'll need to download and update the product from your account.

Hi @Paul_P28A, It's almost definitely this: https://support.torquesim.com/hc/en-us/articles/360057635513-Steps-to-resolve-plugins-not-loading-Error-Code-126-

There are intentions for this, but as to when is unknown for the moment. We have been in contact with the team though.

On the first page of this topic

Please attach your log.txt file in your X-Plane folder after opening the M20 in sim.

https://discord.gg/J56w9t2g

It was not forgotten. That is an optional add-on, and is not on all 650's from the factory. A google image search of the 650 will probably show you right away that most any 650 does not have this. The camera is infrared for the EVS (Enhanced Vision System), and It provides images of the approach, runway lighting, and of terrain scenery that's viewed on the pilot's HUD and on the co-pilot's multi-function display. It was considered for the add-on, but determined not something that could be implemented due to limitations in X-Plane.

Can run at 30Hz, yes. But the actual MONITOR max refresh rate being 30Hz? Rare as can be in the X-Plane user world, or really even in general. Most monitors are at least 60Hz.

As I remember, I had originally told you about V-Sync being a likely culprit. Gotta be honest, you're the first person I've met with a 30Hz monitor. I think you're going to find yourself in a pretty slim group.

X-Plane does not draw the avionics in full screen mode, and so the simulation pauses. You must be in a 3D mode view. You cannot do what you're trying to do here. You can use the 'w' key to look ahead, and then adjust the height of the camera up or down to only show the bottom glare shield.