I know this request isn't going to be on top of anyone's priority list, but in my quest to complete my set of Technic models I am now down to only a few.  8010 Darth Vader looks pretty bad with his missing parts.

• 41671 Bionicle Bohrok Windscreen 4 x 5 x 7 (at least this might be useful to some other people)
  
• 43363 Technic Darth Vader Helmet (only appears in this set)
  
• cape (virtually impossible to make)
  

LDView doesn't run in new Ubuntu 16.04, is there an alternative viewer or a tick for install LDView?

It looks like search engines are sending people to the old forum URLs.

Here is an example. This is now a 404 error:
http://forums.ldraw.org/read.php?20,16260,18104

It should redirect to here:
http://forums.ldraw.org/thread-16260-pos...l#pid18104

On apache servers this can be accomplished with mod_rewrite and an htaccess file. The rewrite syntax can capture the old numbers and "rewrite" the URL into the new format. Additionally, the rewrite can serve a 301 response, which tells search engines the resource is at the new location permanently.

Hello,
I can not find the LEGO Speed Champions rims and wheels. Are they not there?
I found the part numbers right below and right above but not the actual ones.

I would appreciate it if someone could answer because I made a car that uses them.

FINN

I'm not sure how long ago it was that I used the LDPattern Creator software to draw out the patterns for the Astro Torso from the Mars Mission theme. I managed to finish it, and somehow attach it to the default torso object. Somehow I got it to open in an .mpd file using Leocad, but now I cannot copy it into the file I need it in. When I try, it appears as the default stud-less rectangular prism. I'd like to be able to copy it into the file at least, and maybe even put it into my parts library, bu I am unskilled at these things.

Is there anyone who would be willing to look at the part to see what might be wrong with it?

I don't usually start like this on a forum I'm new to, but the whole stuff is totally frustrating, and I need to vent off some steam. Nonetheless, these are (imho) legal complains about something that should be an out-of-the-box success instead of a chain of failures and frustrations.

I'm really a beginner with all this digital building stuff, but I've learned that ldraw & co can be frustrating to no end.

