Search results

I am happy with being able to select when exporting that the material names remains unchanged. Hopefully the separation at the first "_" shouldn't cause any problems since it also appears in the names themselves.

I wanted the names of the materials from the imported mesh to be stay unchanged. eg. Material name from the mesh "LM_Hull_t" should not become "LM_Hull_t_ProjectApollo\LMASC_LM_VC" and stay "LM_Hull_t"

The example above with “LM_Hull.dds” was only intended to show the changes made after importing. I used the .dds to immediately recognize whether it was a material with textures or not. But I changed it and just use a "_t" for it now.

For the "." the extended Meshc takes this into account and replaces it with “_”

The material names are written into an xxx_resource.h file using an extended version of meshc. These names are then used in source code to address the materials. Now if someone imports the mesh file again, the materials names will be changed and the source code will no longer work.

For example, when I import a mesh, the material name is: E.g. “LM_Hull.dds” and it becomes “LM_Hull.dds_ProjectApollo\LMASC_LM_VC”. For me it is important not to have this “extension” and to leave the material name as it is. I made changes to the importer code myself for this, but I think it's...

@Blake Can you add a checkbox to enable or disable adding name extension for the materials when importing meshes?

Meshes with a transparent texture must be rendered last, otherwise the meshes rendered afterward will also be transparent.

It would be better to include the entire build log. But paste it as CODE don't just copy it into your comment.

This is not a problem with the Blender mesh tools addon. Your problem is that the file was not saved correctly. Try loading the file with a text editor and then saving it as UTF8. Alternatively, take this file.

#UPDATE Should Work in Textures and Textures2 Based on my last post, if you also add the following in the file "import_tools.py" starting at line 350, it should work automatically without having to rename the files, at least it does for me. The problem with the capitalization of texture names...

The problem arises because Windows does not differentiate between upper and lower case. Linux, on the other hand, does. I can work around the problem by changing the lines 429 and 430 in the file "import_tools.py". from .... up = [pp.lower() for pp in p.parts] orbiter_path =...

You can use "Export Selected" and Select the Objects you want to be in the mesh.

Thanks Blake, I tested V2.1.1 and it works perfectly. I work on the NASSP VC and there are many switches, rotarys etc where the mesh of each one is the same, so just one mesh with multiple instances so I can make a change to that obejct that affects them all. Before that I had a workaround that...

@Blake I have a problem with the exportet Normals when Groups has not applied Rotation. https://github.com/BMCDad/orbiter-blender/issues/22

You seem serious about Orbiter's portability. I'm still waiting for the mobile phone version. 🙃

@Blake Done -> https://github.com/BMCDad/orbiter-blender/issues/21

That's exactly what I suggested in my previous post. But what I asked for may be useful to me.

@Blake Is it possible that the groups are sorted in the following order? eg. I have 2 collections and want the groups of the 1st collection to be at the beginning and then the groups of the 2nd collection. Currently the groups are sorted by their names Mesh01 Mesh01.001 Mesh02 Mesh02.001 But...

How did you build it on windows?