- after viewing collada, while I open a new file, I got a screen of random pixels
I see on the screenshot random pixels under the "open" file dialog. Do they disappear when you close the dialog with "cancel"? Also, after viewing which Collada file?
- fancy_light_spot_shape.x3dv shows a black screen, with a warning : VRML parse error at position 1095, inside "SpotLight" got "effects".
With view3dscene 3.9.0 (or even not-the-latest SVN) it's normal. Like before, everything inside composited_shaders/ is highly development and depends on latest features in SVN. If you don't want to compile yourself, you can get latest version from
http://michalis.ii.uni.wroc.pl/vrmlengine-snapshots/ . You can see some screenshot of their correct rendering in png files inside
https://vrmlengine.svn.sourceforge.net/svnroot/vrmlengine/trunk/papers/compositing_shaders/ .
- chess.x3dv is so slow and makes the program exit without message (I guess access violation)
Run view3dscene.exe from the terminal (console) to see the message. Otherwise, the console disappears when view3dscene exits --- so the message is probably there, you just have no chance to see it

This is an artifact that we use windows console.
This probably goes in pair with crash on cubemap_generated... Which may indicate that the problems lie in FrameBuffer Object (FBO) treatment on this GPU.
Can you test
1. x3d/cubemap_composed2.x3dv
2. rendered_texture/rendered_texture_with_background.x3dv
If we'll confirm that the problem is within FBO usage on this GPU, I can workaround it by disabling FBO for this GPU. Googling a little for your GPU name "Mobile Intel(R) 4 Series Express Chipset Family" and fbo suggests it may be a known problem.
I wonder if the rendering of the 3ds plane is correct.
Yes. The non-perfectly smooth wings are just the way they are in the model.
And fancy shapes, have they lost their textures ?
The result is OK. They are just not textured.
And why is ranshrine so dark ?
Because it's dark

This is a demo for new SVN feature, you should use "View -> Force Shader Rendering" with view3dscene from SVN to see the nice results, if your GPU has good GLSL support.
Here is room parallax rendering.
Note that to actually see the nice bump mapping, in 3.9.0 you have to set "View -> Bump Mapping -> " to some value other than Off. (In SVN, bump mapping is already turned on by default, and is part of our "Force Shader Rendering" pipeline.) Then this room will look much nicer.
The two boxes with shadow does not work correctly. The shadow seems to be drawn over the box from which it comes.
That actually may be correct if you realize that the light source is a point light, and so even the upper box can cast shadows on itself.
That said, some artifacts are possible with shadow maps. They depend on GPU, also the SVN with "Force Shader Rendering" again improves things here. It looks much better on Radeon or NVidia here

, small artifacts just have to be tolerated on some GPUs.
With a certain angle, the house in a glass has some artifacts.
Ah, the transparent glass wasn't propely marked. Fixed, and I also changed and moved this demo to x3d/ subdirectory. VRML 1.0 is very old.
Again, many thanks for testing, and keep it coming

As I mentioned above, I would like to know the results for x3d/cubemap_* and rendered_texture/* models --- exactly which ones fail, which don't. This can confirm that the cause of problems lies in FBO on your GPU, which can be workarounded.