POV-Ray

The Persistence of Vision Raytracer (POV-Ray).

This is the legacy Bug Tracking System for the POV-Ray project. Bugs listed here are being migrated to our github issue tracker. Please refer to that for new reports or updates to existing ones on this system.

Tasklist

FS#210 - UV mapping broken for parametric

Attached to Project: POV-Ray
Opened by Christoph Lipka (clipka) - Saturday, 04 June 2011, 05:46 GMT
Last edited by Christoph Lipka (clipka) - Thursday, 21 June 2012, 22:56 GMT
Task Type Definite Bug
Category Backend → Geometric Primitives
Status Closed
Assigned To Christoph Lipka (clipka)
Operating System All
Severity Medium
Priority High
Reported Version 3.70 RC3
Due in Version 3.70 RC4
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

UV-mapped textures for parametrics are broken in POV-Ray 3.70 RC3, in cases where two (or more) parametrics overlap in a scene.

In the following scene, note how the texture per se is always taken properly from whichever parametric is in front, while the UV coordinates are erroneously taken always from the red parametric where both overlap, no matter whether it is in front or back.

camera {
  location  <0.0, 1.5, -3.0>
  direction 1.5*z
  right     x*image_width/image_height
  look_at   0
}

light_source { <-30, 30, -30> color rgb 1 }

#declare Param = parametric {
  function { u*v*sin (15*v) },
  function { v },
  function { u*v*cos (15*v) }
  0, 1
  contained_by { box { -1,1 } }
  accuracy 0.002
  precompute 15 x,y,z
  rotate 180*x
  translate  <0.3,0.5,0>
}

object {
  Param
  uv_mapping
  texture {
    pigment {
      gradient x frequency 3
      color_map {
        [0 color red .5 ]
        [1 color red 1 ]
      }
    }
  }
}

object {
  Param
  uv_mapping
  texture {
    pigment {
      gradient x frequency 7
      color_map {
        [0 color green .5 ]
        [1 color green 1 ]
      }
    }
  }
  rotate y*180
}

POV-Ray 3.62 renders the scene properly.

As this bug has been found during code inspection, the uderlying cause has already been identified; I’m currently working on a fix.

This task depends upon

Closed by  Christoph Lipka (clipka)
Thursday, 21 June 2012, 22:56 GMT
Reason for closing:  Fixed
Comment by Christoph Lipka (clipka) - Saturday, 04 June 2011, 08:47 GMT
  • Field changed: Status (Investigating → Requires testing)
  • Field changed: Due in Version (Undecided → 3.70 RC4)
  • Field changed: Percent Complete (0% → 100%)

fixed with change #5450

Loading...