 | | Hollow LDraw models
|
|
Many months ago I posted a question regarding making hollow shells or mesh objects out of LDraw models. In the POVray links section, under the macro subheading, is a listing for something called 'Tristan Macro for MegaPOV'. Anyone test this to see (...) (22 years ago, 28-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: Segmented parts (ie hoses and flex tubes)
|
|
(...) [snip] (...) I agree, I did that with the hoses on my loco (URL) and it seems the best solution. ROSCO (22 years ago, 27-Aug-02, to lugnet.cad.dat.parts, lugnet.cad.dev)
|
| |
| | Re: Segmented parts (ie hoses and flex tubes)
|
|
(...) No, moving the hose segments to parts/s/ would NOT prevent the shrinkage problem. It doesn't matter whether a part is located in PARTS or PARTS/S, it is still considered as a part. Whenever a (sub-)part is referenced from another part, it is (...) (22 years ago, 27-Aug-02, to lugnet.cad.dat.parts, lugnet.cad.dev)
|
| |
| | Re: Part 3650a
|
|
Is anyone opposed to my moving 3650a.dat to 3650.dat? If someone later makes a file for one of the other versions of this part, we can do another move at that time. Steve (...) (22 years ago, 27-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: Segmented parts (ie hoses and flex tubes)
|
|
(...) Actually, by the guidelines for parts I posted, the flex-axle subparts should be in the parts directory. Moving the hose segments to parts/s/ would prevent the shrinkage problem, but I think there are better solutions. Steve (22 years ago, 27-Aug-02, to lugnet.cad.dat.parts, lugnet.cad.dev)
|
| |
| | Re: Segmented parts (ie hoses and flex tubes)
|
|
(...) Oh, I meant the first one *I* mentioned, not the 751.dat :-) (...) Well, after second thoughts and various comments from you guys, I think we should keep segments in PARTS. (...) Yup, I agree, that is the solution. The curve generator should (...) (22 years ago, 26-Aug-02, to lugnet.cad.dat.parts, lugnet.cad.dev)
|
| |
| | Re: Ldglite bug report (Was: Portable Ldraw system)
|
|
(...) Good idea! My biggest problem, though, is in trying to figure out how to join many line segments into one long line; for example, in Jacob's rendering the wings look *too* broken up, where one jagged line would have served better. That, and (...) (22 years ago, 26-Aug-02, to lugnet.cad.dev)
|
| |
| | New Minifig
|
|
Since all the new Minifig parts (hand, left/right arms) are now available on the LDraw.org Parts Tracker, I though I'd make a minifig using them. The render can be found here: (URL) (22 years ago, 26-Aug-02, to lugnet.cad, lugnet.cad.dev, lugnet.cad.dat.models, lugnet.build.minifigs)
|
| |
| | Re: Ldglite bug report (Was: Portable Ldraw system)
|
|
(...) illustration, however, be careful not to over-use it! Perhaps it would be even better if you, at random, split some of the lines in two, and then jittered their end points as well. You could possibly even do this recursively, so that a line (...) (22 years ago, 26-Aug-02, to lugnet.cad.dev)
|
| |
| | Portable ldraw system
|
|
I just noticed that we need also a program like TD "a.k.a Track desingner" but for all these tools they must not use or need: No Visual Basic DLL "why because they don't work in all my 3 PC only in my good one" No run time stuff like I said above or (...) (22 years ago, 26-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: Segmented parts (ie hoses and flex tubes)
|
|
(...) Can the hose segments go in the S folder with the flex-axle subparts? Would that solve the shrinkage problem? Don (22 years ago, 26-Aug-02, to lugnet.cad.dat.parts, lugnet.cad.dev)
|
| |
| | Re: Part 3650a
|
|
Hmm, interesting. Thanks for digging into this, Clark. It's hard to judge from the Technica pictures, but I'm guessing that for LDraw, we probably won't want separate files for 3650 and 3650a (if we did want separate files, we'd call them 3650a and (...) (22 years ago, 26-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: Segmented parts (ie hoses and flex tubes)
|
|
(...) These files don't work as primitives. A primitive file should be either a geometric construction (like an arc, disc, cylinder, etc) or a lego-centric feature that is likely to be reused among a large number of different files (like studs, (...) (22 years ago, 26-Aug-02, to lugnet.cad.dat.parts, lugnet.cad.dev)
|
| |
| | Re: LDGLite sketch feature
|
|
(...) Beats me. I'd probably grep for the render_*() functions in the lex and yacc sources files. But then you'd need to grab some lex and yacc executables for the PC to build it. You can look in the lex/yacc output files lex.yy.c and y.tab.c but (...) (22 years ago, 26-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: LDGLite sketch feature
|
|
(...) Ahhh. And as I showed in my example, I didn't use "-l3". When I do, I get nice pictures like this one: (URL) of it. :-) Play well, Jacob -- Bregnerod (a LEGO town): (URL) (22 years ago, 26-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: LDGLite sketch feature
|
|
(...) Thanks, Don. :-, That's the trick, it seems. Using -l3 turns it on for me, -ld turns it off. Where do I make changes so that this will still work when using the ldlite parser? Cheers, - jsproat (22 years ago, 26-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: LDGLite sketch feature
|
|
(...) Don't be silly. You're probably just making some simple mistake that'll seem so obvious you'll wonder why you didn't think of it yourself. For example, L3View.cpp is only used by the l3 parser. If you don't use -l3 on the command line, you (...) (22 years ago, 26-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: LDGLite sketch feature
|
|
(...) Fixed that, cleaned out all the ".o" files, rebuilt and tried again. With the same result. :-( I hope this isn't because the Linux and Win32 versions of LDGLite actually use different source code. The make file doesn't look like it. Play well, (...) (22 years ago, 25-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: LDGLite sketch feature (Was: Ldglite bug report)
|
|
(...) Whoops! I forgot to change one item before I uploaded the cpp! Change the line (around line #67), const int jitter_num = 0; to use some positive number, e.g. const int jitter_num = 2; Cheers, - jsproat (22 years ago, 25-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: LDGLite sketch feature (Was: Ldglite bug report)
|
|
(...) substituted "L3View.cpp" with (URL), deactivated off-screen rendering in the make file, and compiled. But when I try to use it: jsproat.ldglite -mc fly.mpd I just get the usual image. Is your function hidden in some Win32 specific code? Should (...) (22 years ago, 25-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: LDGLite sketch feature (Was: Ldglite bug report)
|
|
(...) Let's re-write that, and break it up a bit: - modified function DrawPart() - color 24 is replaced with CurColor instead of edge_color(CurColor), just like color 16 - switch(LinePtr->LineType) cases 3 and 4 use a constant color 15 - (...) (22 years ago, 25-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: LDGLite sketch feature (Was: Ldglite bug report)
|
|
(...) I didn't add any flags, I still haven't taken the time to learn that part of the code yet. However, the only changes were to L3View.cpp, and are very straightforward. Note that this is just a proof-of-concept, and is far from being ready for (...) (22 years ago, 25-Aug-02, to lugnet.cad.dev)
|
| |
| | LDGLite sketch feature (Was: Ldglite bug report)
|
|
(...) > > (URL) wants that! Can you dump the source somewhere, so I can rebuild LDGLite with that feature? Which flags are needed to get that look? (...) :-) (...) Certainly. Play well, Jacob (22 years ago, 25-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: Ldglite bug report (Was: Portable Ldraw system)
|
|
(...) D'OH That last line should read: - copy libz.a to \mingw-1.1\lib\ Cheers, - jsproat (22 years ago, 25-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: Ldglite bug report (Was: Portable Ldraw system)
|
|
(...) Cool, thanks. I've never had much luck with windows and cvs and sourceforge, so your batch file should prove to be useful in snarfing the latest source. (...) Again, thanks. Does it include the latest changes you made for the line endcaps? (...) (22 years ago, 25-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: Ldglite bug report (Was: Portable Ldraw system)
|
|
(...) I've been pounding on ldglite and I think I've gotten the effect I was thinking of. I have a screenshot here (warning: 1024x768x32 PNG ahead): (URL) I made: - line types 3 and 4 render in white - color 24 renders same color as 16 (to make up (...) (22 years ago, 25-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: Ldglite bug report (Was: Portable Ldraw system)
|
|
(...) I guess that means nobody's ever bothered to build the windows version on their own before. Oh well, I sorta knew that. I recently attempted to update the visual C++ project files because they were also way out of date, but I didn't get the (...) (22 years ago, 25-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: Ldglite bug report (Was: Portable Ldraw system)
|
|
(...) Actually, the makefile was straight from ldglitesrc0_9_5.zip (...) I ended up having to rebuild libpng and libz because I was hitting against an "unresolved __imp__iob" linker error with the libpng supplied in ldglitesrc0_9_5.zip. Evidently, (...) (22 years ago, 25-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: Ldglite bug report (Was: Portable Ldraw system)
|
|
(...) Yeah, I knew about that. I've also heard some hardware opengl drivers have a max width of 1. I was kinda hoping nobody would notice. I mean 20 pixel wide lines? Who needs that much? Perhaps Sproat can enlighten us on what he plans to do with (...) (22 years ago, 25-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: Ldglite bug report (Was: Portable Ldraw system)
|
|
(...) I think it's missing a source file, glfont.c . Hmmm, how'd that get in the makefile? Did you grab the latest makefile out of CVS or something like that? Anyhow, you don't really need it and can remove it from the makefile. I think USE_GLFONT (...) (22 years ago, 25-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: Ldglite bug report (Was: Portable Ldraw system)
|
|
(...) So I decided to get off my duff and see if I could contribute more than just testing efforts, and installed MINGW32 v1.1 and the GLUT headers/libs, etc. and set about to build ldglite for myself. I think it's missing a source file, glfont.c . (...) (22 years ago, 25-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: Ldglite bug report (Was: Portable Ldraw system)
|
|
(...) It worked! You, sir, are a steely-eyed missile man. Be careful about posting fixes so quickly, you're already giving me more ideas for feature requests. :-, But thanks! Cheers, - jsproat (22 years ago, 24-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: Ldglite bug report (Was: Portable Ldraw system)
|
|
(...) You might find the following info from Microsoft's help page on glGet useful: GL_LINE_WIDTH_RANGE The params parameter returns two values: the smallest and largest supported widths for antialiased lines. See glLineWidth. That's the first I'd (...) (22 years ago, 24-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: Ldglite bug report (Was: Portable Ldraw system)
|
|
(...) I applied the fix Travis pointed out, and it seems to smooth out some of the bumpies in antialiased mode with wide lines on my PC. Give it a try: http:\\ldglite.sourc...e_test.zip I also noticed that the opengl drivers seem to top out their (...) (22 years ago, 24-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: Segmented parts (ie hoses and flex tubes)
|
|
(...) Doing so would cause a problem with LeoCad which doesn't display primitives not included in a part. This is the case with flexible axles (created form primitives), they have to be created as part, then imported as new part in LeoCad library... (...) (22 years ago, 24-Aug-02, to lugnet.cad.dat.parts, lugnet.cad.dev)
|
| |
| | Re: Segmented parts (ie hoses and flex tubes)
|
|
(...) Actually, the part mentioned was in the Parts directory (it is an official part), so it would presumably be shrunk by L3P. As for the rest, I agree that making them primitives makes sense, but I'm not sure the part authors will agree. I guess (...) (22 years ago, 24-Aug-02, to lugnet.cad.dat.parts, lugnet.cad.dev)
|
| |
| | Re: Segmented parts (ie hoses and flex tubes)
|
|
(...) I think it would be reasonable to consider segments as primitives. Move them to the P folder. Then they will not be shrunk. End pieces are still considered as parts. I don't know how the curve generator works, but if it generates a new (...) (22 years ago, 24-Aug-02, to lugnet.cad.dat.parts, lugnet.cad.dev)
|
| |
| | Re: Ldglite bug report (Was: Portable Ldraw system)
|
|
(...) I tried this on a quasi-high-end machine, same DAT and options, same results. Here's the l3glite output: ZClip = (-1000, 4000) GL_VERSION = 1.2.1 GL_EXTENSIONS = GL_ARB_multitexture GL_ARB_texture_compression GL_ARB_texture_cu be_map (...) (22 years ago, 24-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: Segmented parts (ie hoses and flex tubes)
|
|
(...) This sounds like a good idea to me, except for one thing: the 0 LDRAW_ORG lines are generated at release-time by the release script. Every type listed is determined by other data in the file, or about the file -- parts are in the /parts (...) (22 years ago, 23-Aug-02, to lugnet.cad.dat.parts, lugnet.cad.dev)
|
| |
| | Segmented parts (ie hoses and flex tubes)
|
|
Looking at some of the files generated using the new curve generator LDDesignPad plugin by Orion (as well as files generated by the EMacs macro it is based on), I noticed a problem when displaying with LDView (which might also effect L3P output). (...) (22 years ago, 23-Aug-02, to lugnet.cad.dat.parts, lugnet.cad.dev)
|
