I produced 2 patterned unofficial parts from 3857 "Baseplate 16 x 32 with Square Corners".
Stud orientation used are the same as the official files (parallele to the 16 studs edge).

Photo found on web for [color=#000000][color=#333333][color=#000000]patterned parts [/color][/color]show the same orientation.[/color]

   
Ok, it's not very clear but i don't find better.

   
But real not patterned parts I have, show an orientation of stud parallele to the 32 studs edge.
Do you think 2 versions [color=#000000][font=Arial]exist with 2 differents stud orientation, one for patterned, one for non patterned, or an old version with an orientation (1990's) and a new version with another orientation ?  [/font][/color]

HEY so I'm new to LDraw (and part authoring, of course), and I'm having a VERY tough time wrapping my head around texture mapping and subfiles. I'm an artist much more than a programmer, so everything's really confusing for me. It took me a couple days to even figure out how to recolor polygons.

My primary issue is that I've already made a PNG and an SVG version of a custom texture of a lego torso. Converting the PNG is simple, but it has this nasty white line around the outside that looks really bad, stemming from the anti-aliasing? It's passable on lighter colors, though. Using solid would fix the border issue, but if you zoom in it'd look pretty icky, I think, unless the image size was super high.

So I was wondering if any of you could explain to me how I could work around the issue of the ugly white borders, preferably without having to scrap the art I already made and start over from scratch.

I assumed using a vector was the right way to go, since vectors don't have anti-aliasing in the first place, but I quickly ran into the issue of how to actually apply it to the model. It's really easy to texture minifigs with the stud.io part editor, but for a reason that is unclear to me (I'm sure it's a real good one) the SVG wouldn't work. If there's another file type I could use, or something, that'd be amazing, but I'm really at a loss right now! Attached are the textures I made, if that would be of any help in figuring out the issue!!


As a side note: is it OK to post completely custom textures/models in the Ldraw unofficial parts list? (As in, parts that were designed by me, and not LEGO.)

Thank you so much for the help...!

Hej,
I got a request in the Ambassador Forum, if we can create the Minifig Tails: Link to Bricklink.
Of course this is a request of another ambassador and not from TLG. 

/Max

We have reached a new quality level of our parts library:
* EVERY official part is now BFC certified.
* there are NO unofficial parts on the PT which are not BFC certified

Here is the proof:
https://www.ldraw.org/cgi-bin/ptbfcstatus.cgi

This is another great milestone in the quality of our parts.

To keep this situation,
I would like to suggest to adjust the PT now to require that an uploaded file carries the statement
0 BFC CERTIFY
in its header, and to reject submittal otherwise.

Hi,

could someone please fix the legend at the bottom of the Parts Tracker Parts List?
https://www.ldraw.org/cgi-bin/ptlist.cgi

There, the letter "X" is explained, which nowadays was replaced by "N" (which I like a lot).

The 2019-03 LDraw Parts Update has been now been released. This adds 627 new files to the core library, including 474 new parts and 24 new primitives. Update versions of the colour definition files (LDConfig.ldr and LDCfgalt.ldr) are included in this release.

After discussion on this forum we have decided to stop releasing files representing LEGO part numbers for 'Physical_Colour' parts, as other automatically updated resources (such as BrickSet), provide a better source for this information. Included in this update are more re-issued versions of many of the 'Physical_Colour' parts as obsoleted files.

Thanks are due to all the part authors who created or corrected parts for this release. The small, but dedicated, band of reviewers also play an important role in keeping files moving through the Parts Tracker and deserve just as much credit. 

You can preview the new parts in 2019-03 here, and download the zip-file update or Windows install package here. Alternatively you can use the LDView menu option File | Check for Library Updates... to install the update.

There are still a significant number of 'problem' files which fail to meet our standards and have been left on the Parts Tracker, some for several years. As a reminder, if these have remained untouched by the original author for three months, they are considered 'fair game' for any author to correct. We would welcome any effort to reduce this backlog.

Due to other 'real-life' conflicts, the planned end-of-October update was not forthcoming, but I hope this third 2019 release is a welcome increase in throughput.

I made a pair of river-sailing vessels for my D&D realm (because hobbit architecture is very boat-like), using LDCad 1.6c on linux mint.
Both boats have a cooking stove submodel. The larger of the pair has a guest bed and a lounge area, and two masts.

Attached Files

  Hobbit Boats.ldr (Size: 53.51 KB / Downloads: 14)

This may be another one with incorrect dimensions, but I don't have the real part to confirm. Should the axle hole be a full stud long on the Technic steering wheel (2741.dat)? At the moment it's only 16L, so it doesn't fit snugly to an axle with a 20L space on it (as in set 8880, for example).

Just recently I've tried to install LeoCAD into windows 10, which I have now, BUT somehow It showed a black screen upon startup, so I've discontinued the use of such a program, & just recently installed Studio ver. 2.0, from Bricklink.com, now I'm thrilled to use the program, which does in fact runs in Windows 10 perfectly without any flaws.

From Richard

Hi Y'all,

I have been totally AWOL from the LDraw community and Bricksmith dev, but I wanted to poke my head in and let people know where I was at with Bricksmith.  Allen has not had time to work on the project in quite a while and gave me carte blanche to maintain it, but I too have been really strapped for time.

The problem we have with BrickSmith is that Apple's platform SDK is an evolving target, as are the dev tools, and at this point we've picked up some serious bugs and problems due to not keeping up.  Here's the ones I am aware of and their status:

- No 3-d drawing at all - this can be fixed by setting a clear color to an overlay view, as (I think Travis) observed.  This happens when compiling on new tools.

- Incorrect scrolling and zooming, and blocky, pixelated bricks when zooming.  This is due to some change in how the scroll and clip views interact - the UI framework is literally "zooming" the GL surface instead of telling us we should draw bigger, resulting in blocky pixels.  This happens when compiling on new tools.

- Very slow search times in the part browser. Something changed in the perf of the regex thingie Allen was using; I have a rewrite of this that fixes this.  This is OS specific, not tool-chain specific as far as I can tell.

- Code signing/notarization issues - past versions of Bricksmith were not signed and notarized to be compliant with the increased security checks in Catalina and late Mojave.  This is OS specific, although there are work-arounds you can do on your machine to turn off the security squawks.  On the very newest X-code, code signing seems to be entirely broken and I can't even get a clean build without command-line hacking; as best as I can tell the way lsynth is packed into the app package now violates some new code signing rule.

I have not seen Z-thrash artifacts in my own use of the code.

The thing that drove me to re-examine some of this (instead of procrastinating due to the hurricane of work from my day job) is that I am upgrading my laptop, and in doing so, I will be giving away my last machine that was capable of compiling a shippable Bricksmith (by compiling on the old tool chain).

So my goal over the next week is to do one of either:
- Getting the current code into good enough shape that a clean build off of source with the latest Apple tools with the latest Apple X-Code actually works or
- Cutting a binary from my old machine that (somehow) runs on Catalina, so people can at least use the app until we can get a current compile working.

Edit: it looks like document opening is broken on Catalina (but not Mojave) when a build from legacy dev-tools is used.  This is not a problem on builds from current tools, so I think I have to fix the clipping/zooming issues.  It also looks like a side-effect of the clip-zoom issues is that a bunch of things in the culling/LOD system are broken, resulting in lousy performance and sometimes entirely missing buildings - this wasn't obvious for small models but is for large ones.

If anyone else is/has played with the code and has ideas or fixes for some of the issues or experience with Mac sw development, please ping me - dealing with crazy AppKit regressions is definitely not my area of expertise.

I am sitting on one _feature_ that I'd love to ship when we can get the code cleaned up: Bricksmith is very grid-focused - you can really rapidly build something up if it's orthogonal (think 80s style lego town models).  But this strength has always been a weakness when you get off the grid.  For example, the dentist chair from Assembly Square is murder to model in Bricksmith because it can and should be posed at non-right angles.

In the latest code, there is a new mode where rotations and nudges for a part work _relative to its current orientation_.  This means you can rotate a part 45 degrees and then nudge it along its new axis.  If a plate is hanging off of a bar (by a clip) at an odd angle, building off that plate is still "in grid" and just works.

I've been testing the feature by modeling the Corner Garage - the entire front facade is at 45 degrees, with stuff hanging off of it - it's as easy to model as the rest of the building with the new change.  

cheers
Ben