loadRawData fails on IE8

[Steg]

I am developing an O3D application and noticed that I was getting
issues when using IE8, but not in Firefox. I tracked it down the the
o3djs.io.loadRawData() function failing to load texture data from the
server.

After banging my head against a brick wall trying to track this down
for half a day, I tried browsing some of the links in the "Community
Gallery" and the same sorts of errors happen, for example:

http://www.patapom.com/O3D/Cathedral_Intro.html
http://www.kylehayward.com/o3d/WaterScene.html

and virtually every example in the list (at http://code.google.com/apis/o3d/docs/gallery.html).
Typically, I get lots of alert windows saying "Could not load ...".

Anybody have similar issues?

[Gregg Tavares]

I just tried those links in IE8 on XP and it worked on my machine. I wonder what is different on yours.

What OS are you on and what version of O3D?

You can check the version of O3D in firefox by typing "about:plugins" in the address bar.

--

You received this message because you are subscribed to the Google Groups "O3D-discuss" group.
To post to this group, send email to o3d-d...@googlegroups.com.
To unsubscribe from this group, send email to o3d-discuss...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/o3d-discuss?hl=.

[Steg]

I think my last message must have got lost somewhere!!! It went
something like this:

I'm using XP SP2, and O3D 0.1.42.3.

I downloaded and compiled the source to see if I could find anything
useful, but no. I whittled it down to some MS code and then I can
debug no further:

- In stream_operation.cc:599, there is a call to URLOpenStream().
- While this function is being executed, the function
StreamOperation::OnStopBinding() (stream_operation.cc:296) is called
with an hresult argument of E_NOINTERFACE - in terms of the O3D source
code, this seems to be where the errors originate from i.e. this error
is then passed all the way up to the point where the javascript
callback is called. I cannot do any detailed debugging beyond this
since it's in MS code, so another approach needs to be taken

Also tried on a different machine with IE7 and it worked OK. I
originally thought that it may be some IE security settings regarding
activeX, but after playing around with them I don't think it is.