Changes of parameters from materials do not update in viewport after UE restart until recompiling

Look at the following bug I recently reported to UE by a submission form: UE-54670

I actually very EXPLICITLY and REPEATEDLY wrote, that this issue corncerns only vector parameters and not scalar parameters, but this information seems to be omitted.

Here is my original report:


Vector parameters in the material editor do not update immediately in the level viewport. This is always the case when you start UE and did not yet compile (“apply”) the material. That is, the progress of a vector parameter you get by applying and saving a material is lost after UE restart.

Scalar parameter, in contrast, do not make any problems, everythings works as expected.

Steps to reproduce:

    1. Create new material and assign it to an object in the level.
    2. Edit this material: Create vector parameter “Color” and connect it to BaseColor; create scalar parameter “Emission” and connect it to EmmisiveColor.
    3. Apply, save, and restart Unreal Engine Editor. Place viewport editor and material editor side by side, so that you can see both simultaneously.
    4. Change both parameters for testing.

Result: Scalar parameter changes immediately, vector parameter does not, but actually both parameter types should give a real time preview.


Can you really not reproduce it? So perhaps something in my report was unclear? But there was no query by mail although How to report a bug indicates that there would be in case of lack of clarity.

1 Like

Hello,

We’ve recently made a switch to a new bug reporting method using a more structured form. Please visit the link below for more details and report the issue using the new Bug Submission Form. Feel free to continue to use this thread for community discussion around the issue.

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

Thanks

You can feel free to use the submission form to include additional details on existing issues, as we are currently working out of our queue where those submissions come in. We’re working on updating language to reflect our new process on all of our connected sites, but we haven’t gotten everything up to date just yet. I’ll add that language on the public tracker to my list, so thanks for pointing it out.

The issue in question was closed as Cannot Reproduce in 4.19 Preview 4, indicating that the issue has been resolved in that version. Are you still seeing the issue in 4.19 P4? If so, let me know and I can follow up with the creator of the report and get it re-tested.

Thanks

Well, Sean … you must be kidding, or?

As I mentioned, I already did use this new bug reporting method. Once again, you can find it here: UE-54670
You can also read there: “Have Comments or More Details? There’s no existing public thread on this issue, so head over toAnswerHub just mention UE-54670 in the post.” What I did, didn’t I?

The UE internal issue tracker set the problem to “Cannot Reproduce”, and I think that’s wrong because some very essential information are curiously missing in that report.

I guess: Yes, probably still an issue in 4.19, because it is not marked as fixed, although versions 17 to 19 are marked as affected.

But because of this I do not want to install 4.19 Preview for just a 2 minute test, and therefore, I cannot say with certainty. Perhaps I test and get in touch later, perhaps someone else wants to test it (?), perhaps no one …

Now tested with 4.19, problem not solved.