 | | Re: Ldglite bug report (Was: Portable Ldraw system)
|
|
(...) I did some work on the other solution, rendering in the background. There's a beta of this here: (URL) -n2 to render each part in the backbuffer, -n4 does the whole model. Also the backbuffer is retained for faster refreshes on window expose (...) (22 years ago, 22-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: Ldglite bug report (Was: Portable Ldraw system)
|
|
(...) Oops! A quick visit to the L3P site reveals that's the camera position in polar coords relative to the look-at point. I'm not sure how I missed that before. But I like it because it avoids the weird LDRAW coordinate system. So I'm gonna have (...) (22 years ago, 22-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: Ldglite bug report (Was: Portable Ldraw system)
|
|
(...) Yes! Awesome. Drawing time seems to be a little slower, I don't have any numbers for that though. But the refresh is ligntning fast. Hmm, the menu seems to be more responsive too. (...) You sure? Lemme go double-check the docs... Oh my. I seem (...) (22 years ago, 22-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: Ldglite bug report (Was: Portable Ldraw system)
|
|
(...) OK I added it. Ldglite now takes -cg<la>,<lo>,<r> like l3p, and I like it. I admit it's not exactly like l3p since I still leave the origin at ldraw world coords (0,0,0) whereas l3p moves them to the center of the bounding box of the model. (...) (22 years ago, 23-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: Ldglite bug report (Was: Portable Ldraw system)
|
|
(...) (URL)And always remember to use -J to get the most out of the camera settings. (...) (22 years ago, 23-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: Ldglite bug report (Was: Portable Ldraw system)
|
|
(...) I try to think of the -a as a rotation matrix for the model, whereas the -cc stuff is a manipulation of the view matrix. Unfortunately the LDRAW default -a matrix "squishes" the model as if it were a view matrix. I guess this is because the (...) (22 years ago, 23-Aug-02, to lugnet.cad.dev)
|
| |
| | Re: Ldglite bug report (Was: Portable Ldraw system)
|
|
(...) Take a look at this thread at OpenGL.org: (URL) short summary is that you apparently can't guarantee it will work on all cards, but if you set things up right, you can get it to work on most cards. In addition, it may be that cards that don't (...) (22 years ago, 23-Aug-02, to 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: 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: 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)
|
|
(...) 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)
|
|
(...) 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)
|
|
(...) 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)
|
|
(...) 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)
|
|
(...) 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)
|
|
(...) 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)
|
|
(...) 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)
|
|
(...) 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)
|
|
(...) 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)
|
| |
| | 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 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)
|
| |
| | 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)
|
|
(...) 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)
|
|
(...) 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
|
|
(...) 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
|
|
(...) 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
|
|
(...) 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
|
|
(...) 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
|
|
(...) 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 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)
|
| |
| | 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)
|
