Without more information, I think there's a mistake in something you're doing. The camera plane shouldn't intersect the plane you're trying to show, you need to move the camera or otherwise rotate something to prevent the intersection.

Sir LoLz

Try moving the camera further away instead of adjusting the near plane.

andreyin

sorry for the double post.

Just remembered the best way to do this is to use a viewport object. It has the same kind of raycasting conditions, but lets you test a ray exactly based on the mouse position accounting for the effect of the projection matrix. If you create a viewport and make it the size of the screen you should be able to do this easily by casting a ray using the absolute mouse position.

andreyin

Q3D Master should have a camVecX/camVecY/camVecZ property that you can use to get the view direction which would be more convenient. Also I think nTx/nTy/nTz will be pointing away from the view direction if you copy the camera rotation like that (it's a quirk of openGL, the camera looks in the opposite direction of the Z axis), and you might need to force a model matrix update using the action for this to get up to date values.

If I misunderstood your issue let me know.

Sir LoLzeverard999

Manual Link:

dropbox.com/s/vpn0mbh4m7lo9zj/Q3D%20Users%20Manual%20V2-4_2.docx

"...Will we see new stuff from you again e.g. plugins or demos?"

If this would happen, i would by 5x more Q3D-plugins ! :-) (especially if the update would include any ThreeJS connection)

No, the Construct 2 SDK is too limited to really do any more with the plugins.

FlyingRam

There is no completed manual.

ok... that's kind of annoying.

Is private messaging removed from the new forum? I can't seem to find it anywhere...

FunkY Koval

There is no texture based control over reflection maps, you'll need to separate the models you want at a different reflective level. You can control specularity with a map however.

Emissive maps are also not supported, it wasn't a feature in the three.js build used a couple of years ago to make Q3D, and updating the api is not easy since it causes many many regressions.

You can again, use a different model with meshbasic material or some emissive color to add emissive elements however.

undeadbobop

just redownload it using you original info from the email you got. Then follow the same "plugin installation" procedure you did, making sure to remove the older plugin versions. Some versions aren't completely compatible though (depending how far back you go), so be mindful of that.