Strange bug with shape keys in BGE #39401

Closed
opened 2014-03-25 01:22:16 +01:00 by Richard R · 7 comments

System Information
WIndows 7, 2.4ghz celeron cpu, 2gb ram, Geforce8400GS

Blender Version
2.7

Short description of error
Loading a scene, which adds a new scene with a background scene, causes the shape key animation (from the background scene) to freeze at a specific point; even though there is no call for the animation to play.

Exact steps for others to reproduce the error
Everything was working fine until I removed a Message actuator from a object that has animated shape keys and 2 other actuators. The bug doesn't show up unless the current scene replaces itself with a scene, that then loads a background scene with the object with the shape keys.

I conducted a test where I put back the Message actuator I took out. Unfortunately, it did not fix the problem. I am thinking that taking out the Message actuator the first time was just a coincidence. I conducted another test with a new blend file, and set up a similar situation across 3 scenes. I could not reproduce the bug. Either this bug is completely random or am I missing something? See strange_shapekeys.jpg. There is no code or logic bricks telling it to do that.

strange_shapekeys.jpg

\This doesn't happen if the Scene.HUD or the Scene.L1 is loaded first. The problem is carried over to Scene.L2 and Scene.L3 if the ball isn't lost. If the ball is lost, it plays the animation normally. The problem is both in the view port and standalone.

I conducted another test by removing the action actuator from the "Ready? Begin!" object. The bug still shows up, so the problem isn't from the action actuator. The problem went away after I removed the animation keyframes from the shape key value properties. Now there is no animation to play; but, it proves the problem is in or connected to the animation data.

I deleted all the shape keys and animation, and tried to reproduce the original animation (ended up doing something different), and I still end up with the same bug (see strange_shapekeys2.jpg).

strange_shapekeys2.jpg

After a thorough investigation, I found the problem. The issue is the starting animation frame between scenes. Scene.Intro had a starting frame of 0, Scene.HUD had a starting frame of 1, and Scene.L1 had a starting frame of 0. For some reason, changing scenes in the bge that have a different start frame causes this abnormality to happen. The issue is solved; however, the bug remains.

I tried to included my project "blockbreaker" with the blend and animation files; however, there was a upload error because of a size limit. If you still need a blend file, I will try to get one uploaded when I have the oportunity.

**System Information** WIndows 7, 2.4ghz celeron cpu, 2gb ram, Geforce8400GS **Blender Version** 2.7 **Short description of error** Loading a scene, which adds a new scene with a background scene, causes the shape key animation (from the background scene) to freeze at a specific point; even though there is no call for the animation to play. **Exact steps for others to reproduce the error** Everything was working fine until I removed a Message actuator from a object that has animated shape keys and 2 other actuators. The bug doesn't show up unless the current scene replaces itself with a scene, that then loads a background scene with the object with the shape keys. I conducted a test where I put back the Message actuator I took out. Unfortunately, it did not fix the problem. I am thinking that taking out the Message actuator the first time was just a coincidence. I conducted another test with a new blend file, and set up a similar situation across 3 scenes. I could not reproduce the bug. Either this bug is completely random or am I missing something? See strange_shapekeys.jpg. There is no code or logic bricks telling it to do that. ![strange_shapekeys.jpg](https://archive.blender.org/developer/F82442/strange_shapekeys.jpg) \This doesn't happen if the Scene.HUD or the Scene.L1 is loaded first. The problem is carried over to Scene.L2 and Scene.L3 if the ball isn't lost. If the ball is lost, it plays the animation normally. The problem is both in the view port and standalone. I conducted another test by removing the action actuator from the "Ready? Begin!" object. The bug still shows up, so the problem isn't from the action actuator. The problem went away after I removed the animation keyframes from the shape key value properties. Now there is no animation to play; but, it proves the problem is in or connected to the animation data. I deleted all the shape keys and animation, and tried to reproduce the original animation (ended up doing something different), and I still end up with the same bug (see strange_shapekeys2.jpg). ![strange_shapekeys2.jpg](https://archive.blender.org/developer/F82444/strange_shapekeys2.jpg) After a thorough investigation, I found the problem. The issue is the starting animation frame between scenes. Scene.Intro had a starting frame of 0, Scene.HUD had a starting frame of 1, and Scene.L1 had a starting frame of 0. For some reason, changing scenes in the bge that have a different start frame causes this abnormality to happen. The issue is solved; however, the bug remains. I tried to included my project "blockbreaker" with the blend and animation files; however, there was a upload error because of a size limit. If you still need a blend file, I will try to get one uploaded when I have the oportunity.
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @remnar

Added subscriber: @remnar
Member

Added subscriber: @brita

Added subscriber: @brita
Member

You have made several tests to pin down the origin of the bug, can you upload a minimal file? Take out everything that is not related.. textures.. etc. Or make a new file with that start frames inconsistency that you found to see if the error is reproducible.

You have made several tests to pin down the origin of the bug, can you upload a minimal file? Take out everything that is not related.. textures.. etc. Or make a new file with that start frames inconsistency that you found to see if the error is reproducible.
Member

@renmar I really need a minimal file, or I will waste too much time with this

@renmar I really need a minimal file, or I will waste too much time with this
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Inês Almeida self-assigned this 2014-06-26 21:34:12 +02:00
Member

No response, closing.

No response, closing.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#39401
No description provided.