Ambiera ForumDiscussions, Help and Support. |
|
|
|||||
|
Why coppercube lag so much when i import complex mesh in copper cube?!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! I have pc with good specs but still lag |
||||
|
Can you provide some more details please? Which mesh are you using? Which platform are you using as a target - WebGL/DirectX/OpenGL? Are you using terrain, animated mesh or just a static mesh? Which file format for the mesh are you using? How many separate textures does the mesh use? etc.. Coppercube runs smoothly on my mid-range laptop when I import a textured photogrammetry 3D scan scene with millions of polygons. Photo-realism with no lag. Main thing that introduces lag for me is using dynamic lighting, real-time shadows and multiple "collide-when-moved" calculations on a complex mesh. To prevent slow-down/lag, whenever I use a very complex mesh, I create a second simplified version of the mesh to use as a "collision mesh". A collision-mesh has the same basic outline as the complex mesh, but it's made of very simple geometry (invisible cubes/planes), with as few polygons as possible - then I turn off collision for the complex mesh. |
||||
|
as @Vp, has mentioned, it depends on the model type and texture data, most of the time coppercube handles the models pretty decently. |
||||
|
i am importing static mesh with obj and some times gltf formats |
||||
|
CopperCube can only handlesao many polygons - depends on your system but I don't go above 500k polys myself as starts to slow down and even 250k can slow it down some... after polygons, dynamic use shadows is the biggest performance hog of all....then normal maps and collisions with complex geometry... |
||||
|
|
){kind=link}