| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 5,848
» Latest member: Daniele B
» Forum threads: 6,485
» Forum posts: 53,697
Full Statistics
|
| Online Users |
There are currently 151 online users. » 0 Member(s) | 146 Guest(s) Applebot, Baidu, Bing, Google, Yandex
|
| Latest Threads |
2026 - New Parts -> Raw M...
Forum: Part Requests
Last Post: Timothy Hall
1 hour ago
» Replies: 24
» Views: 5,242
|
Bionicle Tahu Cosplayer f...
Forum: Part Requests
Last Post: Chris Böhnke
9 hours ago
» Replies: 20
» Views: 1,160
|
47430 messurements
Forum: Parts Authoring
Last Post: Jeff Jones
10 hours ago
» Replies: 0
» Views: 65
|
Updates available for MLC...
Forum: LDraw Editors and Viewers
Last Post: Manfred Schaefer
Yesterday, 13:27
» Replies: 2
» Views: 249
|
[LDPE] 1.8.97 Released (s...
Forum: Parts Author Tools
Last Post: Philippe Hurbain
Yesterday, 8:04
» Replies: 7
» Views: 2,311
|
[LDPE] 1.8.95 Released (p...
Forum: Parts Author Tools
Last Post: Philippe Hurbain
Yesterday, 7:56
» Replies: 7
» Views: 6,334
|
LDraw.org Official Parts ...
Forum: Parts Tracker Discussion
Last Post: Peter Blomberg
2026-05-09, 18:03
» Replies: 6
» Views: 886
|
"Fixing" Older Stickers (...
Forum: Parts Authoring
Last Post: Chris Böhnke
2026-05-09, 17:17
» Replies: 0
» Views: 105
|
Existing Part Edit Reques...
Forum: Parts Authoring
Last Post: Rene Rechthaler
2026-05-09, 16:00
» Replies: 165
» Views: 414,873
|
Request for new primitive...
Forum: Parts Authoring
Last Post: Magnus Forsberg
2026-05-09, 12:36
» Replies: 29
» Views: 4,661
|
|
|
| Bitmap quastion |
|
Posted by: Stan Isachenko - 2014-01-07, 20:44 - Forum: Parts Authoring
- Replies (8)
|
 |
I there any working way to atach bitmap to Ldraw parts? Specifically for minifigs. There are almost all bitmaps from Minifigs series in LDD. I extract them from it, but i am thinking about attaching them to ldraw parts.
|
|
|
| LDView POV output |
|
Posted by: Michael Horvath - 2014-01-05, 21:26 - Forum: LDraw File Processing and Conversion
- Replies (15)
|
 |
Some of my parts are written as having color "LDXColor60_slope", but this color is not defined anywhere in the POV file. What should I do in the meantime? Is there a workaround?
[edit]
This is the change to the POV code I did to fix it. Instead of this:
Code: #ifndef (LDXSkipChromeColorMacro)
#macro LDXChromeColor(r, g, b)
#if (version >= 3.1) material { #end
texture {
pigment { rgbf <r,g,b,0> }
#if (LDXQual > 1)
finish { ambient LDXAmb diffuse LDXDif }
finish { phong LDXPhong phong_size LDXPhongS reflection LDXChromeRefl brilliance LDXChromeBril metallic specular LDXChromeSpec roughness LDXChromeRough}
#end
}
#if (version >= 3.1) } #end
#end
#end
I did this:
Code: #ifndef (LDXSkipChromeColorMacro)
#macro LDXChromeColor(r, g, b)
#if (version >= 3.1) material { #end
texture {
pigment { rgbf <r,g,b,0> }
#if (LDXQual > 1)
finish { ambient LDXAmb diffuse LDXDif }
finish { phong LDXPhong phong_size LDXPhongS reflection LDXChromeRefl brilliance LDXChromeBril metallic specular LDXChromeSpec roughness LDXChromeRough}
#end
}
#if (version >= 3.1) } #end
#end
#macro LDXChromeColor_slope(r, g, b)
#if (version >= 3.1) material { #end
texture {
pigment { rgbf <r,g,b,0> }
#if (LDXQual > 1)
finish { ambient LDXAmb diffuse LDXDif }
finish { phong LDXPhong phong_size LDXPhongS reflection LDXChromeRefl brilliance LDXChromeBril metallic specular LDXChromeSpec roughness LDXChromeRough}
normal { bumps 0.3 scale 25*0.02 }
#end
}
#if (version >= 3.1) } #end
#end
#end
And then I did this:
Code: #ifndef (LDXColor60) // Chrome Antique Brass
#declare LDXColor60 = LDXChromeColor(0.392157,0.352941,0.298039)
#declare LDXColor60_slope = LDXChromeColor_slope(0.392157,0.352941,0.298039)
#end
|
|
|
| DATHeader 3.0.14.0 - just released |
|
Posted by: Michael Heidemann - 2014-01-05, 19:05 - Forum: Parts Author Tools
- Replies (12)
|
 |
Based on the items below I updated DATHeader today.
You can download as usual from DATHeader homepage.
Please leave your comments to this version as answer to this post - thanks.
I like to sum up here my and hopefully your ideas for improvements of DATHeader. Or, if you say your ideas are not good please also leave a comment. The result should be to improve DATHeader for better work.
1)
Based on the current origin of this part (http://www.ldraw.org/cgi-bin/ptdetail.cg...s/x582.dat) I think it might be worth to check for the origin to be inside the bounding box. If not give a warning. (Already coded in my develop version).
2)
Based on the current comment on this part (http://www.ldraw.org/cgi-bin/ptdetail.cg.../u9292.dat) I think it might be worth to check from the end of the file to the first occurence of a real line for only line breaks and delete those empty lines.
Edit:
DATHeader write only one CR_LF after the last line with content if it is saved. So it is only necessary to detect those unnecessary lines and present the result to the user.
Edit:
Check for those empty lines is now also implemented (Already coded in my develop version).
3)
Based on the current comments on this part (http://www.ldraw.org/cgi-bin/ptdetail.cg...47326c.dat) further documented in the thread http://forums.ldraw.org/showthread.php?t...0#pid11690 I think it might be worth to implement a basic language check for at least some common wrongly used words like "color vs. colour", "gray vs. grey". The words to check should be in a separate file, so we can easily extend the list of words. (Already coded in my develop version).
Edit:
I did not know that it is sooo different: http://www.statsci.org/smyth/ozus.html. There are still more pages about this issue so maybe we need a complete dictionary in australian english that I should use in DATHeader.
4)
While working on parts that should use pattern from another part it found it anoying to seach for the data of the pattern that should be integrated into the part. So I added a infobox where the dimensions of the bounding box and the center of the bounding box is noticed, so I only need to open this file in DATHeader and have the values that i need to calculate the position and the zoomlevel. (Already coded in my develop version).
|
|
|
|