christian.wolf2 Posted March 20, 2019 Share Posted March 20, 2019 Hi, I got a strange behavior with the latest UNIGINE version (2.7.3) regarding working with PhysicalTrigger. I am sure that I have found two bugs with them. Tasks to re-create those issue: Create a new empty project and open the main world. Create two new PhysicalTrigger and set only for one of them a PhysicalMask. Issue 1: Select the second PhysicalTrigger. It got the same PhysicalMask as the first, modified, one. If you change that mask to a complete different one, the first one will be changed as well. Unfortunately only the "frontend" will be changed and not the object itself. Close the editor and open them again resets the PhysicalMasks for both Trigger. Issue 2: I guess that problem is linked to the first one. Change the PhysicalMask and save the world. Now open an IDE and get the PhysicalTrigger via code (I did that with simple Editor::get()). All PhysicalMasks have 1 applied to them, so changes in the editor was not saved correctly. Regards Christian Link to comment
morbid Posted March 21, 2019 Share Posted March 21, 2019 Hello Christian, It's a bug. There's a workaround - you can manually set physical mask in xml with this string: <physical_mask>0x8(or other value)</physical_mask> Sorry, we'll try to fix this in the nearest release. Thanks. 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
morbid Posted March 22, 2019 Share Posted March 22, 2019 Hi, fix will come in 2.8 release. Thanks for the feedback! 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
christian.wolf2 Posted March 22, 2019 Author Share Posted March 22, 2019 Awesome morbid. Thanks a lot for the quick fixing. Link to comment
Recommended Posts