| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 4,959
» Latest member: Doe
» Forum threads: 5,961
» Forum posts: 50,534
Full Statistics
|
| Online Users |
There are currently 549 online users.
» 2 Member(s) | 542 Guest(s)
Baidu, Bing, DuckDuckGo, Google, Yandex, Jeff Jones, Max Martin Richter
|
| Latest Threads |
Part request 5649 Brick, ...
Forum: Part Requests
Last Post: Jeff Jones
11 hours ago
» Replies: 2
» Views: 83
|
LDCad 1.7 Beta 1 (win+lin...
Forum: LDraw Editors and Viewers
Last Post: Quandore
Yesterday, 18:31
» Replies: 124
» Views: 62,323
|
Events on my submits does...
Forum: Help
Last Post: Quandore
Yesterday, 17:16
» Replies: 7
» Views: 398
|
New function in the Parts...
Forum: Parts Tracker Discussion
Last Post: Quandore
Yesterday, 17:15
» Replies: 5
» Views: 262
|
Duplo 65110
Forum: Parts Authoring
Last Post: Philippe Hurbain
2025-04-24, 17:30
» Replies: 1
» Views: 114
|
Technic 2025
Forum: Official Models
Last Post: Paweł Turalski
2025-04-24, 16:27
» Replies: 1
» Views: 191
|
Request for parts 67244, ...
Forum: Part Requests
Last Post: Philippe Hurbain
2025-04-24, 11:43
» Replies: 7
» Views: 977
|
Parts we are Working on -...
Forum: Part Requests
Last Post: Willy Tschager
2025-04-24, 6:15
» Replies: 152
» Views: 109,241
|
Official Part Fixes
Forum: Parts Tracker Discussion
Last Post: Orion Pobursky
2025-04-22, 20:20
» Replies: 0
» Views: 123
|
New Meta command PREVIEW
Forum: Parts Tracker Discussion
Last Post: Roland Melkert
2025-04-22, 20:10
» Replies: 9
» Views: 1,154
|
|
|
| p/low fast draft parts |
|
Posted by: Ben Supnik - 2014-01-08, 21:59 - Forum: Parts Authoring
- Replies (18)
|
 |
Hi Y'all,
I was dusting off my notes on LOD when I noticed that octa-studs have already been moved to /8 in the official library, something that was discussed here.
http://forums.ldraw.org/showthread.php?t...45#pid9745
This gives us three levels of detail by searching /p/8 and /p/48 for primitives.
I would like to propose a fourth level of detail, designed to be the lowest quality rendering possible. Such rendering would have:
- No studs at all.
- No part interiors.
The LOD would be targeted for real-time viewing of stupidly-huge models, e.g. all of Datsville at once, etc. The goal is to preserve some vague shape and color of the model while bringing down vertex count as much as possible.
The goal would _not_ be to replace every single part with a simpler version, but rather to replace a subset of parts that are very commonly used (e.g. all of the standard dimension bricks, plates, etc.), possibly using a human-directed script.
In my past experimenting with this technique I found that a small number of 'draft' quality bricks could have a pretty huge impact on the weight of a model.
Anyway, if anyone thinks this is a terrible idea, or has strong feelings on how such a sub-set should be built, please let me know. I'd like to start putting a part set together.
Cheers
Ben
|
|
|
| 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).
|
|
|
|
|
