search

Scirra / Construct-bugs

Public bug report submissions for Construct 3 and Construct Animate. Please read the guidelines then click the 'Issues' tab to get started.
https://www.construct.net
107 stars 83 forks source link

Hierarchy and timeline conflict #5114

Closed elfwy-uwu closed 3 years ago

elfwy-uwu commented 3 years ago

Problem description

Adding hierarchy in the editor with previously created value track in timeline causes construct to crash Creating value track with existed hierarchy or removing hierarchy in any time doesn't cause crash

Attach a .c3p

https://drive.google.com/open?id=1DwGi7pZJijiL1r10VZcu1xVzGgAzPs4U&authuser=versysdev%40gmail.com&usp=drive_fs

Steps to reproduce

(Pass to the 3rd step if using attached .c3p)

  1. Create a new timeline
  2. Add standalone value track to it
  3. Try to create hierarchy in the editor

Observed result

Crash dialog, attached the details below

Expected result

It's presumably not supposed to crash

More details

Affected browsers/platforms: Chrome, Firefox, Opera GX

First affected release: r264 (since value track feature was implemented in r264)

System details

View details Error report information Type: unhandled exception File: https://editor.construct.net/r267/projectResources.js, line 732, col 85 Message: Uncaught TypeError: Cannot read properties of null (reading '$V') Stack: TypeError: Cannot read properties of null (reading '$V') at d.$mc (https://editor.construct.net/r267/projectResources.js:732:85) at d.Df (https://editor.construct.net/r267/projectResources.js:732:374) at r5a (https://editor.construct.net/r267/components/editors/layoutView/layoutView.js:25:197) at https://editor.construct.net/r267/components/editors/layoutView/layoutView.js:13:39 at https://editor.construct.net/r267/main.js:1670:78 Construct 3 version: r267 URL: https://editor.construct.net/r267/ Date: Thu Oct 14 2021 09:47:39 GMT+0500 (Екатеринбург, стандартное время) Uptime: 803.2 s Platform information Browser: Chrome Browser version: 94.0.4606.81 Browser engine: Chromium Context: webapp Operating system: Windows Operating system version: 10 Device type: desktop Device pixel ratio: 1 Logical CPU cores: 4 Approx. device memory: 8 GB User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.81 Safari/537.36 C3 release: r267 (beta) Language setting: en-US WebGL information Version string: WebGL 2.0 (OpenGL ES 3.0 Chromium) Numeric version: 2 Supports NPOT textures: yes Supports GPU profiling: yes Supports highp precision: yes Vendor: Google Inc. (NVIDIA) Renderer: ANGLE (NVIDIA, NVIDIA GeForce GTX 1070 Direct3D11 vs_5_0 ps_5_0, D3D11-30.0.14.9613) Major performance caveat: no Maximum texture size: 16384 Point size range: 1 to 1024 Extensions: EXT_color_buffer_float, EXT_color_buffer_half_float, EXT_disjoint_timer_query_webgl2, EXT_float_blend, EXT_texture_compression_bptc, EXT_texture_compression_rgtc, EXT_texture_filter_anisotropic, EXT_texture_norm16, KHR_parallel_shader_compile, OES_texture_float_linear, WEBGL_compressed_texture_s3tc, WEBGL_compressed_texture_s3tc_srgb, WEBGL_debug_renderer_info, WEBGL_debug_shaders, WEBGL_lose_context, WEBGL_multi_draw, OVR_multiview2
DiegoScirra commented 3 years ago

Will be fixed in the next release.