dragosburian

Hello,
I made a simple example with the issue. Also I have pasted an image of how it work in blender if I copy the element and rotate it by 10 degrees each time, just like how it happens in verge(only that in verge it looks that it repeats). Thank you!

Hello Mikhail,

For our use case we have 26 scenes, with around 500 objects in the scenes, which depending on users’ input can be combined (the scenes, and the objects within). Items scale,move, morph, appear/disappear depending on each selected situation. The number of combinations is literally in the millions. Baking AO is absolutely impossible in our use case(and we have other similar use cases present and future), both because it would take a LOT of time, and also technically because loading so many maps would use too much Vram on users’ devices. For instance, we can have a post that can have house numbers on it from 1 to 9999, we can’t make 10000 AO maps for that :).

I do understand that addressing the quality of the AO is a very difficult task, but for many users it is very important and for big projects baking is out of the question.

Hello Alexander,

There are 2 problems with the approach in our use case:
1)The models we append are very complex and there are more materials to them->but the material re-assignment is sorted by me in js so that one is fixed.
2)The appended models also have morphed objects in them, and sometimes morphing stops working or materials do not show properly on them when we assign a material that is already in the scene. The only solution I found to it is make a new material for them, but that beats our purpose since we want to make the scene lighter.

I will do some fps testing and get back to you on the first issue.

Dragos

Also of high importance, could appending scenes be done in such a manner that if the material already exists in the first scene, the second one will just use that instead of doubling it?

Kind regards,
Dragos

The models have morph targets and get loaded in pieces, depending on user input(so as not to load all geometry whether needed or not). Because we don’t want to load the same texture maps multiple times(appending scene makes new materials even if the same material was loaded from another appended scene), I use one scene that always gets appended to load materials, the other scenes have placeholder materials and the intention is to change those materials with the intended one from the main scene. This works with single-material objects, object with multiple materials fail to load them and turn black.

Now that I test it thoroughly, I can say FXAA is mildly better for aliasing between geometry, if it’s between geometry and transparent background, aliasing is much harder in the case of MSAA.