This is a cool demo!

I found that I can use more complex models without much frame rate loss. Only when the models get a bigger size, the frame rate gets down, probably because more pixels are drawn.

I get steady 50fps and 2.1ms with 4000 entities on my PC

17k entities with multiple skins but simple meshes, dynamic flag REset, no movement attached.... 4 fps. That's awfully slow.

no instancing is the simple reason

17k entities where around 16k are unique.

I'm curious as to what kind of situation you'd need 16k unique entities on-screen.

Jibb

Mesh generation algorithms.

If most of them are unique and they're generated by code, couldn't you put a lot of them into a single mesh?

And mesh generation is kinda vague... why do you need so many unique meshes on-screen?

I would've assumed it was related to A3, but I wouldn't have thought any A3 projects would be that complex.

Jibb

It is related to A3 and complex is relative.

They region concept of a raycaster just is not as simple to handle. If you remove lighting completely, then meshes can be merged, otherwise it gets really tricky and you'd have to fix that via some complex mechanism to split material definitions into many other materials in order to get the lighting effect.

And you lose the feature to modify single regions as it was possible in A3.

But... different topic.

I'll take your word for it.

(sorry Superku for going offtopic)

Jibb