- This topic has 8 replies, 5 voices, and was last updated 2 years, 4 months ago by
.
-
With the major changes in 4.0, there are naturally still some things to resolve and improve.
- Show Outline on Hover only works when one is very close to the object. There was no such problem with outlines in former Verge3D versions. (Even when using an environment dome and the camera is outside the dome, there was no such problem.)
- If one enables LZMA compression, HDR images get gzipped. This doesn’t work well with image compression and decompression.
I had to disable image compression for HDR image files otherwise my verge3D applications wouldn’t render. (See my former post with the error log.) - JPG and even PNG images get larger when compressed to KTX2. Why should I use image compression when it actually makes the image file larger?
- I don’t use AO with puzzles. I only enable Eevee AO in Blender. But I get the following error message in my browser console:
v3d.App: wrong post-processing effect “ao”. Luckily, Eevee AO renders just fine in the browser although everything seems to have a bit too much contrast. (see former post with the error logs) - The fog is much brighter than in version 3.9.1. (see my former post)
- Tracking constraint is not as precise as in version 3.9.1. everything seems to sometimes lag. Eyetracking for my Gargoyles was working great in 3.9.1 and everything worked smoothly. (I included some screenshots for comparison.)
- In Firefox I get this message: WEBGL_debug_renderer_info is deprecated in Firefox, and will be removed. Please use RENDERER.
So in Firefox, we can’t print the render info anymore. Can this be fixed?
The following is purely a Firefox issue:
In Firefox the KHR_parallel_shader_compile extension is not supported. Do you know why this is so? Any idea if it will be supported in the future?
I hope things can be resolved in future updates,
Simonehowever we could not reproduce it on our own scenes. It’s also possible the color of the previous version was not correct.
as it appeared, the cause of this issue is in the chosen color managment method. If you choose “Filmic” instead of “Standard” you can reproduce this issue )))
p.s. as for me, I don’t even remember why I’ve chosen “Filmic” (I’m nearly sure it was set by default). In 3.9.1 and older it had no noticable visual effect. There was no any visual difference between
AA AutoandAA MSAA16…p.s.
The fog is much brighter than in version 3.9.1. (see my former post)
in this case the problem is really in the fog density ))) reducing the density from 0.28 to 0.05 and switching
app.postprocessing.toneMapPass.material.toneMappedtofalsereturn nearly the previous look. something changed in the addFog() function…Puzzles and JS coding. Fast and expensive.
If you don’t see the meaning in something it primarily means that you just don’t see it but not the absence of the meaning at all.
The screenshots got somehow lost when I edited my post. Sorry to add them only now.
I understand that meanwhile some issues have been fixed in 4.0.1.I have sent a test file to Yuri and more issues will be corrected.
As for the eye-tracking issues, I switched from using Damped Track constraint to Track To constraint, which works well for Blender 3.2 and Verge3D 4.0(.1).
(I made a separate post on this for Blender users.)ETC1 compression indeed works well, files get smaller and give quite good visual results. I’m curious how it will compare to WebP, which will be supported in future updates.
Simone
- You must be logged in to reply to this topic.