Hello Ventuzians!
THE FORUMS ARE CLOSED!

Please join our discord server HERE!! << click me :D

We are shutting our Ventuz Forum, but don't worry, it will all be archived for you to search in if you have a query. From now on, please add all your comments, questions or observations into our Discord Server

Thanks for the great time - see you on discord!!
Dee, Karol, Daniel and the whoooole Product and Support team!

Changed Argument of Array is not Exposed through Scene Port

Please report bugs in this group. We will maybe populate a list of known bugs with a possibly modified description at a later time.

Moderator: Support

Post Reply
User avatar
Eric_RD
Posts: 103
Joined: 04 Jun 2014, 14:01
Contact:

Changed Argument of Array is not Exposed through Scene Port

Post by Eric_RD » 08 Jan 2015, 10:37

I have two scenes (Scene1, Scene2) And loaded Scene2 into Scene1 with a Scene Port.
Scene 2 Exposes a bool array to Scene1 which contains an indexer to split the Values.
The input of this indexer does change. The output however does not and the changed Event of the indexer is not triggered.

If I add another exposed variable (not an array), both values work like they should. If I delete the added variable the output of the indexer does not change again.
Attachments
Scenes.zip
(7.4 KiB) Downloaded 258 times

User avatar
Eric_RD
Posts: 103
Joined: 04 Jun 2014, 14:01
Contact:

Re: Changed Argument of Array is not Exposed through Scene P

Post by Eric_RD » 08 Jan 2015, 10:44

Eric_RD wrote: If I add another exposed variable (not an array), both values work like they should. If I delete the added variable the output of the indexer does not change again.
Not Quite:

If I add another variable the change of this variable triggers the change of the Array, although there is no direct connection.
Changing the Array itself still changes nothing on the output of the indexer.

User avatar
Karol
Posts: 640
Joined: 10 Jan 2012, 12:07

Re: Changed Argument of Array is not Exposed through Scene P

Post by Karol » 09 Jan 2015, 15:38

Fixed in upcoming 4.6.0!

Post Reply