Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums

(Advanced Search)

Forum Statistics
» Members: 5,161
» Latest member: Zachary Porter
» Forum threads: 6,081
» Forum posts: 51,258

Full Statistics

Online Users
There are currently 440 online users.
» 0 Member(s) | 435 Guest(s)
Applebot, Baidu, Bing, Google, Yandex

Latest Threads
80503pb01 lute instrument...
Forum: Part Requests
Last Post: N. W. Perry
2025-07-16, 14:24
» Replies: 9
» Views: 5,901
Parts we are Working on -...
Forum: Part Requests
Last Post: Jeff Jones
2025-07-16, 10:14
» Replies: 158
» Views: 151,001
Modulex parts
Forum: Parts Authoring
Last Post: Chris Böhnke
2025-07-15, 20:30
» Replies: 31
» Views: 4,487
Same set, different sheet...
Forum: Parts Tracker Discussion
Last Post: Magnus Forsberg
2025-07-15, 6:15
» Replies: 8
» Views: 391
71613/30346c01 too high?!
Forum: Part Requests
Last Post: Chris Böhnke
2025-07-14, 23:21
» Replies: 18
» Views: 4,823
5724pr0001 Bubble Canopy ...
Forum: Part Requests
Last Post: SNIPE
2025-07-12, 21:08
» Replies: 2
» Views: 377
Friends 2014
Forum: Official Models
Last Post: Takeshi Takahashi
2025-07-11, 16:20
» Replies: 18
» Views: 17,226
LDCAD about Add custom p...
Forum: LDraw Editors and Viewers
Last Post: Nate87
2025-07-11, 8:13
» Replies: 5
» Views: 3,289
Hi-res logo primitives
Forum: Official File Specifications/Standards
Last Post: Jens Brühl
2025-07-10, 20:40
» Replies: 16
» Views: 2,123
Part 5561, Door 1 x 4 x 1...
Forum: Part Requests
Last Post: Gerald Lasser
2025-07-10, 9:55
» Replies: 1
» Views: 490

 
  [split] Teemu's Part Checker
Posted by: Chris Dee - 2019-06-24, 8:18 - Forum: Parts Author Tools - Replies (21)

(2019-06-16, 9:06)Steffen Wrote: yes please.

we have brought the BFC-problematic files to nearly 0 now.

just a small handful of "weird relicts" are remaining:
https://www.ldraw.org/cgi-bin/ptbfcstatus.cgi

I suggest to delete all of them from the PT:
- one is a "minifig torso + head" physical shortcut assembly which - if we would add these combinations to the library - would make the library size explode due to the possible combination
- the others are mockups which have no visual resemblence with the parts they mimick and are waiting unfinished for years now on the PT.

All now deleted.

Print this item

  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!

Print this item

  LDCheck - part checking program (1.0)
Posted by: Santeri Piippo - 2019-06-24, 7:34 - Forum: Parts Author Tools - Replies (13)

I had some time to work on the checking tool and I put up a new version up at the usual location, roughly doubling the amount of detected issue types. I've attached here a table of the current implementation status of the tool:

.pdf   problems-2019-06-24.pdf (Size: 36.15 KB / Downloads: 13)
A couple of things that I'd like to discuss on our current hold reasons table:

  • "HELP entry length": didn't we decide that help entry length was not limited?
  • "Filename ending does not match declared LDRAW_ORG file type.": what does this mean? How do filename endings correlate with LDRAW_ORG file type? I guess subfiles have 's01' and so on but other than that I don't really get it.
  • "Filename ending does not match declared LDRAW_ORG part type qualifier." likewise...?
  • "Wrong BFC command found." What is a wrong BFC command?
  • "T-Junction detected." T-junction detection can be very difficult to implement and only a small minority of T-junctions are actual problems. Do we really want to automate this?

Print this item

  Lugnet Partsref
Posted by: Orion Pobursky - 2019-06-24, 2:54 - Forum: Website Suggestions/Requests/Discussion - Replies (4)

There a few links to Lugnet's Partsref scattered about the PT. What should we replace them with? Maybe we should roll our own solution?

Print this item

Information 30361-1: Fire ATV Parts Missing
Posted by: jmdsdavid - 2019-06-22, 9:05 - Forum: Part Requests - No Replies

Hello.

