david.cambre Posted August 2, 2020 Share Posted August 2, 2020 Hi, When adding a dummy_node under the default first_person_controller the position does not automatically update. To solve this I created a component to attach using Unigine; [Component(PropertyGuid = "cb0e1963a4eeaf66d7667f8d783a9b88e1a90947")] public class set_world_partner : Component { public String partner_name = "first_person_controller"; private Node partner; private void Init() { partner = World.GetNodeByName(partner_name); node.SetWorldParent(partner); } } Am I missing something? Link to comment
samuel.bruner Posted August 2, 2020 Share Posted August 2, 2020 maybe try first to unpack node content (fps controller) then add the child ( fireposition ) Link to comment
david.cambre Posted August 3, 2020 Author Share Posted August 3, 2020 Yes, then the parenting works. I do want to keep my code separate and modular. In the basic project it seems to have the same issue for all referenced nodes. And after double-checking the following links.https://developer.unigine.com/en/docs/2.12/objects/nodes/reference/?rlang=cshttps://developer.unigine.com/en/docs/2.12/editor2/instancing_nodes/?rlang=cs The only thing that stands out is "place as node content" in video 3:06 So i think it should just work or it needs to be clarified in the docs. Link to comment
silent Posted August 4, 2020 Share Posted August 4, 2020 Hi David, We will check how we can improve this behavior prior to 2.13 update. Right now children of NodeDummy are moving independently from the parent (which looks like a bug to me, but it can be the generic limitation as well). How to submit a good bug report --- FTP server for test scenes and user uploads: ftp://files.unigine.com user: upload password: 6xYkd6vLYWjpW6SN Link to comment
Recommended Posts