[3D MODELS] Render glitch if making animation changes before model has been rendered on screen

[ma6x]

Checks

• I have read and understand the bug report guidelines
• I checked for existing similar reports to avoid submitting a duplicate
• I verified the issue occurs in the latest beta release to avoid submitting an issue that has already been resolved

Problem description

If you start a project and the camera isn't looking at a model, changes to that models animation may make it look wrong/offset visually, even if that objects position hasn't changed.

If you're wondering why someone may need the window and van instances seperated, it's because with this model I need to be able to change the opacity of the window without affecting the rest of the van, also for alpha clipping with sprites inside the van against the window it helps to change the layer that the window is on to be above or below the sprites as needed.

Upload a project

c3 render bug.c3p.zip

Steps to reproduce

1. Run the project

2. click the view van camera button

3. then click change animation

4. observe that it looks correct

5. close the window and run the project again

6. this time click change animation before changing the camera to view the model

7. observe that the window is now offset from the rest of the model

Observed result

Expected result

Affected platforms

macOS

Affected browsers

Chrome

Last unaffected release (including beta releases)

N/a

First affected release (including beta releases)

happens in latest r499 but also earlier versions

Additional remarks

I believe this is related to another issue which I think was an intentional choice to improve performance (?) , where models will flash pop in the first time you look at them, rather than be rendered immediately from start of layout.

Also the weird thing is that the position of the windows instance stays the same whether its offset wrong or looks correct, so it is not to do with the objects position changing.

Platform information

Platform information
Product: Construct 3 r498 (beta)
Browser: Chrome 151.0.7922.140
Browser engine: Chromium
Context: browser
Operating system: macOS 15.7.4
Device type: desktop
Device pixel ratio: 1
Logical CPU cores: 8
Approx. device memory: 16 GB
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/151.0.0.0 Safari/537.36
Language setting: en-US

Local storage
Storage quota (approx): 16 GB
Storage usage (approx): 5.7 GB (36.4%)
Persistent storage: No

Browser support notes
This list contains missing features that are not required, but could improve performance or user experience if supported.

Nothing is missing. Everything is OK!
WebGPU information
Renderer: WebGPU
Compatibility mode: no
Supports GPU profiling: yes
Major performance caveat: no
Maximum texture size: 16384
Adapter vendor: apple
Adapter architecture: metal-3
Adapter device: (unavailable)
Adapter description: (unavailable)
Adapter type: (unavailable)
Adapter backend: (unavailable)
Adapter features:

bgra8unorm-storage
clip-distances
core-features-and-limits
depth-clip-control
depth32float-stencil8
dual-source-blending
float32-blendable
float32-filterable
indirect-first-instance
primitive-index
rg11b10ufloat-renderable
shader-f16
subgroups
texture-component-swizzle
texture-compression-astc
texture-compression-astc-sliced-3d
texture-compression-bc
texture-compression-bc-sliced-3d
texture-compression-etc2
texture-formats-tier1
texture-formats-tier2
timestamp-query
Audio information
System sample rate: 48000 Hz
Output channels: 2
Output interpretation: speakers
Supported decode formats:

WebM Opus (audio/webm;codecs=opus)
WebM Vorbis (audio/webm;codecs=vorbis)
MPEG-4 Opus (audio/mp4;codecs=opus)
MPEG-4 AAC (audio/mp4;codecs=mp4a.40.2)
MP3 (audio/mpeg)
FLAC (audio/flac)
PCM WAV (audio/wav;codecs=1)
Supported encode formats:

WebM Opus (audio/webm;codecs=opus)
MPEG-4 Opus (audio/mp4;codecs=opus)
MPEG-4 AAC (audio/mp4;codecs=mp4a.40.2)
Video information
Supported decode formats:

WebM AV1 (video/webm;codecs=av01.0.00M.08)
WebM VP9 (video/webm;codecs=vp9)
WebM VP8 (video/webm;codecs=vp8)
MPEG-4 AV1 (video/mp4;codecs=av01.0.00M.08)
MPEG-4 H.265 (video/mp4;codecs=hev1.1.2.L93.B0)
MPEG-4 H.264 (video/mp4;codecs=avc1.420034)
Supported encode formats:

WebM AV1 (video/webm;codecs=av01.0.00M.08)
WebM VP9 (video/webm;codecs=vp9)
WebM VP8 (video/webm;codecs=vp8)
WebM H.264 (video/webm;codecs=avc1.420034)
MPEG-4 AV1 (video/mp4;codecs=av01.0.00M.08)
MPEG-4 VP9 (video/mp4;codecs=vp9)
MPEG-4 H.265 (video/mp4;codecs=hev1.1.2.L93.B0)
MPEG-4 H.264 (video/mp4;codecs=avc1.420034)

[ma6x]

@DiegoScirra Any updates on this bug? I noticed a new bug in r501 which i believe is related and I think fixing this issue will fix that new one so I'll wait before making a report

[DiegoScirra]

This will be fixed in the next beta.

Try this out in the next beta but also try that other issue you noticed, r501 introduced significant changes to support animation cross fading, so there might be some new problems, particularly with models that don't use bones for animations.

[ma6x]

This will be fixed in the next beta.

Try this out in the next beta but also try that other issue you noticed, r501 introduced significant changes to support animation cross fading, so there might be some new problems, particularly with models that don't use bones for animations.

Ah yes that makes sense. It was about default model positions with the meshes being offset, as soon as you played any animation it would fix immediately - but obviously with this bug if you played for example an idle animation at the start of the layout, if it wasn't visible on screen it wouldn't work