tipforeveryone Posted May 13, 2020 Posted May 13, 2020 I was playing with Visualize::renderVector() and found this, not sure this is a bug but I feel it is not right. I use this function in 2 cases (the first one is commented block) Case 2 is ok, visualized vector display with exact start/end position In case 1, when I replace start/end Vec3 postion by using 2 objects (a moving airPlane model and static material_ball), I got this
silent Posted May 13, 2020 Posted May 13, 2020 Are you sure that metalBall is referenced to the correct node? There is no bugs with renderVector method. How to submit a good bug report --- FTP server for test scenes and user uploads: ftp://files.unigine.com user: upload password: 6xYkd6vLYWjpW6SN
tipforeveryone Posted May 13, 2020 Author Posted May 13, 2020 This is how I got metalBall. in header file: NodePtr metalBall;
silent Posted May 13, 2020 Posted May 13, 2020 As for a temporary solution, could you please check if Visualizer::setSize(100) will improve the situation? How to submit a good bug report --- FTP server for test scenes and user uploads: ftp://files.unigine.com user: upload password: 6xYkd6vLYWjpW6SN
tipforeveryone Posted May 13, 2020 Author Posted May 13, 2020 Yes, it fixed the problem, I did not use Visualizer::setSize() before, that means default size of renderVector is too big?
silent Posted May 13, 2020 Posted May 13, 2020 Yeah, by default visualizer size is set to 128, we will check how to improve this behavior. How to submit a good bug report --- FTP server for test scenes and user uploads: ftp://files.unigine.com user: upload password: 6xYkd6vLYWjpW6SN
mvb_sub Posted July 2, 2021 Posted July 2, 2021 On 5/13/2020 at 9:38 AM, tipforeveryone said: I was playing with Visualize::renderVector() and found this, not sure this is a bug but I feel it is not right. I use this function in 2 cases (the first one is commented block) Case 2 is ok, visualized vector display with exact start/end position render this 2 points and You`ll get wrong end position!
Recommended Posts