XNAMatrixFromMSTSCoordinates returns NaN value for very-close coordinates

[Dennis A T]

Under certain conditions involving vehicles less than 1mm in length, eg spacer/headboard/tailboard vehicles, XNAMatrix contains bad values. This causes OR to freeze, see http://www.elvastower.com/forums/index.php?/topic/27127-xnamatrixm32-returns-a-nan-value/.

A suggested patch to detect the zero divide condition that occurs in XNAMatrixFromMSTSCoordinates() is attached.

[Carlo Santucci (carlosanit1)]

Dennis, I see that the bug has been assigned to you. Do you have the access rights to commit the patch? If not, I can do that, as I see that things don't move here :)

[Dennis A T (dennisat)]

Hi Carlo,

I'm still very much an amateur and have no developer rights.

In the last post on the "Maybe it's a bug" forum, James suggested that he or someone else who knew the area of concern should check the patch. I have presumed that it's been waiting for assignment to a qualified person to do the checks.

I've tested this as well as I'm able and have been running with it installed on my system since I produced the patch. I've noticed no adverse effects and had no crashes.

Because the crash only happened about once every 4 tests, I put a rather "Mickey Mouse" message in the patch to reassure me that when the conditions occurred the patch was working. This message probably doesn't need to be there if the patch goes live.

Dennis

[Carlo Santucci (carlosanit1)]

OK Dennis,
I've committed it in release x.3244 removing the trace line. Thank you for your contribution!