Bugle
09-16-2003, 07:26 PM
10.5i
In chor, select a null belonging to a character, then press enter to unselect, then attempt to select a bone that lies _within_ the bounding box of the null.
This behaviour results in 100% crashes
Tested with own models and CD models ("Eddie"). This does not happen in action window. Appears to be related to incorrect deselection of the null, as it remains highlighted after enter or clicking on empty space.
This is my new proposed "bughunt" thread format, please do not reply (Unless you find a workaround*), only answer the poll yes or no. If "yes" please send a bug report to support@hash.com. Multiple reports should ensure it is caught.
I will bump this thread every AM update until it's fixed.
Feel free to start your own [BUGHUNT] threads ( unless the moderators object :))
*Workaround is to select another bone outside the bounding box and then select the one you want, BTW, I mean something else like "Doesn't happen in Direct3D" (for example, doesn't actually make a difference in this case) and generally speaking for these types of threads the workarounds would be the only replies needed.
That is if it catches on.
In chor, select a null belonging to a character, then press enter to unselect, then attempt to select a bone that lies _within_ the bounding box of the null.
This behaviour results in 100% crashes
Tested with own models and CD models ("Eddie"). This does not happen in action window. Appears to be related to incorrect deselection of the null, as it remains highlighted after enter or clicking on empty space.
This is my new proposed "bughunt" thread format, please do not reply (Unless you find a workaround*), only answer the poll yes or no. If "yes" please send a bug report to support@hash.com. Multiple reports should ensure it is caught.
I will bump this thread every AM update until it's fixed.
Feel free to start your own [BUGHUNT] threads ( unless the moderators object :))
*Workaround is to select another bone outside the bounding box and then select the one you want, BTW, I mean something else like "Doesn't happen in Direct3D" (for example, doesn't actually make a difference in this case) and generally speaking for these types of threads the workarounds would be the only replies needed.
That is if it catches on.
