Shape key value is buggy when using Time Stretching. #99206

New Issue

Eric · 2022-06-27T13:49:29+02:00

Eric commented

2022-06-27 13:49:29 +02:00

System Information
Operating system: Windows 10 64 bit
Graphics card: RTX 3070

Blender Version
Broken: 3.2.0
Worked: Unknown

Short description of error
Can't keyframe shape key value when using Time Stretching.

Exact steps for others to reproduce the error
A simple example does not work, If I simplify to reproduce the bug it will not happen.
I tried making a box with a shape key, everything works. But with a rigged character it doesn't allow me to add more than one shapekey keyframe value, if the Time Stretching is other than old 100 new 100. If the shape key is keyed to a value of .123 and further down the timeline I give it a value of 1. it will go back to .123 as soon as I touch the timeline.

But with a rigged character it doesn't allow me to add more than one shapekey keyframe value, if the Time Stretching is other than old 100 new 100. When I type the second shape key value and keyframe it, the value changes and the keyframe is set but as soon as I click anywhere on the timeline the shapekey value changes to the previous keyframe value.

**System Information** Operating system: Windows 10 64 bit Graphics card: RTX 3070 **Blender Version** Broken: 3.2.0 Worked: Unknown **Short description of error** Can't keyframe shape key value when using Time Stretching. **Exact steps for others to reproduce the error** A simple example does not work, If I simplify to reproduce the bug it will not happen. I tried making a box with a shape key, everything works. But with a rigged character it doesn't allow me to add more than one shapekey keyframe value, if the Time Stretching is other than old 100 new 100. If the shape key is keyed to a value of .123 and further down the timeline I give it a value of 1. it will go back to .123 as soon as I touch the timeline. But with a rigged character it doesn't allow me to add more than one shapekey keyframe value, if the Time Stretching is other than old 100 new 100. When I type the second shape key value and keyframe it, the value changes and the keyframe is set but as soon as I click anywhere on the timeline the shapekey value changes to the previous keyframe value.

Eric commented

2022-06-27 13:49:29 +02:00

Added subscriber: @JJLee

Germano Cavalcante commented

2022-06-28 14:46:07 +02:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2022-06-28 14:46:07 +02:00

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

Germano Cavalcante commented

2022-06-28 14:46:07 +02:00

Thanks for the report, but unfortunately this can't be triaged as a complete bug report.

For the development team to be able to help, there needs to be reproducible steps (start blender, press this, then that ...).

But this report does not contain a .blend file with exact steps to reproduce the problem.

A guideline for making a good bug report can be found at https://wiki.blender.org/wiki/Process/Bug_Reports

Thanks for the report, but unfortunately this can't be triaged as a complete bug report. For the development team to be able to help, there needs to be reproducible steps (start blender, press this, then that ...). But this report does not contain a .blend file with exact steps to reproduce the problem. A guideline for making a good bug report can be found at https://wiki.blender.org/wiki/Process/Bug_Reports

Eric commented

2022-06-29 04:37:56 +02:00

I know it's a horrible bug report but I am getting this bug nonetheless.

So they will have to remain as part of Blender forever because the bug is intermittent, or only occurs in a complex file but can't be reproduced in a "simple as possible" file.

It's discouraging to get bugs and even moreso that you can't tell anyone about them.

I know it's a horrible bug report but I am getting this bug nonetheless. So they will have to remain as part of Blender forever because the bug is intermittent, or only occurs in a complex file but can't be reproduced in a "simple as possible" file. It's discouraging to get bugs and even moreso that you can't tell anyone about them.

Germano Cavalcante commented

2022-06-29 17:07:51 +02:00

This channel is constantly filled with bug reports, if you didn't manage to delimit what causes the bug, it's possible that someone else can do it in another case or that it's even already reported and being investigated.

Unfortunately, we are unable to investigate every possible cause of a non-replicable bug as, to troubleshoot it, developers need to have direct access to the hardware and even then it is not clear whether it's a solvable from Blender side.

Something that can help is to provide log files, (but even then there is no guarantee that the developer will identify the cause).

To provide log files, please open Blender's installation directory and double click on the blender_debug_gpu.cmd. (This will start Blender in debug mode).
Try to reproduce the error again.
Once it crashes, the Windows Explorer should open and show you up to two files, a debug log and the system information.
Add them to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop.
Please also upload the crash log located in C:\Users\[your username]\AppData\Local\Temp\[project name].crash.txt (or simply type %TEMP% into the path bar of the Windows Explorer).

