Misbehavior on copy object with actuator(add object) #41937

New Issue

Michaël Timbert · 2014-09-24T10:04:09+02:00

Michaël Timbert commented

2014-09-24 10:04:09 +02:00

System Information
Linux Debian 7 64bit. &

Blender Version
Tested on 2.71
and 2.72 eb464ee

Short description of error
I have an empty object for simply spawn an enemy, this work, this spawn an enemy with child.
BUT if i copy (ctrl-c ctrl-v) this empty object for spawning a new enemy, he make a new copy of the original enemy but without child.
AND if i duplicate link (alt-D) the behavior is correct (i think) this copy empty object who spawn Ennemi1, but game logic between spawn and spawn.001 are not linked.

Exact steps for others to reproduce the error
with this file:
spaceinvader.blend

select spawn object and duplicate it.
the new object (called spawn.001) don't spawn the object Ennemie1 but Ennemie1.001.
If we go to the layer 9 we can see a second enemy have being added (over the first).
But this new Ennemie1.001 don't have child Ennemi_gun.

comment:
I make this empty object spawn because we cant duplicate linked (Alt-D)
dont link game logic of object.

solution:

add game logic on data linked to the object with duplicate linked.
actuator Edit Object need more option like:
- copy child ( recursive or not )
- make new object or reuse object

I hope to have explained well.

**System Information** Linux Debian 7 64bit. & **Blender Version** Tested on 2.71 and 2.72 eb464ee **Short description of error** I have an empty object for simply spawn an enemy, this work, this spawn an enemy with child. BUT if i copy (ctrl-c ctrl-v) this empty object for spawning a new enemy, he make a new copy of the original enemy but without child. AND if i duplicate link (alt-D) the behavior is correct (i think) this copy empty object who spawn Ennemi1, but game logic between spawn and spawn.001 are not linked. **Exact steps for others to reproduce the error** with this file: [spaceinvader.blend](https://archive.blender.org/developer/F111970/spaceinvader.blend) select spawn object and duplicate it. the new object (called spawn.001) don't spawn the object Ennemie1 but Ennemie1.001. If we go to the layer 9 we can see a second enemy have being added (over the first). But this new Ennemie1.001 don't have child Ennemi_gun. __comment:__ I make this empty object spawn because we cant duplicate linked (Alt-D) dont link game logic of object. __solution:__ 1. add game logic on data linked to the object with duplicate linked. 2. actuator Edit Object need more option like: - copy child ( recursive or not ) - make new object or reuse object I hope to have explained well.

Michaël Timbert commented

2014-09-24 10:04:09 +02:00

Changed status to: 'Open'

Michaël Timbert commented

2014-09-24 10:04:09 +02:00

Added subscriber: @BlackCat

Jorge Bernal commented

2014-09-28 01:59:44 +02:00

Added subscriber: @JorgeBernalMartinez

Jorge Bernal commented

2014-09-28 01:59:44 +02:00

For me this isn't a bug.

You have 3 possibilities:

Ctrl-C Ctrl-V (copy/paste): you obtain a copy of the spawn with a copy (.001, .002, etc) of any associated action.
Shift + D (Duplicate): you obtain a duplicate of the spawn that calls to the same associated actions than the original one.
Alt + D (Duplicate linked): you obtain a duplicate linked of the spawn that calls to the same associated actions than the original one.

I have checked your example and with the options 2 or 3 it works perfectly. I mean when you move the ship under whatever (duplicate or duplicate linked) enemy ship, this enemy ship shoot you.

For me this isn't a bug. You have 3 possibilities: Ctrl-C Ctrl-V (copy/paste): you obtain a copy of the spawn with a copy (.001, .002, etc) of any associated action. Shift + D (Duplicate): you obtain a duplicate of the spawn that calls to the same associated actions than the original one. Alt + D (Duplicate linked): you obtain a duplicate linked of the spawn that calls to the same associated actions than the original one. I have checked your example and with the options 2 or 3 it works perfectly. I mean when you move the ship under whatever (duplicate or duplicate linked) enemy ship, this enemy ship shoot you.

Michaël Timbert commented

2014-10-01 11:39:41 +02:00

Thank,

i agree with you.

BUT:

Ctrl-C Ctrl-V (copy/paste): make a copy of spawn but don't copy children (ennemi_gun) and relationship. I don't know if it's a normal behavior.

Second:

When we Duplicate linked game logic is not linked. But i think it's a limitation in BGE
(maybe if we link game logic, one sensor of one object can affect all linked object, i don't know) i need to go deep in BGE for understand
this thing. But its going to take me a while.

Thank for review.

Thank, i agree with you. BUT: Ctrl-C Ctrl-V (copy/paste): make a copy of spawn but don't copy children (ennemi_gun) and relationship. I don't know if it's a normal behavior. Second: When we Duplicate linked game logic is not linked. But i think it's a limitation in BGE (maybe if we link game logic, one sensor of one object can affect all linked object, i don't know) i need to go deep in BGE for understand this thing. But its going to take me a while. Thank for review.

Jorge Bernal commented

2015-05-15 16:28:59 +02:00

Changed status from 'Open' to: 'Archived'

Jorge Bernal closed this issue

2015-05-15 16:28:59 +02:00

Jorge Bernal self-assigned this 2015-05-15 16:28:59 +02:00

Jorge Bernal commented

2015-05-15 16:28:59 +02:00

I close the report as the behaviour described is the normal behaviour expected.

Thanks for taking time reporting.

I close the report as the behaviour described is the normal behaviour expected. Thanks for taking time reporting.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Misbehavior on copy object with actuator(add object) #41937