SylvainLS

LDraw uses BrickLink colour names now (2016.01) (just replace spaces with underscore). The codes (numbers) are still different though. I don’t use BrickStock but I’d guess everything is in the database and ID-matching is outdated.

If no file imports at all, you have a corrupted ldraw.xml file. (By the way, your example file imports well here… but for a couple collisions.) Please check the file (ldraw.xml) content and integrity (md5sum).

Do you have an example file available?

Update 2017-12-07 Corrected: 2554 / 2554.dat Door 1 x 3 x 6 with 1/4 Circle Top Added: 20179 / 20398c01.dat Minifig Cup Take Out with Dome Lid 92713 / 92713.dat Belt for Conveyor Belt 92715 / 92715.dat Brick 4 x 16 with Holes for Conveyor Belt 92716 / 92716.dat Roll 4M for Conveyor Belt md5sum: 31d861b04941d373756426c98d9141f7

I don’t know how LDD2POVRay works but with regular POVRay, I delete the brick altogether and use a light_source instead with the brick in its “looks_like” parameter. Here’s an example with an LDView export where I replaced a 1x2 plate (3023) with a light source (an array light placed at mid-height). The last matrix and rotation are what places the light_source where the plate was, all the previous transformations are generic (the same for all 3023 plates). (Scale in cm.) light_source { <0, 0, 0>, srgb <173,237,237>/255 area_light 1.52*x, 0.72*z, 6, 3 adaptive 1 jitter looks_like { lg_3023_clear rotate <90, 0, 0> rotate <0, 90, 0> translate <0, -0.16, 0> material { texture { lg_glowing_light_blue } interior { lg_ior } } } fade_power 2 fade_distance 2 photons { reflection on refraction on } translate <0, 0.16, 0> matrix <1, 0, 0, 0, 0.707107, -0.707107, 0, 0.707107, 0.707107, -8.799998, -8.318311, -1.9\ 41052> rotate <-90, 0, 0> }

As I said, you need to use the developper mode (there’s a topic about that in the forum). You can then look at this thread to locate the red bricks. If you don’t want to use the developper mode (I wouldn’t know why but…), you can still open the file in an editor, the “materials” parameters code the color, yellow is 24, red 21. But if you have several parts of the same shape (designID), it becomes very complicated very quickly as you need to use the coordinates. I think there’s also a trace of the designID in the DCLTrace.txt log file but it’s not as useful as finding the parts in 3D. Oh, and you can also use a dichotomic method: move half the parts in the model, save (in another file of course), load, if there still are collisions the same number of collisions/removed parts, continue splitting your model, otherwise, the collisions were between the two halves.

It’s useable in developper mode with physical tests disabled, otherwise, you just see your model in yellow, without the colliding bricks.

Reminder: The program hasn’t changed (much) for a while but the decors (colors and patterns) and parts matches (a.k.a. ldraw.xml) are updated as soon as a new part is added in LDraw Unofficial

Update 2017-12-02 Corrected (revised LDraw file): 47846 / 47846.dat Cockpit 4 x 10 x 2 Curved Added: 10314 / 10314.dat Brick 1 x 4 x 1.333 with Curved Top without Understuds 18587 / 18587.dat Six Shooter Trigger 18588 / 18588.dat Six Shooter Housing 72475 / 72475.dat Windscreen 3 x 4 x 4 Inverted with Rounded Top Corners, Cutout Bottom Corners md5sum: 3af9191848c18307a14b57f02adf932a

First, are you sure the parts dubbed “invalid” are actually invalid? There may just be problems in the conversions (LDD to LDraw to BrickLink). Next, about looking for a brick in a model, here’s how I do it: place a new instance of that brick near the model use select by shape, by color, or by shape and color to select all the similiar bricks If I don’t see them immediately, or some are hidden in the model: hide these bricks (clicking the hide tool button will hide the currently selected bricks) go back to select mode select all (or, for big model, a part of) the visible bricks (that is, with an area select, not Ctrl-A) so all the bricks but the ones I’m looking for are selected unhide click the hide tool button (so all the bricks but the ones I’m looking for (selected in 3) are hidden) That allows me to know where they are in the model, so that I can focus on these areas. It’s a “hide and se(l)ek(t)” game

