[X3D courses] R: Re: cathedral model checked into version control

Don Brutzman brutzman at nps.edu
Wed Feb 15 06:08:23 PST 2012


Summary:  additional changes made, everything published online and checked
into version control.  Subversion changes (diffs) visible at

http://x3d.svn.sourceforge.net/viewvc/x3d/www.web3d.org/x3d/content/examples/X3dForAdvancedModeling/

http://x3d.svn.sourceforge.net/viewvc/x3d/www.web3d.org/x3d/content/examples/X3dForAdvancedModeling/SanCarlosCathedral/SanCarlosCathedral.x3d?view=log

http://x3d.svn.sourceforge.net/viewvc/x3d/www.web3d.org/x3d/content/examples/X3dForAdvancedModeling/SanCarlosCathedral/SanCarlosCathedral.x3d?r1=10410&r2=10445

these diffs will get much cleaner/simpler when submodels are checked
into their own separate files.


On 2/14/2012 5:40 PM, Don Brutzman wrote:
> On 2/14/2012 4:12 PM, miczaska at libero.it wrote:
>> San Carlos Cathedral model in progress:
>>
>> - Viewpoints: A possible guided tour in 20 steps

see below.  future work once it looks good: add ViewpointSequencer

>> - Modeling: Bells, Cross, Altar and some decorations added

Are you ready to start splitting out some of these individual items
as separate files, which we then Inline into the master?

This will make the overall model much more modular and maintainable,
we can perfect each piece separately.

Am hoping that we can use English names for Bell.x3d, Cross.x3d, Altar.x3d,
Bench.x3d etc.

