POV-Ray : Newsgroups : povray.newusers : Texture Coords : Re: Texture Coords Server Time
29 Jul 2024 10:24:31 EDT (-0400)
  Re: Texture Coords  
From: Chris B
Date: 10 Mar 2006 05:02:22
Message: <44114eae$1@news.povray.org>
"Bo" <nomail@nomail> wrote in message 
news:web.4411376c4a827609ec325a890@news.povray.org...
> Hi there, thanks for your time.
>
> Okay, you are right. By saying "import" I meant that I have converted a 
> Open
> Invetor File (.iv) to .pov using a converter named "ivtopov.exe". I did 
> not
> look more closely to it asuming that it works correct (maybe an error 
> :) ).
>
> So I have a CAD Software called VPack (www.erpa.de) using OI (Open 
> Inventor)
> libs to create .iv Files. Those images are to be printed with a fairly 
> high
> resolution on DinA3 formated pages. That is where pov-ray comes in.
>
> But for now my textures, which are stored in uv-coords in the .iv-File (so
> thats what I guess from overlooking sample files) are not being displayed
> correctly. Maybe thats a problem with the converter. I will try IVCON on
> that one.
>
> I hope I explained it a little better this time.
>
> Bo
>


Hi Bo,

The good news is that, from what I've just read, what you are attempting 
seems to be possible.

POV-Ray 3.6 (and possibly earlier versions) supports UV mapping of textures 
onto mesh objects. See section 3.5.7 UV Mapping of the docs where there's an 
example of the syntax. You could take a look inside the output from 
'ivtopov' to see whether it specifies a mesh or mesh2 with uv mapping and to 
check whether it's specifying the syntax correctly. POV-Ray supports quite a 
few formats - See Bitmap-Type in section 3.5.1.5.1  "Specifying an Image 
Map" of the POV-Ray documentation.

You also need to check the file generated by the converter to see how the 
texture is specified. I suspect it might be an RGB image in a separate file. 
If it is you could open it in a graphics editor to check that it contains 
the texture you think it should contain. Also make sure it is in a format 
that POV-Ray understands and obviously check the POV-Ray message stream to 
make sure it's not complaining about anything to do with the file.

I found a reference at 
http://www.hammerve.com/NewHome/FreeStuff/Converters/iv2pov.c++ to iv2pov (a 
google of 'ivtopov' came up empty).
I notice they say "The mapping between Inventor's texture scheme (UV 
mapping) and POV 3.0's is (at best) an estimate - don't expect a perfect 
fit.". They also say " By the way - it does not convert any .rgb files used 
by textures into the .tga format POV wants - you have to do that by hand.".

If I had to guess, I'd say that the converters you are using are generating 
a texture file as a bitmap and that the texture specification in the output 
file isn't being set correctly.

If you can't spot the problems I would suggest cutting and pasting a few 
lines of the mesh definition and a couple of lines showing the texture 
definition into a posting here to see whether anyone can spot the problem.

Hope this helps.
Regards,
Chris B.


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.