Mario Donick

Thanks for the quick response, install now works again

Of course X-Plane was not running. And of course I re-downloaded the installer from the shop.

Hi, thanks for the constant updates of this plane! Esp. thanks for the Linux support, because a few months ago I dropped Windows on my main PC. Using this on Ubuntu 18.04, works very fine so far. However, the update to 1.1.7 fails. The installer is, as usual, uninstalling the previously installed version. Then it is downloading the Gizmo core files, which works fine. Once it starts to download the TBM files, it fails with a "file not found" error: I tried re-starting the installer twice, same result. Of course I also selected my main X-Plane folder. When I click "ignore", the following message (with reference to a file name) appears: Error writing file /mnt/4e7d6d83-75ed-44be-afb0-560a7f1c6d72/X-Plane 11/Aircraft/X-Aviation/TBM-900/objects/Fuselage.obj There are sufficient write rights to that folder, though.

Excellent!

To be expected. The new night lighting textures were added just a few days ago in a beta version of X-Plane.

If my impression is correct, TerraMaxx simply issues the "reload scenery" command to X-Plane (the same which you can call from X-Plane's developer menu and which takes the same amount of time). This is probably necessary because of the way how X-Plane's scenery works: It loads entire scenery tiles for an area, with mesh, streets, buildings, and so on. This simply takes as long as it takes and as long X-Plane's own scenery loading method does not change significantly, any texture-based seasons addon will have these loading times. It's not TerraMaxx' fault.

Thanks for this very helpful document!

Just want to note that yesterday another Windows 10 update (KB3189866) arrived. As updates are cumulative, this shows the same problem as the other one. Apparently only OpenGL games are affected (there are mostly threads about this by users of Second Life viewers, and some games like RuneScape, D&D Online and even WoW). Only solution is uninstalling and blocking the updates, until Microsoft gets aware of it (there are a few threads at answers.microsoft.com about it, but so far no official reaction) and tries to solve it.