294.4 Rendering Bug with Buttons

[Christian_Wheel]

When I add a button to my frame, the frame loses the ability to render any other graphics except macos native UI elements on the frame. Actives, Backdrops all disappear and I'm just left with a gray background.

Running Monterey on an M1 Max.

See the attached example file. Build a Mac App as-is and you'll just get a gray box with the button. Delete the button and build it again and you'll have the frame as designed.

button-294.4-test.mfa

[Christian_Wheel]

Update: Happens with an edit box as well.

[Yves]

Thanks! Probably due to the changes for the shaders, we'll take a look.

[Fernando]

Hi, just tested in Monterey 12.5 Mac mini M1 and seems fineScreen Shot 2022-08-10 at 11.08.32 AM.jpg

can you test this app with Rosetta (emulating Intel x86) just to be sure, don't ring a bell to me, why doesn't work in MAC with M1 max

[Christian_Wheel]

It is indeed running in Rosetta for me. When I export a Mac app I don't get a universal app, it's all in Rosetta.

Here's what I see on that frame:

[Christian_Wheel]

I tested the binaries on an M1 Mac Mini and it's also broken there.

Here are my binaries if that helps you track it down.

Test1 has the button and the frame is broken.
Test2 does not have the button and the frame renders fine.

button-294.4-test1-withbutton.zip
button-294.4-test2-withoutbutton.zip

[Fernando]

Can you try this example built here in your MAC M1 max

====

Your example test1 didn't show the correct screen here

====

After some review, i can properly tell you that your application have a mix between old code and new code, seems that the patch or update wasn't copied/applied correctly.

If my example runs Ok in your MAC

can you please show me the dates of your full MAC folder located at data/runtime/MAC of your fusion instalation.

[Christian_Wheel]

Your example ran perfectly! That's a good catch, would make sense that my exporter is borked.

The majority of the files in my data\runtime\mac folder are dated Feb 25 2017, with a few .dat files dated Jul 27 2020. Version.ini is the newest file in there, dated today. It was probably set when I tried reinstalling the patch, but none of the files updated. I've verified that the folder is not read-only and I can copy files to it successfully.

[Fernando]

Your example ran perfectly! That's a good catch, would make sense that my exporter is borked.

The majority of the files in my data\runtime\mac folder are dated Feb 25 2017, with a few .dat files dated Jul 27 2020. Version.ini is the newest file in there, dated today. It was probably set when I tried reinstalling the patch, but none of the files updated. I've verified that the folder is not read-only and I can copy files to it successfully.

please grab an image to know which files are not updated, but must have 2022

[Christian_Wheel]

Image attached. Thanks for the help!

2022-08-18_10-27-35.jpg