[peabody]

Originally Posted by Ducimus

The problem comes when the game has to instantiate two player objects at the same time. (parent or child objects). If your using it, and the game has to start a new instance of it while it's in use, the game gets confused i guess. Now mind you, the game has to start the instance for the error to occur. Just having it in the campaign files isnt enough.

You can totally clone the player object in every detail, but the game won't have a tizzy, UNTIL IT TRIES TO RENDER IT. (usually within 30 KM or so.). Which makes tracking down this error really hard. Sometimes there was an AI sub around and you didn't know it. Lucky for you, others have already done hours of this: ( ) so you don't have to.



No, I meant if its an AI object, you should use AI sensors. If your watch crew is using something like "crewWatchVisual" and the AI is using "AI_visual", then use "AI_Visual". Same for radar and hydrophones, etc.

edit: Some nodes are player specific and never used by the AI. TAR node for example. I mention this specifically because it was giving me issues. I let this one node slip by not realizing the game was trying to insantiate two instances of this player specific node. (its for submarine coatings)

Thanks, I think I get it now. And I thank you guys for "doing hours of this" so I don't have to.
I usually do hours of something and end up empty handed. I think it should work but for some reason it doesn't. Sometimes the light comes on but a lot of times it doesn't. (and it's only a 25watt light so it's not too bright.)

Peabody