I was recently made aware that my Quesa Wrappers failed to work on
Windows XP when compiled with RB2006r4 or RB2007r1 but worked fine
with 2006r3. A little digging revealed that creating an Object3D no
longer initializes Quesa (an implementation detailed my wrappers rely
on). This happens on Windows at least, Mac builds work fine. I
suppose this could be a general problem with global private
properties going out of scope when they shouldn't, but I'd suspect a
bug like that would bite many more users...

Anyway, just thought I'd post here to get some feedback from others.
The "fix" is to forcefully initialize Quesa with a declare prior to
using any other declares, but the fact that you can't predict when
RB3D initializes Quesa means that it might also decide to shutdown
Quesa before you're done with it - which is also very nasty.

I'm assuming this is a bug, but it's a pain for me to debug on XP
right now so it might be a while before I get around to posting a
report.