Collada exporter bind_shape_matrix value is invalid #75125

New Issue

Adrian · 2020-03-27T11:28:34+01:00

Adrian commented

2020-03-27 11:28:34 +01:00

Windows 10
Blender Version 2.82a

When exporting a bone animation the bind_shape_matrix values are all high values :

<bind_shape_matrix>19.45208 0 0 -0.3147154 0 19.45208 0 1.118382 0 0 19.45208 0.06304169 0 0 0 1</bind_shape_matrix>

The matrix made sense from output in the previous blender version I was using 2.79 and were basically the relative to the position of the model influencing the bones in the world.
So moving about the boned model in the scene would relate back to this value directly and could see an obvious relationship.
In the new version of blender this value doesn't seem to change even if moving everything back to around zero.

The prevous working value exported in version 2.79 of blender:

<bind_shape_matrix>0.6139576 -0.789339 0 -0.6377065 0.7893391 0.6139575 0 -0.06193837 0 0 1 2.872992 0 0 0 1</bind_shape_matrix>

On loading up the same scene with no changes into blender 2.82a and then exporting the value jumps up to the higher values (mentioned at start of bug) where I have no idea where it is getting them.

Thanks in advance for help with this.

Windows 10 Blender Version 2.82a When exporting a bone animation the bind_shape_matrix values are all high values : <bind_shape_matrix>19.45208 0 0 -0.3147154 0 19.45208 0 1.118382 0 0 19.45208 0.06304169 0 0 0 1</bind_shape_matrix> The matrix made sense from output in the previous blender version I was using 2.79 and were basically the relative to the position of the model influencing the bones in the world. So moving about the boned model in the scene would relate back to this value directly and could see an obvious relationship. In the new version of blender this value doesn't seem to change even if moving everything back to around zero. The prevous working value exported in version 2.79 of blender: <bind_shape_matrix>0.6139576 -0.789339 0 -0.6377065 0.7893391 0.6139575 0 -0.06193837 0 0 1 2.872992 0 0 0 1</bind_shape_matrix> On loading up the same scene with no changes into blender 2.82a and then exporting the value jumps up to the higher values (mentioned at start of bug) where I have no idea where it is getting them. Thanks in advance for help with this.

Adrian commented

2020-03-27 11:28:34 +01:00

Added subscriber: @AdrianFox123

Germano Cavalcante commented

2020-03-27 19:51:50 +01:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2020-03-27 19:51:50 +01:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Germano Cavalcante commented

2020-03-27 19:51:50 +01:00

Thanks for the report.

Could you provide a simple file and steps to reproduce the problem?
As explained in our submission template and guidelines.
Also explained here: https://www.youtube.com/watch?v=JTD0OJq_rF4

