60 likes | 173 Vues
This text presents personal observations from Jonathan Harris, known as "Marginal," about the development of tools for X-Plane, including PlaneMaker, Blender, FS2XPlane, OverlayEditor, X-Publish, and XPOSM. It discusses the history and evolution of these tools, noting the strong backwards compatibility of X-Plane v8 formats while highlighting the challenges of forwards compatibility. Harris shares insights on feature compatibility, the need for flexibility in tool updates, future intentions regarding developers' tools, and performance considerations, all while inviting questions from the community.
E N D
Some personal observations Jonathan Harris (aka “Marginal”) Developing tools for X-Plane
History of my tools • X-Plane v6 / PlaneMaker • Blender • FS2XPlane • OverlayEditor • X-Publish • XPOSM
Developing tools for X-Plane • X-Plane v8 formats have lasted well • Good backwards compatibility • Networks (roads/rail)! • Forwards compatibility is a challenge • How to signal compatibility issues to users of tools • Difficult to plan ahead • Have to try to react to new features as they arrive • New features not always compatible with existing internal architecture of tools
Future intentions • Blender • Manipulators • still working on best way to represent these • Light level • using Materials – per Mesh object • Draw disable • using “Invisible” Texture Face button • Camera constraint • Re-using “Collision” Texture Face button • Bug fixes!
Future intentions • FS2XPlane • Not expecting FS11, so no intention to update • Can't do FSX photo-scenery – sorry • OverlayEditor • Performance! • Tracking new X-Plane features • Roads??? • XPOSM • No new features planned • Expect this to become redundant soon