Hi guys

My work on the Nexo Knight Power shields is progressing slowly.
Found the first shield that was not listed on https://www.spyrius.org/nexo/. It is the shield #133 "Alpha Drill".
Does anyone have the shield or a picture of the shield on which the code can be seen?
Thanks in advance.

Regards Johann

Attached Files

  133_AlphaDrillIcon.png (Size: 5.27 KB / Downloads: 18)

Guys,

I'm looking for some pictures of:


https://www.bricklink.com/v2/catalog/cat...ge?P=20193

as well as its measurements.

Furthermore I'd like to discuss the naming. I'm fine with "Foam" as we also have "Canvas" and strangely "Sail" in the category. I think we have to decide if we go with, either the name of a thing or its material for all non-ABS parts. I certainly do not like:

Curtain for Window  1 x  4 x  3 with Red/Green/Dark Flesh Plaid Pattern
http://www.ldraw.org/cgi-bin/ptdetail.cg.../97122.dat

which should read:

Canvas Curtain for Window  1 x  4 x  3 with Red/Green/Dark Flesh Plaid Pattern

w.

Hi Roland, and others,

I have LDCad 1.6b running and configured like it should, but no texture is rendered on textured parts.
I still have LDCad 1.6a running on the same machine that uses the same libraries and there all my custom texturemapped parts render just fine.

What could be wrong?
I obviously checked and made sure Texture mapping was enabled in 1.6b.

If anyone wanted to take a look at 11103 I wouldn't complain.  I am just looking to use it in a build.  Not a new piece, looks like it was just never made, no rush at all.

https://www.bricklink.com/v2/catalog/cat...=11103#T=C

Thank you.

Does any one know if it is possible when using the parts tracker lookup to include constraints so that the returned results exclude parts which contain the given word?

For example, I want to search for "slope brick" but I don't want the results to include "slope brick curved". Searching for "slope brick" also includes the curved slope bricks. I tried to exclude the "curved slopes" with a simple "-curved" value in the search. Sadly, this did not yield the desired result.

Regards,

David

Hello,

I'm wondering if someone has this part, it would be much appreciated, thanks!

Hey guys,
I was just browsing through parts during a build and noticed this:
0 Slope Brick Curved  2 x  2 x   2/3 with Fin and 2 Studs
0 Name: 47456.dat
0 Author: Paul Izquierdo Rojas [pir]
0 !LDRAW_ORG Part UPDATE 2009-02
0 !LICENSE Redistributable under CCAL version 2.0 : see CAreadme.txt

I'm pretty sure the Description of the part is in error.

I believe it should be 
0 Slope Brick Curved  2 x  3 x   2/3 with Fin and 2 Studs

(2 x 3... instead of 2 x 2...)

I noticed because it was clearly larger than a 2x2 at the base when perusing in MLCad/LDCad. 
Here it is on BL: https://www.bricklink.com/v2/catalog/cat...=47456#T=C

Sorry if this has already been pointed out, but I searched and didn't find any threads with the part # in them. I also verified that my version matches the one in the latest complete.zip.

Jeff

I haven't made any models in a while and I ran into an issue guiding the cable of an M-Motor. At first I thought I was out of practice, but then I noticed the cable on the sensor I used looked different: none of my motor parts have editing points in the cable.

I have recently updated to LDCad 1.6b, but I am not aware of having made any changes. 
How can I get the editing points back?

   
   

An updated version of the LDraw All-In-One-Installer, in short AIOI, has been released.

The AIOI supports Windows XP (Home and Pro), Windows Vista or higher (all versions). On 64-Bit Operating Systems it will install in the "Program files (x86)" folder. The Installer will NOT run on Windows 95, 98, ME, NT Ver 4, 2000, or XP below SP2.

It contains the following changes:

* Update to LeoCAD 18.02
* Update to LDCad 1.6b
* Update to MPDCenter 2.4.1.0

You can download the AIOI from:

Home > Help > Get Started > LDraw All-In-One-Installer

Many thanks to all the programmers who contributed to this release.

Willy Tschager
(LDraw Content Manager)

Hey guys,

Long time MLCad user (in fact, it's my old 3DStudio render of the 8816 kit that Michael used for the splash screen and I did the MLCad logos for him).
I just started playing with LDCad and had one question.
Being a part author from *way* back in the days when James was still with us  , I'm very much into keeping my .dat source ordered in a very specific way, with parts being added in a sequential order from bottom to top (Y) back to front (Z) and left to right (Z) so that each piece can be seen as it is added, regardless of the step separations. Just the way I like to work. This means I'm often dropping parts into the middle of the existing list as I copy/paste, decide to break things into smaller steps, etc.

With MLCad parts were always added (or duplicated) immediately following the current item you have selected in the .dat window (part, step, comment, whatever). So far it seems like adding (or duplicating an existing) part or step in LDCad always wants to place it at the end of the current model/submodel source. This is cumbersome for me as I then have to move the part up where I want it in the actual source if I happen to be making a mid-dat edit. It's just my preferred way of organizing elements within steps. 

I've looked at the docs, checked the shortcuts and all pref settings I can find but see nothing that allows me to specify that I want new pieces (whether they be dragged from the parts bin or duplicated from existing pieces with key shortcuts) to be placed immediately following my current location in the source. Can this be done?

I'm sure lots of people don't even edit with their source window open and never worry about it, but I keep it open and docked and want very tight control over the order of every element placed in it, so not having to manually move things around after adding them would be very helpful.

And thanks to lots of you here. After being all about MLCad for... wow, like almost 20 years now... I forced myself to check out LDCad after reading lots of praise for it. For now it's still a bit cumbersome in many ways (for me) over MLCad, but I can see the potential and hopefully it'll make future documentation/releases of our model line easier.

TIA
Jeff
BrickGun.com owner
LUGNET User #114