Mantis Bug Tracker
Main | My View | View Issues | Change Log | Roadmap
  

View Issue Details [ Jump to Notes ] [ Issue History ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0001227LuxRenderCorepublic2012-05-01 06:262012-09-11 06:10
ReporterSATtva 
Assigned ToLord Crc 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version1.0RC1 
Target Version1.0Fixed in Version1.0RC4 
Summary0001227: Fresnelname IOR loader falsely considers external NK file as a bundeled preset name
DescriptionLet's say we have a metal2 material with IOR property defined by external NK file. The file itself is defined as "fresnel" texture with "fresnelname" loader. However, despite the "filename" property Lux still thinks it's an internal metal preset and throws out an error:

WARNING : 41] Fresnel preset '/home/blender/nk/Ag.nk' not found, using aluminium instead

Here's a material definition (same as what's exported by LuxBlend):

===============================================
Texture "Material_nk" "fresnel" "fresnelname"
    "string filename" ["/home/blender/nk/Ag.nk"]
MakeNamedMaterial "metal2"
    "float uroughness" [0.075000002980232]
    "float vroughness" [0.075000002980232]
    "texture fresnel" ["Material_nk"]
    "string type" ["metal2"]
===============================================

Below is a similar definition with old "metal" material which is working fine:

===============================================
MakeNamedMaterial "metal"
    "float uroughness" [0.075000002980232]
    "float vroughness" [0.075000002980232]
    "string filename" ["/home/blender/nk/Ag.nk"]
    "string type" ["metal"]
===============================================
TagsNo tags attached.
Mercurial Changeset #668054088617
Requires Documentation UpdateNo
Requires Exporter Update
Attached Files

- Relationships

-  Notes
(0003385)
Lord Crc (administrator)
2012-05-01 06:56

 I've pushed a fix for this, which was a copy/paste error.

However we need to figure out a better way of handling the current construction of "fresnelname" as it will generate errors if the "filename" parameter is not a valid SOPRA file, since it blindly tries SOPRA, then LuxPop then Preset.

However for now it will work, it'll just generate some errors.
(0003386)
J the Ninja (developer)
2012-05-01 08:11

 Isn't that how it's supposed to work? I thought the idea was it will eventually fall back to the aluminum preset if no file can be read?
(0003387)
Lord Crc (administrator)
2012-05-01 08:14

 Yes, but currently it will generate error messages as it fails to load it as a file.
(0003388)
jensverwiebe (developer)
2012-05-08 10:26
edited on: 2012-05-08 10:27

 I also corrected the exported presets ( fresnel_name -> preset ) now.
We can close this i think.

Jens
(0003391)
SATtva (developer)
2012-05-08 11:37

 Yep, everything works as expected.

- Issue History
Date Modified Username Field Change
2012-05-01 06:26 SATtva New Issue
2012-05-01 06:56 Lord Crc Note Added: 0003385
2012-05-01 08:11 J the Ninja Note Added: 0003386
2012-05-01 08:14 Lord Crc Note Added: 0003387
2012-05-01 12:05 SATtva Assigned To => Lord Crc
2012-05-01 12:05 SATtva Status new => feedback
2012-05-08 10:26 jensverwiebe Note Added: 0003388
2012-05-08 10:27 jensverwiebe Note Edited: 0003388 View Revisions
2012-05-08 10:28 jensverwiebe Note Added: 0003389
2012-05-08 10:28 jensverwiebe Note Deleted: 0003389
2012-05-08 11:37 SATtva Mercurial Changeset # => 668054088617
2012-05-08 11:37 SATtva Note Added: 0003391
2012-05-08 11:37 SATtva Status feedback => assigned
2012-05-08 11:37 SATtva Status assigned => resolved
2012-05-08 11:37 SATtva Fixed in Version => 1.0
2012-05-08 11:37 SATtva Resolution open => fixed
2012-08-21 06:54 jeanphi Fixed in Version 1.0 => 1.0RC4
2012-09-11 06:10 jeanphi Status resolved => closed

Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker