| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
LDraw.org 2026-02 Parts U...
Forum: LDraw.org Announcements
Last Post: Orion Pobursky
2 hours ago
» Replies: 0
» Views: 33
|
2026 - New Parts -> Raw M...
Forum: Part Requests
Last Post: Peter Grass
6 hours ago
» Replies: 20
» Views: 705
|
Smort bleek stuff
Forum: Parts Authoring
Last Post: Jeff Jones
10 hours ago
» Replies: 2
» Views: 111
|
mpd2glb - LDraw to GLTF c...
Forum: LDraw File Processing and Conversion
Last Post: Carlos Antelo
Yesterday, 18:03
» Replies: 4
» Views: 197
|
LEGO Icons 2025
Forum: Official Models
Last Post: Jur Huisman
2026-03-04, 20:30
» Replies: 8
» Views: 7,722
|
v 1.7 beta 2a snapping fe...
Forum: LDraw Editors and Viewers
Last Post: Nicolas19
2026-03-04, 17:00
» Replies: 3
» Views: 248
|
2026/2027 LDraw.org Steer...
Forum: LDraw.org Announcements
Last Post: N. W. Perry
2026-03-04, 15:56
» Replies: 4
» Views: 243
|
Minifigure (series 28) - ...
Forum: Part Requests
Last Post: Jose
2026-03-04, 15:53
» Replies: 3
» Views: 646
|
71613/30346c01 too high?!
Forum: Part Requests
Last Post: Jeff Jones
2026-03-04, 14:32
» Replies: 19
» Views: 12,731
|
98295c01pb02
Forum: Part Requests
Last Post: Peter Grass
2026-03-03, 12:11
» Replies: 4
» Views: 3,444
|
|
|
| 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).
|
|
|
|
| British vs. American English |
|
Posted by: Michael Heidemann - 2014-01-05, 18:12 - Forum: General LDraw.org Discussion
- Replies (5)
|
|
There is just an actual discussion on the part: http://www.ldraw.org/cgi-bin/ptdetail.cg...47326c.dat that I like to have here for future reference.
Some years ago we where talking about british vs. american english for part description.
If I remember correctly we decided to use the british english to honor James Jessiman as an Australian guy.
Therefore the meta command is f.e. !COLOUR and not !COLOR.
Now I am aware that the decription of the colours in the LDConfig.ldr is not made this way. There is often gray instead grey used.
If I am right and this is our current policy the LDConfig.ldr should immediately be updated.
Also in our document for part authoring this detail should be mentioned.
|
|
|
|
|
