Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#2573 closed defect (fixed)

Warnings flood when playing with the camera

Reported by: serveurix Owned by: wraitii
Priority: Should Have Milestone: Alpha 17
Component: Core engine Keywords:
Cc: Patch:

Description

On many maps when I play with the camera (mostly when I deactivate "restrict camera" in the dev overlay and go over an area of a different altitude), the screen is filled up with "warning: SpatialSubdivision Query too large. Results truncated." This is particularly annoying since you can't prevent those messages to be displayed, and, you know, when you play with the camera, usually it's to take captures...

One simple way to reproduce this bug is to choose the first acropolis skrimish map, reveal the map, unrestrict the camera, and move to the center of the map.

Attachments (1)

0001-Revert-r13854-spatial-subdivision-optimisations.patch (45.4 KB ) - added by Philip Taylor 10 years ago.

Download all attachments as: .zip

Change History (10)

comment:1 by leper, 10 years ago

IIRC this is related to #2430.

in reply to:  1 comment:2 by serveurix, 10 years ago

Replying to leper:

IIRC this is related to #2430.

Ok, so the problem existed before, and the warnings appear because of the new Spidermonkey ?

comment:3 by leper, 10 years ago

No, this is not related to JS at all. It occurs because r13854 introduced a fixed limit for SpatialSubdivision queries, and even though r13888 bumped that fixed limit #2340 is still a better solution to that IMO.

comment:4 by Josh, 10 years ago

These are because of r14532 which starts requesting two times more data from SpatialSubdivision if the camera is unlocked. (See session.xml changes)

in reply to:  3 comment:5 by historic_bruno, 10 years ago

Replying to leper:

No, this is not related to JS at all. It occurs because r13854 introduced a fixed limit for SpatialSubdivision queries, and even though r13888 bumped that fixed limit #2340 is still a better solution to that IMO.

Can today be the day someone reverts them? Hopefully there wouldn't be too many conflicts. It should have been done for A16.

comment:6 by Philip Taylor, 10 years ago

Something like that? (Just did a revert and fixed the conflicts in the obvious ways. Not tested much, and not tested performance at all.)

comment:7 by wraitii, 10 years ago

Owner: set to wraitii
Resolution: fixed
Status: newclosed

In 15617:

Revert RedFox's changes to Spatial subdivisions in the simplest possible way (hopefully won't cause OOS, but at least we'll get reports). Fixes #2573, Refs #2430 . There probably are opportunities to remove more things.

comment:8 by wraitii, 10 years ago

Milestone: BacklogAlpha 17

comment:9 by Stan, 10 years ago

Will that have an impact on performance ?

Note: See TracTickets for help on using tickets.