| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 5,318
» Latest member: Cristian
» Forum threads: 6,180
» Forum posts: 51,805
Full Statistics
|
| Online Users |
There are currently 244 online users.
» 1 Member(s) | 238 Guest(s)
Applebot, Bing, Google, Internet Archive, Yandex, Hageta
|
| Latest Threads |
New parts from Lego Instr...
Forum: Parts Authoring
Last Post: Timothy Hall
10 hours ago
» Replies: 85
» Views: 70,668
|
axleend2
Forum: Parts Tracker Discussion
Last Post: Gerald Lasser
Yesterday, 20:03
» Replies: 3
» Views: 373
|
A fresh list of "most com...
Forum: Part Requests
Last Post: tom alphin
Yesterday, 15:36
» Replies: 8
» Views: 1,352
|
Parts request
Forum: Part Requests
Last Post: Peter Grass
Yesterday, 5:58
» Replies: 2
» Views: 667
|
Transparent sticker colou...
Forum: General LDraw.org Discussion
Last Post: Travis Cobbs
Yesterday, 1:42
» Replies: 10
» Views: 1,163
|
The Emperor Zurg
Forum: Part Requests
Last Post: Julian Raymond Ruan
2025-09-15, 13:07
» Replies: 0
» Views: 500
|
Batman Cowls
Forum: Part Requests
Last Post: Peter Grass
2025-09-15, 1:13
» Replies: 1
» Views: 626
|
Fix for slightly incorrec...
Forum: Part Requests
Last Post: Huib Versteeg
2025-09-14, 9:50
» Replies: 4
» Views: 1,278
|
Lego Town Racer 1996 - 63...
Forum: Official Models
Last Post: Chris Böhnke
2025-09-13, 23:39
» Replies: 14
» Views: 2,795
|
Eyesight on Linux
Forum: Rendering Techniques
Last Post: Orion Pobursky
2025-09-13, 18:56
» Replies: 12
» Views: 9,437
|
|
|
| Tiles 1 X 8 from latest Architecture sets |
|
Posted by: Vincent Messenet - 2019-06-24, 7:53 - Forum: Part Requests
- Replies (69)
|
 |
Hi,
Could someone work on 1 x 8 tiles from latest Architecture sets?
"San Francisco":
https://www.bricklink.com/v2/catalog/cat...1#T=C&C=11
"Paris":
https://www.bricklink.com/v2/catalog/cat...1#T=C&C=11
[color=#333333][size=small][size=small][font=Tahoma, Verdana, Arial, sans-serif][color=#333333][size=small][size=small][size=small][font=Tahoma, Verdana, Arial, sans-serif]"[/size][/size][size=small][size=small]Trafalgar Square":[/size][/size][/font][/size][/size][/font][/size][/color][/color]
[color=#333333][color=#333333][size=small][size=small][size=small][font=Tahoma, Verdana, Arial, sans-serif][size=small][size=small][size=small][size=small][font=Tahoma, Verdana, Arial, sans-serif]https://www.bricklink.com/v2/catalog/cat...only%22:0}[/size][/size][/size][/font][/size][/size][/size][/font][/size][/color][/color]
[color=#333333][size=small][size=small][font=Tahoma, Verdana, Arial, sans-serif]"[/size][size=small]Las Vegas"[/size][/font][/size][/color][color=#333333][size=small][size=small][size=small][size=small][font=Tahoma, Verdana, Arial, sans-serif]:[/size][/size][/font][/size][/size][/color]
https://www.bricklink.com/v2/catalog/cat...1#T=C&C=11
"Shanghai":
https://www.bricklink.com/v2/catalog/cat...0#T=C&C=11
"Statue of Liberty":
https://www.bricklink.com/v2/catalog/catalogitem.page?id=166139#T=C&C=11
"Great Wall Of China":
https://www.bricklink.com/v2/catalog/cat...6#T=C&C=11
and also its variant with Asian characters:
https://www.bricklink.com/v2/catalog/catalogitem.page?id=166357#T=C&C=11
All are done now. Thanks to all authors!
Many thanks!
|
|
|
| LDView povray export |
|
Posted by: Michael Horvath - 2019-06-20, 6:47 - Forum: LDraw File Processing and Conversion
- Replies (18)
|
 |
Here are some things I suggest for LDView's povray export. They all make things easier when using an external file to set variables, which I do often. I.e. I will create a "wrapper" file that is used in common by several scenes.
1. Precede all variable declarations with #IFNDEF. For instance:
Change this
Code: #declare LDXQual = 3;
To this
Code: #ifndef (LDXQual) #declare LDXQual = 3; #end
2. Check the variable's value when disabling lights and camera. For instance:
Change this
Code: // Camera
#ifndef (LDXSkipCamera)
camera {
#declare LDXCamAspect = image_width/image_height;
location LDXCameraLoc
sky LDXCameraSky
right LDXCamAspect * < -1,0,0 >
look_at LDXCameraLookAt
angle 77.011589
}
#end
To this
Code: // Camera
#ifndef (LDXSkipCamera) #declare LDXSkipCamera = false; #end
#if (LDXSkipCamera = false)
camera {
#declare LDXCamAspect = image_width/image_height;
location LDXCameraLoc
sky LDXCameraSky
right LDXCamAspect * < -1,0,0 >
look_at LDXCameraLookAt
angle 77.011589
}
#end
3. Create a variable to enable/disable the background. For instance:
Code: #if (LDXShowBackground = true) background { color rgb <LDXBgR,LDXBgG,LDXBgB> } #end
4. Lastly, if you could do the camera calculations inside the POV file instead of "hardcoding" the values, that would be great. For instance, start with latitude, longitude and radius to generate the camera location; then translate the camera based on the center of the bounding box. (I'm not 100% sure exactly what LDView does to output the camera.)
Thank you!!
|
|
|
|
| 0 BFC NOCLIP |
|
Posted by: Steffen - 2019-06-19, 23:56 - Forum: Parts Authoring
- Replies (19)
|
 |
I just stumbled over files on the PT containing
0 BFC NOCLIP
...
0 BFC CLIP
sections, for example
https://www.ldraw.org/cgi-bin/ptdetail.c...02ap03.dat
I think we need to decide if those sections shall be
* kept or
* removed.
They usually enclose the patterned areas of a part.
I think the reason why they were added (probably long time ago) was
that somebody thought "hmm. these patterns could be visible from behind
when the part itself is being used in a transparent color".
However, that reasoning is based on a wrong assumption I think.
Maybe the tools of older times needed such statements, but today, these lines are not necessary.
Especially it makes no sense to just include the pattern by those lines.
If the argumentation towards having these lines would be correct, then the whole part
would need to be BFC NOCLIP.
But as said, the reasoning behind the addition of these lines is probably wrong I think:
As soon as a part is using transparent portions, these portions allow to see other surfaces "from behind".
It does not matter whether those other surfaces are colored (patterns) or color 16.
Therefore, 3D rendering software anyway must have an implementation for dealing with that problem.
Usually its solution will be to simply turn off BFC at all for parts that contain transparent portions.
That would be the only way to get a correct rendering for all such parts as a general solution.
Therefore it is not necessary that such parts individually and additionally enclose some of their implementation by
0 BFC NOCLIP.
Doing that is a kind of "poor man's solution" to the overall 3D rendering problem just described.
And most of the current files on the PT incompletely solve that problem,
because they do not include their color 16 surfaces in that section.
It follows:
these sections should be removed I think.
|
|
|
|
|
did not understand how I could attach attachments, has now worked
