We have a lot of exciting news for XPlane2Blender users on three fronts: the Blender 2.49 Converter, Blender 2.8 support, and v3.5.1-beta.2!

Firstly I want to say a huge thank you to all the community for all your patience, advice, and support during this time of heavy development and slow releases. One of the biggest changes, I think, to XPlane2Blender in the last few months has actually been all of you! I’ve asked for advice and gotten constructive comments in droves, I’ve asked for projects and I’ve gotten example files to work with! I even asked for help with contributions to the project and gotten several pull requests to merge! Your passion for Blender and X-Plane inspires my passion for making the tools you want and need!

Now for the details!

The 2.49 Converter

The XPlane2Blender 2.49 converter has been in development for nearly a year, and the alpha is almost here. Some doubted if it was even possible to save these old projects, but the results speak for themselves. Observe these screenshots of Laminar Research’s KingAir C90B, F-4, and Boeing 737 that have been converted and exported with XPlane2Blender for 2.79!

KingAir C90B

KingAir C90B Cockpit Lit Up At Night
KingAir C90B Exterior, Showing Flaps Animating
KingAir C90B Interior Seating

McDonnell Douglas F-4

F-4 Cockpit Showing Panel Textures And Dials Rotated

Boeing 737

737 Main Gear, Beginning Retraction Animation

These are not proofs of concept, they actually work very well! Animations, manipulators, panel textures, meshes, lights, OBJ directives like shading, no shadow, DISABLE_DRAW, ATTR_light_level, and more, autodetecting textures, and preserving workflow features like picking the same OBJ file names and BULK export vs Regular export are all in the alpha. Basic scenery objects also convert, but some directives aren’t included yet.

We are not feature complete, and it will never be perfect: pre-conversion and post-conversion fixes will likely be necessary. However, spending only a day or two for the conversion is far better than redoing years of work!

Getting Your Old Projects Ready

The alpha is about two weeks away from release. In that time I HIGHLY recommend finding your old projects and doing the following

  1. Make backups of your files, because there is no return if you accidentally save over a 2.49 file after opening it in 2.79
  2. Ensure that ALL the OBJs in your project exports correctly with Blender 2.49b2 (the last version ever released) and our version of the 2.49 XPlane2Blender scripts.

    If you are able to do so and it can run in X-Plane 11.36, the converter has a very good chance of bringing it forward with few things to fix post conversion.

    The big thing I’ve noticed is that DataRefs usually need to be fixed as future versions of X-Plane added more that made unambiguous Datarefs ambiguous.

    I’ve noticed that some Blender 2.49 Datablocks have become “haunted” – where it crashes Blender 2.49 if clicked on or changed. I have no idea why or how. I can’t see a pattern or do anything about it, so take notes as these objects may need special attention post-conversion. If you have ideas, let me know!

    Also be on the look out for game properties with bad values, like an “litlevel” that is missing a dataref, or a “GLOBAL_tint” that doesn’t have two numbers separated by a space. X-Plane may fill in defaults, but the converter doesn’t. Don’t worry, the converter will help find some of these – as long as the property names are spelled correctly!
  3. If you are unable to run Blender 2.49, the converter may still work but you won’t get a chance to clean up the file and correct mistakes – it may require a lot more work post-conversion if you even get the chance. I highly recommend finding an old computer in the attic if needed.
  4. Most importantly, make sure you have the DataRefs.txt that 2.49 was or is using during export. Otherwise it may be impossible to correctly convert animations.

The cleaner the input file, the cleaner the conversion, the better the 2.79 file. That is why I’m releasing this guide before releasing the alpha – so that some of this work can be done beforehand and day 1 questions will be about the converter and not 2.49 problems.

One last note: Releasing our internal version of XPlane2Blender for 2.49 does not indicate support for it. It is merely there to help prepare your project for use with the converter. Remember, we’re trying to run away from 2.49 as fast as possible.

Blender 2.8 Support

A person recently e-mailed me: “Will Blender 2.8 have support before the New Year?” My answer: Yes! Yes it will! Don’t lose hope!

During the alpha cycle for the converter I will be finishing the alpha for Blender 2.8 as fast as possible. We’re very close – the UI is working and I’m about half way through figuring out which API calls need to be replaced and how.

XPlane2Blender’s UI and Custom Data in Blender 2.80

Before September is over you will start seeing more commits on the 399-blender-28-support branch. To keep up the hope, check out this screenshot of the BD-5J Microjet in XPlane2Blender in 2.8!

v3.5.1.beta.2 + Pull Requests

When I put out a desperate plea for some help developing the project I was gladly surprised by Kim Brandwijk, who has made several high quality pull requests that are small enough in scope to be added to v3.5.1.beta.2. I regret that I did not have time to merge them in a timely matter, but now with both alphas releasing soon all users can look forward to some excellent optimizations and speed increases soon. Hopefully the pull requests and community development can pickup some energy again.

I hope you all are as excited about this as I am! It has been a long summer of lots of coding, but I think people will be very happy with all the new features! Stay tuned for more news!


3 comments on “Status Update For XPlane2Blender!

Leave a Reply

Your email address will not be published. Required fields are marked *

Please do not report bugs in the blog comments.
Only bugs reported via the X-Plane Bug Reporter are tracked.