| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
Stud groups
Forum: Official File Specifications/Standards
Last Post: Magnus Forsberg
44 minutes ago
» Replies: 1
» Views: 22
|
A fresh list of "most com...
Forum: Part Requests
Last Post: Peter Blomberg
5 hours ago
» Replies: 11
» Views: 1,846
|
Part Request - 51008pb01 ...
Forum: Part Requests
Last Post: Julian Raymond Ruan
9 hours ago
» Replies: 2
» Views: 2,268
|
New parts from Lego Instr...
Forum: Parts Authoring
Last Post: Timothy Hall
Yesterday, 2:41
» Replies: 85
» Views: 72,835
|
axleend2
Forum: Parts Tracker Discussion
Last Post: Gerald Lasser
2025-09-16, 20:03
» Replies: 3
» Views: 674
|
Parts request
Forum: Part Requests
Last Post: Peter Grass
2025-09-16, 5:58
» Replies: 2
» Views: 860
|
Transparent sticker colou...
Forum: General LDraw.org Discussion
Last Post: Travis Cobbs
2025-09-16, 1:42
» Replies: 10
» Views: 1,474
|
The Emperor Zurg
Forum: Part Requests
Last Post: Julian Raymond Ruan
2025-09-15, 13:07
» Replies: 0
» Views: 669
|
Batman Cowls
Forum: Part Requests
Last Post: Peter Grass
2025-09-15, 1:13
» Replies: 1
» Views: 804
|
Fix for slightly incorrec...
Forum: Part Requests
Last Post: Huib Versteeg
2025-09-14, 9:50
» Replies: 4
» Views: 1,508
|
|
|
| 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.
|
|
|
|
| LDRAW and LDD to SolidWorks, Inventor and DXF |
|
Posted by: BrickWorks - 2014-01-04, 20:43 - Forum: LDraw File Processing and Conversion
- Replies (36)
|
 |
Greetings,
I've just recently written 4 different translators for both LDRAW (.dat) and LDD (.g) files that can write to SolidWorks, Inventor, DXF and LDRAW. This was the result of some issues with the previous DAT2DXF translator I was running into with some bad .dat files and other requests that I have seen on these forums with regards to wanting SolidWorks and Inventor translation. I've attached a video showing how these small applications work.
Below are the links to setup files for each application. Unfortunately, I do not yet know how to create a trusted certificate for my ClickOnce Installer, so you may get a warning when downloading. The link will install the application to your Start Menu in SolidPerformance -> BrickWorks -> Application Name.
There are some requirements as of now, though because I am using ClickOnce, I could possibly rollout an update to support older version of the limitation listed below.
Does not support Windows XP and older.
Requires Microsoft .NET 4.5 (this causes the above limitation and is something I can most likely roll back to .NET 3.5 or 4)
The SolidWorks translator currently only supports SolidWorks 2014 and newer (though I could roll this back to around SolidWorks 2010 possibly, I should have the older SolidWorks.Interop files somewhere, which are forward, but not backwards compatible).
The Inventor translator currently only supports Autodesk Inventor 2014 also, for the same reasons. It will be much harder for me to get the older interop files for this.
For both the SolidWorks and Inventor translators, you can try to run them with older versions, but I have not checked all the api calls to see which versions of their respective software they were implemented. So if I used an API call that was implemented in say, 2013, it would require that as a minimum version.
Finally, here are the links
SolidWorks Brick Builder
Inventor Brick Builder
DXF Brick Builder
LDRAW Brick Builder
|
|
|
|
|
