roland

Eurobricks Citizen
  • Content Count

    369
  • Joined

  • Last visited

1 Follower

About roland

Spam Prevention

  • What is favorite LEGO theme? (we need this info to prevent spam)
    technic

Contact Methods

  • Website URL
    http://www.melkert.net/LDCad

Profile Information

  • Gender
    Male

Extra

  • Country
    Netherlands
  • Special Tags 1
    https://www.eurobricks.com/forum/style_images/tags/ldraw_builder.gif

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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.