> I know people get tired of hearing me keep saying "we're a small team and we have limited resources". It's because it's true and 99% of the time it's the answer to "why hasn't XYZ been done yet".

Ashley - a suggestion/request to help with this: expose more of the SDK to allow third party devs to create more powerful addons/effects - we can help XYZ get done.

If you see this as valuable, we can post tight and directed requests for addon SDK features for specific XYZ-like addons (e.g. 3D view change in editor with access to more of the editor SDK / renderer.)

This please.

Oh cool, never knew that's what it was called. Thx

Newest Effect is a glitch Shader bsed on this Shader by user Coolok : shadertoy.com/view/4dXBW2

download here: https://www.construct.net/en/make-games/addons/1113/glitch

This one is nice!

> Maybe a nw.js issue then? If you can reproduce it reliably then filing a bug with scirra is your best bet. As an alternate to nwjs they have that webview2 export which seems to have less issues. Maybe that's a solution.

I made a video to demonstrate it better. If you notice, out of nowhere, the camera goes all Exorcist, as if it's twisting the player's 'neck' upwards or sideways. THIS HAPPENS WITH ANY CONSTRUCT EXAMPLE, and the funniest thing is that it only occurs on one of my computers, not the other.

Subscribe to Construct videos now

Go in the discord bro. There are people doing 3d there. Its hard to know what's happening if this doesn't happen to anyone else.

> Well I’m not familiar with those examples and i don’t have access to a mouse so I can’t test for myself.

> Does the issue you’re encountering happen in those examples or just in your game?

> If it’s just happening in yours then somehow you’re not doing it the same. You’ll need to double check to look for any differences.

> If it happens in the examples too then I guess it’s flawed somehow? No idea where. You only posted a partial of how the camera is rotated from moving the mouse.

This occurs in all examples of 3D third-person in Construct, whether through events or via JavaScript.

All the examples work good for me in both of my computers.

Ok thank you. I closed the bug report then.

Don’t use dt and it won’t be.

Im sorry I said it wrong, the dt actually fixes it. using only clamp(self.8direction.maxspeed + 1, 0, 250) becomes framerate dependent.

moving it with this btw

Just asking, since I thought 8direction behavior already has dt.