Goran_M

After some consideration, and after reading your post, I’ve decided to allow it. Feel free to edit your post and re-attach the file. But please add a disclaimer that we don’t officially support it for now. For more permanent changes, please get in touch with me so we can collaborate.

Please do not redistribute our cockpit object file, or any other files in the CL650. The obj files undergo constant changes through updates. Please, just post the self made vrconfig file, with instructions on how to implement it. I don't have any issues about vrconfig files being created, as long as there is a disclaimer stating that the file is not officially supported by X-Aviation, Hot Start or LES. If you want to modify the cockpit object file, please contact me directly, either though these forums or on discord, and I'm happy to work with you to help create one. If I have it in my blend file, I can export it with each update, so your one doesn't get overwritten. The very first update will have major changes to the cockpit object file.

The way we have the FBO modelled, and the transition into it, is by way of a "wall" surrounding the aircraft. If we expand it, then I'm afraid people would get completely lost and wonder when they would enter the FBO. There may be ways around that, and we could consider it, but it would have to wait until after a few urgent updates are prepared and shipped.

Very early to tell. Perhaps for the X-Plane 12 update, but no promises.

Can you remove ShadeX from your plugins menu and try again?

It's difficult to know what caused the crash, or how hard your landing was, without seeing a replay. I've seen streamers land it quite hard, and there was little to no damage. We have no control over the damage/crash limits of the add on. This is all handled by X-Plane itself. If you can provide accurate data, feel free to contact Laminar and they can perhaps look into it and include it in X-Plane 12.

This is a definite trait of the aircraft. Maybe reduce your curves slightly.

A PSD and a Substance Painter file will be made available.

ok, the video has graphical issues, but going by what you're saying, and regarding your click spot problem, yes, there is something we can do to isolate click spots further. I'll make a note of it and we'll put it in a soon to be released update. skiselkov will post back with a response to the EFIS problem.

I'm afraid not. It has been designed as a real world, wear and tear add on. But look on the bright side. Eventually, you'll get much better at your landings.

I understand it can become frustrating. Just rest assured we're here to help.

Order doesn't matter. Just start putting them back and see what happens after each test. I know it can be frustrating, but in the vast majority of cases, it's a plugin that doesn't play nice with the aircraft. And by all intents and purposes, the problem might go away after putting the plugins back. Good luck and please post back results.

The demo install is fine to install if you have another copy installed. There will be no issues. I have 3 installations of X-Plane on my PC. As for the TBM, you can install it as many times as you want on the same PC.

A little bit of a drastic move. Any chance you can download a clean install of X-Plane, then install the TBM and test. I've tried duplicating this, and so far, I've had no success. This is almost definitely something in your X-Plane install.

You're welcome.

Can you try completely removing those plugins and re-test? (All plugins remain loaded, even if they are disabled.) If that doesn't work, I'll investigate further with Saso.

Navigraph are preparing a Hot Start navdata file for the CL650, and this will also be used in the TBM once we get around to updating it. Due to the impending 650 release, the TBM will be updated soon after the 650.

I've never seen this problem in the TBM before. DO you have some kind of plugin that messes with viewpoints installed?

If you have SCEL scenery installed, this is a known issue. The problem has been addressed in these forums in the past and a solution has been posted.

https://discord.gg/qPVbuybS GPU specs are found on the first page of this thread. "We have pulled out all the stops on this one and decided to place our minimum supported GPU configuration at a still relatively decent Nvidia GTX 970 or Radeon RX 570. " CPU specs...if you can run most add ons, the 650 shouldn't be a problem. We'll have a more comprehensive minimum spec sheet some time in the next few days.

Very interesting. First of all, without reading the whole thread over there, Vulkan is native to Nvidia GPU's. That thread is talking about AMD cards using Vulkan.(???) I can confirm, as far as Mac's are concerned, no one is having issues with AMD and Metal. As far as the testers running Windows, on Nvidia GPU's with Vulkan, also, no issues.

Mac, Linux and Windows

Absolutely.

@BE19Pilot... What @Andydigitalsaid is correct. We planned to model the EVS, and I modelled the sensor for it. But it soon became apparent that it wasn't possible. Legitimate X-Plane limitation. The HUD is modelled and fully functioning, and will be seen on stream. Along with a lot more that we haven't shared yet.