| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 5,419
» Latest member: PatrTher
» Forum threads: 6,245
» Forum posts: 52,218
Full Statistics
|
| Online Users |
There are currently 255 online users.
» 0 Member(s) | 251 Guest(s)
Applebot, Baidu, Bing, Google
|
| Latest Threads |
The colour of textures in...
Forum: Parts Authoring
Last Post: Travis Cobbs
19 minutes ago
» Replies: 3
» Views: 88
|
Keywords and invalid 0 li...
Forum: Parts Tracker Discussion
Last Post: Orion Pobursky
2025-11-03, 22:17
» Replies: 6
» Views: 145
|
Minifigure Head MINI HEAD...
Forum: Part Requests
Last Post: Bailey Meyer
2025-11-03, 20:37
» Replies: 5
» Views: 368
|
Friends 2025
Forum: Official Models
Last Post: Philippe Hurbain
2025-11-02, 19:24
» Replies: 1
» Views: 289
|
Technic 1990
Forum: Official Models
Last Post: Takeshi Takahashi
2025-11-02, 15:05
» Replies: 14
» Views: 18,379
|
Sorting by date
Forum: Website Suggestions/Requests/Discussion
Last Post: Peter Blomberg
2025-11-01, 10:22
» Replies: 5
» Views: 480
|
Parts request , spider we...
Forum: Part Requests
Last Post: Peter Grass
2025-10-31, 11:23
» Replies: 1
» Views: 205
|
Part 4070 differences in ...
Forum: Parts Authoring
Last Post: Peter Grass
2025-10-31, 10:58
» Replies: 7
» Views: 624
|
Empty file with MLCad
Forum: Parts Authoring
Last Post: Orion Pobursky
2025-10-30, 0:20
» Replies: 2
» Views: 291
|
Duplo parts not yet in LD...
Forum: Part Requests
Last Post: Peter Grass
2025-10-29, 9:46
» Replies: 16
» Views: 2,308
|
|
|
| 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}
