openvrml-develop

[openvrml-develop] A few Questions

[Christian L. <chr...@vd...>]

Hi

i had trouble building openvrml 0.18.5 in Visual C++.
First i got the newest releases from boost, freetype and the other 
required stuff and tried to run openvrml but it resulted in an error:

The application failed to initialize property (0xE06D7363)

The guide says this is because OPENVRML_DATADIR is not set, but it was set.

(By the way there were some minor issues, too:
- in some project folders (like 
openvrml-0.18.5\ide-projects\Windows\VisualC9_0\OpenVRML\x3d-cad-geometry) 
the *.vcproj file had an incorrect or missing file ending
- in openvrml-0.18.5\src\node\x3d-cad-geometry (and only there) was the 
register_node_metatypes.cpp missing, which i got by a google query
- when building freetype 2.3.12 the libraries have an "MT" included in 
the name, which had to be removed for openvrml to find them)

So i tried openvrml 0.17.12 which worked well.
But i encountered another problem: to load a 3MB wrl-file it takes quite 
a long time. Is this normal or is it caused by some wrong configuration 
or something?
(other vrml-viewers load this file on my machine way faster so i hope 
there is a fault on my side)

Later i gave 0.18.5 a second try. This time i used the versions of 
boost, freetype and so on that were mentioned in the guide.
And i set the OPENVRML_NODE_PATH and OPENVRML_SCRIPT_PATH this time, too.

I don't remember if i did something in addition to that but in the end 
it worked to the point that the error mentioned above did not occure any 
more.
But another one did :-)

Now it says
"
Assertion failed!

Program: ...
File: c:\....\component.cpp
Line: 264

Expression: class_
"

