BD34D commented

Replying to [#2420 LZ compromised]:

This bug occured every time I went through the campaign. In away missions after Beta 05 (CAM_2C, the one where you encounter ripples for the first time) certain parts of the map stick out from the fog of war.

These parts lie within the NW quadrant of the map. Every away mission has different "highlighted" spots, but they remain the same if I load the same mission several times.

About 5-15 seconds into the mission I see
Error! (Check your logs!): [visRemoveVisibility] Assert in Warzone: ../../../src/visibility.c:289 (psTile->watchers[psObj->player] > 0), last script event: 'N/A'

Here are the spots for every mission this happens in:

Beta 06 (SUB_2DS)
http://img840.imageshack.us/img840/5018/wz210020101219230014sub.jpg

Beta 07 (SUB_2_6S)http://img840.imageshack.us/img840/5018/wz210020101219230014sub.jpg

Beta 08 (SUB_2_7S)http://img695.imageshack.us/img695/3761/wz210020101219230223sub.jpg

Beta 09 (SUB_2_8S)
http://img842.imageshack.us/img842/7605/wz210020101219230316sub.jpg

The funny thing is, if I load Beta 05 (CAM_2C) at this point, I see these spots too. They don't reveal any units or buildings (ripples are visible due to my CB sensor, I figure), but they're there:

http://img440.imageshack.us/img440/6819/wz210020101219230741cam.jpg

Same thing is happening to me, in the first campaing, when the 'away missions' start, but only on the main map (not on the away maps).
I'm playing the latest version (2.3.6) on Windows 7 (no compatibility mode active, and not executing as administrator) and Radeon x1650 Pro as graph card.
On the log, these two lines repeat over and over. The only things that change are tt:tt:tt (the time when it was logged), x and y (the coordinates).

error   |tt:tt:tt: [visRemoveVisibility] Not watching watched tile (x, y)
error   |tt:tt:tt: [visRemoveVisibility] Assert in Warzone: ../../../src/visibility.c:289 (psTile->watchers[psObj->player] > 0), last script event: 'N/A'

I'm using the Comodo Internet Security, and these days it is presenting an odd behavior, so it may be also at fault, I'm not sure.

BD34D changed _comment0 which not transferred by tractive

BD34D changed _comment1 which not transferred by tractive

Per changed status from new to closed

Per changed resolution from `` to later

Per commented

Probably worked around by commit 276fa53 in 2.3; probably remains in master, campaign needs proper testing there anyway, so closing.