This is maybe similar to the other bug with unselected bones, but not the same. Everything is to be exported here, as you can see.

It is an old model (> 5 years), so something here may be invalid. I have no idea what. The last mentioned mesh by the exporter looks like a simple editable mesh. No skin, no animation. I don't know what the next mesh to export would be, the last exported mesh is in the middle of a bunch of meshes that haven't been processed yet.

I have this error and I don't think it's because of my model. A previous version of babylon (I think downloaded the 17th of november) exported it just fine:

Currently, only standard and physical materials are supported by the exporter.
For other materials only a warning is displayed but mesh's materialId remain unchanged.

To do to fix issue:
Such material should be ignored and meshes' materialId set to null.

I just get purple space. Exporting the same file to .obj, importing into Blender, and then exporting to .babylon "works" in the sense that it will load (there are problems with textures being off in association with going from Max -> OBJ).

Also, the resulting babylon file using the Max exporter is huge: more than twice the size of Max file. This is not the case using the Blender exporter.

I'm using the latest 0.36.0 zip file.

These are the errors I see when I call addMeshTask (and presumably why I'm not seeing any of my meshes):

errorObject.message:

"Unable to import meshes from assets/scenes/agency/babylon/agency.babylon: importMesh of agency.babylon from 3dsmax version: 2017, exporter version: 0.4.5 Material Name: Floor Material Name: Walls Material Name: Ceiling Material Name: Baseboard Material Name: 23 - Default Multi-Material Name: Material #258 Mesh Name: Room, isInstance: NO, # of submeshes: 4, n vertices: 276, parent: NONE Mesh Name: Camera001.Target, isInstance: NO, # of submeshes: 0, n vertices: 0, parent: NONE Material Name: Wood 01"
(Despite the error I am using 3ds Max 2018)

errorObject.exception.message:

Cannot read property 'toString' of null

What about adding some way to force image format for textures ?
http://www.html5gamedevs.com/topic/35026-image-format-in-3d-max/

Would be nice to have possibility to define environmentTexture (dds or any other supported format) for scene in 3d max so preview can use it for PBR materials

Is it deprecated?

Hi,

We ran into an issue of indices. The problem is two-fold:

• The indices are always stored as an array of unsigned shorts. When the number of vertices exceeds this, the indices wrap around to 0 and are invalid.
• The number of exported vertices is always 3 times the number of triangles. Vertices are not re-used. This means the problem is encountered significantly faster (as well as cause data size bloat).

A side-effect of the second point is that it is significantly harder to optimize a mesh.

Best,
Selmar

Would be nice if there would be a way to set light maps (shadow maps) inside 3d max.

http://www.html5gamedevs.com/topic/35025-add-light-map-to-material-in-3d-max/

When using a DDS texture on a material, when exporting, the following error appears and nothing is generated:

Exportation cancelled: Parameter is not valid.

Someone found I typo in Blender exporter. I had put the file zip process into Gulp, but no Gulp dir here. Probably could use a very stripped down version.

If you try to animate a mesh in Max and export it, then any keyframes that have the easing changed from the default value will produce a continuous drift in whatever property is being animated until it hits the next key frame.

See this post for sample files demonstrating the problem. http://www.html5gamedevs.com/topic/34055-3ds-max-exporter-animations-with-non-default-easing-produce-drift/

http://www.html5gamedevs.com/topic/34047-babylon-exporter-from-max-removes-camera-animations-in-gltf-export/

Exemple: to have an array in the babylon options in 3ds in order to manually enter the range of different animations and put them inside the export (0-50: walk, 100-150: run)? This option would greatly help 3D graphic designers for complex projects.
BabylonJS/Babylon.js#2360

• Geometries
• Materials

Hi folks

I recently discovered this exporter for 3ds max and thought is was the solution to all my issues :)
I tried both 3ds max versions (2015/16 and 2017), but the resulting gltf/glb get twisted up:

Any ideas, why this is happening? The model han be found here:
A319_gen.zip

The twist looks quite similar to the .fbx export I get when using the built-in fbx exporter from 3ds max 2016. The fbx exporter in version 2018 solved these issues for me. I know there is work in progress on the 2018 babylonjs-exporter as well...so this might solve also this issue. Or is this not connected?

Thanks for your hints!

From the .max file available here, animation is working correctly in gltf format but not in babylon.

Why is it not working in babylon?
Tracks:

• meshes and bones are grouped
• group is animated

Why is it working in gltf since all data come from babylon?
Tracks:

• thx to invertBindMatrices issue is not encountered

@noalak can you provide a sample scene for the morph target in the exporter folder?

Hello everybody,
I try to export a simple meeple from blender to babylon. It does not export the materials which consist of a simple diffuse bsdf shade. The exporter always bakes the texture which is not my intendet aim.
Does anyone have an idea about it? The corresponding files are attached below.
Thanks a lot in advance!
meeple.zip

Conventions:

• in 3ds max, camera and light default direction is downward
• in Babylon, their default direction is sideways

As such, a FreeCamera (no target) with a (0,0,0) rotation is looking wrong way once exported to babylon.

As for TargetCamera, since the rotation of the camera is dynamic, the camera is looking correctly to the target once exported.
However, camera's children are rotated 90°. A TargetCamera with a (0,0,0) rotation (target is below camera), when exported to babylon will have a (90,0,0) rotation, looking at its target.

To do to fix issue:

• for FreeCamera, add a 90° rotation to the camera (and its animations).
• for TargetCamera, if it has any child, add a TransformNode with a 90° rotation as child to the camera. Camera's children are then added as child to this extra node.

Currently, if the system unit scale is set to 1 unit = 1 centimeter, the exporter exports the units as if they were meters regardless.

Correct behavior would be to convert all units to meters before exporting, as per spec:

The units for all linear distances are meters.

Using latest blender 2.79 -

Camera and cube animated 1-990 frames. On export, two things wrong occur:

• cube position array is cloned to camera, ensuring camera playback is dead center of cube

• once returned to blender, all /most keyframes sometimes deleted.

I Check out and open with unity 5.6,

are you use 2017.X?

http://www.html5gamedevs.com/topic/33519-3ds-max-exporter-skeleton-exportation/

Marketing Updated with latest hairstyles on google drive

Hello :)
I think it will be very useful if we will be able to export 3dsmax hair & fur modifer as Babylon.FurMaterial

in the meantime do we have any other way to export fur & hair from 3dsmax to Babylon.js?

Thanks!

is unity5 new version ready?

If you export a scene with animations on the camera, they are removed when exporting to GLTF. The camera object in Babylon will have an empty array as it's 'animations' property.

Issue was originally reported here:

http://www.html5gamedevs.com/topic/34047-babylon-exporter-from-max-removes-camera-animations-in-gltf-export/

I'm following the instructions here: https://doc.babylonjs.com/resources/3dsmax

Using the latest 0.36.0 zip:
I unblocked all the 2018 dll files and copied over to 3ds Max 2018/bin/assemblies/

Restarted 3ds Max and still no Babylon menu item.

Exporting materials is abnormally slow. it is stuck exporting gltf materials for a long time. The total export time is 144 seconds. I don't recall it being this slow last month (same file).

Initially I thought the problem was because I had very large textures attached (multilayer .tiff, > 100 MB), however after replacing the maps with previously exported .jpg files, it still takes around 140+ seconds.

If copy textures to output is selected, the time increases to around 240 seconds (I did not test this with the smaller textures).

There is nothing abnormal about the exported materials.

	"materials": [{
			"pbrMetallicRoughness": {
				"baseColorFactor": [0.612745166, 0.612745166, 0.612745166, 1.0],
				"metallicFactor": 0.0,
				"roughnessFactor": 0.9
			},
			"emissiveFactor": [0.0, 0.0, 0.0],
			"name": "04 - Default"
		}, {
			"pbrMetallicRoughness": {
				"baseColorFactor": [1.0, 1.0, 1.0, 1.0],
				"baseColorTexture": {
					"index": 0
				},
				"metallicFactor": 0.0,
				"roughnessFactor": 0.9
			},
			"emissiveFactor": [0.0, 0.0, 0.0],
			"name": "09 - Default"
		}, {
			"pbrMetallicRoughness": {
				"baseColorFactor": [1.0, 1.0, 1.0, 1.0],
				"baseColorTexture": {
					"index": 1
				},
				"metallicFactor": 0.0,
				"roughnessFactor": 0.9
			},
			"emissiveFactor": [0.0, 0.0, 0.0],
			"name": "05 - Default"
		}
	],

Steps:

1. Make a box (box1)
2. Convert to poly
3. Duplicate it (box2)
4. Morpher modifier on box1
5. Edit box2 and set a morph animation (optionally export and run after to see the previewer preview the animation now)
6. Put a material on box1
7. Put a different material on one face of box1
8. Export and run now, to see that animation doesn't play

I think that means there's an issue with the exporter. Importing this model into Godot 3 RC3 crashes it. This doesn't happen if either the morpher modifier is removed or box1's material is changed to a non- multi material. Having both on the same model causes the babylon.js preview in "Export & Run" not to show the animation, which I take to mean something's breaking in the exportation, as trying to import this same model into Godot 3 RC3 crashes it. This happens whether you export to .gltf or .glb

Models look inside out. 3D max 2016.

• Better logo placement
• Combo box to pick file format (gltf / glb / babylon / binary babylon)

For our project, we require a custom material exporter. At this point, the material is not ready for public usage, nor may it even be proper to add it to babylon. Thus, we would like a way to add a custom material exporter to the project, preferably with minimal merging effort.

I envision it'd work somewhat like this: you create a new class that has an interface (e.g. `IMaterialExporter) that allows the exporter to get the material class ID associated with it and provides a function to export from a material handle. The exporter will find and create these material exporters using reflection.

I believe this material exportation should somehow allow for custom parameters that can be added to the glTF file format (like "extras" or material extensions).

Another difficulty is that when you add files to a project, the solution file is changed (and thus merging is still slightly annoying). Perhaps a good idea is to create a separate project for.. well.. extensions to the plugin?

Any thoughts are welcome.

Ways to reduce export duration:

• Cache processed images to re-use them in similar conditions (ie do the job only once)
• Enable multithread

@noalak

See BabylonJS/Babylon.js#3411 for context.

Since Max/Maya support animation clips, but don't support animation groups, it would be good if the glTF exporters for Max and Maya supported some mechanism (some additional options in the export window, etc.) that allow selecting of animation clips that should play together in a single Babylon animation group and export them to glTF as a single glTF animation with multiple channels.

unity 2017.2
exporter unity new version
babylon.js 3.x 2017-11-4

viewer:

This occurs when trying to export a selected mesh that has dummy nodes used for animation outside of the selection. If the nodes are properly selected the issue does not occur.

Some 3dsmax animations do not export correctly. See attached information provided by one of our artists.

gtlf animation issues.zip

Checking a rawgit link to the current zip should work

As there are significant differences between PBRMetallicRoughnessMaterial and PBRMaterial features but they both support MetallicRoughness workflow, would be nice if there could be some drop down or other way to specify what type you want to export, as right now to use features that are available only in PBRMaterial you need to manually parse exported file and rename fields.

BabylonJS/Babylon.js#2647