Got it, thanks so much for explaining.
Original Message:
Sent: 02-06-2024 12:29
From: Jeff Mayer
Subject: child of text covering in a layer object
Scott,
There are several options in the Rendering tab of each object that you'll need to adjust. The behavior you're seeing is occurring because a Layer Object's default Depth Sorting mode for Rendering is Manual, which renders objects towards the bottom of the Object Manager in front of objects towards the top. So a child of a text object, which is necessarily below the text in the Object Manager, gets rendered in front of it.
You can change the Depth Sorting mode in the Layer Object's Rendering tab to Automatic, but you'll have to make some other adjustments to your objects at that point, depending on how complex your scene is.
When I tested a simple scene as you described, once I set the Layer Object to Automatic Rendering, I had to either (a) check the option on the the masks's Rendering tab to "Render on Top" OR (b) change the Text's Render Order Priority from Text on Top to Normal, so it would get hidden by the mask, then set the Z Position of the Quad to -1 so it would appear behind the text.
I should also add, it's probably easier to accomplish what you're looking to do using Visual Logic, rather than Auto Scale. You can tie either the width or the Scale.X of the quad to the BoundingBox.Width of the Text Object, then you don't need to worry about having the Quad be a child of the text object, nor changing your render settings for your Layer Object.
------------------------------
Jeff Mayer
Ross Video
Original Message:
Sent: 02-05-2024 15:05
From: Scott Carmichael
Subject: child of text covering in a layer object
I made a quad a child of a text object to use auto scale. It works fine, but as soon as I put the text object(with the quad child ) in a layer object, the quad child covers the text. The only way I have found to uncover the text is to break the parent child relationship I have them in a layer object because I also have a mask so it looks as if they slide from behind another object. Why is it having this behavior and is there any way around it?
Thanks,
Scott
------------------------------
Scott Carmichael
Indiana University
------------------------------