stjerneidioten / i3d-blender-addon Goto Github PK

Is your feature request related to a problem? Please describe.
It would be nice if the plugin had the possibility of importing I3D-files to fx. rework old projects without having to start from scratch etc.

Describe the solution you'd like
Support for merge groups.

Wopster's explanation:

You select an object.. set an attribute that defines the identifier of the merge group e.g. 1 (merge group 1)
And an option to select if it's root or not. (bool)
Then you select all the childs that belong to the group (which is within the same material) that you just identified with '1' and also add the identifier to those objects.

Another note is that the merge group should all be using the same material. Or it could cause performance issues. Maya throws a warning.

Additional Context
Here is an i3d, where a merge group has been setup in maya.
nonBinaryCubes.zip

It might be of interest to evaluate the dependency graph and then use evaluated objects for the SceneGraph to make sure that all the data is updated and modifiers are applied.

If I use 'duplicate linked' in Blender to create multiple instances of an object, the export result is not the same as in Giants exporter for 2.79 (or the NLD community exporter for 2.80). The translation is not applied succesfully, so all instances appear in the location of the original one.

As you can see in the screenshot, the triangle count is 12 (the same as a single cube), as well as the vert count, but the cubes are overlapping.

This is an export from the official Giants exporter. Tris 12, Verts 8, and the translateZ is in there like it should, showing the instanced second cube in the right position.

These two screenshots show something else. When I export a cube in 2.79, it is exported with 8 verts. If I export the same cube in 2.80 with your exporter, it uses 24 verts. On a big model, that becomes a problem quickly. Although I do not use sharp edges a lot for 'hero' parts of my model, they are used plenty in less visible parts, so that adds up.

Unfortunately, I use instancing a lot in the model I'm working on, and this means that I cannot use your exporter currently, so I hope there's an easy fix. I have attached both exports for comparison, if you need anything else, please let me know.

i3d.zip

Export paths that point to the FS data directory as relative paths. Also perhaps add options for relative paths and maybe export of files (primarily for materials) with regard to the blend file itself.

Is your feature request related to a problem? Please describe.
The old exporter had a checkbox 'Skin Weights', although I never actually got that to work. Either way, it would be nice to have support for exporting vertex weights.

Describe the solution you'd like
Include blendweights in the export file

Describe alternatives you've considered
x

Additional context
I'll add an example when I can find it again :)

Objects that are mirrored by having a negative scale does not export properly to GE.

Is your feature request related to a problem? Please describe.
It's impossible to effectively export materials that use a different shader in Blender than Principled.

Describe the solution you'd like
Ideally, I'd like to be able to manually specify the texture paths specifically for export. Can be part of #3 to be able to specify this. That way, if I use a custom shader, the exporter wouldn't try to 'find' the textures in the shader, but just use whatever I specify. I took inspiration for this FR from the SCS tools, where there's also a custom shader, but at the same time custom property fields for the standard texture properties (albedo, specular, normal).

Describe alternatives you've considered

Additional context

