![how to add objects to a plane in ac3d for xplane 11 how to add objects to a plane in ac3d for xplane 11](https://cdn.renderguide.com/bpKGiTU.Zxeg~589d8/w:341/h:191/q:90/dpr:2.6/https://renderguide.com/wp-content/uploads/Blender-model-sculpting-blender-manual.png)
Compared to version 1.4 many changes and bug fixes have been made. Version 1.5 replaces version 1.4 as the stable release. The new stable release of ModelConverterX is out. In ModelConverterX, Programming, Tools | Leave a comment ModelConverterX 1.5 stable release And this understanding, in this case about the DDS file format and its limitations, also helps to understand better why the sim works like it does.
How to add objects to a plane in ac3d for xplane 11 pro#
So in the end I decided to write my own DDS writer and that’s what I’m working on now.Īnd of course there is one more pro of writing some feature yourself, you learn a lot from it. I tried to find a library for that, but the only good one I found targeted a much newer version of dotnet and updating MCX to thst version proved to have a lot of errors. So why am I talking about all this now? At the moment I’m implenting a feature to write DDS files without ImageTool. But sometimes there are issues where the library just throws an error and you can’t easily debug them, so then I wish I still had my own reader (of course forgetting at that moment how much work I can be to maintain that code). For example initially I made my own COLLADA reader, while later I switched to the Assimp library to read COLLADA and other formats. And for bugs the library is sometimes a black box where you can’t look into.įor MCX I have been meandering between these approaches for quite a while already. It’s often quicker to use a library, but glueing all kind of libraries can result in a messy architecture of the tool as well. When using a third party library the arguments are kind of reversed. And when there are bugs in a functionality they are often easier to solve.
![how to add objects to a plane in ac3d for xplane 11 how to add objects to a plane in ac3d for xplane 11](https://marginal.org.uk/x-planescenery/imgs/Blender_tiny.jpg)
But on the other hand it gives you more flexibility to implement it the way your tool needs it. When coding something yourself you possibly reinvent a wheel that somebody else already did. Both approaches have their pros and cons of course. When developing my tools I often have to choose between implenting a functionality myself or using a third party library that provides it. In ModelConverterX, MSFS, Tools, X-Plane | Leave a comment DIY or not? In the texture settings there are a few new options that influence this selection as well.įrom the testing I have done the new DDS export seems to work just as well as ImageTool, but if you find any texture that has issues when exporting, just let me know in the forum. So I have implemented my own exporter now for DXT compressed textures.īased on the preferred FS version and the characteristics of the alpha channel of the texture MCX will automatically select if it uses DXT1, DXT3 or DXT5 compression for the textures. For people with only MSFS or X-Plane installed this dependency on the FSX/P3D SDK did not make sense. The second change in the latest development release is that DDS and DXT BMP textures are no longer generated using the ImageTool tool from the FSX/P3D SDK. Because if you want to ensure that mipmaps can be generated the size has to be a power of two.ĭDS and DXT BMP generation without ImageTool The fact that MSFS has the requirement that the texture size is a multiple of four, does also imply that MSFS does not use mipmaps when compressing the textures. Any other preferred sim will give the previous behaviour of resizing to a power of two. If you set the preferred version to MSFS in the options the default behaviour is to resize to a multiple of four. The material editor has been updated so that it can perform both actions now.
![how to add objects to a plane in ac3d for xplane 11 how to add objects to a plane in ac3d for xplane 11](http://developer.x-plane.com/wp-content/uploads/2015/10/ops-1024x768.png)
FSX and Prepar3D have the more strict requirement that the size should be a power of two. This is the requirement that MSFS has for the textures. The first is that MCX now also supports resizing textures so that their size is a multiple of four. The latest development release contains two texture related changes.