4.8.1: AI Perception By Affiliation?

,

When trying to configure the AI Perception component on my controller, the Perception By Affiliation section in each sense is completely blank, so I am unable to configure it at all.

Trying to do it via C++ didn’t yield better results unfortunately.

Am I doing it wrong or is this a bug?

Can you give some example screenshots and describe how reproduce this in raw template project?

Hi ,

Are you looking at the details pane in your blueprint? I pulled it up and this option seems to be directly tied to what sense you are attempting to utilize. Specifically, Affiliation should occur with both Hearing and Sight but is not associated with the other perception types.

Hey there. I just got into the office, opened up my enemy controller to take a screenshot of the missing dropdown and suddenly it was there. When I wrote this there was just the header but no drop-down arrow to expand the section. I have no idea what caused it to start working properly… Thanks for your time in any case and I’ll make sure to report if it happens again (With screenshots this time).

Hi ,

I’m happy to hear that this isn’t affecting you any longer. I’m going to go ahead and mark this as answered for tracking purposes. If this occurs again please comment back with the updated information and I’ll be happy to take another look!

maybe it was caused by creating something and not saving everything, at least in blueprints it usually written on variable detail panel after creation

I have exactly the same problem on 4.8.1. Unfortunately I haven’t tested it in earlier versions. Please take a look at the screenshot.

Edit: Seems like this is only the case when component is inherited from C++

49257-affilation.png

Hey -

As parabolainteractive pointed out, I was able to reproduce this issue when setting up the component through code. I have submitted a bug report (UE-18378) for investigation. For the time being the best solution would be to set the component up directly through the blueprint editor rather than doing so through code.

Cheers

Hey,

It didn’t even occur to me to mention I was setting it up through code, didn’t think it made any difference. Glad we could help!

Any news to this. I am having the same problem.

Hey -

The report for this issue is still open in our tracking system. You can find the status of the report hereissues.unrealengine.com/issue/UE-18378 .

Not sure if I should submit this as a separate issue, but in 4.15.2 Win7x64 if the AI Perception Component was added in C++, you cannot assign a sense to it. The drop down works but when you click on a sense it still shows “None”. Tried selecting with keyboard as well. No form of input selects the sense. Once I configure the sense in C++ I can edit values in the editor as normal.

Hey -

This issue was to report the Detection by Affiliation field of a Senses Config element. Since it sounds like you are unable to set any elements of the Senses Config array at all, I would advice creating a new post for your issue.

Additionally, when I follow the steps in the issue linked above (UE-18378) which sets up an AI Perception component in code, I am able to set elements of the Senses Config array. If you’re following these steps and cannot set any values, please provide a sample project demonstrating the behavior you’re seeing. If you’re using a different setup, please include the reproduction steps used to help me test on my end.

ue4.16.2 still broken

4.18 - still broken.

Any chance to fix this issue?

Hey -

We do not have timeframe for when this issue will be addressed. As mentioned below, using the component from within the editor avoids this issue.

I just happened upon this because I was wondering about it. Another workaround (until an official fix), keeping the Component setup in the C++ code, is to configure it by copy-pasting the struct property into Notepad or similar, modifying the affiliations, then copy-pasting the modified struct back onto the property.

It’s not amazing, but lets you do any other config still in C++.

Same problem for me with 4.21.1. The Bug reported is still open.

The bug still is present on 4.19.2, we need a fix for this asap.

The bug still is present on 4.19.2, we need a fix for this asap.