| Welcome, Guest |
You have to register before you can post on our site.
|
| Online Users |
There are currently 297 online users.
» 0 Member(s) | 291 Guest(s)
Applebot, Baidu, Bing, Facebook, Google, Internet Archive
|
| Latest Threads |
30305c01 Rock Monster (Ro...
Forum: Part Requests
Last Post: Peter Grass
5 hours ago
» Replies: 16
» Views: 14,932
|
looking for the complete ...
Forum: Help
Last Post: Gerald Lasser
5 hours ago
» Replies: 5
» Views: 135
|
Looking for Experienced L...
Forum: Help
Last Post: nobusiness909
9 hours ago
» Replies: 15
» Views: 3,329
|
[LDPatternCreator] Releas...
Forum: Parts Author Tools
Last Post: Nils Schmidt
11 hours ago
» Replies: 0
» Views: 49
|
LEGO Parts Guide - Only 3...
Forum: Part Requests
Last Post: tom alphin
2026-02-06, 16:37
» Replies: 34
» Views: 3,764
|
Creator 2025
Forum: Official Models
Last Post: Philippe Hurbain
2026-02-06, 10:28
» Replies: 3
» Views: 196
|
Discussion - proposal to ...
Forum: Official File Specifications/Standards
Last Post: Hageta
2026-02-04, 16:28
» Replies: 25
» Views: 2,404
|
Help Wanted: Discord Admi...
Forum: Help Wanted
Last Post: Cam's Bricks
2026-02-04, 15:44
» Replies: 1
» Views: 268
|
A fresh list of "most com...
Forum: Part Requests
Last Post: Gerald Lasser
2026-02-03, 16:04
» Replies: 12
» Views: 7,183
|
77255 Lightning McQueen p...
Forum: Part Requests
Last Post: Peter Grass
2026-02-03, 0:53
» Replies: 3
» Views: 498
|
|
|
| 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.
|
|
|
|
| Access |
|
Posted by: Stefan Weinert - 2019-06-18, 19:12 - Forum: Help
- Replies (1)
|
 |
Hello guys,
I've been a member here for about two weeks now and still can't access my private messages. Can you help me?
Best regards
Stefan
|
|
|
|
|
did not understand how I could attach attachments, has now worked
![[Image: thumbsup.png]](https://forums.ldraw.org/images/icons/thumbsup.png){kind=icon}
