x

Search in
Sort by:

Question Status:

Search help

  • Simple searches use one or more words. Separate the words with spaces (cat dog) to search cat,dog or both. Separate the words with plus signs (cat +dog) to search for items that may contain cat but must contain dog.
  • You can further refine your search on the search results page, where you can search by keywords, author, topic. These can be combined with each other. Examples
    • cat dog --matches anything with cat,dog or both
    • cat +dog --searches for cat +dog where dog is a mandatory term
    • cat -dog -- searches for cat excluding any result containing dog
    • [cats] —will restrict your search to results with topic named "cats"
    • [cats] [dogs] —will restrict your search to results with both topics, "cats", and "dogs"

Actor Component not reporting correct Owner

When an Actor Component blueprint has a variable exposed to spawn, the Owner is incorrect.

In this example, I made a new Third Person Project. Added a projectile Actor that has no code. Then added an Actor Component (which prints the name of its owner). Finally, added a keypress event to the Third Person Character blueprint so it can spawn a projectile and add the custom component to it. This correctly reports that the owner of the actor component is the projectile it is attached to.

However, if you add any variable to the actor component and expose it to spawn, the owner now reports as the Third Person Character. alt text

Product Version: UE 4.9 Preview
Tags:
glitch.png (571.4 kB)
more ▼

asked Aug 23 '15 at 10:24 PM in Bug Reports

avatar image

Ohriginal
26 1 3 7

avatar image Adam Davis STAFF Aug 25 '15 at 02:08 PM

Hi Ohriginal,

I haven't been able to reproduce this on my end. Do you have a sample project that I can take a look at to repro this? I'll be happy to take a look.

avatar image Ohriginal Aug 25 '15 at 11:09 PM

Sure. Just load it up and click "1". As you can see the components are identical except one has an extra variable, yet they report different owners.

https://drive.google.com/folderview?id=0B4YNFuHrbHCafktIY3c2SmhhWmd2cU00WkRjZkgteWk4VXR1MGZsUTNrLXlyUWJYWDJJNUE&usp=sharing[link text][1]

[1]: /storage/temp/55774-glitch.rar

glitch.rar (2.0 MB)
(comments are locked)
10|2000 characters needed characters left

2 answers: sort voted first

The 'Owner' is the Actor to which the component belongs (normally the one that created it), not the one it is attached to. It is valid to attach one of your components to another actor, but that does not transfer 'ownership'.

more ▼

answered Aug 27 '15 at 07:38 AM

avatar image

JamesG STAFF
1.3k 8 6 32

avatar image erinacea Aug 27 '15 at 07:55 AM

So how do you get the actor owning a component?

avatar image Ohriginal Aug 27 '15 at 12:38 PM

Hmm well in that case the bug appears when you attach an actor component without any variables to an actor. I'm curious then, is there a variable that's GetActorThisComponentIsAttachedTo or something to this effect?

avatar image JamesG STAFF Aug 27 '15 at 12:45 PM

You can call GetAttachParent on the Component to see what it is attached to, and then GetOwner on that to see which actor 'owns' that component.

(comments are locked)
10|2000 characters needed characters left

Hi Ohriginal,

I was able to reproduce this on my end and have entered a bug report, UE-20417, to be assessed by the development staff.

more ▼

answered Aug 26 '15 at 02:38 PM

(comments are locked)
10|2000 characters needed characters left
Your answer
toggle preview:

Up to 5 attachments (including images) can be used with a maximum of 5.2 MB each and 5.2 MB total.

Follow this question

Once you sign in you will be able to subscribe for any updates here

Answers to this question