Here the output:
""
sdl-viewer.exe": "C:\Dokumente und 
Einstellungen\Administrator\Desktop\temp\openvrml-0.18.5.tar\openvrml-0.18.5\ide-projects\Windows\VisualC9_0\OpenVRML\Debug\bin\sdl-viewer.exe" 
geladen, Symbole wurden geladen.
"sdl-viewer.exe": "C:\WINDOWS\system32\ntdll.dll" wurde geladen
"sdl-viewer.exe": "C:\WINDOWS\system32\kernel32.dll" wurde geladen
"sdl-viewer.exe": "C:\WINDOWS\system32\winmm.dll" wurde geladen
"sdl-viewer.exe": "C:\WINDOWS\system32\advapi32.dll" wurde geladen
"sdl-viewer.exe": "C:\WINDOWS\system32\rpcrt4.dll" wurde geladen
"sdl-viewer.exe": "C:\WINDOWS\system32\secur32.dll" wurde geladen
"sdl-viewer.exe": "C:\WINDOWS\system32\gdi32.dll" wurde geladen
"sdl-viewer.exe": "C:\WINDOWS\system32\user32.dll" wurde geladen
"sdl-viewer.exe": "C:\Dokumente und 
Einstellungen\Administrator\Desktop\temp\openvrml-0.18.5.tar\openvrml-0.18.5\ide-projects\Windows\VisualC9_0\OpenVRML\Debug\bin\openvrml.dll" 
geladen, Symbole wurden geladen.
"sdl-viewer.exe": "C:\WINDOWS\system32\shlwapi.dll" wurde geladen
"sdl-viewer.exe": "C:\WINDOWS\system32\msvcrt.dll" wurde geladen
"sdl-viewer.exe": "C:\WINDOWS\system32\xmllite.dll" wurde geladen
"sdl-viewer.exe": 
"C:\WINDOWS\WinSxS\x86_Microsoft.VC90.DebugCRT_1fc8b3b9a1e18e3b_9.0.30729.1_x-ww_f863c71f\msvcp90d.dll" 
wurde geladen
"sdl-viewer.exe": 
"C:\WINDOWS\WinSxS\x86_Microsoft.VC90.DebugCRT_1fc8b3b9a1e18e3b_9.0.30729.1_x-ww_f863c71f\msvcr90d.dll" 
wurde geladen
"sdl-viewer.exe": "C:\Dokumente und 
Einstellungen\Administrator\Desktop\temp\openvrml-0.18.5.tar\openvrml-0.18.5\ide-projects\Windows\VisualC9_0\OpenVRML\Debug\bin\openvrml-gl.dll" 
geladen, Symbole wurden geladen.
"sdl-viewer.exe": "C:\WINDOWS\system32\glu32.dll" wurde geladen
"sdl-viewer.exe": "C:\WINDOWS\system32\opengl32.dll" wurde geladen
"sdl-viewer.exe": "C:\WINDOWS\system32\ddraw.dll" wurde geladen
"sdl-viewer.exe": "C:\WINDOWS\system32\dciman32.dll" wurde geladen
"sdl-viewer.exe": "C:\WINDOWS\system32\imm32.dll" wurde geladen
"sdl-viewer.exe": "C:\WINDOWS\system32\wxvault.dll" geladen, Die 
Binärdaten wurden nicht mit Debuginformationen erstellt.
"sdl-viewer.exe": "C:\WINDOWS\system32\psapi.dll" wurde geladen
"sdl-viewer.exe": "C:\WINDOWS\system32\mpr.dll" wurde geladen
"sdl-viewer.exe": "C:\WINDOWS\system32\version.dll" wurde geladen
"sdl-viewer.exe": "C:\WINDOWS\system32\detoured.dll" wurde geladen
"sdl-viewer.exe": "C:\WINDOWS\system32\shell32.dll" wurde geladen
"sdl-viewer.exe": 
"C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.5512_x-ww_35d4ce83\comctl32.dll" 
wurde geladen
"sdl-viewer.exe": "C:\WINDOWS\system32\comctl32.dll" wurde geladen
Eine Ausnahme (erste Chance) bei 0x7c812afb in sdl-viewer.exe: Microsoft 
C++-Ausnahme: `anonymous namespace'::no_registry_key an Speicherposition 
0x0012f528..
Eine Ausnahme (erste Chance) bei 0x00000000 in sdl-viewer.exe: 
0xC0000005: Zugriffsverletzung beim Lesen an Position 0x00000000.
Eine Ausnahme (erste Chance) bei 0x00000000 in sdl-viewer.exe: 
0xC0000005: Zugriffsverletzung beim Lesen an Position 0x00000000.
"sdl-viewer.exe": "C:\WINDOWS\system32\msctf.dll" wurde geladen
"sdl-viewer.exe": "C:\WINDOWS\system32\msctfime.ime" wurde geladen
"sdl-viewer.exe": "C:\WINDOWS\system32\ole32.dll" wurde geladen
"sdl-viewer.exe": "C:\WINDOWS\system32\kbdus.dll" wurde geladen
"sdl-viewer.exe": "C:\WINDOWS\system32\kbdus.dll" entladen.
"sdl-viewer.exe": "C:\WINDOWS\system32\kbdgr.dll" wurde geladen
"sdl-viewer.exe": "C:\WINDOWS\system32\kbdgr.dll" entladen.
"sdl-viewer.exe": "C:\WINDOWS\system32\nvoglnt.dll" wurde geladen
Der Thread 'Win32 Thread' (0x11cc) hat mit Code 0 (0x0) geendet.
"sdl-viewer.exe": "C:\WINDOWS\system32\mcd32.dll" wurde geladen
"sdl-viewer.exe": "C:\WINDOWS\system32\mcd32.dll" entladen.
Eine Ausnahme (erste Chance) bei 0x7c812afb in sdl-viewer.exe: Microsoft 
C++-Ausnahme: `anonymous namespace'::no_registry_key an Speicherposition 
0x0012e470..
Eine Ausnahme (erste Chance) bei 0x7c812afb in sdl-viewer.exe: Microsoft 
C++-Ausnahme: 
boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::filesystem::basic_filesystem_error<boost::filesystem::basic_path<std::basic_string<char,std::char_traits<char>,std::allocator<char> 
 >,boost::filesystem::path_traits> > an Speicherposition 0x0012e390..
