[Radiance-general] Re: OCONV Error

[Greg Ward]

Hi Marcus,

As it turns out, the bug you discovered is related to the number of 
modifiers in your files rather than the number of polygons.  You have 
over 114,000 uniquely named colorpict primitives in your input files.  
If you had named them all the same, this error would not have occured.  
There was a place in my hash table function where I was overflowing a 
signed integer on the secondary hashing scheme.  This was quite easy to 
fix, and now oconv runs and produces a 63 Mbyte octree on your files 
with no trouble.  I have included the fix on the HEAD distribution if 
you wish to download it (src/common/modobject.c).

Thanks for discovering this bug!
-Greg

> From: "" <marcdevon@msn.com>
> Date: Mon Sep 29, 2003  1:22:51  PM US/Pacific
>
> Dear Greg
>
> Thank you for your help with this problem.
>
> I knew the error messages would not really help unless someone else 
> has encountered a similar problem in the past.
>
> I will send you these files. I have broken the scene file down into 3 
> indivdual files along with the material file (house6.mt). This is the 
> first of 3 emails due to the attachment limit set by my ISP. Together 
> they will be about 5.5 Megs compressed (65 Megs uncompressed). As I 
> said before, compiling them individually is no problem. The problem 
> comes when I try to merge them. The following should be noted.
>
> 1. These files were generated by a scene converter that I wrote to 
> translate POVRAY triangles and smoth_triangles into Radiance polygons. 
> Even though I wrote and compiled the scene for the Windows 
> environment, in the source code all end of line are terminated with a 
> "\n". I do not believe that this will pose a problem for Radiance 
> compiles because I did not explicetly add in any CR. Please let me 
> know if there are any problems with this.
>
> 2. The POVRAY files were generated by an architectural software that I 
> use called "Chief Architect". For some odd reason, they have many 0 
> area triangles in their POVRAY export. OCONV will let you know when 
> you encounter this. I'll add a feature to my converter that will 
> calculate the area of all of the triangles to determine which ones 
> should be written to the *.rad output file. However, I have been able 
> to compile and render previous scene despite this flaw.
>
>
> Please let me know if you can find out any information about this. 
> Once again, thank you for your help.
>
>
> Marcus D. Jacobs