4.5.1/4.6 Bug (Mac): Parameter Collection value not passed to material

This seems to work in editor view, both in 4.5.1and 4.6, but fails to render when playing in Viewport. It also seems to work in mobile preview in 4.6.

Basically just a blueprint passing a parameter value to offset a texture. Material displays correctly as long as value is not from the parameter collection sent from blueprint. Everything was working fine in 4.4.3.

The project is an updated version of a 4.4.3 one. Blueprint and Material redone from scratch due to huge display bugs in 4.5.1. I tried everything from updating original project to migrating assets only to redoing from scratch with new parameter collection in 4.6.

Mac OSX 10.9.5, Macbook Pro, AMD Radeon HD 6770M

MaterialParameterCollections don’t retain any changes made during a play session, this includes changes made in the editor through a blueprint. Here is a quote from the documentation:

“Values set through Blueprint only exist in the current world being simulated. That means a Play-In-Editor session which modifies collection parameters will not modify the way the Materials look in the editor.”

To get around this issue you need to set all of the parameters from the “Event Begin Play” as well as the construction script. In my case I just copied and pasted the nodes there from my construction script, this way I know that any of the changes made in the editor before playing the game also get set in-game to the same values.

Hope that helps!

Thanks, but I’m not modifying parameters while playing-in-editor. The play session apparently fails to read the value altogether, even when it is read and displayed correctly in the editor.

Also, like I said, whatever I am doing was working fine before 4.5.1. I don’t know if it was only on Mac, but this project had all kind of rendering problems as soon as I moved it from 4.4.3 to 4.5.1, things like post process values not working, running the game would display everything in black and white, major stuff. It still looked fine in the editor view though.

4.6preview kind of fixed the big stuff, but I noticed this one bug while trying to rebuild the material from scratch as a way of debugging it.

Hi, I have been trying the method suggested below while in 4.6, and running the blueprint from the event graph AND the construction script seems to have solved it.

However, I still don’t understand why it was working all the time in 4.4.3 while running the blueprint only from the construction script? When I migrated the project it stopped working, that’s what caused me trouble. What changed exactly?

Also, the above method only seems to render fine in a new map created after 4.4.3. I wish I could be more specific but I’ve just been witnessing a ton of bizarre rendering behaviour in the last few days on Mac since trying to use this project in 4.5.1/ 4.6 , so I’ve been trying all sorts of small things to get it working again.

I’ll try experimenting in the next few days and post if I find anything concrete, for the moment I suppose this one can be marked as solved.

Hey Sogosha -

I have tested this internally and am not able to reproduce this behavior as you describe. The Material Parameter Collection is working correctly on 4.5.1 for us. Can you possible give us a screenshot of how you are using the Parameter collection in the Material and in the Blueprint?

Thank You

Eric Ketchum

Hey Sogosha -

There was an issue in both Mac and PC for Collection Parameter information not being passed into Blueprints in 4.5.0 but was corrected in 4.5.1. I know from experience that collection parameter’s created in 4.4.3 would still work in 4.5.0 but newly created ones would not. This may have some baring to what you are experiencing, but it should all be fixed in 4.5.1 and 4.6 Preview.

Thank You

Eric Ketchum