Visibility Issues with Meshes in krpano-Three.js Integration

Hello everyone,

I'm experiencing a problem with rendering trajectory line mesh in a Krpano-Three.js integration project. The mesh become invisible after scaling them above a certain factor, despite making adjustments to camera settings, scaling, and rendering properties.

Here are the key details:

Project Setup: I'm using Krpano with the Three.js plugin.

Camera Configurations:
camera.near = 0.1
camera.far = 10000000

Object Configurations:
Frustum culling is disabled (frustumCulled = false).
Depth testing is disabled for the materials (depthTest = false).
Render order is set to a high value (renderOrder = 9999).

I've tried various adjustments, such as enabling logarithmic depth buffering and ensuring all objects remain within the clipping planes, but the problem persists.

I have two attachments where the blue mesh curve has a discontinuity in one of the images which is because of the scaling.

Any insights, suggestions, or solutions would be greatly appreciated!

klaus.krpano please look into this.

Thank you in advance for your help!

klaus.krpano thank you for your quick response klaus, really appreciate it!

regarding the solution you proposed, i have already tried setting the depthbuffer range to the highest available and yet the THREE.js meshes vanishes after a certain scaling factor. right now this is the only issue I am facing and a solution to this would be extremely appreaciated!

thank you!

klaus.js

sharing the drive link which contains the file. right now, the scale factor inside the code is scaled upto my requirement but causes the meshes to get clipped off at farther distances.

klaus.krpano any update? The above message has the code file I am facing the scaling issue with. The file is named klaus.js

Thanks!

klaus.krpano after making the suggested edits you mentioned, isn't it possible to have a larger scale value?

because I have already modified the display.depthrange setting to the max possible value as per the documentation.

thanks!

klaus.krpano After trying the suggested fixes, including modifying the display.depthrange setting, I still can't resolve the issue. Could you clarify or provide further guidance please? A solution to this problem would be really helpful for me.

if you need any additional files from my side, please do let me know.

thank you!

Hi team, thank you for your response, but I think I have identified the issue. it seems the display.depthrange of near had to be set to a very small value. Previously, I had experimented the near values between from 0.1 to 0.0001 but turns out the near value decimal had to be shifted to 10^-12 at least, for the meshes to be visible.

Could you please provide an explanation as to why such a low value is required? Understanding this would help me troubleshoot similar issues in the future.

thank you.