Requesting this parts:

  • 39802pb01 [color=#000000]Minifigure, Utensil Axe with Red Head and Silver Blade Pattern, Pick End and Long Handle[/color]
  • 970c00pb160 [color=#000000]Hips and Legs with Reflective Stripes Pattern[/color]
  • 973pb1302 Torso Fire Reflective Stripes with Utility Belt and Fire Badge on Back Pattern
  • 3626cpb1466 [color=#000000]Minifigure, Head Brown Eyebrows, Goatee and Moustache, White Pupils, Gray Soot Marks Pattern - Hollow Stud[/color]
Thanks

Print this item

  Spliting ndis prims
Posted by: Johann Eisner - 2019-06-21, 15:00 - Forum: Parts Authoring - Replies (2)

Small question by the side.
Is it allowed to split ndis-prims or must be a 4-4ndis around a 4-4ring as well?

see attached picture.



Attached Files
.png   ndis.PNG (Size: 30.99 KB / Downloads: 45)
Print this item

  PT Page Update Tracker
Posted by: Orion Pobursky - 2019-06-20, 16:20 - Forum: Website Suggestions/Requests/Discussion - Replies (9)

A list of all the web accessible PT pages and their update status:

Done:
https://www.ldraw.org/library/tracker
https://www.ldraw.org/cgi-bin/tracker/activity.cgi
https://www.ldraw.org/library/tracker/ref/policy/
https://www.ldraw.org/cgi-bin/ptdetail.cgi
https://www.ldraw.org/cgi-bin/pthist2.cgi?h=10&i=15
https://www.ldraw.org/cgi-bin/tracker/submit.cgi
https://www.ldraw.org/cgi-bin/tracker/review.cgi
https://www.ldraw.org/cgi-bin/tracker/myreviews.cgi
https://www.ldraw.org/cgi-bin/tracker/mysubmits.cgi
https://www.ldraw.org/library/tracker/tools/
https://www.ldraw.org/library/tracker/ref/
https://www.ldraw.org/library/tracker/tree/
https://www.ldraw.org/library/tracker/status/
https://www.ldraw.org/library/tracker/ref/catkeyfaq/
https://www.ldraw.org/cgi-bin/ptpatterns.cgi
https://www.ldraw.org/cgi-bin/ptscan.cgi
https://www.ldraw.org/cgi-bin/ptqueue.cgi

Errors on computer resolution:
None!

Errors on mobile resolution:
https://www.ldraw.org/cgi-bin/ptbfcstatus.cgi (can probably retire)
https://www.ldraw.org/library/primref/
https://www.ldraw.org/cgi-bin/tracker/adminedit.cgi (will not be fixed)
https://www.ldraw.org/cgi-bin/tracker/pt...editCA.cgi (will not be fixed)

Error free but old markup:
https://www.ldraw.org/cgi-bin/ptlist.cgi (table at bottom only)
https://www.ldraw.org/cgi-bin/ptfilecheck.cgi
https://www.ldraw.org/cgi-bin/ptdatdiff.cgi
https://www.ldraw.org/cgi-bin/tracker/ptsubmitalias.cgi
https://www.ldraw.org/cgi-bin/tracker/pt...colour.cgi
https://www.ldraw.org/library/tracker/ref/faq/
https://www.ldraw.org/library/tracker/ref/reviewfaq/
https://www.ldraw.org/library/tracker/ref/numberfaq/
https://www.ldraw.org/library/tracker/ref/filetypesfaq/
https://www.ldraw.org/library/tracker/ref/patterns/
https://www.ldraw.org/library/tracker/ref/reviewinfo/
https://www.ldraw.org/library/tracker/ref/l3pmsg/
https://www.ldraw.org/cgi-bin/tracker/ptuserlist.cgi

Print this item

  Need help with primitives
Posted by: Vincent Messenet - 2019-06-20, 8:27 - Forum: Parts Authoring - Replies (2)

Hi,

I'm working right now on a part, its image is available here: https://imgur.com/NzGgDBp

I try to use primitives as far as I can because there are many rounded parts.

So far I have been able to do the attached file but now I'm stuck because I cannot use a ndis primitive to continue further because the vertex will be in the black border. Could you please help me identifying which primitive I can use to complete that part or perhaps what change should be done to move forward?

Thanks for your help!


.dat   3070bpb118 WIP.dat (Size: 7.63 KB / Downloads: 4)

Print this item

  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!!

Print this item

  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.

Print this item