Ulrich and me had a small exchange concerning the Sticker Sheets for the train sets as he saw that I uploaded a few ones again and he was also active in the past on those. To avoid double work, I would like to start this thread here to keep somehow track of what is in the works and what needs attention. I hope it is fine here in the Request section.

I focussed in the past only on stickers that appear on the rolling stock, but feel free to add also the stickers that adorn the surroundings...

A few requests:

• One Set per post
  To avoid clutter, each post below this one shall only concern one set.
  If a set has more than one sheet, please post them all into the same.
  
• Add a link from the Table of Content to the correct post
  To make the search easier, if you start a new post, create a link from the ToC this  this very post. If you do not have privileges to do so, drop me a PM.
  
• Post also the stickers arranged as they are on the sticker-sheet
  

I'd like suggestions on what should be in these 2 articles:
https://www.ldraw.org/authorfaq.html
https://www.ldraw.org/reviewfaq.html

Especially the Review FAQ.

Hi folks,

I just updated the MLCad.ini file accordingly to the latest LDraw.org parts update 2020-01. The .ini file defines (among other things) the parts available in MLCad's, LEOCad's and Bricksmith's minifigure generator.

Download the file from my website: http://www.holly-wood.it/mlcad/mlcad_ini-en.html

Bye, w.

Due to my comment reviewing part s/2880s09.dat on using a "48\1-8tang" primitive to smoothen the part when doing primitive substitution.

First of all why: Here's how the part looks when the Prim-Subst (PS) is turned on:
   

The top and bottom surfaces reach over the refined cyli/edges

To overcome this issue the 48\1-8tang could be used.

Now here's the issue, when using PS, LDView increases the number of sections in a circle from either 16 or 48 to 96, this works also with the tanges primitives. I have created already the 48\1-16tang and to make use of the PS in the 49949 part.

I noticed that LDView will smoothen the inner-segment, but keeps the outer one always at 16 division, even if the 48\tang primitive has the outer segment done with 48 divisions as well, so that is what we will get without PS (left) and with PS (right)
   

As this ends up now with a pretty wide segment, it cannot be used at the bottom of the part.
For the top part it is working, see this code: (becuase of the overlap, when PS is ON, you can see that it will fit nicely)

Hi

I want to make a modified Caribbean Clipper but I cannot find the sails
It should be those 3 sails:
Cloth Sail 27 x 17 Top with Blue Thick Stripes Pattern, Cloth Sail 30 x 15 Bottom with Blue Thick Stripes Pattern  and Cloth Sail Triangular 15 x 22 with Blue Thick Stripes Pattern

images are here:
http://peeron.com/inv/parts/x420px2
http://peeron.com/inv/parts/x419px2
http://peeron.com/inv/parts/x421px2

or here:

https://www.bricklink.com/catalogItemInv...ailbb72c01
 
The same sails are also used for the Barracuda.

It would be great if someone can create them (maybe like the other sails that are looking like the wind is blowing them) as blank white sails, where I can change the colour of the stripes

Hi all,

Is this part done?


Can the globe print be done trough texture mapping?
The part exists.

I am trying to make the image for mapping, but I am unsure how to map the image on the part.

Something like this (WIP)
   



[size=xx-small][font=Tahoma,Arial]* 
 2 
 61287pb002
Dark Tan Cylinder Hemisphere 2 x 2 with Cutout with Europe, Africa, Asia, Australia Reddish Brown Globe Pattern
Catalog: Parts: Cylinder, Decorated
1 


* 
 2 
 61287pb001
Dark Tan Cylinder Hemisphere 2 x 2 with Cutout with the Americas and South Pacific Reddish Brown Globe Pattern
Catalog: Parts: Cylinder, Decorated[/font][/size]

Please vote on the following two sets of changes. Note: a single vote for or against both sets of changes, since the two are related.

!TEXMAP spec (changes highlighted in red):

https://www.ldraw.org/draft-texmap.html


[color=#333333][size=small]Official Library spec:
Under [color=#0072bc]META Commands add:
!TEXMAP Meta

Sufficient !TEXMAP <geometry2> and/or <geometry3> lines (as outlined in the Texture Mapping (!TEXMAP) Language Extension) must be included such that the part renders correctly in non-!TEXMAP supporting programs. It is highly encouraged that the included geometry reflect the pattern created by the !TEXMAP, even if it is reduced in resolution or colors, but this is not required.[/color][/size][/color]

Since there seems to be no further discussion regarding this, I formally submit my changes to the !TEXMAP spec and the Official Library Spec:

!TEXMAP spec (changes highlighted in red):

https://www.ldraw.org/draft-texmap.html

Official Library spec:
Under META Commands add:
!TEXMAP Meta

Sufficient !TEXMAP <geometry2> and/or <geometry3> lines (as outlined in the Texture Mapping (!TEXMAP) Language Extension) must be included such that the part renders correctly in non-!TEXMAP supporting programs. It is highly encouraged that the included geometry reflect the pattern created by the !TEXMAP, even if it is reduced in resolution or colors, but this is not required.

I only use LDraw to build official models, not MOCs. But although I don't need to create instructions, I like the build process in my model to match the official ones as closely as possible. (That's for the same reason I like the model itself to closely match the real model; it's all just part of the fun.)

Back in my Bricksmith days, I often used rotation steps to match the view in the official instructions, but I'd never experimented with buffer exchange. Since LDCad supports both, I decided to add them to my latest model and see how it affects the workflow. Here are some of my observations—and please regard them as just that: some ideas or suggestions perhaps, but no criticism intended. :-)

ROTSTEP
LDCad's implementation is a lot more intuitive than Bricksmith's. It's easy to set up the rotation you want—I don't get too precise, so I just use relative steps, but I could always match the instruction views exactly with absolute steps. (Haven't figured out a need for additive steps yet.)

There are a few drawbacks:

• ROTSTEP necessitates using trackball camera control, which I really still can't get used to.
  
• With relative steps, it depends on what the default view is. For perspective views, the default can be either left-sided or right-sided. It could be handy if LDCad allowed setting a default view per file, and maybe also allow fine-tuning the rotation for default views.
  
• Because step commands go at the end of each step, if the final step in your model is a ROTSTEP then it adds an extra (empty) step to the model. This is only a problem for those of us who like things all nice and orderly. ;-)
  

• Buffer exchange is an either/or operation. When you retrieve a stored view, you lose whatever work you've just done; you can't, for example, add a stored view to your current one. MLCad's REMOVE GROUP meta is said to allow more flexibility in certain cases, but LDCad doesn't support it at the moment.
  
• If an assembly appears unrotated throughout a subfile, but rotated in the main model, you have to add a step to the end of the subfile to show the rotated assembly. Again, this is only a problem if your OCD kicks in, which for me is usually. :-)
  
• As with all BUFEXCHG applications, it's necessary to re-insert everything you've added between STORE and RETRIEVE. In my case this means creating a subfile for each standalone section in the main step sequence, together with the individual instances of all those parts in the steps themselves.
  

There are a lot of pages on the main site that still use the article/<number> paradigm. I plan on transitioning away from this (with appropriate redirects added to the .htaccess file) to more descriptive URLs. This will set the stage for us to have a documentation specific SY theme on the main site.