roland

Eurobricks Citizen
 View Profile  See their activity

  • Content Count

    369

  • Joined

  • Last visited

Everything posted by roland

  1. roland
    Unfortunately the Middle mouse button is currently hardcoded to open the property dialog for the selection. Moving the camera/lookat is done using shift+right mouse button. I have had this request before so I will look into making it an option for the next version.
  2. roland
    Hello all, I'm proud to present the first beta version of LDCad 1.7. It's been some time since the last update, so I hope it was worth the wait. Major new features: - Interactive animations - Full !DATA meta (embedded texture) support. - Collada export (partial, deprecated). - gtTF2 export - Lots of new scripting objects. There are also stacks of small changes / tweaks, some new examples and lots of bugfixes. See changeLog.txt for the full list of changes. You can get the latest version at: https://www.melkert.net/LDCad/download
  3. roland
    Not exactly, but you can get close using a macro. function runPasteReplace() ldc.action('editSes_selAll'):run() ldc.action('editSes_selDel'):run() ldc.action('editSes_editPaste'):run() end ldc.macro('Paste replace'):setEvent('run', 'runPasteReplace') This will replace the current model with whatever is on the clipboard. Tested in 1.7 alpha, but should also work in 1.6. Just put the above snipped in a new global lua file (ldcad restart needed), or append it to e.g the default misc.lua global script (will trigger reload) and assign a hotkey to it. Now if you start a new model you can use it multiple times given your excel sheet puts stuff on the clipboard.
  4. roland
    Far I know it used the LDConfig.ldr inside the chosen base library location (instellingen/algemeen/algemeen). But it might cache the list somewhere like it does with the parts.
  5. roland
    I think MLCad is using/loading the wrong LDConfig.ldr file. One without a definition for those 3xx colors. MLCad probably applies the old dithered color rules on colors >=256 and <512 (a blend of two <16 colors). For example color 353 is a blend of 6 ( (353-256) div 16 ) and 1 (353-256-6*16), so a mix of brown and blue -> dark blue.
  6. roland
    Select one plate and then using the select menu choose "Same part". Then in the bin double click the replacement part. or Select the old part in the bin and choose "Working part" from the select menu (while nothing is selected) followed by double click on the new part. In both cases use the "Nested editing mode" if you are working with a model containing submodels if you want the parts to be recursively replaced.
  7. roland
    You can assign a different key. Right mouse click anywhere on the top tool bar Choose "Hotkey config.." In the new dialog set the top left drop list to "Edit session" In the list of actions look for the one currently assigned to "ins" Change the key using the top drop list or by clicking the sample space (not sure if that works under wine). You could use 'I' but be sure to clear the existing binding to "Show/hide Info panel" (will be red).
  8. roland
    Thanks for the suggestions, unfortunately most of these will probably need to wait for a 2.0 version which is a long way out. Getting 'rid' of some of the part bin things can be done with the current version, just delete the corresponding .pbg files in the %appdata%/LDCad/partBin folder But be aware it will reset after an upgrade unless you create you own configuration along side the default one. ps: The "Sorted by function" division is my attempt at a more natural way of selecting parts, a bit like working with a physical storage system containing out of multiple cases/boxes etc.
  9. roland
    It is possible to move the selection to a submodel. But with that many parts selecting things might be a bit slow. To compensate for that you might be better of using a source window. And because LDraw is a text format you can also use e.g. notepad to cut and paste a large chunk of text to a second .ldr given it is a 'flat' model. There is currently no default bin group listing all unique parts in the current model. I might add it to 1.7 though as I actually thought it was already there :)
  10. roland
    Is it a yellow or red crosshair? If yellor it means a render preparation error, in which case I would be interested in the .dat file used. If red it means it couldn't find the referenced part. In that case make sure it is findable by placing it in the same folder as the model using it or in a parts folder of a known library location.
  11. roland
    The size of the model file doesn't really matter, it is the size of the resulting 3D data which will eat memory like it's limitless. There are some options regarding memory use in LDView's preferences though.
  12. roland
    LDView uses a lot of memory with larger models, maybe it runs out of memory. This will happen at 2 or 3GB if you're using the 32bit version no matter how much memory the pc itself has. So make sure you're using the 64bit version. LDCad uses less memory as it only reserves bits for the used unique bricks, while LDView flattens the whole model to a single mesh.
  13. roland
    Do you mean the part bin inventory group (icon with the Orange mpd text followed by the little house one with all red parts in its white bubble) doesn't contain all the model's parts? If so that's a bug, because unless you are using >2 billion parts in the 32 bit version there is no real maximum. Or is it the (csv) export of the bin content,,assuming you've using that (right click on the part bin) , itself somehow failing with this many parts? @Jaco If you're using a script that takes to long to do the job, you can change then maxExecTime option in main.cfg. Or set it to 0 for infinite (only allowed in the later 1.6 versions).
  14. roland
    Are you using an ascii (human readable) stl file? If so be sure it's encoded as utf8 and not using some windows codepage. The python error is about an invalid unicode character, which is what happens if you try to use a non utf8 file containing 'weird' (e.g ß etc) characters like it is utf8.
  15. roland
    Forgot to mention it here, but I released a 1.7 test version last week. So if you're comfortable with a possible unstable version feel free to test it. Be sure you don't copy it over an existing stable version, just unpack it somewhere writable and execute the executable directly. http://www.melkert.net/LDCad/nextVer Main new features are additional export options and support for embeded textures. All feedback/comments are welcome.
  16. roland
    LDCad internals uses double precision everywhere. But because the LDraw format is human friendly you will loose information due to rounding once you save and reload a model. In very complex models this might become very noticeable after an couple of save/load sequences. A possible solution might be to increase the number of digits LDCad uses during saving. For this edit the main.cfg file while LDCad is closed and change modelFileDecCnt=3 into eg modelFileDecCnt=6 Some additional options might be available in 1.7, but the increased number of digits should at least help right now given you set it before you start a complicated model.
  17. roland
    You can rotate the parts in the bin by holding down ctrl and moving the mouse around. This will be temporary and can differ per bin view. You can make it the default orientation from the bin's right click menu. New in the d version is the ability to set the default bin orientation of single parts, but you'll have to edit the library shadow for that. I added that for the 1x4 patterned panels which all look the same at the default angle.
  18. roland
    There is currently no way to do that using the gui, might add it to 1.7 though. But you can make it work by editing the favorites file. It's at %appdata%\LDCad\config\partBin.fav When you used the windows setup or an similar location besides the exe if you used the (Linux) archive version. Inside that file all your favorite's are listed by their ldraw filename, e.g. 3001.dat:16 Change the 16 into the color number you need (1 for blue, 19 for tan. It' might be more logical to just make a custom pbg (bin group file) with these kinds of parts as the favorites group/cfg was never really intended for this use, it just inherited this mechanism from the part bin handling code :)
  19. roland
    Weird one. It's not the actual searching that crashes the program. It's actually the shadow library content for the 31111 flamingo pattern duplo brick. Good news it only seems to affect the 32 bit version, it works fine in the 64bit one, You can fix it for 32but too by fixing the shadow content, for this you'll need to install the latest shadow as found here: http://www.melkert.net/action/download/shadow.sf While the program is closed copy the above file over the existing one in the seeds folder located in the same place as the ldcad32.exe you're using.
  20. roland
    This could be the groundwork for a new editor, I would prefer that instead of studio replacing LDD.
  21. roland
    It should, but it might get confused by the two 'nested' libraries, that's a known issue. It's designed to use parallel libraries, like e.g. My Documents LDraw Offical Parts P Custom Parts P Then in the Prefs/LDraw/Search paths dialog register My Documents/LDraw/Official My Documents/LDraw/Custom
  22. roland
    You can make any ldraw (sub)file a 'part' by adding (at least) 0 UNOFFICIAL PART 0 BFC CERTIFY CCW before the first '1 ....' line This can be done with the header editing dialog, but is usually easier with e.g. notepad. LDCad doesn't really care about the extension but some programs will only accept parts when called .dat You might need to close and reopen the model for LDCad to start treating it as a part though. If you want to use the new part from multiple models you can move it to an library folder (a parts an p folder, and put the new part in the parts one). When registered in LDCad the contents will be mixed with the other library parts, so be sure to add a decent description and or category. Or just add it to the existing official library's parts folder if you don't want a second library.
  23. roland
    You can save the assembly as a loose ldr or mpd and when needed in another model just drag and drop it from the file explorer into LDCad. It will then ask if you want to edit it or use it in the current model. Alternatively you could make it a template (whom show up in the part bin), by putting the .ldr in the %appdata%/ldcad/templates/shortcut folder. Just be sure the ldr has logical description and preferably an 0 !KEYWORDS shortcut line. The keyword is needed for it to show up in the 'Misc shortcuts' template part bin group. Or if you really adventures you could add a custom bin group specially for your own templates by editing a pbg file.
  24. roland
    The crash is caused by the extremely short 2L pneumatic hoses (pneumaticHose-2L_1.ldr) Those are basically just the caps, so you could just as well just place to 165.dat's in a sub-model to avoid the problem. That said it shouldn't crash so it will be fixed in 1.7 Thanks for reporting.
  25. roland
    I did make some minor flexible part related changes in 1.6d not sure how that would affect the statistics panel though. If you could send me the file by mail or pm it would help greatly. If copying is a issue, you could strip anything but the tubing, just be sure it still crashes before sending me the file. Ether way I won't share it and delete it when the issue is identified/fixed.