Search the Community

Showing results for tags 'ldr'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Frontpage, Forum Information and General LEGO Discussion
    • Frontpage News
    • Forum Information and Help
    • General LEGO Discussion
    • The Embassy
  • Themes
    • LEGO Licensed
    • LEGO Star Wars
    • LEGO Historic Themes
    • LEGO Action and Adventure Themes
    • LEGO Pirates
    • LEGO Sci-Fi
    • LEGO Town
    • LEGO Train Tech
    • LEGO Technic, Mindstorms & Model Team
    • LEGO Scale Modeling
    • LEGO Action Figures
    • Special LEGO Themes
  • Special Interests
    • Minifig Customisation Workshop
    • LEGO Digital Designer and other digital tools
    • Brick Flicks & Comics
    • LEGO Mafia and Role-Play Games
    • LEGO Media and Gaming
  • Eurobricks Community
    • Hello! My name is...
    • LEGO Events and User Groups
    • Buy, Sell, Trade and Finds
    • Community
    • Culture & Multimedia




Website URL








Special Tags 1

Special Tags 2

Special Tags 3

Special Tags 4

Special Tags 5

Special Tags 6

Country flag

Found 7 results

  1. Please read the guidelines! GUIDELINES Type the number, name and theme of the model (I prefer Brickset themes) at the top of your post. This topic only makes sense if you give a link to your model, so other people can download it Put a picture of the virtual model in your post. Say if there are errors, if there are, tell what the errors are. Not too big pictures, please follow the EuroBricks guidelines. One set in one file. So not one set in 2 files, or 2 sets in file. The set should be build using the original instructions. Exporting models from ldd is forbidden unless you have the permission from the original author. Pleas do check everything very, very carful (also the inside of the model), because the export is not very accurate. Models like Montly Mini Builds or Club models are allowed. software files/programs that are allowed MLcad SR3D Builder Leocad Bricksmith BrickDraw 3D LDCad
  2. I am converting a lego model to an .ldr file. However, the chain link models are not converted/present in the export! Is there a way to export the chain models too? Otherwise how can I get their models into my .ldr file? I've created an animation here:
  3. Greetings,LPub3D 2.0.14 is released. LPub3D is an Open Source WYSIWYG editing application for creating LEGO style digital building instructions. It uses the LDraw parts library, the most comprehensive library of digital Open Source LEGO parts available and reads the LDraw LDR and MPD model file formats. LPub3D is available for free under the GNU Public License v3 and works on the Windows Operating Systems. Portions of LPub3D are based on LPUBĀ© 2007-2009 Kevin Clague, LeoCADĀ© 2015 Leonardo Zide.and additional third party components. LPub3D can run under POSIX-compliant operating systems, such as Linux, Mac OSX, & BSD using WINE HQ. You can download from or check for updates in your existing installation. LPub3D Features and enhancements ------------ Fix: File reload after external source change breaks page drop-down combo dialogue(r837) * When a file is reloaded after being changed by an external source, the drop-down menu for selecting a page doesn't work until after navigating using another method. Fix: Image orientation does not conform when page orientation changed to Landscape (r836) * Image generation was not inheriting the proper page size values. Fix: Extra characters "%3" in margin meta and page size meta does not display the page size identifier(r835) * Oops, allocated the page size identifier variable to the wrong meta - should have been allocated to page size meta instead of units meta (units meta is used for setting the margin). Consequently, the page size meta is missing the size identifier (A4, Letter, etc...) because the place-holder to pass the variable is not there. This must have happened during the patch process from the maintenance branch because it did not present during my tests. Both issues are now corrected. Cheers,
  4. Greetings, LPub3D 2.0.13 is released. You can download from or check for updates in your existing installation. Interesting fixes are the ability to switch part occurrence (times used) in the PLI between per step and per submodel on called out and submodel pages; the ability to insert one-to-many non-faded models (e.g. with alternate attachments/views etc...) when fade step is on; and new meta for pages size including the standard identifier - e.g. A4, Letter, Legal etc... and print/export performance improvements. LPub3D Features and enhancements ------------ Fix: Logging options added to Preferences (r832) * Select logged attributes and logging levels. Fix: Prompt search directory settings reset (r831) * Prompt to inform that the search directories have been reset after the search directory reset button is clicked. Restarting LPub3D is not required. Also changed menu items "Reset 3D Viewer Model Cache" to "Change Temp File Cache" and "Reset Image and Model Caches" to "Reset All Caches". Fix: Inconsistency between part counts in submodels and part counts in call-outs where multiple instances are involved (r829) * For submodels, the PLI part counts reflect only one instance of the submodel, even if multiple instances are used in the same step. The instance count is correct, and the BOM has the correct total number of parts. With this update, sub-model pages displaying instance count now have a context menu option to display parts per step/page or not (total parts consumed by the number of instances indicated. Previously, for callouts, you have the options (see context menu) to display parts list per callout (one instance) or not. When you select no parts list per callout, the PLI will show all the parts consumed by the total number of instances in the callout. If you choose parts list per callout, the PLI is moved to the callout and only the parts for a single occurrence of the callout is shown. The idea here is if you have 5 occurrences of the called out assembly, you'll need 5x the parts total, but only 1x parts are shown to indicate what you need to build an instance of the called out assembly. On sub-model pages displaying the instance count, there is only one behaviour for PLI counts (the most intuitive) which is to display the parts list per step. This is intuitive because the primary role of the PLI is to show what you'll need to build an occurrence of the step shown - it is not the intention to mimic the BoM. Nevertheless, I added a context menu item to not display parts list per step and instead display total parts consumed by the number of occurrences of the submodel in the parent submodel/step. Fix: Page size and orientation processing update (r826/833) * Further industrialization of the print/export module. This update streamlines the process and realizes some performance gains. There are some key changes. Notably, page orientation and page size are now mutually exclusive. This means when switching from Portrait to Landscape, accompanying the orientation meta with a transposed page size meta no longer required or managed. Here is an illustration: Previous behaviour when editing a page size change required the following meta commands: 0 STEP 0 LPUB PAGE ORIENTATION LOCAL LANDSCAPE 0 LPUB PAGE SIZE LOCAL 11.0000 8.5000 Note that the page width and height have been transposed. Going forward, transposition of the page width and height when switching from Portrait to Landscape is automatically managed by LPub3D. NOTE: This update is NOT backward compatable. An accompanying transposed page size meta to indicate the switch from portrait to landscape as shown above will be treated as a new page size meta for that page. Consequently, using this meta to 'switch' orientation will actually result in NOT switching the orientation as LPub3D will automatically switch again the switched page size meta. If the user is only interested in changing the orientation, the proper meta command going forward will be: 0 STEP 0 LPUB PAGE ORIENTATION LOCAL LANDSCAPE To help with accurately displaying the page size identifier in the setup and context menus, the standard page identifier is now appended to the page size meta command. For example: 0 LPUB PAGE SIZE 8.5000 14.0000 Legal 0 LPUB PAGE SIZE LOCAL 8.5000 11.0000 Letter 0 LPUB PAGE SIZE LOCAL 5.8000 8.3000 A5 0 LPUB PAGE SIZE LOCAL 5.8678 8.3456 Custom Along with the width and height values, if the page size is non-standard, the identifier "Custom" will be automatically used. Additionally if an identifier is not present, the identifier "Custom" will automatically used. The page identifier is displayed in the Page Setup dialogue and Size/Orientation change context menu dialogue. Also, the LPub3D print/export function no longer needs to parse the model file to capture, in advance, page sizes. This capture is performed during the existing page parse and load functions and is exposed to the print routines during printing/exporting. This change was necessary to better enable mixed-size page export/printing where it is necessary to 'look ahead' to get the next page's size and orientation parameters in order to configure the printer engine before processing the page. Fix: Expand INSERT MODEL meta command behaviour (r825) * When using part fading LPUb3D will now process multiple INSERT MODEL commands rendering the CSI content at each command. For example, if the instruction document includes different model attachments, the editor can now include a non-faded image of the entire model with each attachment. Here is an example of he proper command sequence when used in conjunction with BUFEXCHG: 0 BUFEXCHG B STORE 0 //... default model content... 0 STEP 0 BUFEXCHG B RETRIEVE 0 BUFEXCHG A STORE 1 0 445 -46 -10 1 0 0 0 1 0 0 0 1 attachment1.ldr 0 STEP 0 LPUB INSERT MODEL 0 LPUB INSERT PAGE 0 STEP 0 BUFEXCHG A RETRIEVE 1 0 0 0 0 1 0 0 0 1 0 0 0 1 attachment2.ldr 0 //STEP These last 3 lines are optional when editing the model file. 0 //LPUB INSERT MODEL If they don't exist and fade step is ON, they will be automatically created by LPub3D 0 //LPUB INSERT PAGE Fix: The PNG output of a model with various page orientations is not correct (r824) * Cleared page buffer before rendering each page. Also corrected a typo causing page range to sometimes not work for image exports. Cheers,
  5. Opening LDR files

    I found a really cool model i'd like to build, but when I clicked download, It sent me here- Does anyone know how to open it? Thanks!
  6. The Bricksperience

    I created a little game called "The Bricksperience". In this casual game you can build sets virtually from the point of view of a minifig, earn Bricksperience points and spend them on new features. It uses LDR files to arrange the bricks and calculate the steps. Later on the game will have a challenge and you build against the time to earn different amounts of money which you need to unlock the sets and advance in the LEGO timeline. Since it's a game, low poly models with simple textures are required to keep the performance steady. Therefore I have to recreate each brick individually. That means you can only use the bricks that are available in the game in custom models. To see which bricks are available there are two options in the options menu to export an LDD palette as well as an LDR file (more reliable) with all the parts. Currently there are only four sets from 1980 - 1982 and 60 parts but there will be way more. I spent the most of the time creating the foundation for this game and now it's time to fill it with content. DOWNLOAD Known issues: - The menus are ugly - Some menu buttons have no sound effects - Only windowed mode - Requires good hardware Please give it a try and let me know what you think! Thank you! DasMatze
  7. can someone clarify if brick #64230 aka "spiral tube w. tube stud" aka "hose flexible 8.5L without tabs" (in real LEGO sets it is numbered "73590c01a" is actualy realy interpreted as #64230 during export from LDD? What I mean is that when I try to export it from LDD to .ldr it simply isn't there at all although I did edit ldraw.xml in LDD directory to implement it...and yes, my added one line script is implemented ok cos if I change 64230 for anything else it works like a charm. Simply to me it looks like real internal interpretation of the brick inside LDD is different than it should be, it is "64230" - can anyone test it, please? cos I am like completely mad about it now...