


#Xplane 11 controls code#
Here’s what happened and why:Īs part of our work to port X-Plane to Vulkan, I rewrote the code that renders a frame in two ways: They aren’t going to go back to the way they were, because we don’t spend time trying to support hacks based on art controls. In X-Plane 11.30, a number of art controls have stopped behaving the way they used to. Backward compatibility takes a lot of planning and effort and there’s just no way we can keep a bunch of internal tweaks the same while modifying the sim. But we also spend absolutely zero time trying to maintain art control compatibility with previous versions of the sim. We don’t go in and change their names in every beta just to mess with third parties. We don’t go out of our way to break art controls. Our first instinct isn’t to encrypt everything. X-Plane has always been a relatively open sim to play with and lots of X-Plane authors got their start just poking around. We leave them in the final product because they are sometimes useful to third parties, useful for in-field debugging, and because we are generally okay with people hacking the sim if they understand the limitations. Art controls are internal tuning constants in X-Plane that we put in so that our art team can modify the behavior of X-Plane while they work without having to recompile the sim from source code.
