Skip to content
This repository has been archived by the owner on Apr 17, 2022. It is now read-only.

Campaign Beta 8 becomes unplayable after about five minutes. #3403

Closed
wzdev-ci opened this issue Apr 11, 2012 · 17 comments
Closed

Campaign Beta 8 becomes unplayable after about five minutes. #3403

wzdev-ci opened this issue Apr 11, 2012 · 17 comments

Comments

@wzdev-ci
Copy link
Contributor

resolution_fixed type_bug | by Searge-Major


About five minutes into the mission, when the Collective tanks start advancing on my positions, the game becomes incredibly slow and jerky, making gameplay impossible. The possible cause for this effect is the fact that when I make an attempt to play anyway, whether by slowing down the game to 1/40 or lower, the game generates enormous log files, the attached one when uncompressed was 188,000 kilobytes.


Issue migrated from trac:3403 at 2022-04-16 09:44:17 -0700

@wzdev-ci
Copy link
Contributor Author

Searge-Major uploaded file WZlog-0408_142529.7z (1000.2 KiB)

Log

@wzdev-ci
Copy link
Contributor Author

Searge-Major uploaded file Beta 8.tar.gz (68.4 KiB)

Save game at the start of beta 8

@wzdev-ci
Copy link
Contributor Author

vexed changed priority from normal to major

@wzdev-ci
Copy link
Contributor Author

vexed changed milestone from unspecified to 3.1

@wzdev-ci
Copy link
Contributor Author

vexed commented


Well, you were hit with asserts.

For the savegame, once the transporter is launched, it crashes out here.

@wzdev-ci
Copy link
Contributor Author

Searge-Major uploaded file Midgame 01.gam.tar.gz (106.9 KiB)

A few minutes into the game. Don't know if it'll help, but thought I'd post it anyway.

@wzdev-ci
Copy link
Contributor Author

Searge-Major commented


I never had any issues with the transporter, but my computer could have just been taking a while to take up the strain.

If there's anything else I need to post, just let me know. :)

@wzdev-ci
Copy link
Contributor Author

crass commented


I have the same issue but on level 2.
The game got really slow making it unplayable with a huge log file of over 200 megs!

@wzdev-ci
Copy link
Contributor Author

Hysteresis00 commented


I have the same error in campaign beta 8. Initially encountered on 3.1beta7 so I upgraded to 3.1beta8 and still the same issue, even from a new saved game.

Log file entries that are repeated endlessly:

info    |07:17:39: [mapTile:434] Assert in Warzone: map.h:434 (x < mapWidth + 1), last script event: 'N/A'
info    |07:17:39: [mapTile:435] mapTile: y value is too big (74,85) in 64x64
info    |07:17:39: [mapTile:435] Assert in Warzone: map.h:435 (y < mapHeight + 1), last script event: 'N/A'
info    |07:17:39: [map_Height:1367] map_Height: x value is too big (75,85) in 64x64
info    |07:17:39: [map_Height:1367] Assert in Warzone: map.cpp:1367 (x < world_coord(mapWidth)+(1<<7)), last script event: 'N/A'
info    |07:17:39: [map_Height:1368] map_Height: y value is too big (75,85) in 64x64
info    |07:17:39: [map_Height:1368] Assert in Warzone: map.cpp:1368 (y < world_coord(mapHeight)+(1<<7)), last script event: 'N/A'
info    |07:17:39: [map_Intersect:1184] map_Intersect(): map Bounds 9600 10991, 9748 4750 -> 9600,10991,9634,11008
info    |07:17:39: [map_Intersect:1184] Assert in Warzone: map.cpp:1184 (tileX>=0 && tileY>=0 && tileX<mapWidth && tileY<mapHeight), last script event: 'N/A'
info    |07:17:39: [map_Height:1367] map_Height: x value is too big (75,85) in 64x64
info    |07:17:39: [map_Height:1367] Assert in Warzone: map.cpp:1367 (x < world_coord(mapWidth)+(1<<7)), last script event: 'N/A'
info    |07:17:40: [map_Height:1368] map_Height: y value is too big (75,85) in 64x64
info    |07:17:40: [map_Height:1368] Assert in Warzone: map.cpp:1368 (y < world_coord(mapHeight)+(1<<7)), last script event: 'N/A'

@wzdev-ci
Copy link
Contributor Author

vexed changed priority from major to blocker

@wzdev-ci
Copy link
Contributor Author

vexed commented


Bumping to blocker to keep better track of campaign issues.
Thanks for the savegames.

@wzdev-ci
Copy link
Contributor Author

vexed changed status from new to closed

@wzdev-ci
Copy link
Contributor Author

vexed changed resolution from `` to fixed

@wzdev-ci
Copy link
Contributor Author

vexed commented


Let's try to stop checking for tiles when we are offscreen via a Transporter.

fixes #3403

  • Changeset: [/changeset/9775d0c4f66f80d6378cee0dc9ea31d3cdfe5708 9775d0c4f66f80d6378cee0dc9ea31d3cdfe5708]
  • URL: [9775]d0c4f66f80d6378cee0dc9ea31d3cdfe5708

@wzdev-ci
Copy link
Contributor Author

vexed commented


Let's try to stop checking for tiles when we are offscreen via a Transporter.

fixes #3403

  • Changeset: [/changeset/9775d0c4f66f80d6378cee0dc9ea31d3cdfe5708 9775d0c4f66f80d6378cee0dc9ea31d3cdfe5708]
  • URL: [9775]d0c4f66f80d6378cee0dc9ea31d3cdfe5708

2 similar comments
@wzdev-ci
Copy link
Contributor Author

vexed commented


Let's try to stop checking for tiles when we are offscreen via a Transporter.

fixes #3403

  • Changeset: [/changeset/9775d0c4f66f80d6378cee0dc9ea31d3cdfe5708 9775d0c4f66f80d6378cee0dc9ea31d3cdfe5708]
  • URL: [9775]d0c4f66f80d6378cee0dc9ea31d3cdfe5708

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Aug 4, 2012

vexed commented


Let's try to stop checking for tiles when we are offscreen via a Transporter.

fixes #3403

  • Changeset: [/changeset/9775d0c4f66f80d6378cee0dc9ea31d3cdfe5708 9775d0c4f66f80d6378cee0dc9ea31d3cdfe5708]
  • URL: [9775]d0c4f66f80d6378cee0dc9ea31d3cdfe5708

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant