To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.cadOpen lugnet.cad in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 CAD / *38950 (-20)
  The Cub's head in Lego Digital Designer format 1.3
 
(URL) The Cub's head in Lego Digital Designer format 1.3> See the full rotation in the Gallery---> click (3 URLs) Minus a few parts that are not in the 1.3 Pallet, here is the Cub's head: (URL) I'm going to convert it in to LDD 1.4 and see what I (...) (19 years ago, 23-Nov-05, to lugnet.build.mecha, lugnet.cad, lugnet.inst, FTX)
 
  How's LEGO Factory working out?
 
I got trapped under something heavy and haven't followed things in the LEGO world for the last couple of months. Last I was in it, a few of us had just figured out how the LEGO Factory bags are organized, and how to get part sets into LDD that (...) (19 years ago, 22-Nov-05, to lugnet.cad, FTX)  
 
  Re: LDraw files for Large models/scenes?
 
(...) One possibility would be to make the 'background' town and render it with a spherical camera (angle 180,90 IIRC). This can be saved and then mapped onto the sky_sphere (or a smaller encompassing sphere) and used as the background for scenes. I (...) (19 years ago, 17-Nov-05, to lugnet.cad)
 
  Re: LDraw files for Large models/scenes?
 
(...) Aah! Mr. Goldman's stuff, yes. Well, I kinda figured out that needed something like that, but you've just hit the same wall that I did, when I'd finished those mocs: None of those architecture guys seem to be interested in modelling their (...) (19 years ago, 17-Nov-05, to lugnet.cad)
 
  Re: L3P-Bug using LGEO
 
--SNIP-- (...) IMO the best solution would be to have a magic number at the start of the parts. eg. 0 LDP or something. That way the 'partness' of each part would be quicly verified merely be reading the first five bytes of the file regardless of (...) (19 years ago, 16-Nov-05, to lugnet.cad.dev)
 
  Re: L3P-Bug using LGEO
 
(...) Surely the extension is entirely to identify the type of file, otherwise they would be irrelevant? While I understand that .dat is a widely used extension it would be foolish if any change was to .ldr (for parts), another extension would make (...) (19 years ago, 16-Nov-05, to lugnet.cad.dev)
 
  Re: L3P-Bug using LGEO
 
(...) I think Tim meant LDraw files distinctive from other programs' .DAT files. Also from (URL) is problematic because its an ambiguous file format, many different programs use it. To identify more with LDraw, we chose LDR." Anyway, as Travis (...) (19 years ago, 16-Nov-05, to lugnet.cad.dev)
 
  Re: Scorpion
 
(...) I just met with Chris Dee who is here in New Jersey on a biz trip. He just showed me his render of the Scorpion! I am so impressed! There is hardly another part as hard to make as the Scorpion. He did a fine job. Thank you so much. Lego Fans (...) (19 years ago, 16-Nov-05, to lugnet.cad.dev)
 
  Re: L3P-Bug using LGEO
 
(...) What can I say? Tim has always been focused sharply on models. Although he used "model" extensively throughout that post, any implication of having separate definitions of "part" vs "model" as file-types is inaccurate. (...) That was entirely (...) (19 years ago, 15-Nov-05, to lugnet.cad.dev)
 
  Re: L3P-Bug using LGEO
 
(...) this is what I did in the end. nontheless I consider this a bug worth reporting and subsequently sort out the ldr-dat mess we are currently in ;-) w. (19 years ago, 15-Nov-05, to lugnet.cad.dev)
 
  Re: L3P-Bug using LGEO
 
In lugnet.cad.dev, Steve Bliss wrote: [snip-snap] (...) hmm ... I always understod .ldr as scene file and .dat just for parts. at least this was what I thought reding from tim's post back in 2001: (URL) extension change is just that. Nothing changes (...) (19 years ago, 15-Nov-05, to lugnet.cad.dev)
 
  Re: L3P-Bug using LGEO
 
(...) Yes, I would be great. But while it doesn't distinguish, we have to deal with it. I think the naming convention we had had before the .ldr extension, with officicial models named m926.dat and so on, solves this problem. So I suggest you name (...) (19 years ago, 15-Nov-05, to lugnet.cad.dev)
 
  Re: L3P-Bug using LGEO
 
(...) Getting back to the problem at hand, yes I do think this is a bug in L3P, the line specifically says include 926.ldr. Maybe L3P should include the extension as part of the inc file name unless it is .DAT? Of course that will break if the parts (...) (19 years ago, 15-Nov-05, to lugnet.cad.dev)
 
  Re: L3P-Bug using LGEO
 
(...) I read Steve's email as saying that they shouldn't and that the extension doesn't matter but IMO it does. Rereading it, it sounds like the extension does matter but that it shouldn't be used to identify the type of file which I agree with. /me (...) (19 years ago, 14-Nov-05, to lugnet.cad.dev)
 
  Re: L3P-Bug using LGEO
 
(...) I don't think L3P pays any attention to parts.lst. To be honest, I don't think that it should. It's not an editor that's expected to give you a list of parts available for use. (And to be honest, I think that parts.lst is a generally bad idea, (...) (19 years ago, 14-Nov-05, to lugnet.cad.dev)
 
  Re: L3P-Bug using LGEO
 
(...) The point is that it is not MLCad which differentiates, it is mklist. Tim (19 years ago, 14-Nov-05, to lugnet.cad.dev)
 
  Re: L3P-Bug using LGEO
 
(...) But that DOES differentiate between .dat and .ldr by the very fact it has the extension in parts.lst. If it didn't, 3010.dat and 3010.ldr would be interchangeable everywhere. This means that 3010.dat is NOT the same as 3010.ldr but L3P appears (...) (19 years ago, 14-Nov-05, to lugnet.cad.dev)
 
  Re: L3P-Bug using LGEO
 
(...) No, it doesn't. (...) MLCad has no such restriction - that restriction is put in place by mklist. Go ahead - create parts/3010.LDR, edit parts.lst, add 3010.LDR and a description, it will magically appear in MLCad and be usable just as any (...) (19 years ago, 14-Nov-05, to lugnet.cad.dev)
 
  Re: L3P-Bug using LGEO
 
(...) Actually, there's really no easy way to do part detection, but filenames really aren't a good idea. I'm pretty sure Lars is fully aware of the part detection problem (since it also affects the seams option in L3P), and there have been (...) (19 years ago, 14-Nov-05, to lugnet.cad.dev, FTX)
 
  Re: Scorpion
 
Eric Sophie schrieb: (...) It is now on the parts tracker. mikeheide (19 years ago, 14-Nov-05, to lugnet.cad.dev)


Next Page:  5 more | 10 more | 20 more

Redisplay Messages:  All | Compact

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR