Collada .dae export: Setting "Limit Precision" has no effect #121426

New Issue

Christoph-Walter · 2024-05-04T23:22:28+02:00

Christoph-Walter commented

2024-05-04 23:22:28 +02:00

System Information
Operating system: macOS 14.4.1
Graphics card: Apple M2 Pro

Blender Version
Broken: Blender 3.6.11 LTS
and also Blender 4.1.1

Short description of error
The exported dae files with mesh objects are identical no matter if the export setting "Extra" -> "Limit Precision" is selected or not (except for the time stamp of course).

**System Information** Operating system: macOS 14.4.1 Graphics card: Apple M2 Pro **Blender Version** Broken: Blender 3.6.11 LTS and also Blender 4.1.1 **Short description of error** The exported dae files with mesh objects are identical no matter if the export setting "Extra" -> "Limit Precision" is selected or not (except for the time stamp of course).

Christoph-Walter added the

labels 2024-05-04 23:22:29 +02:00

Jesse Yurkovich commented

2024-05-05 20:36:35 +02:00

I'm not able to reproduce this on Windows at least. Attached are 2 files, both from the default scene, the first exported normally and the second with the "Limit Precision" option checked. There are appropriate differences for the Camera and Light objects if you diff the 2 files.

untitled.dae

7.4 KiB

untitled-2.dae

7.3 KiB

Pratik Borhade commented

2024-05-06 07:14:29 +02:00

Hi, unable to confirm either. File from @deadpin clearly shows the difference without and without "Limit precision" option. I don't think this is a bug. Maybe attach .blend if you observe it in specific file (possibly all values are already within LIMITTED_PRECISION/6)?

Pratik Borhade added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2024-05-06 07:14:46 +02:00

Christoph-Walter commented

2024-05-06 11:51:27 +02:00

I did not test it with camera or light objects but mesh objects (where high precision or low precision is a big factor for the file size).

Here is the beginning of the mesh data from the attached dae file:
<float_array id="Cube-mesh-positions-array" count="3078">0.3170335 0.3742044 -0.09267431 0.3170335 0.3742044 ....

The hover info on that setting says that precision is limited to 6 digits but most numbers still have more than 6 digits. The shorter ones have zeroes at the end I guess.

I did not test it with camera or light objects but mesh objects (where high precision or low precision is a big factor for the file size). Here is the beginning of the mesh data from the attached dae file: <float_array id="Cube-mesh-positions-array" count="3078">0.3170335 0.3742044 -0.09267431 0.3170335 0.3742044 .... The hover info on that setting says that precision is limited to 6 digits but most numbers still have more than 6 digits. The shorter ones have zeroes at the end I guess.

limit.dae

289 KiB

dae-export-test.blend

145 KiB

no-limit.dae

289 KiB

Jesse Yurkovich commented

2024-05-06 19:18:25 +02:00

Ah, so the limit_precision option is only used on the various matrix transform data for objects (including blend shape and armature transform matrices), not the actual vertex data. This is why you'll see the Camera and Light's <matrix sid=transform element change in the default scene but not something like the Cube's position array.

The documentation/tooltip for this option is overselling the effect of this setting.

Ah, so the `limit_precision` option is only used on the various matrix transform data for objects (including blend shape and armature transform matrices), not the actual vertex data. This is why you'll see the Camera and Light's `<matrix sid=transform` element change in the default scene but not something like the Cube's position array. The documentation/tooltip for this option is overselling the effect of this setting.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Collada .dae export: Setting "Limit Precision" has no effect #121426