Eine Ausnahme (erste Chance) bei 0x7c812afb in sdl-viewer.exe: Microsoft 
C++-Ausnahme: `anonymous namespace'::no_registry_key an Speicherposition 
0x0257f5b4..
Eine Ausnahme (erste Chance) bei 0x7c812afb in sdl-viewer.exe: Microsoft 
C++-Ausnahme: 
boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::filesystem::basic_filesystem_error<boost::filesystem::basic_path<std::basic_string<char,std::char_traits<char>,std::allocator<char> 
 >,boost::filesystem::path_traits> > an Speicherposition 0x0257f4d4..
Der Thread 'Win32 Thread' (0x658) hat mit Code 3 (0x3) geendet.
Der Thread 'Win32 Thread' (0x710) hat mit Code 3 (0x3) geendet.
Der Thread 'Win32 Thread' (0x109c) hat mit Code 3 (0x3) geendet.
Das Programm "[692] sdl-viewer.exe: Systemeigen" wurde mit Code 3 (0x3) 
beendet.
"
I cancelled the program through the error window.

That's it so far. I hope you understand my english :-)

Greets Christian

Re: [openvrml-develop] A few Questions

[Braden M. <br...@en...>]

On Wed, 2010-04-28 at 11:18 +0200, Christian Lang wrote: 
> Hi
> 
> i had trouble building openvrml 0.18.5 in Visual C++.
> First i got the newest releases from boost, freetype and the other 
> required stuff and tried to run openvrml but it resulted in an error:
> 
> The application failed to initialize property (0xE06D7363)
> 
> The guide says this is because OPENVRML_DATADIR is not set, but it was set.

Perhaps it was not set correctly.

> (By the way there were some minor issues, too:
> - in some project folders (like 
> openvrml-0.18.5\ide-projects\Windows\VisualC9_0\OpenVRML\x3d-cad-geometry) 
> the *.vcproj file had an incorrect or missing file ending
> - in openvrml-0.18.5\src\node\x3d-cad-geometry (and only there) was the 
> register_node_metatypes.cpp missing, which i got by a google query

Whoops. :-(

I suspect these two bullet points are the same problem.  (If they
aren't, could you be more specific about what's going on with the first
one?)

I will commit a fix to ensure that this file gets distributed in 0.18.6.

> - when building freetype 2.3.12 the libraries have an "MT" included in 
> the name, which had to be removed for openvrml to find them)

You built the wrong configuration of FreeType.  Did you build the one
specified on the BuildOpenvrmlOnWindows wiki page? (It's possible that
page is incorrect; but I can't check it at the moment.)

> So i tried openvrml 0.17.12 which worked well.
> But i encountered another problem: to load a 3MB wrl-file it takes quite 
> a long time. Is this normal or is it caused by some wrong configuration 
> or something?
> (other vrml-viewers load this file on my machine way faster so i hope 
> there is a fault on my side)

OpenVRML's parser does some fairly rigorous checking of the input, so
it's probably going to be consistently slower than some other parsers.
However, I am hopeful that the forthcoming rewrite of the parser using
Spirit2 will improve the situation.

> Later i gave 0.18.5 a second try. This time i used the versions of 
> boost, freetype and so on that were mentioned in the guide.
> And i set the OPENVRML_NODE_PATH and OPENVRML_SCRIPT_PATH this time, too.
> 
> I don't remember if i did something in addition to that but in the end 
> it worked to the point that the error mentioned above did not occure any 
> more.
> But another one did :-)
> 
> Now it says
> "
> Assertion failed!
> 
> Program: ...
> File: c:\....\component.cpp
> Line: 264
> 
> Expression: class_
> "
> 
> Here the output:

[snip]

Hm... Any chance you could use the debugger to check the value of the
"urn" variable right before this happens?  (In the
openvrml::local::component::add_scope_entry function.)

I suspect what has happened here is that OpenVRML has read a component
descriptor corresponding to a module that, for some reason, wasn't
loaded.  What do you have OPENVRML_NODE_PATH set to?

This could be related to the problem you had with
x3d-cad-geometry/register_node_metatypes.cpp.  Can you try the svn
sources?

        http://svn.openvrml.org/svnroot/openvrml/branches/0.18

-- 
Braden McDaniel <br...@en...>

Re: [openvrml-develop] A few Questions

[Christian L. <chr...@vd...>]

> Perhaps it was not set correctly.
>    
I think it was, because the 0.17.12 version worked fine. Could it be 
that blanks in the path are a problem?
I'll try around more tomorrow.
>> (By the way there were some minor issues, too:
>> - in some project folders (like
>> openvrml-0.18.5\ide-projects\Windows\VisualC9_0\OpenVRML\x3d-cad-geometry)
>> the *.vcproj file had an incorrect or missing file ending
>> - in openvrml-0.18.5\src\node\x3d-cad-geometry (and only there) was the
>> register_node_metatypes.cpp missing, which i got by a google query
>>      
> Whoops. :-(
>
> I suspect these two bullet points are the same problem.  (If they
> aren't, could you be more specific about what's going on with the first
> one?)
>
> I will commit a fix to ensure that this file gets distributed in 0.18.6.
>    
I was wrong about the first one: in x3d-cad-geometry the vcproj file is 
alright. But:
(in the following lines i will refer to subolders of 
openvrml-0.18.5\ide-projects\Windows\VisualC9_0\OpenVRML)

in \x3d-environmental-effects it is "x3d-environmental" instead of 
"x3d-environmental-effects.vcproj"
in \x3d-event-utilities it is "x3d-event-utilities.vcp" instead of 
"x3d-event-utilities.vcproj"
in \x3d-key-device-sensor it is "x3d-key-device-sensor" instead of 
"x3d-key-device-sensor.vcproj"

This applies to 
http://sourceforge.net/projects/openvrml/files/openvrml/0.18.5/openvrml-0.18.5.tar.gz/download

In the current svn revision the filenames are correct, as i noticed today.

> You built the wrong configuration of FreeType.  Did you build the one
> specified on the BuildOpenvrmlOnWindows wiki page? (It's possible that
> page is incorrect; but I can't check it at the moment.)
>    
I built the LIB Debug Multithreaded and LIB Release Multithreaded as 
specified on the wiki page.
This produces the freetype2312MT_D.lib whereas openvrml wants the 
freetype2312_D.lib.

Besides, in version 0.17.12 openvrml requires the freetype239MT_D.lib 
and not the freetype239_D.lib.

> [snip]
>
> Hm... Any chance you could use the debugger to check the value of the
> "urn" variable right before this happens?  (In the
> openvrml::local::component::add_scope_entry function.)
>    
I'll try that tomorrow hopefully.
> I suspect what has happened here is that OpenVRML has read a component
> descriptor corresponding to a module that, for some reason, wasn't
> loaded.  What do you have OPENVRML_NODE_PATH set to?
>    
to [blabla]\openvrml-0.18.5\openvrml-0.18.5\src\node
> This could be related to the problem you had with
> x3d-cad-geometry/register_node_metatypes.cpp.  Can you try the svn
> sources?
>
>          http://svn.openvrml.org/svnroot/openvrml/branches/0.18
>    
What is the difference between

http://svn.openvrml.org/svnroot/openvrml/branches/0.18

and

http://svn.openvrml.org/svnroot/openvrml/trunk
?


Greets

Re: [openvrml-develop] A few Questions

[Braden M. <br...@en...>]

On Thu, 2010-04-29 at 12:52 +0200, Christian Lang wrote: 
> > Perhaps it was not set correctly.
> >    
> I think it was, because the 0.17.12 version worked fine.

0.17.x does not require this setting.

> Could it be 
> that blanks in the path are a problem?
> I'll try around more tomorrow.

I don't *think* spaces in the path are a problem; but this might be
worth testing.

> >> (By the way there were some minor issues, too:
> >> - in some project folders (like
> >> openvrml-0.18.5\ide-projects\Windows\VisualC9_0\OpenVRML\x3d-cad-geometry)
> >> the *.vcproj file had an incorrect or missing file ending
> >> - in openvrml-0.18.5\src\node\x3d-cad-geometry (and only there) was the
> >> register_node_metatypes.cpp missing, which i got by a google query
> >>      
> > Whoops. :-(
> >
> > I suspect these two bullet points are the same problem.  (If they
> > aren't, could you be more specific about what's going on with the first
> > one?)
> >
> > I will commit a fix to ensure that this file gets distributed in 0.18.6.
> >    
> I was wrong about the first one: in x3d-cad-geometry the vcproj file is 
> alright. But:
> (in the following lines i will refer to subolders of 
> openvrml-0.18.5\ide-projects\Windows\VisualC9_0\OpenVRML)
> 
> in \x3d-environmental-effects it is "x3d-environmental" instead of 
> "x3d-environmental-effects.vcproj"
> in \x3d-event-utilities it is "x3d-event-utilities.vcp" instead of 
> "x3d-event-utilities.vcproj"
> in \x3d-key-device-sensor it is "x3d-key-device-sensor" instead of 
> "x3d-key-device-sensor.vcproj"
> 
> This applies to 
> http://sourceforge.net/projects/openvrml/files/openvrml/0.18.5/openvrml-0.18.5.tar.gz/download
> 
> In the current svn revision the filenames are correct, as i noticed today.

They're correct in the tarball, too:

        $ tar tvf openvrml-0.18.5.tar.gz | grep x3d-environmental-effects[.]vcproj
        -rw-r--r-- braden/users    4598 2009-07-04 17:20 openvrml-0.18.5/ide-projects/Windows/VisualC9_0/OpenVRML/x3d-environmental-effects/x3d-environmental-effects.vcproj
        $ tar tvf openvrml-0.18.5.tar.gz | grep x3d-event-utilities[.]vcproj
        -rw-r--r-- braden/users    5904 2009-07-04 17:20 openvrml-0.18.5/ide-projects/Windows/VisualC9_0/OpenVRML/x3d-event-utilities/x3d-event-utilities.vcproj
        $ tar tvf openvrml-0.18.5.tar.gz | grep x3d-key-device-sensor[.]vcproj
        -rw-r--r-- braden/users    4785 2009-07-04 17:20 openvrml-0.18.5/ide-projects/Windows/VisualC9_0/OpenVRML/x3d-key-device-sensor/x3d-key-device-sensor.vcproj
        
It sounds like there's probably something wrong with the program you're
using to unpack the tarball.  Make sure the program supports the tar pax
format.

> > You built the wrong configuration of FreeType.  Did you build the one
> > specified on the BuildOpenvrmlOnWindows wiki page? (It's possible that
> > page is incorrect; but I can't check it at the moment.)
> >    
> I built the LIB Debug Multithreaded and LIB Release Multithreaded as 
> specified on the wiki page.
> This produces the freetype2312MT_D.lib whereas openvrml wants the 
> freetype2312_D.lib.

Yes, the page was incorrect.  You want the "LIB Release" and "LIB Debug"
configurations.

> Besides, in version 0.17.12 openvrml requires the freetype239MT_D.lib 
> and not the freetype239_D.lib.

Yeah; but I think this is a bug in the 0.17 project files.  The OpenVRML
project files are set up to be built with /MD(d); so its dependencies
should match that.

> > [snip]
> >
> > Hm... Any chance you could use the debugger to check the value of the
> > "urn" variable right before this happens?  (In the
> > openvrml::local::component::add_scope_entry function.)
> >    
> I'll try that tomorrow hopefully.
> > I suspect what has happened here is that OpenVRML has read a component
> > descriptor corresponding to a module that, for some reason, wasn't
> > loaded.  What do you have OPENVRML_NODE_PATH set to?
> >    
> to [blabla]\openvrml-0.18.5\openvrml-0.18.5\src\node

That's probably not correct.  It needs to be set to where the DLL
modules are located (i.e., vrml97.dll, x3d-core.dll, etc.).  Similarly,
OPENVRML_SCRIPT_PATH needs to be set to where the scripting engine
modules live (javascript.dll and java.dll).

> > This could be related to the problem you had with
> > x3d-cad-geometry/register_node_metatypes.cpp.  Can you try the svn
> > sources?
> >
> >          http://svn.openvrml.org/svnroot/openvrml/branches/0.18
> >    
> What is the difference between
> 
> http://svn.openvrml.org/svnroot/openvrml/branches/0.18
> 
> and
> 
> http://svn.openvrml.org/svnroot/openvrml/trunk
> ?

branches/0.18 is what future 0.18.x releases will be made from.  trunk
will become 0.19.0.

-- 
Braden McDaniel <br...@en...>

Re: [openvrml-develop] A few Questions

[Christian L. <chr...@vd...>]

 > > > What do you have OPENVRML_NODE_PATH set to?
 > > >
 > > to [blabla]\openvrml-0.18.5\openvrml-0.18.5\src\node
 >
 > That's probably not correct.  It needs to be set to where the DLL
 > modules are located (i.e., vrml97.dll, x3d-core.dll, etc.).

Yep, that was the problem. But for the sake of completeness:

 > Hm... Any chance you could use the debugger to check the value of the
 > "urn" variable right before this happens?  (In the
 > openvrml::local::component::add_scope_entry function.)

It seems to be:

0x00e5d000 "urn:X-openvrml:node:Anchor"

and it points to:

117 'u'

But with the correct setting of OPENVRML_NODE_PATH this does not occur 
any more.
By the way, this (the setting of OPENVRML_NODE_PATH) is a point missing 
on the wiki page.


 > It sounds like there's probably something wrong with the program you're
 > using to unpack the tarball.  Make sure the program supports the tar pax
 > format.

I used 7zip for that, but i will use the svn sources from now on.

Now it seems to work so far (my world loads), but with the svn sources i 
get some errors in the output about some "incorrect handle"s.

By the way, is there already a implemented way to rotate the world 
around another point than the centre?

Re: [openvrml-develop] A few Questions

[Braden M. <br...@en...>]

On Fri, 2010-04-30 at 16:10 +0200, Christian Lang wrote: 
> > > > What do you have OPENVRML_NODE_PATH set to?
>  > > >
>  > > to [blabla]\openvrml-0.18.5\openvrml-0.18.5\src\node
>  >
>  > That's probably not correct.  It needs to be set to where the DLL
>  > modules are located (i.e., vrml97.dll, x3d-core.dll, etc.).
> 
> Yep, that was the problem. But for the sake of completeness:
> 
>  > Hm... Any chance you could use the debugger to check the value of the
>  > "urn" variable right before this happens?  (In the
>  > openvrml::local::component::add_scope_entry function.)
> 
> It seems to be:
> 
> 0x00e5d000 "urn:X-openvrml:node:Anchor"
> 
> and it points to:
> 
> 117 'u'
> 
> But with the correct setting of OPENVRML_NODE_PATH this does not occur 
> any more.
> By the way, this (the setting of OPENVRML_NODE_PATH) is a point missing 
> on the wiki page.

Yup, I thought that would be it.

And you're right... the correct setting for OPENVRML_{NODE,SCRIPT}_PATH
could be made clearer to Visual Studio users.  I'll put this on the Wiki
page, and possibly augment README as well.

> > It sounds like there's probably something wrong with the program you're
>  > using to unpack the tarball.  Make sure the program supports the tar pax
>  > format.
> 
> I used 7zip for that, but i will use the svn sources from now on.

Then also note

        http://svn.openvrml.org/svnroot/openvrml/tags

... where you'll find the tagged releases that correspond to release
tarballs.

The pax format has been around for a while and is well supported on
POSIXy systems.  It's a little surprising that a modern tool wouldn't
work with it.  (Note that I started using this format precisely to
support the path lengths in the openvrml tarball.)  You might want to
try something like WinZip; at the very least, I'm sure that GNU tar
(which you could get with Cygwin) would work.

But if you're comfortable using svn, that's just fine, too.

> Now it seems to work so far (my world loads), but with the svn sources i 
> get some errors in the output about some "incorrect handle"s.

This isn't ringing any bells for me.  Can you provide more details?

> By the way, is there already a implemented way to rotate the world 
> around another point than the centre?

No.  But a patch to implement this per the X3D
Viewpoint.centerOfRotation field would be welcome.

-- 
Braden McDaniel <br...@en...>