On 31-Jan-07, at 4:00 PM, David Grogono wrote:
As another data point I have many RB3D apps that are all working
fine on Windows. I'm guessing that your projects all use Declares
and mine (and Franco's) do not.
A plain RB3D project comes up blank for me - no declares - but I'll
do some more testing when I have time (i.e. in a couple weeks). The
project in question was a lighting test so maybe Quesa's point lights
are broken on Windows and the scene was black due to that...
I believe there was a change not that long ago where Quesa is built
in to the compiled Windows app as it is on Linux. I thought this
change occurred before 2006r4 but perhaps that was the first
version with the change. Could this explain what you are seeing?
Declares work with 2006r3, but not in 2006r4 or later*. I don't
recall a release note about this but I know several people who'll be
quite upset if declares stopped working on Windows... :/
* If you force-initialize Quesa with a declare things seem to work OK
- not that I tested extensively - this suggests RB3D is linking with
the external DLL, 'cause IIRC, you can't link to two separate Quesa
libraries and not crash horribly - though perhaps Windows expresses
this as a slow death instead of the immediate crash you'd see on OS
X. If Quesa is statically linked the evaluation to bug #nbwdxvgr
would still be bogus however.
Frank.
<http://developer.chaoticbox.com/>
<http://macgameblog.com/>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|