This channel is constantly filled with bug reports, if you didn't manage to delimit what causes the bug, it's possible that someone else can do it in another case or that it's even already reported and being investigated. Unfortunately, we are unable to investigate every possible cause of a non-replicable bug as, to troubleshoot it, developers need to have direct access to the hardware and even then it is not clear whether it's a solvable from Blender side. Something that can help is to provide log files, (but even then there is no guarantee that the developer will identify the cause). To provide log files, please open Blender's installation directory and double click on the `blender_debug_gpu.cmd`. (This will start Blender in debug mode). Try to reproduce the error again. Once it crashes, the Windows Explorer should open and show you up to two files, a debug log and the system information. Add them to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop. Please also upload the crash log located in `C:\Users\[your username]\AppData\Local\Temp\[project name].crash.txt` (or simply type `%TEMP%` into the path bar of the Windows Explorer). ![2019_12_04_upload_icon_developer_blender_org.png](https://archive.blender.org/developer/F8190038/2019_12_04_upload_icon_developer_blender_org.png)

Eric commented

2022-07-06 11:18:55 +02:00

I see what it is now. I have this one file that is corrupt. All these bugs I get only happen to this one file. I even copied all the content in this file and pasted it into a new file and the bug transferred to the new file.

Now I need to find out what to remove, what part is the corruption in the file. Can you recommend a way to sanitize a file?

I see what it is now. I have this one file that is corrupt. All these bugs I get only happen to this one file. I even copied all the content in this file and pasted it into a new file and the bug transferred to the new file. Now I need to find out what to remove, what part is the corruption in the file. Can you recommend a way to sanitize a file?

Germano Cavalcante commented

2022-07-06 17:27:45 +02:00

It could be a corrupted mesh.

You can run:

import bpy
for mesh in bpy.data.meshes:
  me.validate()

in console or text editor.

It could be a corrupted mesh. You can run: ``` import bpy for mesh in bpy.data.meshes: me.validate() ``` in console or text editor.

Eric commented

2022-07-06 17:48:09 +02:00

it says (me) is not defined

Germano Cavalcante commented

2022-07-06 18:05:19 +02:00

import bpy
for me in bpy.data.meshes:
  me.validate()

``` import bpy for me in bpy.data.meshes: me.validate() ```

Eric commented

2022-07-06 19:17:13 +02:00

This comment was removed by @JJLee

*This comment was removed by @JJLee*

Eric commented

2022-07-08 18:01:47 +02:00

All this:

import bpy
for me in bpy.data.meshes:
me.validate()

Just spits out hundreds of lines and no clue what make of it.

All this: import bpy for me in bpy.data.meshes: me.validate() Just spits out hundreds of lines and no clue what make of it.

Germano Cavalcante commented

2022-08-17 20:09:15 +02:00

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

Germano Cavalcante closed this issue

2022-08-17 20:09:15 +02:00

Germano Cavalcante commented

2022-08-17 20:09:15 +02:00

In #99206#1387784, @JJLee wrote:
All this:

import bpy
for me in bpy.data.meshes:
me.validate()

Just spits out hundreds of lines and no clue what make of it.

If any lines return True, this indicates that some mesh has been "fixed" and you can salve the file.

Unfortunately this report does not contain all the requested information, which is required for us to investigate the issue.

Please submit a new report and carefully follow the instructions. Be sure to provide system information, Blender version, the last Blender version which worked, and a .blend file with exact steps to reproduce the problem.

A guideline for making a good bug report can be found at https://wiki.blender.org/wiki/Process/Bug_Reports

> In #99206#1387784, @JJLee wrote: > All this: > > import bpy > for me in bpy.data.meshes: > me.validate() > > Just spits out hundreds of lines and no clue what make of it. If any lines return `True`, this indicates that some mesh has been "fixed" and you can salve the file. --- Unfortunately this report does not contain all the requested information, which is required for us to investigate the issue. Please submit a new report and carefully follow the instructions. Be sure to provide system information, Blender version, the last Blender version which worked, and a .blend file with exact steps to reproduce the problem. A guideline for making a good bug report can be found at https://wiki.blender.org/wiki/Process/Bug_Reports

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

Shape key value is buggy when using Time Stretching. #99206