Safety0ff uploaded file savegame.zip (194.5 KiB)

skoondi commented

I have the same problem with the a checkout of trunk from last night, I can also attach a save game if that would be useful.

Console output:
[{
sunny@sunny-desktop:~/warzone$ src/warzone2100
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
info |12:25:21: [rebuildSearchPath] * Failed to remove path /home/sunny/.warzone2100-trunk/ again

skoondi commented

This bug is a show stopper as far as the campaign goes, it happens every time, no way around it, occurs as the transport lands on the mission where you first get to use mortars.

error   |11:51:38: [mapTile] mapTile: y value is too big (16,65) in 64x64
error   |11:51:38: [mapTile] Assert in Warzone: map.h:317 (y < mapHeight + 1), last script event: 'N/A'
warzone2100: map.h:317: mapTile: Assertion `y < mapHeight + 1' failed.

skoondi uploaded file warzone2100.gdmp-q447I6 (24.4 KiB)

zimboptoo commented

Same problem, different mission. At the beginning of Beta 5 (take out the nuclear reactor), right as the transport leaves the home base map, the game crashes to desktop.

Running Ubuntu 9.10 on a x64 machine, twinview, nVidia GeForce 6200 with updated vendor drivers.
Warzone version TRUNK [9749], no cheats/mods, default everything except screen size.

Excerpt from the crash log:

Dump caused by signal: SIGABRT: Process abort signal
Log message: error   |12:12:52: [scrRandomiseSeed] A script is trying to set the random seed with srand(). That just doesn't make sense.
Log message: error   |12:12:52: [mapTile] mapTile: x value is too big (81,91) in 64x64
Log message: error   |12:12:52: [mapTile] Assert in Warzone: map.h:316 (x < mapWidth + 1), last script event: 'N/A'

As it says, "That just doesn't make sense."

skoondi commented

Well I wanted to keep playing the campaign so I had a little mess with the code, as the transport comes in to land the y value gets to a maximum of 72. I don't know enough about what's going on to fix that so I just made the assert more lenient so I could get on with my game.

zimboptoo commented

See also: #1546

Samowar commented

I'm pretty sure this was caused by [8900]. The "observed tiles" from the old map are iterated over and are checked against the coordinates of the new map.

Per changed status from new to closed

Per set resolution to fixed

Per commented

(In [9809]) Forward port a fix from 2.3 for bad visibility data when changing missions
that closes #1546 and closes #1524

Git SVN Gateway <gateway@...> commented

(In Warzone2100/warzone2100@018b646) Forward port a fix from 2.3 for bad visibility data when changing missions
that closes #1546 and closes #1524

git-svn-id: https://warzone2100.svn.sourceforge.net/svnroot/warzone2100/trunk@9809 4a71c877-e1ca-e34f-864e-861f7616d084

Git SVN Gateway <gateway@...> commented

In Warzone2100/warzone2100@018b646:

#CommitTicketReference repository="" revision="018b64662c3523584794b0c6c061191303074151"
Forward port a fix from 2.3 for bad visibility data when changing missions 
that closes #1546 and closes #1524


git-svn-id: https://warzone2100.svn.sourceforge.net/svnroot/warzone2100/trunk@9809 4a71c877-e1ca-e34f-864e-861f7616d084