Philo

Eurobricks Counts
  • Content Count

    1012
  • Joined

  • Last visited

Everything posted by Philo

  1. A texmapped head is now available: http://www.ldraw.org/cgi-bin/ptdetail.cgi?f=parts/3626cp73.dat
  2. No, not yet but I'll look at it... And thanks for your kind words ?
  3. Not natively, but it might run under wine (see https://forums.ldraw.org/thread-21766.html ). Not beeing a Mac guy, I can't offer much more advice, but you could ask on LDraw forum, several people are mac users
  4. Yes, that's expected. Though the texmap extension was created a few years ago, it was only recently that the parts tracker was updated to allow texmap patterns. The next official release will include the first ones, and the folder will be created. If you download current unofficial parts archive from http://www.ldraw.org/library/tracker/ you will see it too. Both Bricksmith and LDView should support texmap, but do you have a recent enough version? Also - I don't know for Bricksmith -, but texmap must be enabled in LDView (edit -> preferences -> primitives tab -> Use texture maps). You could also try LDCad on Linux.
  5. Useful reminder. Almost "invisible" download button I desperately search each time I need something on github... Even more awesome indeed! Worked fine for me for the few files I converted. The only thing I noticed - but I think that the problem comes from ldraw.xml - is that the 28t differential (62821) is rotated 90°, making the middle bevel gear float in mid air.
  6. Hi @Kendo, I made a patterned torso using TEXMAP so that you have an example... Get it here: http://www.ldraw.org/cgi-bin/ptdetail.cgi?f=parts/973paz.dat. The texture images must be placed in a "textures" subfolder of your parts folder (where you place the torso itself). Making your own torsos shouldn't be very difficult using that template. You just need to put your images in the textures folder and modify the image name in the texmap lines. 0 !TEXMAP START PLANAR -18.5 .5 -10 18.5 .5 -10 -18.5 31.5 -10 973paza.png As for image themselves, they must be PNG images. No need to make them very big (I made them 200 pixels wide wich, considering the size of torso, gives about a 400dpi resolution). Ideally the background (parts of the image that match torso plastic color) should be made transparent to avoid color mismatch. Have fun! Edit: Also made legs: http://www.ldraw.org/cgi-bin/ptdetail.cgi?f=parts/3817bpaz.dat http://www.ldraw.org/cgi-bin/ptdetail.cgi?f=parts/3816bpaz.dat
  7. 42094 - Tracked Loader (Technic 2019) Download MPD (OMR compliant) Known errors: No stickers. Done with LDCad 1.6b Rendered with Studio 2.0
  8. Basically the process is to place the needed unofficial parts (and all their unofficial dependancies!) in Studio custom parts folder. - The detailed, "chirurgical" way. Lets say that I want to import the following LDraw file: If I open this file in Studio, I get all unknown parts: Open a file explorer (I'm talking of Windows, dunno details for OSx) and go to C:\Users\(your user name)\AppData\Local\Stud.io. Create there a CustomParts folder, and in this folder create a parts folder ...AppData\Local\Stud.io\CustomParts\parts). Go to LDraw parts tracker, get the LDraw files for these parts (973p9b.dat, 39613.dat and 35442.dat) and place them in this folder. Restart Studio, reload file. Getting better... The torso and heart are now there, but the plate gear looks weird... Indeed, this parts relies on many subparts (35442s01.dat, 35442s02.dat and 35442s03.dat) that are still unknown from Studio ! Create a "s" folder in parts folder (...AppData\Local\Stud.io\CustomParts\parts\s), get the subparts from parts tracker and place them in this newly created folder. Better? No... That's because the subpart also depends on other unofficial files, scaled primitives this time (3-16con5.dat and 1-16ring9.dat) These are to be placed in a "p" folder, subfolder of CustomParts (...AppData\Local\Stud.io\CustomParts\p). Once this is done, it works... A bit complicated... fortunately, there is... - the brute force method Instead of placing files one by one in their proper folder, download ALL latest LDraw unofficial parts (direct link: http://www.ldraw.org/library/unofficial/ldrawunf.zip). Open this zip and place its contents in ...AppData\Local\Stud.io\CustomParts and you are done! Well... almost. As Studio doesn't contain the latest official LDraw library, some of the unofficial parts may use recent official subparts or primitives unknown from Studio. So if you still see "?" boxes you need to use the "chirurgical" method above... As I said it's not for the fainthearted ;) And I have not addressed another big issue: some Studio part are NOT compatible with LDraw parts (different origin, orientation, etc...). Is there a detailed tutorial for using Cycles? While I like Studio renders, it can be pretty tricky, as detailed above...
  9. Nothing fancy... Photoreal "High", "Building" light type, from right front direction, stud logo on.
  10. 8640 - Polar Copter (Technic 1986) Download MPD (OMR compliant) Known errors: No stickers. Done with LDCad 1.6b Rendered with Studio 2.0
  11. Up to the arrival of Studio 2, I used POV as exported by LDCad. I have now switched to the photorealistic renderer of Studio. It can be a bit tricky to convince Studio to properly display new LDraw unofficial parts or flexible stuff, but it can be done and the result is very nice. See examples below...
  12. 42093 - Chevrolet Corvette ZR1 (Technic 2019) Download MPD (OMR compliant) Known errors: No stickers. Done with LDCad 1.6b Rendered with Studio 2.0
  13. 42096 - Porsche 911 RSR (Technic 2019) Download MPD (OMR compliant) Known errors: No stickers. Done with LDCad 1.6b Rendered with Studio 2.0
  14. Philo

    parts authoring

    @1963maniac Yeah, we desperately lack good documentation - and LDPE beeing more recent, it's even worse. Probably the best documentation available for LDPE is here . Unfortunately, it's written in French, but hopefully Google translate can help... This website (written by a LDraw parts author friend) contains a heap of useful information about part authoring. You can also find some bits of information on my own website and on LDraw wiki . You can also ask questions on LDraw forum!
  15. Philo

    parts authoring

    No, I'm not a real parts author
  16. Philo

    parts authoring

    First check where your library is located: in MLCad (assuming it is properly configured), Settings -> general -> change and see the folder containing the library. Copy and paste the field. Then File -> open -> paste the path in file name field, press open (to go in the folder), choose the file you want to edit, press open again. Note that it may not be a good idea to change a file in your library! make a copy first ;) Finally, if you get serious about LDraw part editing, use LDPartEditor, which is a MUCH better part editor than MLCad (even though I used MLCad during many years for that...)
  17. @SNIPE Favorite file is partBin.fav (a simple text file). On windows it's located in %appdata%\LDCad\config Yes, it would be convenient to have a way to manage such files (eg. for the sets parts bins) from within the program.
  18. Way yo go to get around this rendering bug! I agree that LDPC can be a nightmare for intricate patterns! In this case texture mapping is the only sensible way to do things. But you can change LDPC grid (change "Move Snap" to a lower value, eg. 10 instead of default 100). Can you share an image of one of your decals? To come back to texture mapping... definition is here: http://www.ldraw.org/documentation/ldraw-org-file-format-standards/language-extension-for-texture-mapping.html and you can see an example usage in my EV3 stickers: http://www.ldraw.org/cgi-bin/ptscan.cgi?q=sticker+mindstorms But as I said previously, AFAIK Studio doesn't support TEXMAP extension. If POV renderer is fine with you, texmap is correctly exported by LDView or LDCAD. Photorealistic renderer of Studio is said to be a customized version of Blender renderer, so this direction can be investigated. See https://forums.ldraw.org/thread-22780.html?highlight=blender for a LDraw to Blender conversion tool. Dunno if it supports TEXMAP, and here I'm clearly outside my comfort zone
  19. 10261 - Roller Coaster (Creator Expert) Download MPD Known errors: Missing stickers Done with LDCad 1.6b Rendered with Studio 2.0
  20. 31084 - Pirate Roller Coaster (Creator) Download MPD Known errors: None Done with LDCad 1.6b Rendered with Studio 2.0 Download MPD Known errors: None Done with LDCad 1.6b Rendered with Studio 2.0 Download MPD Known errors: None Done with LDCad 1.6b Rendered with Studio 2.0
  21. Definitely no, complete.zip does contain ALL LDraw official parts and subparts. As for unofficial parts, you can download them in one bunch from http://www.ldraw.org/library/tracker/
  22. Yes exatly. 20460s02.dat is the "boot" subpart, whose color is controlled by the second number. You can see more details on LDraw file format here: http://www.ldraw.org/article/218.html Yes! See here: http://www.ldraw.org/article/547.html. Note that there are several silver colors defined, most probably you can choose color code 80 ("painted" silver) or 135 (silver plastic, slightly translucent) Yes also, look for 3818p01 and 3819p01 (Minifig Arm Right with Short Sleeve and Yellow Arm Pattern). The subparts (3818p01s01.dat and 3818p01s02.dat) are official for a long time, so they are present in Studio library.
  23. @Kendo Have you downloaded and installed all 4 subparts? (s\20460s0x.dat, x[1..4]) The block with question mark means that the part or one of its subparts is missing, neither in regular library nor in custom parts. The subparts must be placed in CustomParts\Parts\s It can work... ...sort of :( As you can see, pre-colored boot is not correctly shaded. But this is clearly a bug in Studio, as this happens also with "normal" parts in Studio library. Here is an example with precolored arms torso (973c02) and the "released" version, with separated arms and hands
  24. These legs have been missing from LDraw library for a too long time... Some of them (red and blue) are now available on LDraw parts tracker: http://www.ldraw.org/cgi-bin/ptscan.cgi?q=boots Don't forget the subparts! Edit: please wait a bit, I managed to goof in design number, should be 20460/20461, not 24060/24061. Renumbering proceeding...