Cameron

What aircraft will you be flying at your school? If you want a good trainer, I would recommend this: https://www.x-aviation.com/catalog/product_info.php/take-command-sr20-g1000-p-195

I think X-Plane sounds like the most suitable option for what you're looking for.

This actually sounds like an unactivated Challenger. Did you not update to the latest version?

That was in reference to some tests we did and discussions with Laminar about the use of DDS and PNG files, and how the texture pager differently interacts with them. PNGs are slower to process, and they must be re-fetched from disk. This slows things down and causes a stutter. It's a piece of the puzzle for objects that get "killed" when you're not looking at certain angles (like facing forward in the cockpit, but not at the engines). When you pan the camera in these situations, there is a momentary pause while X-Plane has to go all the way back to disk and fetch the files again. We solved that situation by providing DDS files, which are already compressed and contain mipmaps. In other words, no, he was not referring to Gizmo.

I think you're referring to something that was thought prior to our discussions with Laminar about the CPU/GPU texture paging situation. Gizmo is not at fault, as has been explained. There was a topic elsewhere here where someone suggested some other plugins can cause these stutter drops as well, like the Skunkcrafts updater. May be worth doing an audit on your plugins just to see. FlyWithLua and anything SASL based would be a good start.

You should be using '6'. All this said, the CPU core count is a workaround to a limitation problem in X-Plane, not a magic fix for a bug or hardware that's just barely getting by minimum specs (if that). You appear to be running the Challenger 650 on a laptop CPU, which is going to be throttled and have issues keeping up with anything trying to work it hard. A 1060 video card is further holding you back, especially as a laptop variant. I'm not even sure the Mobile version of the 1060 meets the minimum required specs of the GTX 970 we have posted on the product page. Your computer specs are simply probably not going to cut it.

Probably not for a couple of weeks, maybe 3.

Replay with custom datarefs requires work that has not yet been put into the product. This really isn't a bug. It's just not implemented for now.

Updating is fine and helpful. Frustration is understandable, but please don't take it out on the forums for people already trying to assist.

Let's settle down a bit. No one is ignoring this. Rome wasn't built in a day.

Thanks for the update! Off to order the hardware now.

Hi there, We have no plans for a demo, but there's TONS of YouTube videos at this point to check out.

Thank you for trying to help out further @BlackBird_GR. I hope you guys can come out the other side successfully!

No worries! Not really hijacking. But, you fall into that same camp of people as I already described. Yet another GPU in that Nvidia 1xxx series. This all, again, comes down to texture paging. No magic solutions to give here, unfortunately.

Ah wow, 30Hz, okay. Rare case, but understandable. Pet peeve alert: Don't ever compare one product to another. They are not even remotely close to equal and I hate when people try to do this. Unfortunately, I don't. The explanation in the CPU thread about all this explains the situation on a high level, and on a low level as I understand it, I can make sense of why it's happening, but there's nothing I/we can do. At the end of the day this comes down to texture paging and how it's done in X-Plane. The most common folks effected are those like you with an Nvidia 1xxx series video card. With exception there's others, but by far and wide that series of video card struggles the most with this issue in our gathering of reports. If you haven't done so already, you can try and give yourself a little more headroom with the 6GB optimized version, but that's really all I have.

So, first thing jumping out at me is you have 'Use Vsync' enabled. VSync lowers the number of fps to match the refresh rate of your monitor, so they're synchronized. ... But if you have less fps than Hz, VSync will reduce the number of frames by half. This results in stuttering. So if your video card only reaches 59 fps, VSync will lower it to 30 fps. We don't do server polling. Outside of the above, I can't really recommend much else I don't think.

Why in the world would you EVER find it okay to post an installer that you have to purchase online? I have removed them from your post. Don't do it again. All of our products include Mac installers. You probably have some weird Anti-Virus deleting it. I suggest you have a read about the response time window on the Contact page. Sending 5 support tickets in 24 hours is a little much: https://www.x-aviation.com/catalog/contact_us.php

You downloaded right in the middle of an update. You'll need to re-download the installer.

Okay, a small hotfix labeled version 1.2.3 is now released to address some minor issues and the Mac build misreporting.

Did you read the post above yours?

Known issue. HotFix is on the way.

You shouldn't turn HT off. It's useful to X-Plane. With it on your setting should be '10' for the CPU shortcut parameter.

Mac target got labeled wrong it looks like. We'll update that soon. For now you can ignore the message and know you have the latest.

Hello All, This will serve as a formal forum announcement that we have released the version 1.2.3 update for the CL650. All customers who have purchased the CL650 up till now have been sent an e-mail by X-Aviation with complete instructions on how to obtain your update. We have made this a very simple process! For those that purchase the CL650 from today forward, your purchased download will already be updated to version 1.2.3 for you. REMINDER! Some customers have experienced performance issues where FPS in sim got very low or unflyable. If this has happened to you, please read the following on how to handle the situation: What if I didn't get the update e-mail? If you did not receive your update e-mail don't fret! X-Aviation has updated our system to allow all customers to update with ease, regardless of whether you received an e-mail for the update! Here's what to do: 1. Login to your X-Aviation account here: https://www.x-aviation.com/catalog/account_history.php  2. Find your original Challenger 650 download and re-download the file. It will download as the latest version! The following is a list of additions/fixes included: What's New / Changed: New Features: 2432: Want to export V-speeds via stable datarefs for 3rd party plugins Bugfixes: 2426: Fixed protruding mesh on AC external panel door 2433: Leg end course needs to be determined from the leg end point, not start point 2427: Copilot AOA vane cover shouldn't affect AUX AOA probe 2307: Crash due to satellite azimuth determination hitting a NAN value 2437: V-bar flight director roll should be absolute to the horizon, not the aircraft's wings 2439: When a SEC FPLN is entered, show the HOLD LIST page when selecting LSK 3R from IDX 2441: Don't show PPOS prompt when entering a hold in SEC LEGS 2454: Drop thread execution priority on any threads we don't strictly need 2455: X-TCAS workaround for XPMP network clients not setting weight-on-wheels wasn't functional 2456: Bird strike texture doesn't need alpha, so conserve some memory for it 2442: Add aliased commands for at_disc 2185: State restore to 1000ft from after landing leaves wheels spinning 2434: Cabin press prevents door opening on reposition to high elevation airport 2459: Fixed rotation animation of throttle labels 2460: Fixed rogue ambient occlusion on emergency exit 2461: Fixed gap between door depressurization flap space and inside of door Improvements: General fine tuning for performance Enjoy these latest updates, and stay tuned to the forum as we continually announce the latest happenings.

I want to tread lightly here. I don't want to call this a "bug", but more a shortsighted situation for the day Laminar didn't account for coming as soon as it did. The workaround we gave is essentially what you can expect to be mostly baked into X-Plane 12, where we'll be able to tell X-Plane ourselves how many CPU cores to reserve for us. Right now you're having to manually do that with the info we gave you. In other words, it will put the responsibility back on us to tell X-Plane what to do once Laminar allows that. I can't speak to performance of 12 as a whole, or if the texture paging system is more refined in 12 either. It's possible it is, or it's possible it's the same as now, in which case you should not assume a miracle change. Just setting the proper expectation here, and setting the record straight that calling this a bug is also not correct. Your CPU is a 16 threaded machine, so you really wouldn't be in the camp of people we would expect to use the guidance we provided either. Keep in mind that we also aren't personally auditing everyone's configuration. Ortho scenery, object scenery, rendering settings, etc all bring this stuff into play. I'd be interested to see your X-Plane rendering settings just for the sake of knowing. Any ortho scenery here too that the paging system is playing around with?