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"

Map variable with value type 'Object' does not work for Blueprint instances

Good evening,

There is a rather significant bug using Map variables with either value type 'Object' or value type of structure which includes another variable of type 'Object'. Changing them in instances of the actor leaves them at default values in Simulate and PIE. But follow the steps to reproduce explains it better:

  1. Create blank project

  2. Create an actor Blueprint

  3. Add a Map variable of type e.g. Name to Object (bug persists with other key types as well)

  4. Add one or more default values to the map: e.g. 'None' -> 127grey texture (any object)

  5. Place the Blueprint in level and change the value(s) of your default map entries.

  6. Simulate game; select Blueprint instance in World Outliner and see there is still 127grey assigned.

Bigger problem with structures: Let's have a Name to Struct map variable with default as follows:

 'Name' -> Struct {
   Object: 127grey 
   String: 'Testing'
   Integer: 42

In the Blueprint instance changing the String and Integer to other values gets ignored in Simulate and PIE. Clearing out the Object to 'None' let the new String and Integer values persist to Simulate and PIE. As long as there is an Object assigned (even the default value), ALL values of the struct are set back to Blueprint default in Simulate and PIE.

Workaround for now: I have noticed that the bug does not happen if you add or remove an element in the Blueprint instance (the objects of the remaining elements are changed correctly in Simulate and PIE). If you have e.g. 3 default key-values and just rename one of them in the level instance, the bug persists, though. Adding or removing is mandatory.

Cheers, Kalabrix

Product Version: UE 4.18
more ▼

asked Nov 15 '17 at 09:55 PM in Bug Reports

avatar image

46 1 6 9

avatar image Kalabrix Nov 17 '17 at 10:21 PM

I thought the following was related, but did not fix it:

4.18.1 patch notes: "UE-51504 Inherited TMap value of type UObject* is not saved on blueprint compile"

avatar image LucidEddy Feb 06 '18 at 03:46 PM

I'm having the same issue and the workaround worked for now

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

2 answers: sort voted first

Hello Kalabrix,

We are using a new bug submission form. Please navigate to the link below for more information.

Link: https://forums.unrealengine.com/unreal-engine/announcements-and-releases/1410408-unreal-engine-bug-submission-form

Make it a great day

more ▼

answered Jan 09 '18 at 09:43 PM

avatar image

Rudy Q ♦♦ STAFF
47.4k 545 132 524

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


A bug has been created here: UE-54903

more ▼

answered Feb 07 '18 at 10:11 AM

avatar image

6 1 3

(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