Error report information

Type: assertion failure

Message: setting texture to current render texture

Stack: Error at Function.d.JYa (https://editor.construct.net/r251-2/main.js:288:209) at window.assert (https://editor.construct.net/r251-2/main.js:200:259) at d.Jd.LLa.ji (https://editor.construct.net/r251-2/main.js:1435:414) at Function.d.Kpb (https://editor.construct.net/r251-2/components/editors/layoutView/layoutView.js:90:25) at u.oed (https://editor.construct.net/r251-2/projectResources.js:657:339) at u.Ff (https://editor.construct.net/r251-2/projectResources.js:655:484) at r.Ff (https://editor.construct.net/r251-2/projectResources.js:626:34) at window.tl.Oyd (https://editor.construct.net/r251-2/components/editors/layoutView/layoutView.js:13:436) at fuc (https://editor.construct.net/r251-2/components/editors/layoutView/layoutView.js:4:236)

Construct 3 version: r251.2

URL: editor.construct.net

Date: Wed Jun 16 2021 14:02:40 GMT+0200 (Central European Summer Time)

Uptime: 26.1 s

Platform information

Browser: Chrome

Browser version: 91.0.4472.106

Browser engine: Chromium

Context: browser

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/91.0.4472.106 Safari/537.36

C3 release: r251.2 (stable)

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 960 Direct3D11 vs_5_0 ps_5_0, D3D11-27.21.14.5671)

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

Hello,

When I test my game in a browser using the Tile Movement behavior, there is a problem if you change the tab in the middle of the movement. The object returns to the previous position instead of going to the next.

To be more clear, if the object is simulating Right from A to B, and I change my browser tab in the middle of the movement, and then return to the game tab, the object did not go to B, but instead returned to A.

This only happens when the browser tab is changed during the tile movement.

I tried to debag and see what happens to the GridTargetX and GridTargetY expressions.

What I realized is that in regular circumstances GridTargetX and GridTargetY change immediately to Grid position B, when the simulating right starts, and stay until the object reached position B.

But if I change the tab of my browser in the middle of the movement, GridTargetX and GridTargetY change back to the grid position A instead of staying grid position B until the object arrives at destination B.

Is this a bug, or there is some other thing I have not considered.

Please help and thank you.