<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Message</TITLE>
<META content="MSHTML 6.00.2900.3243" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial size=2><SPAN class=375525718-05022008>Hi,
</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=375525718-05022008>I've submitted a
temporary patch to repair the RaySensor. Details in the patch
description.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=375525718-05022008>It opens a
discussion: i</SPAN></FONT><FONT face=Arial size=2><SPAN
class=375525718-05022008>n Blender 2.45 the ray sensor stops on the
first object with or without the matching property/material. However the
code in KX_RayCast::RayTest() is an attempt to look behind non matching objects
so it was decided at some point in the past that the ray sensor should "see"
through non matching objects. But there is a bug in that code causing infinite
loop.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=375525718-05022008>The question is: do
we want to keep the 2.45 behaviour or fix the bug and make the ray sensor
"X-ray" capable? I personally think that the 2.45 behaviour is more logical but
the X-Ray mode can also be usefull. So maybe make it
optional?</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=375525718-05022008></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=375525718-05022008></SPAN></FONT><FONT
face=Arial size=2><SPAN class=375525718-05022008><FONT color=#008000
size=2><FONT color=#000000></FONT><FONT color=#000000></FONT><FONT
color=#000000></FONT></FONT><FONT color=#008000 size=2><FONT
color=#000000></FONT> </DIV></FONT></SPAN></FONT></BODY></HTML>