I started with the all-in-one-installer to create building instructions. I got a lot of help and could get the basics up and running with MLCad (which I had used before to create the models) and LPub3D within a few days. But then it got frustrating. LPub3D produced really, really bad (I'm tempted to say shitty) output. Even when I set the DPI to 600 (and cleared the caches), the PDF was horribly blocky. I finally fixed that by upgrading the provided LPub3D to a more current version. Why does the current all-in-one-installer provide outdated, buggy software?

But even with the updated version, the rendering with LDGLite still just crashes when rendering the model, and I never got the PovRay rendering to work, even after hunting for obscure lg_colors and lg_materials files. The only change I got was that instead of staying open and presenting obscure error messages, it now opens and closes povray without producing anything. It still seems to produce an error of some sorts, but it immediately closes the window, so I cannot tell what the problem is, and the stdout_povray and stderr_povray files are empty.

Hunting for the LGEO library (e.g. to look for updates or to find thoses mysterious lg_colors and lg_materials) files only leads to dead ends - looks like el lutzo closed up shop with his website. Why are those mysterious files (and whatever else may be needed for rendering with PovRay) not part of the all-in-one-installer? I finally found those two files somewhere on sourceforge in another projects archive, but I have absolutely no idea if those are the right ones.

Those rendering problems lead to the idea to use L3P and the L3PAddon to attempt a rendering of the model with PovRay. Sorry, but that was a total failure. The program wants to know the location of some files (which cannot be found within the installation, ldraw files, or program installation directories) and a strange tool (ledit.exe, according to google this is a electric circuit/layout program!?!) that it cannot run at all without.

Maybe this all works for some people who have installed numerous updates over time, have some old files still hanging around from 20 versions ago that some current programs still need, but no installer provides, or have tweaked their system over time to cover some of the problems I found. But it just does not work on a freshly installed system.

Please, take a fresh machine, install the AIOI, and try those things yourself if you don't believe me.

At least, with the updated LPub3D i get a decent PDF with the LDView renderer.

But the program is still buggy on many aspects. E.g. all measurements are in inches, even if the default unit is cm. A A4 page is 29.7 by 21.0 cm, not 11.6929 by 8.2677 (without any unit given, but it looks like inches) in Configuration->Page Setup.

If there is anything I can do to help debugging this whole mess, ask me, and I'll try my best. If a developer needs my mpd files to fix his software, no problem, just ask, and you will be given. But working with a software suite where the left hand does not know what the right hand is doing is utterly frustrating.

Leg bedre,
Christian

My first file, i hope everything is right....

Attached Files

  6656 - Tow Truck.mpd (Size: 2.29 KB / Downloads: 22)

Hello all, I've been working on ROTSTEP support for LDCad 1.6 but I have some questions regarding the spec / general behavior of these meta's.

First what is the base orientation (the one for step 1) to be used while calculating the step's orientation using the REL option.

I've been using this:
   

Second is it correct to assume the "ROTSTEP 0 0 0 ABS" will turn out an upside down image (as LDraw is y negative orientated).

  abs.png (Size: 39.31 KB / Downloads: 165)


And then there is the REL option should it act like so when rotating an already rotated model using the x axis only.
   

Hope these issues are clear so experienced rotstep users can help me refine the feature.

Also if someone could donate an (semi) large model using lots of rotstep metas with an known expected output would be very useful.

[size=large]New LEGO 40165 Minifigure Wedding Favor Set and lego Eiffel tower 21019 is beautifully liteup by liteupblock.[/size]

[size=large][/size]
[size=large][/size]
[size=large][/size]

I released 0.8.11 this week... It contained a bug and no triangle selection was possible. I had to fix it with release 0.8.11b... Sorry :|


Hey!

oh well, finally there is a 3D CSG manipulation feature release with LDPartEditor 0.8.11b...
This one was difficult, but the results are worth it :)


As always, you can download LDPE from this page:
http://nilsschmidt1337.github.io/ldparteditor/

Changelog:
(6 new features and 1 bug fix)

With this release you will be able to...

• ...to manipulate the CSG bodies in the same way as the sub-parts (supports also colour changes, "Select All", "Select all with Same Colours" and "Select None", global and local transformation).
  
• ...to quickly convert selected triangles into quads.
  
• ...to create and use angle protractors for 3 points.
  
• ...to create and use distance meters between 2 points (distances depend on local or global manipulator settings).
  
• ...use a little unit converter on the 3D editor window (located at the snapping area).
  
• ...to benefit from better undo/redo performance.
  

1. If you copied a LPE vertex and then tried to move one of them, both copies were moved ("Move Adjacent Data" is OFF).
   

1. Download the zip-Archive
   
2. Extract the archive content to the location of your choice
   
3. On windows, double-click "run.bat" to start LDPE.
   
4. On linux/mac, you have to excecute the shell script "run.sh" to start LDPE.
   

1. On windows, double-click "update.bat" to search for updates.
   
2. On linux/mac, you have to excecute the shell script "update.sh".
   

• Java Runtime Environment (JRE) 1.8
  
• OpenGL 2.1 compatible Graphics Card
  
• Operating System (32/64bit): Windows [XP; Vista; 7 or newer], Mac OS X [>=10.6], Linux [e.g. Ubuntu Linux >=10.4]
  
• CPU: Multicore-Processor e.g. Intel Core 2 Duo or AMD Athlon II (>2.0Ghz)
  
• RAM: 4GB
  
• Video-Memory: 512 MB
  
• Free Disk Space: 100 MB
  

• Operating System (64bit): Windows 7, Mac OS X [>=10.6], Linux [e.g. Ubuntu Linux >=10.4]
  
• CPU: Multicore-Processor with 4 cores (or more)
  
• RAM: >4 GB
  
• Video-Memory: >=1 GB
  
• Free Disk Space: 512 MB