Visualize::renderVector() bug?

[tipforeveryone]

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]

Are you sure that metalBall is referenced to the correct node? There is no bugs with renderVector method.

[tipforeveryone]

This is how I got metalBall. in header file: NodePtr metalBall;

[silent]

As for a temporary solution, could you please check if Visualizer::setSize(100) will improve the situation?

[tipforeveryone]

Yes, it fixed the problem, I did not use Visualizer::setSize() before, that means default size of renderVector is too big?

[silent]

Yeah, by default visualizer size is set to 128, we will check how to improve this behavior.

[mvb_sub]

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!