#more backwards compatibility concerns for cam parents

11 messages · Page 1 of 1 (latest)

modest basin
#

[Bug Description]
Objects that were parented directly to the camera from older levels have been defaulted to use the "above player" layer. This is good! However, any children of those objects are still kept on the normal layer. Generally speaking, many people parent their objects to 1 empty, then parent that empty to the cam. This means all children that should be above the player are still broken in the alpha version, and will not be defaulted to the "above player" layer despite their parent being on that layer.

[How You Got Here]
-in the default branch, parent an object to an empty, then parent that empty to the camera.
-save, then open the level in the latest alpha version
-children object of the empty will not have been properly defaulted to the "above player" layer.

[Game Version]
26.5.9 alpha

[Extra Info]
Sorry for bringing this up again but the current state of this will now actually be worse than before. If nothing can be done about this, i would rather just have every camera parent and their children default to the same layer instead of being spread out across 2 different layers.

#

also sorry if this is only tangentially related but why is there only 4 render depth for the above player layer?

boreal dust
#

yeah shouldnt there be at least 20 to properly mimic camera parenting

proven pulsar
#

it works fine on my end with there being 60 above player render depths

modest basin
#

oh

#

new bug I guess (?)

proven pulsar
#

it makes sense why it'd be like that for the "in background" objects (since render depth controls what bg layer it's on)

#

so probably just a mistake/bug that has to do with that

dense aspen
#

yeah when you switch to bg layer then above layer the slider sometimes stays restricted to 5 layers like this it's just a bug

modest basin
#

ok thats very good to know