Jump to content

2.20 AutomaticTimeLightingComponent not syncking nodes


photo

Recommended Posts

Posted (edited)

Hello,

We use an AutomaticTimeLightingComponent in our celestial node to control the visibility at day and night of nodes with LightSourceComponent (enabling selectively a night node, or a day node).

Previously (2.16), this was enough to sync their state to slaves.

In 2.20, this no longer works as simply, and the day/night enabled state is not syncked to slaves. An easy workaround is to manually add an AddSyncNode component, but it feels like a regression.

Edited by Amerio.Stephane
  • Amerio.Stephane changed the title to 2.20 AutomaticTimeLightingComponent not syncking nodes
Posted

Hello! can you explain in more details your settings of AutomaticTimeLightingComponent ?

I have tested it in 2.20 and everything works fine.

here my setup: two plane red with LightSourceComponent category "test/red" and green with LightSourceComponent categort "test/green"
in AutomaticTimeLightingComponent we have "test/red" for day, and "test/green" for night


AutomaticTimeLightingComponent.png
 

 

when i change time - plane changes for master and slave the same way.

day-red.pngnight-green.png

What did I miss?

Posted

Hum, really strange. Indeed it works in a new world. Checked again in our world, and it, hum, kinda "worked" too. In one run, the slave day/night was the opposite of the master day/night (master day node enabled -> slave night node enabled, etc). Just got this once.

I'll do more tests...

Posted

Okay tried again, and it works and doesn't work at the same time, wtf

Here is a very basic scene, where a white cube is marked as day, and a light is marked as night:

master on left, slave on right, datetime 10 => ok, cube visible on both, light hidden on both

image.png.15efcccf9614000b244341ffa2dabb3b.png

Now datetime 1 => KO, cube hidden on both (cool), but light only visible on master (not cool)

image.png.bb31b5dda8e8a439e83053d49d9baafb.png

Only plugin loaded is UnigineIG

image.png.eaa69a6dff0eef72f1ea957e8ade86b2.png

image.png.a13cdf9a79acd2a6cbb7fb0141c71e86.png

image.png.b991a392ad5c8113cd1ea5309db1931d.png

Here is attached the relevant data:

light_test_scene.zip

Posted

I finally reproduced the issue and fixed it. It was linked with async Node loading somehow. So i change way of initialization LightController.

This will be available with the next update. but in the meantime, you can add the AddSynсNode component to the nodes.

Thanks for you time and feedback!
 

  • Thanks 1
×
×
  • Create New...