Welcome, Guest |
You have to register before you can post on our site.
|
Online Users |
There are currently 241 online users. » 0 Member(s) | 235 Guest(s) Applebot, Baidu, Bing, Google, Internet Archive, Yandex
|
Latest Threads |
Parts request
Forum: Part Requests
Last Post: Peter Grass
7 hours ago
» Replies: 2
» Views: 398
|
New parts from Lego Instr...
Forum: Parts Authoring
Last Post: Timothy Hall
9 hours ago
» Replies: 82
» Views: 68,752
|
Transparent sticker colou...
Forum: General LDraw.org Discussion
Last Post: Travis Cobbs
11 hours ago
» Replies: 10
» Views: 678
|
The Emperor Zurg
Forum: Part Requests
Last Post: Julian Raymond Ruan
Yesterday, 13:07
» Replies: 0
» Views: 297
|
Batman Cowls
Forum: Part Requests
Last Post: Peter Grass
Yesterday, 1:13
» Replies: 1
» Views: 415
|
A fresh list of "most com...
Forum: Part Requests
Last Post: tom alphin
Yesterday, 0:11
» Replies: 7
» Views: 918
|
Fix for slightly incorrec...
Forum: Part Requests
Last Post: Huib Versteeg
2025-09-14, 9:50
» Replies: 4
» Views: 1,058
|
Lego Town Racer 1996 - 63...
Forum: Official Models
Last Post: Chris Böhnke
2025-09-13, 23:39
» Replies: 14
» Views: 2,444
|
Eyesight on Linux
Forum: Rendering Techniques
Last Post: Orion Pobursky
2025-09-13, 18:56
» Replies: 12
» Views: 9,066
|
Another common varient: 1...
Forum: Part Requests
Last Post: Rene Rechthaler
2025-09-12, 14:51
» Replies: 8
» Views: 5,824
|
|
|
LDraw All-In-One-Installer 2018-01 now available |
Posted by: Willy Tschager - 2018-02-22, 0:24 - Forum: LDraw.org Announcements
- No Replies
|
 |
An updated version of the LDraw All-In-One-Installer, in short AIOI, has been released.
The AIOI supports Windows XP (Home and Pro), Windows Vista or higher (all versions). On 64-Bit Operating Systems it will install in the "Program files (x86)" folder. The Installer will NOT run on Windows 95, 98, ME, NT Ver 4, 2000, or XP below SP2.
It contains the following changes:
* Update to Parts Library 2018-01
* Update to MLCad.ini 2018-01
* Update to LDView 4.3
* Update to LPub3D 2.0.20.0.645
* Update to LeoCAD 18.01-10289
* Update to Offline Parts Catalog 2018-01
* Update to LDCad 1.6a
* Update to LICreator 3.2.153
You can download the AIOI from:
Home > Help > Get Started > LDraw All-In-One-Installer
Many thanks to all the programmers who contributed to this release.
|
|
|
LDCad POVray export |
Posted by: Michael Horvath - 2018-02-17, 21:47 - Forum: LDraw File Processing and Conversion
- Replies (15)
|
 |
A couple of observations.
1. slope bricks are not bumpy/grainy like they should be
2. at the POV-Ray newsgroups we came up with some code to add blurred reflections to models:
Code: // this methoid is slower
#macro BlurredReflectionMicroNormals(InPigment, InFinish, InNormal, BlurAmount, BlurSamples)
// texture
// {
average
texture_map
{
#declare iCount = 0;
#declare S = seed(0);
#while (iCount < BlurSamples)
[
1 // The pigment of the object:
pigment { InPigment }
// The surface finish:
finish { InFinish }
// This is the actual trick:
normal
{
average
normal_map
{
[1 bumps BlurAmount translate <rand(S),rand(S),rand(S)>*100 scale 0.001]
[1 InNormal]
}
}
]
#declare iCount = iCount + 1;
#end
}
// }
#end
// this method is faster, but requires a focal blur and/or extra antialiasing to smooth out the pixelation
#macro BlurredReflectionSingleNormals(InPigment, InFinish, InNormal, BlurAmount)
// texture
// {
pigment { InPigment }
finish { InFinish }
normal { InNormal }
normal {bumps BlurAmount scale 0.001}
// }
#end
#if (Use_BlurRef = true)
#ifndef (Use_BlurAmt) #declare Use_BlurAmt = 0.05; #end // amount of surface reflection blurring
#macro ldrawBuildTex(basePigment, baseNormal, baseFinish, pngIdx)
#if (pngIdx<0)
BlurredReflectionSingleNormals(basePigment, baseFinish, baseNormal, Use_BlurAmt)
#else
texture
{
pigment
{
uv_mapping
image_map
{
png getPngName(pngIdx)
getPngMapType(pngIdx)
interpolate 2
}
getPngWarp(pngIdx)
}
}
texture
{
BlurredReflectionSingleNormals(basePigment, baseFinish, baseNormal, Use_BlurAmt)
}
#end
#end
#else
#macro ldrawBuildTex(basePigment, baseNormal, baseFinish, pngIdx)
#if (pngIdx<0)
pigment { basePigment }
normal { baseNormal }
finish { baseFinish }
#else
#local texPigment= pigment
{
uv_mapping
image_map
{
png getPngName(pngIdx)
getPngMapType(pngIdx)
interpolate 2
}
getPngWarp(pngIdx)
}
#local result = texture
{
pigment { basePigment }
normal { baseNormal }
finish { baseFinish }
}
texture
{
pigment { texPigment }
}
result
#end
#end
#end
Unfortunately, there's no way to differentiate between ABS (solid) and Polycarbonate (clear) plastics. Could you add another column to the `ldColor` array for the `BlurAmount` value, in addition to `ior`? It would be great.
See also:
https://www.eurobricks.com/forum/index.p...e-realism/
http://news.povray.org/povray.binaries.i...ay.org%3E/
Thanks!
|
|
|
Voltage in electric part descriptions |
Posted by: Roland Melkert - 2018-02-16, 20:05 - Forum: Parts Tracker Discussion
- Replies (2)
|
 |
Hello all,
Philo and I have been discussing filtering of the electronic parts into their systems/voltages so builders can easily find certain parts when working with e.g. the old 9v RCX stuff.
Problem is many parts don't even mention which voltage they use.
So my suggestion is to modify the description of electric parts missing this.
E.g. taking parts like "u9005c01.dat" which currently uses:
"Electric Switch: Remote Control for Train Crossing"
and change it to:
Electric Switch 12v: Remote Control for Train Crossing
making it clear it s part of the old 12v trainsystem.
Using the voltage as a system name is only needed when there is no 'real' name so the e.g. power function stuff can stay as it is (new 9v system).
Alternative would be to mention the voltage as a keyword but I don't think any part uses that at the moment so it would cause more changes if we want it uniform.
Also no review process would be needed for just a description change as far I understand the current procedures.
Thoughts?
|
|
|
|