>> - Textures: Floor completed
>>
>> - Errors checked: Problems in finding the indexedfacesets with extra points
>> (I'll do it soon), I hope the rest is done
> 
> wow it all looks very good Michele!!
> 
> btw we would have been happy to call you when you mailed this,
> Chad and I were discussing X3D etc. when you sent your email.
> 
> Here are some viewpoints and background I had added recently, please
> decide if you want them.  Yours are likely better.
> 
>      <Viewpoint centerOfRotation='5 0 -30' description='San Carlos Cathedral, front above' orientation='1 0 0 -0.349' position='5.3 16 30'/>
>      <Viewpoint centerOfRotation='5 0 -30' description='San Carlos Cathedral, front' position='4.3 5 25'/>
>      <Viewpoint centerOfRotation='5 0 -30' description='Front doors, looking in' position='5 0 0'/>
>      <Viewpoint centerOfRotation='5 0 -30' description='Left rear balcony' position='3 5 -5'/>
>      <NavigationInfo avatarSize='0.01 1.6 0.75' type='"EXAMINE" "FLY" "WALK" "ANY"'/>

Two NavInfo nodes now provided.  We start outside the church in EXAMINE mode,
once going inside we return to FLY mode.  This is done by ROUTES that connect
the binding of external viewpoints.  When they unbind, we revert to FLY mode.
Later we can also experiment with WALK mode.

    <Background groundAngle='1.57' groundColor='0.9804 0.8235 0 0.6 0.3254902 0' skyColor='0.7216 0.8 0.9922'/>
    <NavigationInfo DEF='FLYnavigation' avatarSize='0.01 1.6 0.75' speed='4' type='"FLY" "ANY"'/>
    <NavigationInfo DEF='WALKnavigation' avatarSize='0.01 1.6 0.75' speed='4' type='"WALK" "ANY"'/>
    <NavigationInfo DEF='EXAMINEnavigation' avatarSize='0.01 1.6 0.75' speed='4' type='"EXAMINE" "ANY"'/>
        <Viewpoint DEF='ViewpointFrontAbove' centerOfRotation='5.8 0 -24.4' description='San Carlos Cathedral, front above' orientation='1 0 0 -0.349' position='5.3 16 30'/>
        <Viewpoint DEF='ViewpointFront' centerOfRotation='5.8 0 -24.4' description='San Carlos Cathedral, front' position='4.3 5 25'/>
        <!--
        <ROUTE fromField='isBound' fromNode='ViewpointFrontAbove' toField='set_bind' toNode='EXAMINEnavigation'/>
        <ROUTE fromField='isBound' fromNode='ViewpointFront' toField='set_bind' toNode='EXAMINEnavigation'/>
        -->
        <Viewpoint centerOfRotation='5.8 0 -24.4' description='Front, closer' orientation='1 0 0 0.2' position='5.8 0 18'/>
        <Viewpoint centerOfRotation='5.8 0 -24.4' description='Front doors, looking in' position='5.8 0 0'/>
etc.

Unfortunately these ROUTEs cause a crash for InstantReality, haven't seen
that before.  We'll have to report this bug if we can't fix it otherwise.

Notice I also increased the NavigationInfo speed so that response is faster.

>      <Background groundAngle='1.5700001' groundColor='0.9804 0.8235 0 0.6 0.3254902 0' skyColor='0.7216 0.8 0.9922'/>

moved to top

> Suggestions on next steps please:
> - put all images in an "images/" subdirectory
> - Use full names for images

Before changing urls to include online addresses, it is important
to have DEF and USE nodes.  This simplifies authoring, and also
greatly improves performance:  image files are only downloaded once,
instead of many times.

I checked and found that this point was not present in the X3D Scene Authoring Hints.
Now added:

            <li>
                It is important to include DEF and USE when multiple copies of an image or movie file are present in a scene.
                This avoids delays and reduces memory consumption that results from reloading the same file multiple times.
                <ul>
                    <li>If the image file might be different each time it is retrieved, then DEF/USE isn't appropriate.</li>
                </ul>
            </li>

http://www.web3d.org/x3d/content/examples/X3dSceneAuthoringHints.html#Images

> - add online url for images - X3D-Edit has a nice feature for this that i can show you,
> 	there is a button to add the url versions if there is a meta identifier tag

The button is called 'Additional urls' and is very convenient, please try it.

> - Can we shift to English for file names?  Or provide a dictionary for words you use?

This is most important for file names and helps readability a lot.

	Pav -> Paving
	PavMat -> PavingMaterial

Naming conventions:
http://www.web3d.org/x3d/content/examples/X3dSceneAuthoringHints.html#NamingConventions
 
> let me fix the image directories and urls, i will then check them in.

done

> When I run it through the conversion tools, I get the following errors:
> 
>> processScenes.X3DtoVRML97:
>> stylesheet compiled=false
>> C:\www.web3d.org\x3d\content\examples\X3dForAdvancedModeling/SanCarlosCathedral//SanCarlosCathedral - Copy.x3d processing with X3dToVrml97 stylesheet
>> &lt;meta name='warning' content='under development'/&gt;
>> C:\www.web3d.org\x3d\content\examples\X3dForAdvancedModeling/SanCarlosCathedral//SanCarlosCathedral.x3d processing with X3dToVrml97 stylesheet
>> &lt;meta name='warning' content='under development'/&gt;
>> [Hint] For best scene portability, append alternate online address for revised url=' "Pav.jpg" "http://X3dGraphics.com/examples/X3dForAdvancedModeling/SanCarlosCatheral/Pav.jpg" ' [check X3D source or VRML output to find pertinent ImageTexture]
>> [Hint] For best scene portability, append alternate online address for revised url=' "PavMat.jpg" "http://X3dGraphics.com/examples/X3dForAdvancedModeling/SanCarlosCatheral/PavMat.jpg" ' [check X3D source or VRML output to find pertinent ImageTexture]
>> [Hint] For best scene portability, append alternate online address for revised url=' "linea.jpg" "http://X3dGraphics.com/examples/X3dForAdvancedModeling/SanCarlosCatheral/linea.jpg" ' [check X3D source or VRML output to find pertinent ImageTexture]
[...]

all fixed

>> [Error] MFVec3f attribute point='0.62265 0.0 0 0.6218712004456791 0.0311325 0 0.6195289277144369 0.062265 0 0.6156053358230011 0.0933' [...] must contain an integer multiple of triplet values [check X3D source or VRML output to find erroneous Coordinate node]
>> [Error] MFVec3f attribute point='0.62265 0.0 0 0.6218712004456791 0.0311325 0 0.6195289277144369 0.062265 0 0.6156053358230011 0.0933' [...] must contain an integer multiple of triplet values [check X3D source or VRML output to find erroneous Coordinate node]
>> [Error] MFVec3f attribute point='0.62265 0.0 0 0.6218712004456791 0.0311325 0 0.6195289277144369 0.062265 0 0.6156053358230011 0.0933' [...] must contain an integer multiple of triplet values [check X3D source or VRML output to find erroneous Coordinate node]

same as previously reported

>> [Error] mismatched node type for&lt;Group DEF='Bar'/&gt; and&lt;Shape USE='Bar'/&gt; [node DEF='']

fixed:  changed

	<Shape USE='Bar'/>
to
	<Group USE='Bar'/>

>> [Error] SFVec3f attribute translation='1.5 0 0 0' must contain 3 values [check X3D source or VRML output to find erroneous Transform node]
>> [Error] SFVec3f attribute translation='1.5 0 0 0' must contain 3 values [check X3D source or VRML output to find erroneous Transform node]
>> [Error] SFVec3f attribute translation='1.5 0 0 0' must contain 3 values [check X3D source or VRML output to find erroneous Transform node]
>> [Error] SFVec3f attribute translation='1.5 0 0 0' must contain 3 values [check X3D source or VRML output to find erroneous Transform node]

	<Transform translation='1.5 0 0 0'>
changed to
	<Transform translation='1.5 0 0'>

This gets you back to XML validation working each time.
Frequent validation is very helpful, it helps you identify and fix
simple problems quickly before they become bigger problems.

>> processScenes.X3DtoVRML97 complete.
>> processScenes.X3dToXhtml:
>> stylesheet compiled=false
>> C:\www.web3d.org\x3d\content\examples\X3dForAdvancedModeling/SanCarlosCathedral//SanCarlosCathedral - Copy.x3d processing with X3dToXhtml stylesheet
>> plotSvgExtrusionCrossSection svgFilename=SanCarlosCathedral.Extrusion1.svg
>> plotSvgExtrusionCrossSection svgFilename=SanCarlosCathedral.Extrusion2.svg
>> C:\www.web3d.org\x3d\content\examples\X3dForAdvancedModeling/SanCarlosCathedral//SanCarlosCathedral.x3d processing with X3dToXhtml stylesheet
>> plotSvgExtrusionCrossSection svgFilename=SanCarlosCathedral.Extrusion1.svg
>> plotSvgExtrusionCrossSection svgFilename=SanCarlosCathedral.Extrusion2.svg
>> plotSvgExtrusionCrossSection svgFilename=SanCarlosCathedral.Extrusion3.svg
>> plotSvgExtrusionCrossSection svgFilename=SanCarlosCathedral.Extrusion4.svg
>> plotSvgExtrusionCrossSection svgFilename=SanCarlosCathedral.Extrusion5.svg
>> plotSvgExtrusionCrossSection svgFilename=SanCarlosCathedral.Extrusion6.svg
>> plotSvgExtrusionCrossSection svgFilename=SanCarlosCathedral.Extrusion7.svg
>> plotSvgExtrusionCrossSection svgFilename=SanCarlosCathedral.Extrusion8.svg
>> plotSvgExtrusionCrossSection svgFilename=SanCarlosCathedral.Extrusion9.svg
>> plotSvgExtrusionCrossSection svgFilename=SanCarlosCathedral.Extrusion10.svg
>> plotSvgExtrusionCrossSection svgFilename=SanCarlosCathedral.Extrusion11.svg
>> plotSvgExtrusionCrossSection svgFilename=SanCarlosCathedral.Extrusion12.svg
>> plotSvgExtrusionCrossSection svgFilename=SanCarlosCathedral.Extrusion13.svg
>> plotSvgExtrusionCrossSection svgFilename=SanCarlosCathedral.Extrusion14.svg
>> plotSvgExtrusionCrossSection svgFilename=SanCarlosCathedral.Extrusion15.svg
>> plotSvgExtrusionCrossSection svgFilename=SanCarlosCathedral.Extrusion16.svg
>> plotSvgExtrusionCrossSection svgFilename=SanCarlosCathedral.Extrusion17.svg
>> plotSvgExtrusionCrossSection svgFilename=SanCarlosCathedral.Extrusion18.svg
>> plotSvgExtrusionCrossSection svgFilename=SanCarlosCathedral.Extrusion19.svg
>> plotSvgExtrusionCrossSection svgFilename=SanCarlosCathedral.Extrusion20.svg

you might find these helpful, the Extrusion crossSection fields are linked to
these diagrams in the pretty-print HTML versions

>> processScenes.X3dToXhtml complete.
>> platformType:
>> initializeWindows:
>> initializeUnix:
>> initializeMac:
>> platformInitialize:
>> processScenes.captureViewpointImages:
>> processScenes.captureViewpointImages complete.
>> processScenes.X3dToX3dvClassicVrmlEncoding:
>> stylesheet compiled=false
>> C:\www.web3d.org\x3d\content\examples\X3dForAdvancedModeling/SanCarlosCathedral//SanCarlosCathedral - Copy.x3d processing with X3dToX3dvClassicVrmlEncoding stylesheet
>> C:\www.web3d.org\x3d\content\examples\X3dForAdvancedModeling/SanCarlosCathedral//SanCarlosCathedral.x3d processing with X3dToX3dvClassicVrmlEncoding stylesheet
>> processScenes.X3dToX3dvClassicVrmlEncoding complete.
> 
>> C:\www.web3d.org\x3d\content\examples\X3dForAdvancedModeling\SanCarlosCathedral\SanCarlosCathedral.x3d validation using compiled X3D Schematron rules
>> <meta name='warning' content='under development'/>[/X3D/head/meta[12], diagnostic]
>> <ImageTexture DEF=''/>  url array address(es) missing online http/https references (url='Pav.jpg') [/X3D/Scene/Transform[1]/Shape/Appearance/ImageTexture, info]
>> <ImageTexture DEF=''/>  url string array needs to begin and end with "quote marks".  Corrected example:<ImageTexture DEF='' url='"Pav.jpg"'/>  [/X3D/Scene/Transform[1]/Shape/Appearance/ImageTexture, error]
>> <ImageTexture DEF=''/>  url array address(es) missing online http/https references (url='PavMat.jpg') [/X3D/Scene/Transform[2]/Shape/Appearance/ImageTexture, info]
>> <ImageTexture DEF=''/>  url string array needs to begin and end with "quote marks".  Corrected example:<ImageTexture DEF='' url='"PavMat.jpg"'/>  [/X3D/Scene/Transform[2]/Shape/Appearance/ImageTexture, error]
>> <ImageTexture DEF=''/>  url array address(es) missing online http/https references (url='linea.jpg') [/X3D/Scene/Transform[3]/Shape/Appearance/ImageTexture, info]
>> <ImageTexture DEF=''/>  url string array needs to begin and end with "quote marks".  Corrected example:<ImageTexture DEF='' url='"linea.jpg"'/>  [/X3D/Scene/Transform[3]/Shape/Appearance/ImageTexture, error]
[...]

as before, all fixed

>> <Shape DEF=''/>  found without child Appearance or Color [/X3D/Scene/Transform[31]/Transform[14]/Transform[1]/Transform[6]/Shape, warning]
>> <Shape DEF=''/>  found without child Appearance or Color [/X3D/Scene/Transform[31]/Transform[14]/Transform[1]/Transform[7]/Shape, warning]
>> <Coordinate DEF=''/>  point array has 82.33333333333333' triples, likely has incorrect number of values or missing whitespace [/X3D/Scene/Transform[31]/Transform[14]/Transform[10]/Shape/IndexedFaceSet/Coordinate, warning]
[...]

same as previously reported

So:  much progress, very impressive.

all the best, Don
-- 
Don Brutzman  Naval Postgraduate School, Code USW/Br       brutzman at nps.edu
Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA   +1.831.656.2149
X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman


More information about the x3d-courses mailing list