Any ETA on when performance issues will be fixed?

[Tompost]

Errors like this:

19:43:07.731 ERROR PerformanceLogger [Trinity][Performance] Execution of the block NavigateTo took 1959.68ms.
19:43:07.731 ERROR PerformanceLogger [Trinity][Performance] Execution of the block HandleTarget.HandleBasicMovement took 1960.37ms.
19:43:07.733 ERROR PerformanceLogger [Trinity][Performance] Execution of the block HandleTarget took 17323.70ms.
19:43:20.330 ERROR PerformanceLogger [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 11981.75ms.
19:43:20.331 ERROR PerformanceLogger [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 11994.46ms.
19:43:20.332 ERROR PerformanceLogger [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 11995.08ms.
19:43:22.410 ERROR PerformanceLogger [Trinity][Performance] Execution of the block NavigateTo took 1958.55ms.
19:43:22.410 ERROR PerformanceLogger [Trinity][Performance] Execution of the block HandleTarget.HandleBasicMovement took 1959.29ms.
19:43:22.412 ERROR PerformanceLogger [Trinity][Performance] Execution of the block HandleTarget took 14075.54ms.

This has caused my bots to die in HC...

 

[deadlywario0]

performance issues are fine for me, probably just something on your end. What are your PC specs? If your on windows 7 do you have gadgets displaying the current use of your CPU/HDD/GPU?

 

[Tompost]

Normally this is not a problem, but when it stops for 15s and does nothing in HC...

 

[tinyphrag]

This is not something "just on your end" many people are having these issues on computers that have never had these issues in the past. It's something with the latest trinity build.

 

[morfious]

.24 trinity and same issues.. didn't happened before.

 

[Tompost]

Yea, still no update about this :|

 

[ury0005]

For me problem was solved by correcting avoidance resolution.
In present version FindSafeZone works with grid 120 x 120:
> const float gridSquareSize = 2.5f;
> const int maxDistance = 150;
I change it to 20 x 20:
> const float gridSquareSize = 5f;
> const int maxDistance = 50;

 

[gotteshand]

wrong thread whops

 

[deadmeat1]

Maybe you should donate a few hundred dollars to rrrix and he'll work faster. Otherwise the speed is just fine for free work.

 

[Oksehode]

For me problem was solved by correcting avoidance resolution.
In present version FindSafeZone works with grid 120 x 120:
> const float gridSquareSize = 2.5f;
> const int maxDistance = 150;
I change it to 20 x 20:
> const float gridSquareSize = 5f;
> const int maxDistance = 50;

So you just changed those 2 values? What class you playing?

 

[ury0005]

As about me, I'm playing DH. But I believe it will work for any class. This code handles finding of save spots, and my changes reduce number of spots to validate from 14400 to 400. It's better to be less witty, but alive, than wise and dead

 

[zerodisbelief]

For me problem was solved by correcting avoidance resolution.
In present version FindSafeZone works with grid 120 x 120:
> const float gridSquareSize = 2.5f;
> const int maxDistance = 150;
I change it to 20 x 20:
> const float gridSquareSize = 5f;
> const int maxDistance = 50;

I tried it however the issue still persists:

[Trinity][Performance] Execution of the block NavigateTo took 1202.12ms.
[Trinity][Performance] Execution of the block HandleTarget.HandleBasicMovement took 1202.56ms.
[Trinity][Performance] Execution of the block HandleTarget took 1203.80ms.

 

[morfious]

For me problem was solved by correcting avoidance resolution.
In present version FindSafeZone works with grid 120 x 120:
> const float gridSquareSize = 2.5f;
> const int maxDistance = 150;
I change it to 20 x 20:
> const float gridSquareSize = 5f;
> const int maxDistance = 50;

Where do i edit this? FindSafeZone works with grid 120 x 120