 |
What appears to be happening: 1 - A card player's animation runs the frame command that spawns a single card and attaches it to his hand. 2 - The game is saved. 3 - The game is restored. 4 - The card player is restored, but restoring the list of objects attached to him is delayed until those objects are spawned. 5 - The card player runs his animation and ONCE AGAIN spawns a single card and it attaches to his hand. 6 - The restore code (now that objects have all been spawned) wants to restore the list of attached objects, and goes to attach the pre-savegame card to the card player's hand. But the post-restore card is already there. They have the same name because all of this happens in the same frame. So the solution is to find out why the card player ran the same frame command both BEFORE the savegame and AFTER the restore game. Alternatively, if an object with the same name is already in the entity's attached list, what's the harm of ignoring the second request to attach the identically-named object? |
|
|
We've only seen this problem with the card players, when the game is saved around the frame when the card player draws a card from his deck. In theory, it could also happen when any objects are spawned by anim frame commands, i.e. the flint used to relight doused lights. The problem occurs because the list of attached objects is saved during a savegame, but during restore the list isn't recreated until after all objects have been spawned (idAFEntity_Base::RestoreAddedEnts()). But when objects are all spawned, each object is allowed to think and update its animation. For some reason, the card player's animation replays the frame command to get a card and puts that into the attached list. When the delayed list of attached objects is allowed to be re-added to the attached list, the card is already there with the same name, because all of this happens in the same frame. I wasn't able to figure out why the frame command was running twice, but we've had problems with this in the past. So I'm taking the simple way out, which is to delete the object already in the list and append the new one to the list. Change the error message to a warning. rev. 6563: Physics_AF.cpp |
|
|
The second attached savegame is from Behind Closed Doors running on 2.03. It's more useful than the first attached savegame, since that one is so old now. |
- Anonymous
