Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Turret do not function correctly after loading object state #8367

Closed
Naka812 opened this issue Dec 22, 2024 · 1 comment
Closed

Turret do not function correctly after loading object state #8367

Naka812 opened this issue Dec 22, 2024 · 1 comment
Assignees
Milestone

Comments

@Naka812
Copy link

Naka812 commented Dec 22, 2024

Problem description

Behavior Turret do not function correctly after loading object state via "Set from JSON" action.

Attach a .c3p

https://drive.google.com/file/d/1YZw0eo2uilxNvL7Mvh8Ikv3w9NqxuR-_/view

Steps to reproduce

1.Preview the project and click on the orange area to add turrets.
2.Click the button labeled 'SAVE TURRETS' to save the current state of all turrets.
3.Close the preview and open it again.

Observed result

At the start of the layout, all saved turrets are loaded and placed in their respective positions. However, the turret behavior does not work initially; you need to wait a few seconds for it to start working again.
This does not happen if you press the 'DESTROY ALL TURRETS' button and then press the 'LOAD TURRETS' button."

Expected result

After starting the preview, at the beginning of the layout, the turrets should work normally and shoot at the target after being created.

More details

Apparently, it seems to be related to the 'set from JSON' action.

Affected browsers/platforms:
Chrome and mobile

First affected release:

System details

View details

Platform information
Product: Construct 3 r416.2 (stable)
Browser: Chrome 131.0.6778.205
Browser engine: Chromium
Context: browser
Operating system: Windows 10
Device type: desktop
Device pixel ratio: 1
Logical CPU cores: 16
Approx. device memory: 8 GB
User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36
Language setting: en-US

Local storage
Storage quota (approx): 134 gb
Storage usage (approx): 1.2 gb (0.9%)
Persistant 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!
WebGL information
Version string: WebGL 2.0 (OpenGL ES 3.0 Chromium)
Numeric version: 2
Supports NPOT textures: yes
Supports GPU profiling: no
Supports highp precision: yes
Vendor: Google Inc. (AMD)
Renderer: ANGLE (AMD, ASUS Radeon RX 580 Series (0x000067DF) Direct3D11 vs_5_0 ps_5_0, D3D11)
Major performance caveat: no
Maximum texture size: 16384
Point size range: 1 to 1024
Extensions:

EXT_clip_control
EXT_color_buffer_float
EXT_color_buffer_half_float
EXT_conservative_depth
EXT_depth_clamp
EXT_disjoint_timer_query_webgl2
EXT_float_blend
EXT_polygon_offset_clamp
EXT_render_snorm
EXT_texture_compression_bptc
EXT_texture_compression_rgtc
EXT_texture_filter_anisotropic
EXT_texture_mirror_clamp_to_edge
EXT_texture_norm16
KHR_parallel_shader_compile
NV_shader_noperspective_interpolation
OES_draw_buffers_indexed
OES_sample_variables
OES_shader_multisample_interpolation
OES_texture_float_linear
OVR_multiview2
WEBGL_blend_func_extended
WEBGL_clip_cull_distance
WEBGL_compressed_texture_s3tc
WEBGL_compressed_texture_s3tc_srgb
WEBGL_debug_renderer_info
WEBGL_debug_shaders
WEBGL_lose_context
WEBGL_multi_draw
WEBGL_polygon_mode
WEBGL_provoking_vertex
WEBGL_stencil_texturing
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.264 (video/mp4;codecs=avc1.420034)

@Naka812 Naka812 changed the title Bug report 21/12/2024 23:20 Turret do not function correctly after loading object state Dec 22, 2024
@AshleyScirra AshleyScirra self-assigned this Jan 2, 2025
@AshleyScirra AshleyScirra added this to the Next beta milestone Jan 2, 2025
@AshleyScirra
Copy link
Member

It should work with saving/loading the full game state with the system save/load actions, but loading an individual object state did indeed have a problem with the Turret behavior in this case. It should be fixed in the next beta.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants