Intersect bug in max

[Klvnk]

run across some strangeness with max

-- run

delete objects;
pobj = convertToPoly(plane dir:[0,1,0]);
r = point pos:[0,50,2] dir:[0,-1,0] cross:off axistripod:on;

-- select the border edges of the plane and shift scale to add a ring of faces  then run....

mobj = convertToMesh pobj; 
intersectRay mobj (ray r.pos r.dir);

-- delete the new extruded Faces then run....

intersectRay mobj (ray r.pos r.dir);

do you get the results

undefined
OK
(ray [0,0,2] [0,1,0])
OK

?

[miauu]

I can confirm the bug. Tested on max2020. Tomorrow will test on 2022.

[denisT]

I remember this bug. It takes place for polyobjects. There should be another thread on this subject on this forum

… or on Area maybe

[denisT]

if you shift newly extruded faces out in ray direction it will work too.
the issue is that new faces overlap the original and faced backward to the ray.

RayMeshGridIntersect has a #doublesided option, and hopefully it can work it this case.

[Senorpablo]

Here are a couple of related threads:

FYI: IntersectRayScene is completely broken with editable poly

I posted this on the Autodesk forum and got no response from Autodesk, so I’m posting here for greater visibility. Hopefully it will save someone from wasting time trying to figure out what’s wrong, and/or motivate someone at Autodesk to get this fixed. DenisT / MaxDoctor has confirmed it’s broken, and we were able to determine it last worked correctly in Max 2016. Here’s a simple test to reproduce the bug. Run 1-3 and 4, 5 should give the same hit counts, but they do not: ( delete objects …

intersectRay speed - 10x times slower in new Max?

Hello, I’m writing a tool which uses the intersectRay method very often. I was using Max 2014 and 2015 for testing, but now I’m kinda shocked after running it in Max 2017 and 2018. Looks like v2017 is like 5 times slower than 2014 and 2015, but Max 2018 is like 10+ times slower… I don’t have the opportunity to test it on Max 2019. Could you tell me what is going on here? I’ve prepared a small benchmark, please test it and paste your results. ( rollout inRaySpeedTest "test"(edittext etext) fn…

[Klvnk]

it’s not just editable poly though, it effects editable mesh too.

change

pobj = convertToPoly(plane dir:[0,1,0]);

to

mobj = convertToMesh(plane dir:[0,1,0]);

and repeat without the additional converttomesh() !

and you still get the same problem. It’s odd as the ray is projected onto the original geometry, not the new extrusion. You can detach it and it works then reattach it and it breaks again

there are situations where this happens with the new geometry can be intersected but the original geometry can’t. My guess is theres a fault in the ray vs kdtree code they are using when things are planar or how the kdtree is constructed deciding the old geometry can be ignored .

[denisT]

there are situations where this happens with the new geometry can be intersected but the original geometry can’t. My guess is theres a fault in the ray vs kdtree code they are using when things are planar or how the kdtree is constructed deciding the old geometry can be ignored .

maybe a forcing some “smart - extra - update” can help?
forcing some notifications?

rebuild normals? invalidate caches?

[Klvnk]

you can add a noise modifier with z set to 0.001m that works

[denisT]

of course it has to be done automatically by the system … but who knows? maybe they forgot or missed something?

as I remember in version something 2018-2019, they changed the intersectRay method… the way of face processing

[Klvnk]

I’ve got plenty of ray intersect stuff I can use instead but it’s not my issue as such

[denisT]

I wrote my own intersection… built-in was too slow for some of my tasks

[Klvnk]

and any fix from autodesk is not going to be back dated

[denisT]

I don’t think we should expect any improvements in this area… you just have to learn to live with these shortcomings

[denisT]

Ha ha ha… believe it or not, noise seems to do wonders. Life takes a turn for the better

[Klvnk]

there’s quite a few ways to duplicate this issue, drag shift a face (poly or mesh) to create a cloned face in the local xy plane will do the trick! how was this never noticed ?