The "catching up on tile delete queue" doesn't justify an ALERT message.

It happens regularly during normal operation (ufo!) and only informs about
unfortunate, but known and deliberate behavior. The user can't do anything
about it, anyway. And finally: flooding the console with this message does
only *add* to fgfs' sluggish performance and makes every other message
go unnoticed.

diff --git a/src/Scenery/tilemgr.cxx b/src/Scenery/tilemgr.cxx
index c0676ad7078ac0ef3dcbf934e06a298549e2c106..e502f55bdbe18e73438c2c4e9e33f14d9c670d9a 100644 (file)
--- a/src/Scenery/tilemgr.cxx
+++ b/src/Scenery/tilemgr.cxx
@@ -359,8 +359,8 @@ void FGTileMgr::update_queues()
                 // get real serious and agressively free up some tiles so
                 // we don't explode our memory usage.
 
-                SG_LOG( SG_TERRAIN, SG_ALERT,
-                        "Alert: catching up on tile delete queue" );
+                SG_LOG( SG_TERRAIN, SG_WARN,
+                        "Warning: catching up on tile delete queue" );
             }
 
             FGTileEntry* e = delete_queue.front();