Thanks for the report. Could you provide a simple file and steps to reproduce the problem? As explained in our [submission template and guidelines](https://developer.blender.org/maniphest/task/edit/form/1/). Also explained here: https://www.youtube.com/watch?v=JTD0OJq_rF4

Adrian commented

2020-03-28 16:17:25 +01:00

Main_Hub_Menu(2_82a_blender).blend

Main_Hub_Menu(2_82a_blender).dae

Main_Hub_Menu(2_79_blender).dae

Main_Hub_Menu(2_79_blender).blend

Here are some files of using blender 2.79 which works fine with a boned hand at correct position in game and version loaded up in 2.82a that hand is suddenly gigantic.
The export from the 2.79 version of blender works fine but as soon as convert to 2.82a it messes up the bind_shape_matrix collada value.
It is the boned hand next to the bottom menu button on the left that I was using as a test.

Thanks in advance.

[Main_Hub_Menu(2_82a_blender).blend](https://archive.blender.org/developer/F8431864/Main_Hub_Menu_2_82a_blender_.blend) [Main_Hub_Menu(2_82a_blender).dae](https://archive.blender.org/developer/F8431863/Main_Hub_Menu_2_82a_blender_.dae) [Main_Hub_Menu(2_79_blender).dae](https://archive.blender.org/developer/F8431862/Main_Hub_Menu_2_79_blender_.dae) [Main_Hub_Menu(2_79_blender).blend](https://archive.blender.org/developer/F8431861/Main_Hub_Menu_2_79_blender_.blend) Here are some files of using blender 2.79 which works fine with a boned hand at correct position in game and version loaded up in 2.82a that hand is suddenly gigantic. The export from the 2.79 version of blender works fine but as soon as convert to 2.82a it messes up the bind_shape_matrix collada value. It is the boned hand next to the bottom menu button on the left that I was using as a test. Thanks in advance.

Germano Cavalcante commented

2020-04-01 13:51:56 +02:00

Changed status from 'Needs User Info' to: 'Needs Triage'

Omar Emara commented

2022-03-09 11:27:17 +01:00

Added subscriber: @OmarEmaraDev

Omar Emara commented

2022-03-09 11:27:17 +01:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Omar Emara commented

2022-03-09 11:27:17 +01:00

I imported both files and they produce identical scale, and no hand is gigantic. But I can confirm the values of the bind_shape_matrix, just not sure if it is in fact an issue.
Is your issue just about the value in the exported file? Or also about how it is imported?

I imported both files and they produce identical scale, and no hand is gigantic. But I can confirm the values of the bind_shape_matrix, just not sure if it is in fact an issue. Is your issue just about the value in the exported file? Or also about how it is imported?

Adrian commented

2022-03-09 11:42:29 +01:00

It's been a while since I looked into this issue.
From looking over my email history, this issue is just with the newer blender collada exporter values being incorrect.
I'm still using the older version 2.79b but this issue was found when first attempt at using 2.8x version of blender. It's possible it's already been fixed with newer version since then, but I've not had time to try any newer versions since.

Thanks

It's been a while since I looked into this issue. From looking over my email history, this issue is just with the newer blender collada exporter values being incorrect. I'm still using the older version 2.79b but this issue was found when first attempt at using 2.8x version of blender. It's possible it's already been fixed with newer version since then, but I've not had time to try any newer versions since. Thanks

Omar Emara commented

2022-03-09 11:56:27 +01:00

Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'

Omar Emara commented

2022-03-09 11:56:27 +01:00

Added subscriber: @GaiaClary

Omar Emara commented

2022-03-09 11:56:27 +01:00

The values is just as you reported, so nothing changed in newer versions of the add-on. But I am trying to identify if the change in the value is indeed an issue or not.
@GaiaClary Can you take a look?

The values is just as you reported, so nothing changed in newer versions of the add-on. But I am trying to identify if the change in the value is indeed an issue or not. @GaiaClary Can you take a look?

Adrian commented

2022-03-09 12:07:48 +01:00

The value change was definitely an issue, but we have decided to not use later version of blender until the end of our current project incase any changes cause errors. It has gone from sensible matrix values to values which make no sense.
Either the value in blender internal code has changed or the exporter code has changed. It seems like it's the later, as the later as blender was working fine it was just the export values that were wrong. I can't see how I can look into any further my side without looking through blender code itself.

It's not an immediate concern to me, just something that might be an issue a year or two in the future.

Thanks

The value change was definitely an issue, but we have decided to not use later version of blender until the end of our current project incase any changes cause errors. It has gone from sensible matrix values to values which make no sense. Either the value in blender internal code has changed or the exporter code has changed. It seems like it's the later, as the later as blender was working fine it was just the export values that were wrong. I can't see how I can look into any further my side without looking through blender code itself. It's not an immediate concern to me, just something that might be an issue a year or two in the future. Thanks

Gaia Clary self-assigned this 2022-03-09 13:33:06 +01:00

Gaia Clary commented

2022-03-09 13:33:06 +01:00

I see two issues (tested with current master):

The exported collada file imports back into current master without scaling issues. However the same dae file shows scaling issues when imported back into Blender 2.79
It looks like the Armature is exported in restpose, The bindshape is either not taken into account or its just exported wrong.

I see two issues (tested with current master): - The exported collada file imports back into current master without scaling issues. However the same dae file shows scaling issues when imported back into Blender 2.79 - It looks like the Armature is exported in restpose, The bindshape is either not taken into account or its just exported wrong.

Omar Emara commented

2022-03-09 13:48:26 +01:00

Changed status from 'Needs Developer To Reproduce' to: 'Confirmed'

Gaia Clary commented

2022-03-09 17:58:34 +01:00

After asking back in the animation chat channel, i see that not exporting the current pose is actually correct and the expected behavior.
So i will only look at the incompatibilities when exporting the bind shape in Blender 2.79 and in Blender 3

After asking back in the animation chat channel, i see that not exporting the current pose is actually correct and the expected behavior. So i will only look at the incompatibilities when exporting the bind shape in Blender 2.79 and in Blender 3

Sign in to join this conversation.