The game is very laggy(again)

[MikeyJY]

This is a continuation of:

Random frame drops on start

Thanks, now I have only 2 collapsed errors that I can’t solve but no lag anymore, thank you.

I decied to create another thread because I know that on older thread I will receive no answer.

I solved all errors and now I have only two:

Same random behaviour. I don’t know what to do.

Profiler on laggy playmode:

Profiler on no-lag playmode:

I noticed that when there is no lag the CPU is 11 - 12 ms. When is lag the CPU is 700 - 800 ms and 600 are for “EditorLoop”. I don’t understand why is RANDOM?

[MartinTilo]

You should switch the Profiler target from Playmode to Editor to see what is going on inside the EditorLoop. The difference could be down to a number of things, but we can only guess as long as you only show cropped screenshots of the Hierarchy or Timeline view of the Profiler, while Profiling Playmode so that we can’t see the EditorLoop contents. The documentation says as much about the EditorLoop too btw

[MikeyJY]

Thanks, and sorry if I duplicate posts, but as I said no one revisit older threads. The main question is why it has a random behaviour?

[MartinTilo]

New messages make them bubble to the top again. You could have tried that first.

Anyways, no idea why it’s random. It could also be reliable and you just didn’t figure out the factor that makes it trigger. Maybe it’s due to the selection? In one screen you have the terrain selected… I don’t know and can’t tell you anything really from these screenshots, you need to Profile the Editor to get any idea on the what and why. Speculation is not a very effective troubleshooting technique here.

[MikeyJY]

Thanks. A lot of users reported “EditorLoop” causing spikes and all of them received the same answer: “Your game won’t have this spikes when you build it”

[BrandyStarbrite]

@MikeyJY
Hmmm. Looking at the two errors…

I was going to say, that you were probably using the non convex mesh collider, in a way that Unity does not support. Or probably this is a unity bug. But looking at the error, I would say, that you’re either using the non convex mesh wrong, or if you are using it correctly, then this somehow seems to be, an odd unity physics bug issue.

As for the texture rectangle problem, I found this old post.
Check the solution in the last post at the bottom.

Texture rectangle is out of bounds

I got a little burnt out on a project I was working on and decided to work on another one I had not touched in a while. I didn’t have much in the scene, a terrain, some random grass and a tree or two, along with some assorted rocks. I had done the entire map in the regular grass texture that comes with unity. I had a few pathways made with another sandy texture that I got from the Unity downloads section, the one with all the bonus trees and whatnot. I had not touched this project in about 5-6…

This might be a long tiring way to solve that problem, but it might work in your case. Thanks to trickyspark for coming up with this solution.

Hope that helps.