Hi Frank -
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.
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?
- David
On Jan 31, 2007, at 1:04 PM, Frank Condello wrote:
On 31-Jan-07, at 1:08 PM, Franco Vaccari wrote:
I tried your Primitives example from the Quesa wrappers, and got
many failed assertions like this, probably one per primitive:
Runtime Error 4: Failed Assertion
loaderX86.cpp: 282
Failure Condition: functionEntry
Could not resolve function 'Q3Error_Register' in Quesa
That looks like an entirely different problem... a functionEntry
failure means it can't find Quesa.Framework, and I believe that's
RB3D firing the assertion. The hard declares in the Quesa Wrappers
would fail on launch with a system-supplied error dialog.
Compiled with 2007r1 Mac IDE, run with Win XP under Parallels on a
Intel iMac
But the RB3D based program I'm working on now runs under Windows
(without any Quesa declare), so the statement "RB3D just plain
doesn't work on Windows" is not true here, as well as the sentence
"Install Quesa an run any RB3D project - you get a blank display
(at least I do)" that I see in the feedback report.
Well I did qualify that statement with "at least I do" ;) All
indications are, that on my XP box, Quesa is never initialized by
RB3D. It's possible you're using some RB3D object that does
initialize Quesa at some point, whereas my test project never does.
Without the RB3D plugin source code in front of me I can't tell
anyone what's really wrong, I can only make an educated guess...
I have to add that I'm unable to track a crash that later occurs
in my own app (only in Win32, not in Mac OS X): after closing all
windows I get a crash if I open a new one, with no way of falling
back to the remote debugger. Possibly a side effect of something
dirty related to your findings...
It's possible that some RB3D objects initialize Quesa, but others
shut it down pre-maturely. From what I understand RB3D basically
ref-counts Quesa initializations (so you don't have to start/stop
it manually), and if those locks/unlocks get out of whack really
bad things can happen.
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>
_______________________________________________
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>
|