I never used the gallery but am I right that they are saying they’re going from an LXF+PNG gallery to a PNG-only gallery? Last nail in LDD’s coffin?

The opposite is true too: a lot of builds are easy IRL and very hard to impossible in LDD. Try, well, about any big Star Wars vessel (old or recent) actually (MF, Destroyers…), you’ll have a hard time finding the right angles for all those bits of hull to fit together.

Update 2017-11-25 Added: 23421 / 23421.dat Pole 32 with Shaft and Helical Groove 23422 / 23422.dat Handle for Pole 32 with Shaft and Helical Groove Rematched: 30152 / 30152p01.dat Minifig Tool Magnifying Glass with Transparent Lens md5sum: 8e73494eabf6a23d4bc669c754fef096

We do “without.” More seriously, we find the most similar pattern or use the unpatterned version. Well, in LDD, x164 / 30370 hasn’t got any print nor paintable area, so you’re stuck with the plain version (Some people add prints (to parts that already can be printed), but that’s a modification of LDD and we don’t talk about that here.)

Update 2017-11-18 Added: 18897 / 18897.dat Brick 6 x 6 Round with Holes 18909 / 18909.dat Panel Cone 3 x 6 x 6 Elliptic Parabolic Rematched: 2714 / 2714a.dat Bar 8L with Stop Ring and Pin - Rounded End md5sum: 0e0c72f38eba19c62594aa1b0dc0870f

No, you can’t. LDD only allows one-stud connections in technic holes. You can fill all the four hole-ends with 1x1 plates (or similar) but you can’t put a 1x2 plate (or similar), even attached by only one stud. (Strangely, you can’t even put a 1x1 brick while you can put a 1x1 brick round.) Using two technic holes is illegal because the connection is considered too strong for a 7-years old to undo. Technic holes are a bit narrower than an antistud, so one stud is the limit. And, yes, official models do use illegal techniques from time to time….

It’s not. Only the rendering engine (Sunflow) is. The GUI and LIF+LXF-reading parts are proprietary.

Well, Stud.io includes Official, Unofficial, and parts from digital-bricks.de, so it’s more complete than a default LDraw installation that only includes Official. (Lack of connectivity info on some parts is a problem but doesn’t preclude using them.) Now if it were less power-hungry…

No, hiding bricks won’t change the Building Guide at all. It was just to help you circumvent your installation problems if you were in a hurry. And yes, it’s a simple way to make instructions as a video or with screenshots (Ctrl-K in LDD / Tool box menu). (Starting from the end also serves well in LDraw-based CADs to organize the building steps. But that’s another story )

If it’s for a one-time build: in LDD, hide the parts that are easily accessible, as if you were carefuly breaking / de-building the model. Then use Ctrl-Z to rebuild the model step by step.

AFAICT, it’s legal. There’re similar decors on the Horizon Express 10233-1. The cheese slope just has too big a collision box in LDD. It happens.

4318 isn’t available in LDD.

Update 2017-11-03 Added: 11092 / 11092.dat Minifig Hand Gorilla Fist 11438 / 11438.dat Minifig Armor Shoulder Pads with Ridges 15086 / 15086.dat Minifig Armor Shoulder Pads with Neck Protection, 1 Stud on Front, 2 Studs on Back 24088 / 24088.dat Minifig Helmet with Wings and Eagle Head 24946 / 24946.dat Egg 1.2 x 1.2 x 1.333 with Hole on Top 98366 / 98366.dat Minifig Helmet Roman Soldier Rematched: 75347 / 75347.dat =Support 2 x 2 x 11 Solid Pillar md5sum: ce831081da12b5e56686878e44b8b0d0

You can edit bluerender.bat file and make it something like: @echo off set JAVA_HOME=Z:\blabla\JRE %JAVA_HOME%\bin\java -cp "bin/*" bluerender.BlueRender pause (You need to know what drive letter to use, so you need to edit it each time. I haven’t used Windows for decades, maybe there’s an automatic way to do that nowadays…) Now, if I were sysadmin for public computers, I wouldn’t allow that to work but YMMV

Java ((that is, JRE / Java Runtime Environment, a JVM / Java Virtual Machine) needs to be installed. Not an easy feat on a public computer