Well it sounds like somewhere you have 2 actors attached to one unit, or one unit attached to one actor... Both would create a similar error. Usually the editor won't let you do this, so I'm not sure where it is coming from, unless you are assigning actors to units through triggers, which I would recommend not doing. You can create a unit with no actor attached to it, and then assign an actor to it through triggers... Still a bit risky in my opinion. I would stick with only creating actors at points, not assigning them to a unit.
Other than that, I don't really know where the error could be stemming from.
if you could give some more info, I (and others) might be able to figure out where the error is actually stemming from.
I'm currently working on a hero rpg map, with multiple unit groups that wander, not assigning actors through triggers, but I do have a respawn system, maybe something is going on with it. I'll go through all my actors and make sure I don't find anything. It doesn't go off when any units respawn that I know of. I think the message popped up when I killed a certain unit. I went back and re-created the unit and it seems to not be showing the message except for when the map begins. I'll eventually redo every unit until I find it.
Thanks for the info tho I'll keep trying and let you know how it turns out.
I used to have the same issue, but it came from having multiple zergling units all with the same actor event for burrowing. Once I got rid of those events the problem subsided, so maybe check your actor events?
Really? Usually it just creates 2 actors on top of each other, but not attached... That's interesting, never heard of that before. Good to know, good to know.
Rollback Post to RevisionRollBack
Great to be back and part of the community again!
To post a comment, please login or register a new account.
Can anyone give me a little insight on how to get rid of this error that is popping up in my map suddenly.
Warning: More than one CActorUnit persisting in the same unit scope:
it seems popup when loading the game up and loading it in the editor. I cant figure out when it started :/
@Demonicus2009: Go
Well it sounds like somewhere you have 2 actors attached to one unit, or one unit attached to one actor... Both would create a similar error. Usually the editor won't let you do this, so I'm not sure where it is coming from, unless you are assigning actors to units through triggers, which I would recommend not doing. You can create a unit with no actor attached to it, and then assign an actor to it through triggers... Still a bit risky in my opinion. I would stick with only creating actors at points, not assigning them to a unit.
Other than that, I don't really know where the error could be stemming from. if you could give some more info, I (and others) might be able to figure out where the error is actually stemming from.
Great to be back and part of the community again!
I'm currently working on a hero rpg map, with multiple unit groups that wander, not assigning actors through triggers, but I do have a respawn system, maybe something is going on with it. I'll go through all my actors and make sure I don't find anything. It doesn't go off when any units respawn that I know of. I think the message popped up when I killed a certain unit. I went back and re-created the unit and it seems to not be showing the message except for when the map begins. I'll eventually redo every unit until I find it.
Thanks for the info tho I'll keep trying and let you know how it turns out.
@Demonicus2009: Go
I used to have the same issue, but it came from having multiple zergling units all with the same actor event for burrowing. Once I got rid of those events the problem subsided, so maybe check your actor events?
@voodude2008: Go
Really? Usually it just creates 2 actors on top of each other, but not attached... That's interesting, never heard of that before. Good to know, good to know.
Great to be back and part of the community again!