In the screenshot, you see both the shader selection (similar), the material attributes (things similar to bump depth, albedo color etc. in GE in the material panel, and the textures.

The exports shits itself when another node (like MixRGB) is connected to Albedo input of the Principled BSDF.

Since it doesnt make any sense that the exporter is supposed to read and export mixed input data for Giants Editor anyway, a failsafe should be added to prevent the error from popping up.

Exporting Albedo Color information is more than enough. I guess you can just add a failsafe if any node other than image texture or RGB is connected to albedo input.

Add support for exporting animation keyframes

See if something can be done about export particlesystems to i3d

During export the visibility of the Collection itself affects the visibility of the collection instance, which is wrong.

Describe the bug
The game gives lua errors when there is a fillVolume exported with the plugin. I've been testing, exporting a fillVolume from the game, importing it into blender and exporting it again and it also gives error. However, I tried to export the same object from Maya and it doesn't give any problem. All this without making any changes in the object.

Log file
1_export_log.txt
log.txt

Screenshots
If applicable, add screenshots to help explain your problem.

Is your feature request related to a problem? Please describe.
There is no testing whether or not a new feature update breaks any of the existing functionality before creating automatically creating a new build on github.

Describe the solution you'd like
Blender supports running through the commandline without gui, this means that unittesting is possible, which could be integrated with the CI that creates the builds on the buildserver.

Additional context
Blender in commandline

If any object in the hierarchy is in edit mode or the view itself is, then the addon crashes.

The UI files are non very organized, could do with a makeover similar to what is done for the different node classes, to make it a bit more obvious what goes where and affects which part of the interface.

Describe the bug
The exporter allows export of a merge group with only the root node in it. Giants Engine crashes if it has to import a single mesh merge group.

Currently some of the node object classes reference specific settings through accessing a named property on the current scene, but the i3d file already loads all of these settings into a dictionary. Basically the whole export settings stuff needs a bit of a rework.

Is your feature request related to a problem? Please describe.
The attributes cast Shadowmap and receive Shadomap should be enabled by default as 90% of the objects have shadows and if you have a project with many pieces and have to go one by one activating those attributes is a bit boring

Describe the solution you'd like
Having the cast Shadowmap and receive Shadomap attributes enabled by default

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

I am making a building in Blender.
Inside blender the UV and the textures on the building look great.
after export i open it up in GE and there some textures look great as in Blender but a few spots there are stretch and deformation going on in the texture.

I added my export log and a pic from blender and GE.

I hope you can fix this.
Love your version of the plugin so far.
Cant wait what else you come up with to do on the plugin.

best regards,

Herman
Distillery Factory Main 1_export_log.txt

Add a possibility to set most of the i3d properties inside of blender. Preferably in the properties panel within the 'object' category as a subpanel called i3d or something similar.

This would of course depend on object type so a camera would only show relevant properties for a camera and the same goes for mesh, light and so on.

Describe the bug
Currently - if an object is a Static rigidbody the Compound Child checkbox cannot be checked.
This is critical, because for collisions it needs to be checked otherwise the collision will not be loaded propperly.

See: https://discordapp.com/channels/292981511588675584/669200409973358625/685195667899285540

Resolution: Add compoundChild="true" via XML editing.

Log file
non needed

Is your feature request related to a problem? Please describe.
Code refactor. The code is under-utilizing object oriented programming, which would make a lot of the node exporting easier.

Add an option for verbose output when exporting. To help catch error and for people to produce error reports.

Me personally like to keep as many objects as possible easily editable.

That is why I rarely convert splines or paths into actual geometry, since its not needed if they are setup correctly (array and curve modifier for example)

One feature very late down the road I would like to see is the exporter to handle those splines and paths as meshes, so that they are automatically converted into meshes for export.

Is your feature request related to a problem? Please describe.
It is annoying to setup all of the properties every time for common scenarios.

Describe the solution you'd like
A solution similar to the way the maya addon does it with presets for different mod types

Additional context

Is your feature request related to a problem? Please describe.
For bigger projects it is hard to see if the exporter has stopped or if it is just hard at work.

Describe the solution you'd like
Some form of progress bar in the blender view

Describe alternatives you've considered
A text output somewhere inside of blender that updates live with the exported nodes.

Is your feature request related to a problem? Please describe.
Currently, there's no way to set user attributes on objects in Blender, they can only be set in GE

Describe the solution you'd like
The same ability as in GE (key, type, value).

Describe alternatives you've considered
None

Additional context
For reference:

Currently file exports and the path modifications used are done using the 'os' module, which isn't outdated but there is a new and better way introduced in python 3.4 with the pathlib module.

https://docs.python.org/3/library/pathlib.htm

Describe the bug
I switched from the original version this one was forked from to his version, and I noticed vertex colors are no longer exported. Is there an ETA for this feature? Thank you!

Describe the bug
When exporting, everything inside an empty is duplicated. Everything inside the transform group moving parts and hydraulics (the yellow underline) is duplicated. Everything that is not underlined is a duplicate of the moving parts and hydraulics transform group

Log file
Please generate a logfile by checking 'Output logfile' in the exporter and attach it to the issue.

Screenshots

Simple bug:

The Smoothness value is not correctly inverted from the Roughness of the BSDF Shader.
https://forum.substance3d.com/index.php?topic=3243.0

Smoothness = 1 - Roughness

In my case, smoothness should be

Describe the solution you'd like
Another option in the selection box in the exporter for selection an object/selection of objects to export. Instead of only collections.

Cleanup the code fx. by removing random print statements and write comments to all the code to ease readability for others as well as my future self.

The exporter ignores the blender unit scaling. So if it is set to fx. use milimeters as its unit the final result in i3d will be a factor 1000 to big.

Currently the conversion to GE coordinate system is done by hardcoding transform-matrices, when blender actually has an ExportHelper mixer class available than can generate this and make it easier and more dynamic across the exporter.

Determining object visibility in blender is sort of a mess at this point since there are four ways to toggle/inspect the visibility of an object and one of them isn't available to the python API (the viewport eye aka the 'h' shortcut)
It is further compounded by the fact that object visibility depends on being disabled in all collections and so on.
Current implementation is to just check for "hide_viewport", but should probably be enhanced to incorporate more, maybe even make it user selectable in the exporter.

Useful discussions:
https://blenderartists.org/t/show-hide-collection-blender-beta-2-80/1141768/4
https://devtalk.blender.org/t/hide-in-viewport-for-collections-in-python-api/8210/3

Describe the bug
If you have several unmerged meshes with different materials applied to them in Blender and export them to i3d, the exporter only applies a single material to all other meshes.

It seems it only reads and applies the first mesh in thats exported (in my case the 03_Cube)

Expected behavior would be the correct export from all materials applied to the correct meshes.

MultiMaterialExport.zip

When exporting custom meshes, the exporter ignores the smoothing set in Blender (be it custom weighted vertex normals via modifier, auto smoothing in data properties, manual smoothing via hard and soft edges or even hard edges set by HardOps addon)

Desired effect is that the exporter keeps the normal information and treats it as is, see attached picture.

Describe the solution you'd like
Support exporting bones/armatures as skinned meshes.

Describe the bug
The plugin does not export when exporting a model with empty (transform group) using the mergegroups. Without using the mergegroup it exports without problems and if I remove the empty and put the mergegroup also exports without problems.

Log file
i3dio.exporter:export_blend_to_i3d:INFO: Blender version is: 2.83.2
i3dio.exporter:export_blend_to_i3d:INFO: I3D Exporter version is: (1, 0, 0)
i3dio.exporter:export_blend_to_i3d:INFO: Exporting to C:\Users\fuent\Documents\My Games\FarmingSimulator2019\mods\Man\1.i3d
i3dio.exporter:_export_selected_objects:INFO: 'Selected Objects' export is selected'
i3dio.exporter:_add_object_to_i3d:DEBUG: [backDoor] is of type 'MESH'
i3dio.i3d.I3D:add_merge_group_node:DEBUG: [1] Adding merge group node
i3dio.i3d.I3D:add_merge_group_node:DEBUG: [1] New merge group
i3dio.node_classes.merge_group.MergeGroup:init:DEBUG: [MergedMesh_1] Initialized merge group
i3dio.node_classes.node.MergeGroupChild:_create_xml_element:DEBUG: [backDoor] Filling out basic attributes, {name='backDoor', nodeId='1'}
i3dio.xml_i3d:write_property_group:INFO: Writing non-default properties from propertygroup: 'I3DNodeObjectAttributes'
i3dio.xml_i3d:write_property_group:INFO: Wrote '0' properties
i3dio.xml_i3d:write_property_group:INFO: Writing non-default properties from propertygroup: 'I3DNodeShapeAttributes'
i3dio.xml_i3d:write_property_group:INFO: Wrote '0' properties
i3dio.node_classes.node.MergeGroupChild:_add_transform_to_xml_element:DEBUG: [backDoor] transforming to new transform-basis with <Matrix 4x4 (1.0000, 0.0000, 0.0000, 0.0000)
(0.0000, -0.0000, -1.0000, 3.4021)
(0.0000, 1.0000, -0.0000, -6.1182)
(0.0000, 0.0000, 0.0000, 1.0000)>
i3dio.node_classes.node.MergeGroupChild:_add_transform_to_xml_element:DEBUG: [backDoor] translation is <Vector (0.0000, 3.4021, -6.1182)>
i3dio.node_classes.node.MergeGroupChild:_add_transform_to_xml_element:DEBUG: [backDoor] has translation: [7.55411e-16 3.40207 -6.11817]
i3dio.node_classes.node.MergeGroupChild:_add_transform_to_xml_element:DEBUG: [backDoor] has rotation(degrees): [90 -0 0]
i3dio.node_classes.node.MergeGroupChild:init:DEBUG: [backDoor] Initialized as a 'MergeGroupChild'
i3dio.exporter:_add_object_to_i3d:DEBUG: [backDoor] processing objects children
i3dio.exporter:export_blend_to_i3d:ERROR: Exception that stopped the exporter
Traceback (most recent call last):
File "C:\Program Files (x86)\Blender\blender-2.83.2-windows64\2.83\scripts\addons\i3dio\exporter.py", line 58, in export_blend_to_i3d
_export_selected_objects(i3d)
File "C:\Program Files (x86)\Blender\blender-2.83.2-windows64\2.83\scripts\addons\i3dio\exporter.py", line 98, in _export_selected_objects
_export(i3d, bpy.context.selected_objects)
File "C:\Program Files (x86)\Blender\blender-2.83.2-windows64\2.83\scripts\addons\i3dio\exporter.py", line 105, in _export
_add_object_to_i3d(i3d, blender_object)
File "C:\Program Files (x86)\Blender\blender-2.83.2-windows64\2.83\scripts\addons\i3dio\exporter.py", line 150, in _add_object_to_i3d
_add_object_to_i3d(i3d, child, node)
UnboundLocalError: local variable 'node' referenced before assignment
i3dio.exporter:export_blend_to_i3d:INFO: Export took 0.014 seconds
Screenshots
If applicable, add screenshots to help explain your problem.

Describe the solution you'd like
A system where you can add premade components (i3d) from the fs $data directly in your blendfile to visualize the final model.

Describe alternatives you've considered
Either importing the i3d and have it directly as a normal object or in a different scene. And maybe keep a reference to the i3d file so it can just be linked on export without converting it back to i3d, since that ressource is already available.

Describe the bug
A clear and concise description of what the bug is.
The plugin doesn't work in Blender 2.83.2

Log file
Please generate a logfile by checking 'Output logfile' in the exporter and attach it to the issue.
i3dio::INFO: Initialized logging for i3dio addon
Traceback (most recent call last):
File "C:\Program Files (x86)\Blender\blender-2.83.2-windows64\2.83\scripts\modules\addon_utils.py", line 351, in enable
mod = import(module_name)
File "C:\Program Files (x86)\Blender\blender-2.83.2-windows64\2.83\scripts\addons\i3dio_init_.py", line 23, in
from . import (
File "C:\Program Files (x86)\Blender\blender-2.83.2-windows64\2.83\scripts\addons\i3dio\ui_export.py", line 16, in
from . import (
File "C:\Program Files (x86)\Blender\blender-2.83.2-windows64\2.83\scripts\addons\i3dio\exporter.py", line 18, in
from .i3d import I3D
File "C:\Program Files (x86)\Blender\blender-2.83.2-windows64\2.83\scripts\addons\i3dio\i3d.py", line 213, in
from i3dio.node_classes.skinned_mesh import *
ModuleNotFoundError: No module named 'i3dio.node_classes.skinned_mesh'

Screenshots
If applicable, add screenshots to help explain your problem.

To always have uptodate textures, and automatic DDS conversion of connected non-DDS textures could be added later down the road.

Wopster made a conversion tool that could be supplied with the toolset eventually

The lookup to know which texture needs which compression could be based on a suffix system
_decals = DXT5
_spec = DXT1
_normal = DXT1
... eca

Currently when exporting you have to set the shader and its variation type per material, which can become timeconsumin if you have several different materials per object, since you have to redo that step everytime you re-export the i3d file.

It would be more convenient to give materials parameters like "Shader Type" and "Shader Variation" so that the task of doing it by hand everytime after export is skipped.

For that, a relative pathing from the users Game library is needed to find the correct shader in the /data/shared/shaders folder

Is your feature request related to a problem? Please describe.
It is annoying that the i3dmappings has to be set manually every time something changes in the model.

Describe the solution you'd like
It should be possible to supply an id for the node, which then gets used to map to a position in the node tree.

Additional context

    <i3dMappings>
        <i3dMapping id="pgII25m_main_component1" node="0>" />

id should be set inside of blender on a per node basis. The node field should be updated depending on its place in the scenegraph. And the xml file of the mod should be suppliable somewhere in blender as well