3D Modeling

[castillor]

Hi,

We are having problems with the old ray testing functions so we are looking into the "api_ray_fire" function which is the newer ray testing function. The problem is we encountered cases where this newer function is more that 10 times slower than the old one. We have a procedure where the ray testing is tied to a mouse move event so the ray testing speed is critical n this situation. Can anyone suggest another way to workaround this problem?

The files attached can demonstrate a situation where the newer function is much slower than the older ones. The "RayTest.txt" define the start points of the rays and the ray vectors are defined by the direction from the start points to the end points.

Thank you,

Raymond

[rajeshc]

I have created a scheme script for this and have noted the performance issue that you mention. I will look into this and get back to you.

[Vi2]

Here is also a problem with api_convert_to_spline. The pcurves 18 from "SampleForCylSlice-1.sat" and "SampleForCylSlice-1.splined.sat" (obtained by (define detail (car (part:load "C:/TEMP/SampleForCylSlice-1.SAT"))) (define sdetail (entity:spline-convert detail)) (part:save "C:/TEMP/SampleForCylSlice-1.splined.sat")) differ too much.

[rajeshc]

Hello Raymond,

I took a look into this and i don't think i can suggest any workarounds to the performance problem. Kindly log this as a performance issue of "api_ray_fire" versus the old ray testing functions so that we can try to address this.

Regards

Rajesh

[castillor]

Hi Rajesh,

Okay, we'll do that. Thank you very much for looking into this issue.

Regards,

Raymond

[triet]

Hi,

Can you tell me which version you referred to? I currently use R20SP3 and would like to move to R21HF6.

Thanks.

[castillor]

I'm currently using R21. I haven't checked if there were any change in performance between R20SP3 and R21.

[triet]

Hi,

Did you mean the function in R21 is 10 times slower than the old function? and in which release the old function is?

Thanks.

Manhtriet.

[castillor]

Okay let me clear this up. There are several ray test functions in ACIS that is supposed to do the same thing. When I say old and new, I am not implying the version of the release but when the function was introduced. What I'm specifically referring as the old one is the function named "api_raytest_ents". In R20, a new ray testing function called "api_ray_fire", which is supposed to provide the same functionality as the older "api_raytest_ents" function.

In our case, we found several situations where "api_raytest_ents" will give us incorrect results and so we decided to look into "api_ray_fire". The results that we are getting is correct with this newer function but the performance is more than 10x slower than "api_raytest_ents".  

[triet]

Thanks Raymond for clarifying in it.

Regards,

Manhtriet.