1.3.16 Assertion bug in Leader_of_the_Drakes campaign
Moderator: Forum Moderators
Forum rules
Before reporting issues in this section, you must read the following topic:
Before reporting issues in this section, you must read the following topic:
1.3.16 Assertion bug in Leader_of_the_Drakes campaign
In start of second scenario in Leader_of_the_Drakes from the Add-on server I get the following bug:
wesnoth: actions.cpp:2323: bool unit_can_move(const gamemap::location&, const unit_map&, const gamemap&, const std::vector<team, std::allocator<team> >&): F?rs?kran "u_it != units.end()" falsk.
Avbruten (SIGABRT)
Attached savegame where bug occurs. Seams like the code for handling bad WML code are broken ?
wesnoth: actions.cpp:2323: bool unit_can_move(const gamemap::location&, const unit_map&, const gamemap&, const std::vector<team, std::allocator<team> >&): F?rs?kran "u_it != units.end()" falsk.
Avbruten (SIGABRT)
Attached savegame where bug occurs. Seams like the code for handling bad WML code are broken ?
- Attachments
-
Drake_Council.gz- (5.24 KiB) Downloaded 119 times
A general remark: when posting a bug about an add-on, please give the name of the add-on, in this case "Children of dragons", "Leader of the Drakes" is just the name of the first scenario. I suppose that it was an error but i often see this kind of report forcing you to guess the add-on name to reproduce the bug.
And post bug here : http://bugs.wesnoth.org A bug posted in forum and needing the previous step to be checked has a high probability to be ignored/forgotten. Also note that this scenario doesn't crash on big screen.
The bug seems to come from a scrolling triggered by a fake_unit_move. The engine incorrectly try to draw the orb of the fake unit (orb color: unit_can_move). So thanks for the report, it is probably a severe problem (but easy to fix).
PS: you can maybe avoid the crash by using a big window. In other cases when you have more time, you can also try to scroll to the source of the move before it starts or use zoom (btw the default zoom key directly toggles a very low zoom).
EDIT: Fixed
And post bug here : http://bugs.wesnoth.org A bug posted in forum and needing the previous step to be checked has a high probability to be ignored/forgotten. Also note that this scenario doesn't crash on big screen.
The bug seems to come from a scrolling triggered by a fake_unit_move. The engine incorrectly try to draw the orb of the fake unit (orb color: unit_can_move). So thanks for the report, it is probably a severe problem (but easy to fix).
PS: you can maybe avoid the crash by using a big window. In other cases when you have more time, you can also try to scroll to the source of the move before it starts or use zoom (btw the default zoom key directly toggles a very low zoom).
EDIT: Fixed