X-Plane 10.40 Beta 10 is posted. This fixes a few big airplane compatibility problems: fuel flow and light size match X-Plane 10.36. (I will post in some detail on this on Monday.) The high-low idle switch isn’t fixed yet – that’s one of the few aircraft compatibility bugs still floating around. See the full release notes for details.
I have seen some bug reports that auto-update is broken on Windows 10; I’m investigating those now. If you try to auto-update and something goes wrong, please do file a bug.
Ideally we will have a release candidate in one week; in practice I am out of the office for a few days this week and it looks like we have Windows-10 specific bugs, so we are more likely to have a release candidate in two weeks.
On my system, the notification of an available update upon startup and the subsequent run of the updater has functioned as it should for both 10.40b9 and 10.40b10 on Windows 10 Pro.
I haven’t seen any notes regards the transponder issue on the beta 10 notes, but it seems to be fixed for me. i was waiting for this fix. thanks
Oops – release notes editing mistake by me – the transponder is indeed fixed, and I have fixed the notes now.
The last 2 betas has been far more stable for me, I had a repeatable ctd just looking around the plane in 7 and 8 but have not had it since 9. That, to me, is more important than anything else in X-Plane. Keep up the good work..
tomcat357
Ben, when I open the ATC window and use the cursor keys to change the selection it moves the view also, is it a bug?
It might be – please file a bug!!!!!
(Please: next time do not ask, just file the bug. It is quicker to go through the bugs then answer the question on the blog “is this a bug” and THEN go through the bug.)
sorry to have asked here, I reported it now… thanks
can you make an option for choosing if you want Global Airports to be downloaded ? each time a beta comes I forget it’s there and then see lego airports on custom airports, have to quit, trash global airports and restart. would be nice to say No to the GA from the start. just an idea, dk if anyone else agrees,
NO.
You’re doing it wrong. If you don’t want global airports, disable them once in scenery_packs.ini and you won’t see them again until you either (1) delete scenery_packs.ini or re-enable them that way.
Have you ever thought that people not only want to tinker but fly 🙂 . Just let the X-Plane Updater/Installer integrate a small box with “Ignore Custom Scenery Folder” and good it is.
Because, It has been naturalized to rename the folders to determine the loading order, therefore you only have to delete the scenery.ini what does not help if you edit the folders anyway.
I -always- think that people want to fly and not tinker. So…
– No, I don’t want to add yet another check box, one that normal users will not understand, that causes users to lose the contents of custom scenery. This is just a tech support nightmare waiting to happen.
– I want to see “renaming files for order” go away forever – when you do that, the installer just puts back the things you renamed, creating chaos.
These are tinkerers solutions, and I do not like them!
cheers
Ben
I can understand that but is it possible, to integrate an installer.exe command for example -nocustomscen? That would be helpful
No.
It seems that 10.40 is making much fuller use of all the available cores. I run another sim for the aircraft and use X-Plane as a scenery generator via a plugin. The new version is having a big impact on the other sim. Is it possible to limit the number of cores that XP uses to free up a bit of cpu for the aircraft simulation?
Yes
–num_workers=N
The default is N = cores – 1. You can set it lower.
Hello
what about the AMD FX CPUs,
Will X-plane support better in the future?
Best regards
What do you believe to be the problem with X-Plane and AMD FX CPUs right now?
I dont know
I always hear with other, with Intel, it was as good and as fast and as many fps
We don’t optimize for a specific CPU vendor, so there really isn’t a “todo” here.