[4.7.6] Blueprint: Inhertited variables can't be accessed

Hi there,

blueprint editor doesn’t let me access inhertited variables from a parent blueprint:


component is not marked as private or something.

After a few minutes of research and slamming my head into a wall I discovered that you can at least access it by dragging out a pin and type name by hand after unchecking context sensivity:


WTF? Please don’t tell me that this is intended behavior, that would be a disaster for my project as I would not be able to extend base classes with functionality any more then…

Hi ,

I’m not sure why it would be intended behavior since it seems inconsistent with creating Get nodes for variables referencing components that aren’t inherited. I’ve put in a bug report for it (UE-15065), and I’ll let you know what happens with it.

It’s strange that Getter isn’t showing for you in search with Context Sensitive enabled. Are you searching with underscores? If so, try searching (with Context Sensitive enabled) for “get sm left door” (no underscores, using spaces instead) and see if it shows up. search is restricted to friendly names, I think.

Hi , many thanks for your quick response as always.

I am searching exact same phrase in both cases.

Okay, so I did a quick test in 4.7.6 by giving a parent a Static Mesh with name SM_left_door. In Child BP, I searched with Context Sensitive enabled, and it showed up regardless of whether I used underscores, spaces, or no spaces. Do you have Force Legacy Menuing System enabled in your Editor Preferences?

Hi , I copied project over to another machine. On this machine, I get a hit even with context sensitive enabled. Maybe just a broken cache or something?

only difference is, that search doesn’t jump to correct result if I type name of variable exact as specified:


If I type it without underscores, this works:


Without context sensitivity, I get variable as only result:

Yep, it will highlight closest to what you’re typing, but actual Get node uses friendly name. I’m not sure why this is different on your machine, but my guess is an engine .ini setting somewhere. Did you check to see if Force Legacy Menuing System is enabled on your machine?

Hi ,

no, its not checked.

Hey ,

Just a quick check: both of systems you tried this on had same version of UE4, yes? Have you checked this in 4.8p1 yet?

Hi ,

yes, they were both 4.7.6. Did a quick check in 4.8.0p1: Same problem here:


It’s not possible to me to drag&drop inherited components to event graph.

Right, that part we have reported in UE-15065, which hasn’t been fixed yet. At this point, I’m trying to track down what’s causing search issue for you on your system. Does that still happen in 4.8p1?

Hi ,

yes, it’s no difference to 4.7.6 (searching for ‘get S_switchLightTech’) stops at first hit instead of getter.

Okay, few more questions:
Does search issue happen with any Blueprints, or only inherited ones? Are Blueprints they’re inherited from inherited from a native C++ class or another BP? If from a BP, please screenshot that BP’s Event Graph with variable selected. If it is from a native class, please give us code where property is declared and set in constructor. Thanks!

Follow up: Drag & Drop still broken in UE 4.8.0 P3.

Update: Same here, I can’t drag&drop inherited components in official 4.8 release. ‘Cannot place variable “…” in external scope ‘…’’ Update: But it works and i can access it when i search for it via right mouse button click menu - so looks like only drag&drop doesn’t work.

Same here!

Is this still happening in 4.9.0 ? Is it worth moving onto that version ? This is a showstopper for me right now TBH.

OK guys, literally 5 minutes after posting my previous comment I found a workaround.
Simply drag component into EventGraph from Components section of Variables UI group rather than more obvious component tree above it. That worked for me, even in 4.8.3.

… or maybe someone could just fix that bug after more than 3 and a half months…? :wink:

Well that would be preferred solution but in its absence this workaround actually works around. :wink:

Hey davek,

This has been fixed for 4.9, and I believe fix has been integrated into latest Preview if you’d like to give it a try. Let us know if you still have this issue (drag and drop, UE-15065) after official release. Thanks!