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"

Root component created in c++ does not show it's details in Blueprint details panel

Here is the property I have public:

     UPROPERTY(VisibleAnywhere, BlueprintReadOnly, meta = (AllowPrivateAccess = "true"))
         UCapsuleComponent* CapsuleComponent;

This is my constructor code:

 AProjectileSwitch::AProjectileSwitch()
 {
     PrimaryActorTick.bCanEverTick = false;
 
     IsSwitchEnabled = false;
     ShouldStayEnabled = false;
     Duration = 2.0f;
 
     bDestroyProjectileOnReact = true;
 
     CapsuleComponent = CreateOptionalDefaultSubobject<UCapsuleComponent>(AProjectileSwitch::CapsuleCompName);
     if (CapsuleComponent)
     {
         CapsuleComponent->ComponentTags.Add(ReactColliderTag);
         RootComponent = CapsuleComponent;
     }
 }

And here is how it looks like in Editor in an Blueprint that inherits the class alt text

It's extremely frustrating. I tried multiple combinations of creating the the component as either default or optiona. Different property specifier. Nothing works. It works fine for any components that are UNDER the root, it doesn't work for the root itself...

Product Version: UE 4.17
Tags:
uebug.png (239.5 kB)
more ▼

asked Sep 13 '17 at 06:12 PM in C++ Programming

avatar image

Pablo1517
6 1 4

(comments are locked)
10|2000 characters needed characters left
Viewable by all users

3 answers: sort voted first

OK, I found it. Apparenly in 4.17 if I add CollapseCategories = ("SomeCategory") to my UCLASS declaration macro, it will mess up the class in some random ways, including weird behaviour with some categories or fields disappearing completely instead of just collapsing it.

more ▼

answered Sep 15 '17 at 02:21 PM

avatar image

Pablo1517
6 1 4

(comments are locked)
10|2000 characters needed characters left
Viewable by all users
more ▼

answered Sep 14 '17 at 11:58 AM

avatar image

FilipeTessaro
1.3k 51 13 50

avatar image Pablo1517 Sep 15 '17 at 01:32 AM

That answer looks like a horrible hack that I would rather avoid. Besides I already managed to get it working. It looks like Visual Studio has a hard time removing old binaries with 4.17, cleaning the solution and using the implementation like in (for example) ACharacter class's CapsuleComponent fixed the issue.

(comments are locked)
10|2000 characters needed characters left
Viewable by all users

What fixed the issue for me was copy/pasting the declaration of my root component exactly how Epic did it with their CapsuleComponent inside ACharacter class and then Cleaning and Rebuilding the solution inside Visual Studio. Not exactly sure if this was it, but after that the properties started showing up.

more ▼

answered Sep 15 '17 at 01:33 AM

avatar image

Pablo1517
6 1 4

(comments are locked)
10|2000 characters needed characters left
Viewable by all users
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