-
Notifications
You must be signed in to change notification settings - Fork 0
Crash on changing repaire unit from wheels to half tracks #523
Comments
anonymous uploaded file Error report |
anonymous uploaded file Call stack |
anonymous uploaded file Savegame |
Buginator commented What language are you playing the game? |
Buginator changed status from |
Buginator set resolution to |
Buginator changed milestone from |
Buginator commented Will reopen when I get the requested info. |
Raffael Joliet <raffael.joliet@...> commented Replying to Warzone2100/old-trac-import#523 (comment:1):
I installed it in german but changed to english (by menu) because i assumed some special characters to cause problems first. Problem is the same |
Buginator changed resolution from |
Buginator commented (In [7486]) Check if the unit has weapons, before trying to see what weapons they have. Fixes #523 |
Buginator commented Thanks for the save game, I fixed the issue. |
Buginator commented (In [7487]) Check if the unit has weapons, before trying to see what weapons they have. Fixes #523 |
Buginator commented (In [7488]) backport [7481]-[7487] On certain mission types (limbo & expand) we still have valid map data that is saved in-between the sub missions, and the radarblip drawing code didn't filter things that are outside the current scroll limits of the map.Excise code of useless abort() & use ASSERT_OR_RETURN to prevent GIGO, and also fix miscellaneous issues of removing '\n', 'watermelon', and other things that made by eyes bug out. NOTE, there should be no logic changes besides converting ASSERT() to ASSERT_OR_RETURN()! -- NOTE, there should be no logic changes besides converting ASSERT() to ASSERT_OR_RETURN()! -- Fixes #523 fixes #499 |
cybersphinx changed milestone from |
cybersphinx commented Milestone 3.0 deleted |
resolution_fixed
type_bug
| by anonymousWhile changing all units from wheels to half tracks wz crashes without any error if half tracks are selected for repaire unit. I could reproduce behaviour but not in every attempt.
Issue migrated from trac:523 at 2022-04-15 18:19:30 -0700
The text was updated successfully, but these errors were encountered: