lgl-tracer-renderer / lgl-tracer-renderer.github.io Goto Github PK

There appears seams on the edges of repeating textures.
To reproduce:
Use the viewer at https://lgltracer.com/viewer/index.html
Unzip and drop the model:
Smeg-Oven-CPF9GP-YW.zip

The seams appear on the repeating edges - The normal maps is flat and it does not show up in other gltf viewers:

Little feedback on the new version, I put my project aside for about 1 month, so I don't know since which update these bugs arrived.

I have a problem when importing an object, sometimes getIndex() returns null, so the following line crashes.
new Uint32Array(***.getIndex().array), ***.STATIC_DRAW);
and I have no rendered object. If I do a test, I have my objects.

Also, objects with refractions look much too black, dark compared to before (1.0.6 or 1.1.0, I don't remember)

Thank you

I can't update materials without having to use the renderer.buildScene(scene, camera) function
I tried renderer.needsUpdate=true, without success.
My goal is not to calculate the BVH unnecessarily...
thanks

Could you support this extension ... ?[TextureTransformTest](https://github.com/KhronosGroup/glTF-Sample-Models/tree/0bc2ad7535aba4e16fb1afba1f85fd827bbbea6d/2.0/TextureTransformTest

Currently the sample glTF, renders like this, in LGLTracer/viewer ...

whereas, it should look like this, when KHR_texture_transform extension is supported...

KhronosGroup/glTF-Sample-Models#177

Feature requests for lglTracer

and future versions may be updated according to the number of demanders (but there will be no clear implementation deadline)

1.KHR_texture_transform extension support

#15
#18

2.Vertex colors support

#3

3.Mesh instancing support

#6

If I load an environment map and set the scene environment like this:

scene.environment = loadedTexture,
scene.background = null;

and I build the scene afterwards it still shows the environment map as the background.
I just need the env map for the lighting and want to use a black background instead.

Am I missing any other setting here?

Can you add support for MeshOpt compression in the glTF loader ?

Here is an example:
https://github.com/zeux/meshoptimizer/blob/master/demo/pirate.glb

This currently gets stuck during the building phase.

Seems LGLTracer currently ignores vertex colors / renders them as white.

The model actually contains vertex colors:

Would be great if this was supported to be able to render more models correctly that were loaded with gltf (which supports vertex colors)!

I am implementing a use case wherein I create a scene using WebGLRenderer and then switch to LGLTracerRenderer just to get the final render of the scene. Both are rendered on separate canvases on the browser.

In the application, I am able to constantly switch between the WebGLRenderer/LGLTracerRenderer and have a separate scene object that is used for each of them. The problem is that when I switch to LGLTracer and back to the WebGLRender the whole application slows down like crazy even when I don't render the LGLTracer's scene.

Could this be because of the load on the GPU, where the memory created for LGL is not cleaned up( Both on RAM/GPU)? In another word how do we clean up all the data that is created by LGL when I exit the mode ?

Any help regarding this would be invaluable.

A material in the attached model is rendered incorrectly when using LGL-Tracer.
The model: https://github.com/LGL-Tracer-Renderer/LGL-Tracer-Renderer.github.io/files/8356457/lglTracerBugs.zip
Drag this into https://lgltracer.com/editor/index.html and toggle between the modes.

Expected (without raytracing):

Actual (with raytracing):

Edit: seems to be related to material tiling. Is that supported?

Seems that when denoising is on, some materials/objects cause black halos/splotches around objects:

This bug reproduces with this model when it's dragged into https://lgltracer.com/editor/index.html and denoising turned on:
lglTracerBugs.zip

Might be related to objects behind other objects? Gets worse from specific camera angles:

ToFix

Seems mesh instancing isn't supported right now, would be nice if the docs could mention that somewhere :)

Currently understanding which things work/don't work is pretty much guesswork, e.g.

• seems AmbientLight is unsupported
• seems LDR environment maps (non float) are unsupported

AmbientLight would be great as a fast alternative to a sky, where simply a color is emitted.
Same for LDR envs, I understand HDR is better and yields higher quality but sometimes there's only LDR for texture size.

It's awesome that LGLTracer autoconverts to traceable materials!
Would be great if each of the new materials would hold a reference to what it was previously, and there was a method to restore original materials.

This would be useful in apps where pathtracing is optional and the user can switch back and forth between "fast" and "pretty".
(right now switching back breaks the WebGLRenderer because of the different materials)