CODEWITHSUNDEEP
c#unity-game-engine
dylan20932
dylan20932

Reputation: 21

Why is my transform.position setter called via OnMouseDown() so slow?

I have the following method in my code:

private void OnMouseDown()
{
    cube.transform.position = new Vector3(0, 1, 0);
}

When clicked on the gameObject, this method is called. It takes long to change the position of the cube (not more than a second, but still long, at least half a second). It does affect the user playing experience.

If I don't change the position of the cube, but for example its material, it is still slow. So I do know that this doesn't have to do with the line in my OnMouseDown() event.

Note however that I do have around 35 imported 3D meshes in my Scene, as well as over 50 primitive game objects. Does this have anything to do with the method being slow? Because when I make an empty Unity project with just 2 gameObjects, the method is fast.

Is it because of my full scene? Any ideas? Thanks!

If someone knows how to speed it up as well, I'd love to know!

EDIT: If I remove all my 3D meshes, the method is fast...

Upvotes: 1

Views: 217

Answers (2)

Hamza Tahir
Hamza Tahir

Reputation: 92

solution

Try to check if there are heavy materials are used that can slow the procedure. The game becomes slow when the objects are being added in the project and it destroy the overall efficiency of the game . It happens with me when i used too heavy models in the project the overall speed of the game is decreased . I replaced them with lightweight models of truck and issue was resolved .

Upvotes: 0

zambari
zambari

Reputation: 5035

Unless your transfom tree is hundereds of children deep, this should be pretty much instant, its one of the things Unity has been designed to do quickly, so I think this has to do with the meshes you import. The should not have too many verticies, too many materials, and too many objects. You can try to go through you objects with a 3D editor package (blender?) and combine the chunks into single objects.

If unity lags when you move an object, it may mean it has too many individual transforms to process. If your scene is intense you can gain a lot of performance by 'baknig' it, combining individual objects into larger meshes (those live on the gpu and cost gpu time not cpu time).

It is also possible that one or more of the meshes you imported has too many verts/triangles. If you currently have 10fps you may want to target having lighter meshes, and as few seperate GameObjects as possible (ideally you want the environment to be just a few combined meshes (to enable culling), not thousands of objects)

Upvotes: 1

Related Questions