View Issue Details

IDProjectCategoryLast Update
0008565Valley 1Bug - GameplayJun 20, 2012 2:27 pm
Reporterjruderman Assigned ToChris_McElligottPark  
Severityminor 
Status resolvedResolutionfixed 
Product Version1.101 ( Post-Launch Series 1) 
Fixed in Version1.103 (Official Hotfix) 
Summary0008565: Minimap lags
DescriptionWhen I first enter a chunk, the minimap is entirely gray. I have to wait a second before the area near me is filled in.

Similarly, if I jump down, I have to wait a second for the area near my new location to be filled in.

This is a new problem; it did not occur in earlier versions.
TagsNo tags attached.
Internal WeightNew

Activities

Chris_McElligottPark

Jun 15, 2012 4:48 pm

administrator   ~0025856

This is by design, it's not really a bug. On large maps, doing a single refresh of the minimap takes about 12-16ms on a latest-gen sandy bridge i7 CPU. On smaller maps, 4-6ms.

So what I introduced was a rule where it couldn't do this more than once per second, since especially on lower CPUs that cost in ms could be 3x to 10x more than what shows on my machine (depending on just how old we're talking).

I suppose potentially it could be reduced to every half second, but I'm not sure this would be a great thing.

TechSY730

Jun 15, 2012 5:10 pm

reporter   ~0025857

How about allowing it to refresh more often (aka, pace less aggressively) for small maps, but have it pace itself at the current rate (or slightly less aggressively, as a second seems rather long) only for large maps.

Of course, defining small and large may be tricky.

jruderman

Jun 15, 2012 5:23 pm

reporter   ~0025858

Perhaps you could force a refresh upon entering the room, and upon coming within X pixels of a "non-explored" portion of the minimap?

NyQuil

Jun 15, 2012 6:47 pm

reporter   ~0025862

I'd go with the refresh on the chunk changing. Or let the frequency be determined in the options menu.

Chris_McElligottPark

Jun 20, 2012 2:27 pm

administrator   ~0025988

Thanks!

* The frequency of how often the minimap updates is now based on how big the chunk in question is; in order to avoid lag, we previously had it set to 1 second between minimap updates. However, in smaller chunks (actually most chunks) that really was excessive.
** The new logic makes it so that in most chunks it will update more like every half second, and in smaller chunks it will update every quarter second if need be. Only the really excessively large chunks still update on a 1-second interval.

* For all chunks, the minimap now updates as soon as you enter the chunk, regardless of how long it has been since the last time you entered a chunk.

Issue History

Date Modified Username Field Change
Jun 15, 2012 4:41 pm jruderman New Issue
Jun 15, 2012 4:48 pm Chris_McElligottPark Note Added: 0025856
Jun 15, 2012 4:48 pm Chris_McElligottPark Assigned To => Chris_McElligottPark
Jun 15, 2012 4:48 pm Chris_McElligottPark Status new => feedback
Jun 15, 2012 5:10 pm TechSY730 Note Added: 0025857
Jun 15, 2012 5:23 pm jruderman Note Added: 0025858
Jun 15, 2012 5:23 pm jruderman Status feedback => assigned
Jun 15, 2012 6:47 pm NyQuil Note Added: 0025862
Jun 20, 2012 2:27 pm Chris_McElligottPark Internal Weight => New
Jun 20, 2012 2:27 pm Chris_McElligottPark Note Added: 0025988
Jun 20, 2012 2:27 pm Chris_McElligottPark Status assigned => resolved
Jun 20, 2012 2:27 pm Chris_McElligottPark Fixed in Version => 1.103 (Official Hotfix)
Jun 20, 2012 2:27 pm Chris_McElligottPark Resolution open => fixed