> By bounding box, I mean the area by which we can drug the 3D object in the editor.

Ah, yes. That may also be related to getting C3 API support for Common Z Elevation ACEs (BB in the editor, automatically adjusted for Z Elevation like 3D Shape does for the back face.)

yeah, I already understood it after your previous post

Thanks for the feedback and info, some comments:

- Z Elevation, can't go up top, those are C3 reserved properties. I have asked that C3 plug-in SDK expose 'common Z-Elevation' ACEs', but Ashley has not done it yet (please vote it up, so perhaps he will):

voted

- Bounding box/collision. This is dependent on the C3 collision system. Currently, the C3 system only supports 2D collision, so it does not take Z elevation into consideration.

I explained wrong probably

By bounding box, I mean the area by which we can drug the 3D object in the editor.

collision is a hard question for sure, but you added zelevation property and it is enough for now.

here is my prototype

will test more

but for now, it is working great

tried to delete objects, no errors

thank you again for this plugin.

will post results of my work little later

I have multiple instances working better (no bugs seen yet, but once I release please let me know if other issues are seen.) See release 2.4.1.

Can you please share the gltf model file that is causing the above error (my suspicion is that it is a model without animation and I'm missing a case checking for that.)

thank you. i will test it asap

I have multiple instances working better (no bugs seen yet, but once I release please let me know if other issues are seen.) See release 2.4.1.

Can you please share the gltf model file that is causing the above error (my suspicion is that it is a model without animation and I'm missing a case checking for that.)

it was my fault, yes, I didn't select the model while exported it from blender, so the file was without a model but with the armature, but better to have some fool protection.

because you know, after export you will not see the error, you can work, but when you will reopen the project, the game will not open

Yeah, im not killing objects now and just hide them. Not a big issue

what is worse is an error

Error: Cannot read properties of undefined (reading 'length') TypeError: Cannot read properties of undefined (reading 'length') at GltfData.loadGLTF

as long as it kills the game project. and game cant be opened after importing gltf file

the same bug destroying game

happen when newly added objects appears on the editor

construct closing with this error

Type: unhandled rejection

Reason: Error: Cannot read properties of undefined (reading 'length') TypeError: Cannot read properties of undefined (reading 'length') at GltfData.loadGLTF (blob:https://editor.construct.net/d7afb5a6-655b-41dc-91e0-3dbdfa574ce8:185:40) at async GltfData.load (blob:https://editor.construct.net/d7afb5a6-655b-41dc-91e0-3dbdfa574ce8:33:20)

Stack: TypeError: Cannot read properties of undefined (reading 'length') at GltfData.loadGLTF (blob:https://editor.construct.net/d7afb5a6-655b-41dc-91e0-3dbdfa574ce8:185:40) at async GltfData.load (blob:https://editor.construct.net/d7afb5a6-655b-41dc-91e0-3dbdfa574ce8:33:20)

Construct 3 version: r266

URL: editor.construct.net/r266

Date: Fri Oct 08 2021 16:50:42 GMT+0500 (Узбекистан, стандартное время)

Uptime: 22 s

Platform information

Browser: Chrome

Browser version: 94.0.4606.71

Browser engine: Chromium

Context: webapp

Operating system: Windows

Operating system version: 10

Device type: desktop

Device pixel ratio: 1

Logical CPU cores: 6

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.71 Safari/537.36

C3 release: r266 (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 1650 Ti Direct3D11 vs_5_0 ps_5_0, D3D11-30.0.14.7212)

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

found one more issue

when destroying the instance of 3d object, some error happens, it stops animation for all instances of this object on the scene

the error message in the console

4b7617fc-a61c-40b6-b58c-bc5cddfd2e60:87 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'GetDt')

at Object3DInstance.Tick (4b7617fc-a61c-40b6-b58c-bc5cddfd2e60:87)

at Array._tickFunc (sdkInstanceBase.js:6)

at EventHandler._FireNonCancellable (handler.js:7)

at EventDispatcher.dispatchEvent (dispatcher.js:4)

at C3Runtime.Step_AfterPreTick (runtime.js:74)

at C3Runtime.Tick (runtime.js:71)

at normal (runtime.js:7)

tried to add sphere as a skybox and found that spheres making errors

it can be previewed, but the angle doesn't change and when trying to start the debug preview, the game is freezing.

any ideas why it is happening?

all export setups are the same as usual

here is the test game drive.google.com/file/d/1BocfQc4xlArzlIEe-hWTA9SR3uDLicZW/view

Thank you for the update, it is amazing.

I already used variables to check animations, but models in the editor is a big plus

we are finally able to make good 3d games now

For those who want to make armature animations in the blender

you need to "Push Down" animations to make them visible after export