Recently they moved rendering to separate thread (finally!), engine is indeed faster, but stability wen from bad to abyssmal. And it was nothing exotic, it was situation which any big project will encounter.Įach release Unity is less and less stable, bug fixing is slower and slower and they still adding suport of other and other platforms and keeping support of ancient HW and DX, so it is logically going worse and worse. I reported out of memory crash bugs with step by step reproduction and after 1,5 year no fix. Unity team totally ignores bug reports regarding this (and we were not alone, everybody with large project experienced same issues). Small projects are working well (so this is reason why community have so much fanboys), but huge are disaster. Until recently it wasnt even possible to bake oclussion for complex scene (crash). Umbra occlusion system is not properly working after cca 2 years after release (crashes, ocluded scene is slower than not ocluded.). Official asset server is corupting data, it crashes.(it is aditional $500 plugin).

Memory leaks almost in everything, shadow artefacts and blinking in deffered mode.Our world builders had out of memory crash 20x per hour (it was special world building project only with assets, not a line of custom code). The biggest issue is stability with large projects. Thanks.Ĭan you comment on the main reasons for switching from Unit圓D to UNIGINE ? Unit圓D seems to be quite a very powerful engine. Is this approach correct, or there is aleady some solution? Or are you planning some update of import process, which would allow to automatically assign material, if requested texture (and so material) is already in project library? Indeed automatical process is not 100% reliable, but it is very easy to manually correct some exceptions (particular object needs some exotic shader and so it needs its own material for existing texture), instead of manually doing all asigning. mat file with material library and so we dont have to create materials by hand (98% will be diffuse+normal anyway, so exceptions can be easily handled manually) and by having node we dont have to assign material manually. Probably by small modification we can achieve merging of this.

I ve noticed functionality 'node export' in 3ds max exporter, which generates node file and. We are missing functionality of automatical assigning materials to objects, it is very time consuming to manually create material for each each texture and assigning it to object. We have 2500+ meshes, 7000+ textures, etc.so lots of work.

We are now importing our asset library to Unigine.

Unity fbx exporter script support