Search results

In the project properties, 'Code Generation/Runtime Libarary', pick one of the /MT (not /MD) options. That should compile the runtime into the DLL and avoid the need for the user to install the runtime libraries independently. For Orbiter add ons /MT (static library) is generally safe. For...

When installing VC 2022 Community (as Urwumpe said) make sure to include the Desktop Development with C++. That should include everything you need. You should not need older version of MSVC unless you are building some add-in that requires it. What I then do is open the ShuttlePB.sln from...

A mesh file is comprised of 'objects' or 'groups' that are defined in the mesh. The order they exist in the file is the order they will render in Orbiter. Also, a 'triangle' only has one side that will ever be visible to the renderer, a two-sided triangle is just two triangles. So, if you...

In Orbiter, the interior needs to be a separate object from the exterior (the object with the window). For example, if you want to see the pilot through the canopy window, the pilot is a separate object from the canopy, and must be sorted so that it comes before the canopy window in the mesh...

By the way, I can recommend this guy for some great Blender tutorials: https://www.youtube.com/@grabbitt This is a good series of his for beginners: https://www.youtube.com/playlist?list=PLn3ukorJv4vvv3ZpWJYvV5Tmvo7ISO-NN

Probably not, if that is working for you. A lot of the work in Blender is in areas we don't much care about for Orbiter work. Still, I usually work with the latest that will work with the plugin. For now that is 4.0. I do notice that 4.0 is slower to open on my machine, so there is that.

Blender 4.1 Heads Up! Blender 4.1 changes how smoothing and normals work in a way that breaks the orbiter mesh plugin. For now just use Blender 4.0. I'm seeing some complaints about this change on the internet, so the plan for now is to wait for a version 4.1.1 or .2 to see how it shakes out.

Google for 'blender low poly' or 'game asset' tutorials. I won't vouch for the quality of any of them, but it will give you some ideas on getting started using Blender for that type of work you would do for Orbiter.

I assume you are placing an 'Empty' object at the coordinates in your VC mesh where the button will be and then asking Blender to write that location to the header file. Blender can get funny with transforms, and its possible they have not really moved to where they belong. Click on them and...

Does the clbkVCMouseEvent get called? Also, the locations for the buttons all appear to be the same, as well as the ids. Still, I would expect the callback to fire.

You should have an 'Orbiter' folder. Under that is 'Meshes', this is where the mesh file you want to import should be located. Also under the 'Orbiter' folder you should have 'Textures' and Textures2'. The plugin looks for 'meshes' folder and assumes the Textures folders are on the same level...

Ok, on your mac it appears the plugin is loading. The import does assume it is importing an Orbiter mesh from an Orbiter installation. It does that so that it can find the textures that may be referenced inside the mesh. It only needs the folder structure and not an actual Orbiter...

As I described above, what does the python console say in the 'scripting' workspace. I still suspect python is somehow not installed correctly in Blender.

Sounds like it could be a bodged Blender install. I'd start with the latest LTS Blender (3.6), get the latest release of the plugin: https://github.com/BMCDad/orbiter-blender/releases/download/v2.1.3/orbiter-blender-2.zip Follow the install instructions on the readme...

Is the import menu option present but not working? Where are you seeing this error?

Where are you not seeing the difference? Your screenshot appears to show the behavior we want. The incoming material name has the texture name and mesh name appended on the left. On the right its just the material name alone (option disabled).

There is a pre-release 2.1.4 version you can try out. It allows you to disable the generation of the material name on import and simply uses the material names in the mesh file. The default behavior remains the same. If you want to see the issues this causes try importing ShuttleA with the...

Yeah, I knew that might be a problem. Another option is to pick another delimiter when building the material name on import and parse on that. Or let the importer pick something they know will be unique. There is probably some way to store that with the blend file so it knows how to pick it...

New release available 2.1.3. Adds a new build parameter that will allow you to parse the material name at the first '_'. As discussed above, that should allow you to save an imported mesh file using the same material name as the original mesh. Also fixes an issue finding texture files on...

There is nothing in the Output window indicating were it wrote the DLL file? Or why it failed to write that given the build worked?