Jump to content

roland

Eurobricks Citizen
 View Profile  See their activity

  • Posts

    372

  • Joined

  • Last visited

 Content Type 

Everything posted by roland

  1. roland
    You can click on the filename at the top right but I'm not very happy with that method myself. The main (intended) way of dealing with multiple (MPD) models is through the partbin overview groups. You can see me setting it up/using in the 1.5 docking demo clip and the mpd tutorial one. The top right method will change sooner or later, a tab approach has been suggested before but I have seen LDraw models which contain 300+ submodels which will result in way to many tabs :)
  2. roland
    Unless it overwrites .dat files with .pov content while keeping the .dat filename it should not matter. Logs through pm or email (see site) will be fine thanks. Just make sure the problem occurred in the last three program usages as only the last 3 log files are kept. MLCad does nothing with OpenGL so it's only limited by cpu/memory limits. LDCad tries to move the info to OpenGL which might fail in certain situations. One thing you could try is disabling 'VBO' in the prefs/opengl menu but it will slowdown rendering considerably.
  3. roland
    There seems to be a bug in 1.5 Alpha concerning working with multiple paths (e.g. pneumatic hoses). It will mess with the auto groups. This is probably why bublible is having troubles with them. So please keep using 1.4b if you want to do serious work involving bendable parts. It will be be fixed in the next (alpha) version. Some locations are protected by Windows (e..g program files) and weird things will happen when programs try to write directly to those places (after they've been installed). The archive version should be unpacked in some user's private folder e.g. 'my documents' which does not have those constrains. I think the 4600 should be enough to handle that base plate, If you can mail me the contents of the logs folder after you loaded the plate I might be able to see what's going on exactly.
  4. roland
    You might have somehow ungrouped the endings. They exist out of two parts (a cap and a point) which are grouped by default but when it is allowed to ungroup them. Try to regroup them by using the 'update auto groups' item from the selection/grouping menu. It's ether that or you discovered a bug in the 1.5 alpha version :) Have you unpacked the archive at a general writable location. e.g. it won't work correctly if you place it in the program files location, you need the use the installer for that. I did not make an installer for 1.5 as it is a test version. Like Philo wrote this is done using the ins key, but new in 1.5 is the ctrl+d key combo which pretty much does the same it only act different on single selections. The ins key will insert the working part when only one part is selected, ctrl+d will now always duplicate. I also look into the alt+lmb way but I'm kinda avoiding the use of the ALT key as it controls the windows/linux window menus by default which makes it act weirdly in some situations. When did it crash? Do you remember what you clicked/did. As It should never ever crash :) Is that 3947.dat, it might be a resources thing as it rather large (27000 poly's/40000 lines) what kind of VGA hardware are you on?
  5. roland
    You are right, might be a bit tricky to implement tough. I'll put it on my todo list. Do you mean while grid snapping is enabled (the default state) or after you set it to part snapping (PS in the compass). Also if you are using the part snapping mode please don't expect LDD level snapping. At the moment I only do basic snapping (no collision detection etc) as it will be more then enough 95% of the time while the feature needs less information and cpu power to do it. A future version will take 'occupied' studs etc into account but it will probably be optional in order to keep things usable with large models. Someone mentioned this on the LDraw forum too, I'm considering dropping left move/camera control in favor of a multiselect rectangle. When that happens a deselect will be done anyway. In the meantime you can deselect everything by using the esc key.
  6. roland
    Thanks, maybe if you decide to take up scripted anmation which I intend to extend feature wise in the 1.6 version :)
  7. roland
    I released the first Alpha version of LDCad 1.5 today. As many people here use LDraw for instruction booklet making I would be very interested in their thoughts about the new LDraw source editing window which can be used to reorganize steps and manage e.g. LPub meta's. You'll find the Alpha version at: http://www.melkert.net/LDCad/nextVer But please be aware this is an Alpha//test version so it might be less stable then the latest 1.4 version.
  8. roland
    The crash was probably while saving the file, resulting in a corrupted file. Don't know from memory if LDD has backup files, so you might want to do a search for *.~lxf and/or *.bak files on your hard drive.
  9. roland
    It isn't aligned in reallife too, the second hook beam attached to the headlights will be lower then the black beams along side it. If you zoom the picture on brickset (http://brickset.com/sets/42021-1/Snowmobile) you'll should be able to see it.
  10. roland
    It wont fit when you have two pins/axles in the left hook beam, but this model uses one pin which allows for additional movement. In such a case it will be possible to get it exactly right You could use my LDCad's selection info feature for it.
  11. roland
    Seems like LDD (as a program) hasn't got write access to files it creates. Which is weird but possible in *nix environments. I have zero experience with mac os but under linux I would be checking the rights of the user account LDD is running under. and or the right of the folder you creating the files in.
  12. roland
    Unless you are working on a large scene and POVRay runs out of memory and starts the swapping game :) I've seen it use 80+ GB on a 16GB system.
  13. roland
    Are you sure you are using the same exact settings? POVRay's parsing can be very (very very) memory intensive, did your old PC have more memory so it didn't need to do swapping? Did your old pc have a faster hdd (could make a huge difference if alot of mem swapping is going on)
  14. roland
    You could try a 'undelete' tool but it will probably only work if you haven't used (written to) the same harddisk after your work went missing and if LDD or SR3D saves files by first renaming the old one followed by writing a new one and deleting the old one afterwards. which I don't know they do.
  15. roland
    It seems to be using some sort of virtual file system, namely: https://www.eldos.com/cbfs/ That extra drive is basically only an alternative name for the folder on the real hdd. Bit over engineered for a simple converter if you ask me :)
  16. roland
    I don't think so, shadows need to be cast on something so without a floor you'll only get shadows on other parts etc. Do you mean the model it self appearing gradient or are you getting the wrong background color? If it's the model it self it's the result of your lighting settings, But I don't know what would cause a wrong background color though.
  17. roland
    I don't know about the export but... 92 degrees Celsius? If so that's way to high for any cpu, You really need to improve the cooling of your pc or it might shut down at an inconvenient moment. Are you sure all fans are in working order?
  18. roland
    Task manager, but I did not realize you are only working with 289 pieces during that test (as you mentioned 20000 before). So it's probably not the memory thing in this case.
  19. roland
    Did you keep an eye on LDD's memory consumption during this? As I still believe the main cause of these kinds of problems is the 32bit memory usage limit as I described above.
  20. roland
    With 2D do you mean an orthographic projection? Which basically means e.g. a front or top view without depth correction. If so you could use my LDCad which is part of the AIOI as of the 1402 version. It allows for ortho projection mode, you can then export the clean (gui free) picture into a png when ever you want. edit: sorry there seems to be a bug in the 1.4 version preventing ortho export,, it will be fixed in the next version though. LDView might also be an option but I'm not sure it supports ortho projection from memory. And if you want HQ (photo realistic) pictures export to pov-ray using LDView might also be an option as you can choose any projection kind with pov-ray. edit2: Workaround / alternative... You could also use the 'prtscr' key to capture your whole screen into paint or something in order to obtain the LDCad ortho picture.
  21. roland
    I think in this case the polygon count isn't the biggest problem it's the potential connection count. During the loading of a file LDD has to figure out what's connected to what etc, using all those 48x48 parts causes an explosion in the number of possible connections which LDD all has to test / discard (and thus eating memory in the progress). Polygon wise you need to make something very big (resulting in millions of triangles, >200 thousand parts) in order to get in trouble on modern GPU's. edit: wend a bit overboard ther :), it should be millions, not billions.
  22. roland
    In the top left you'll find a drop down box listing resolutions, set it to one of the lower(non aa) ones for test rendering the camera / position etc. You can also add new items to that list for custom render quality settings by editing the corresponding ini file.
  23. roland
    It crashed for me too (at ~75% of loading). It's probably due to it running against the 32 bit application memory ceiling as it was using just over 1GB memory, although that's below the 2GB 32 bit limit it is a 'danger' zone. Depending on how LDD manages it memory it will run into fragmentation problems when it tries to allocate more memory (which is often done by doubling the current amount etc). So unless LEGO comes with a 64 bit version of LDD I don't think you will be able to use this lxf file.
  24. roland
    When you start LDCad for the first time it will ask for the location of your main LDraw library. You can recognize the LDraw library folder by it's two subfolders named 'p' and 'parts'. If this somehow went wrong you can change it afterwards like legolijntje wrote but also keep an eye on the color config (adjustable in same menu). Or reset all settings by deleting the main.cfg file in "C:\Users\<username>\AppData\Roaming\LDCad\config" (assuming you used the setup on windows, just config in the smame folder as the exe otherwise) while the program is closed. It will then ask for the location again the next time you start it.
  25. roland
    Yes I would indeed need a list in order to match non symmetrical parts, a simple two column (using comma or tab) text file would be very helpful to kick start such a config file. If you could send me such a file (don't worry about the individual orientations file names is enough for now) it would certainly help things along.
×
×
  • Create New...