 | | Re: L3P "Skip" part metacommand
|
|
(...) It's never too late - I only hope that I'll soon have some time for L3P again. The shortest and easiest to remember keywords I could think of is: 0 L3P CAMERA_CALC OFF ... 0 L3P CAMERA_CALC ON Note, however, that it will only work in the main (...) (19 years ago, 15-Jan-06, to lugnet.cad.dev)
|
| |
| | Re: L3P "Skip" part metacommand
|
|
(...) That's almost there but it still includes that part in the camera position calculations so doesn't really leave me better off. This would still require copying the camera data over. I'll have a look at doing two passes and copying it over (...) (19 years ago, 14-Jan-06, to lugnet.cad.dev)
|
| |
| | Re: L3P "Skip" part metacommand
|
|
(...) True, but IFNOTPOV produces "if(0)" statements that can very easily be replaced by "if(-1)" and all the commented out tracks will be uncommented again. I find that easier than copy and paste camera positions. /Tore (19 years ago, 14-Jan-06, to lugnet.cad.dev)
|
| |
| | Re: L3P "Skip" part metacommand
|
|
(...) Everything inside IFNOTPOV won't show up in the POV file at all, so that would still require two passes (one with IFNOTPOV to generate the camera, and one without to have the correct scene). --Travis (19 years ago, 14-Jan-06, to lugnet.cad.dev)
|
| |
| | Re: L3P "Skip" part metacommand
|
|
(...) It's not what you're asking for, but I have code in an (unreleased) version of LDView that will put a POV camera into the clipboard based on the current view in LDView. It then lets you compose your view in LDView and simply replace L3P's (...) (19 years ago, 14-Jan-06, to lugnet.cad.dev)
|
| |
| | Re: L3P "Skip" part metacommand
|
|
(...) Oh, I think I see now. What about using IFNOTPOV? (19 years ago, 14-Jan-06, to lugnet.cad.dev)
|
| |
| | Re: L3P "Skip" part metacommand
|
|
(...) Not quite. Currently, L3P uses the entire visible "model" to calculate the camera position (-cg? ) to fit it all in. I would like to keep this functionality, but be able to tell it to ignore certain parts, e.g. train tracks which will extend (...) (19 years ago, 14-Jan-06, to lugnet.cad.dev)
|
| |
| | Re: L3P "Skip" part metacommand [DAT]
|
|
(...) If I understand you correctly, I may already have found a solution to your problem with my two ldraw objects "camera.dat" and "look_at.dat". Following camera will be seen in any LDraw renderer, but invisible in POV: 0 ~Camera Position 0 Name: (...) (19 years ago, 14-Jan-06, to lugnet.cad.dev)
|
| |
| | L3P "Skip" part metacommand
|
|
Is it too late to see a command for the new L3P to ignore a part/line when calculating the camera position/angle, but still render it in the final scene? Most of my renders are quite plane, but I'd prefer to have the railway track going beyond the (...) (19 years ago, 13-Jan-06, to lugnet.cad.dev)
|
| |
| | Re: Massive LDraw file repository
|
|
(...) You can, of course, support both. The reason I say SMTP is less reliable on the client side is because you can't know if they even have an mail program, much less what it is or how it works. In an environment you're controlling (like work) (...) (19 years ago, 11-Jan-06, to lugnet.cad.dev)
|
| |
| | Re: Massive LDraw file repository
|
|
(...) I use HTTP POST to have my work computers talk to databases and it seems very unreliable because if there is a network problem, the request dies then and there. But if I use email, the server will keep retrying. But I agree, HTTP POST is easy (...) (19 years ago, 11-Jan-06, to lugnet.cad.dev)
|
| |
| | Re: Massive LDraw file repository
|
|
(...) I think HTTP is more reliable in unknown environments... From the server side, the HTTP method might be more complex, but keeping the complexity on the server side is better than making complex clients. (...) Right - the clients pushing data (...) (19 years ago, 10-Jan-06, to lugnet.cad.dev)
|
| |
| | Re: Massive LDraw file repository
|
|
(...) I find it easier to make a script dump an e-mail with some text in a mailbox than to hack a HTTP POST form. I might not care to implement such an announcement feature in my script, if it was too much work to do. Sending e-mail and posting to (...) (19 years ago, 10-Jan-06, to lugnet.cad.dev)
|
| |
| | Re: Massive LDraw file repository
|
|
(...) Using email for the transport here is just adding comlication - why not just have a web API that the remote repos use to notify of updates? Could be a fancy SOAP/REST interface, or a simple POST form. It's not hard to parse email, but it's (...) (19 years ago, 10-Jan-06, to lugnet.cad.dev)
|
| |
| | Re: Massive LDraw file repository
|
|
(...) I'm very lazy. ;) Any interest in a copy of the program that generates my overview file? (...) Definitely. Maybe we should take a few moments to think about how to announce the available LDraw files on a web site? Is the NNTP/SMTP header (...) (19 years ago, 10-Jan-06, to lugnet.cad.dev)
|
| |
| | Re: Massive LDraw file repository
|
|
And one more comment. It would be cool to have some automation for site owners as well. For example, Jacob wrote a script that auto-generates descriptions of the files on his site. All he does is move a file to his web folder, and a script runs (...) (19 years ago, 10-Jan-06, to lugnet.cad.dev)
|
| |
| | Re: Massive LDraw file repository
|
|
Ok, I'm going to try this again. :) I've learned a few things since my first post. I'm moving this to lugnet.cad.dev BTW. First of all, I know there is interest to in a Massive Ldraw file repository as I have gotten many private emails about the (...) (19 years ago, 10-Jan-06, to lugnet.cad.dev)
|
| |
| | Re: LDRAW Package format?
|
|
Sven Moritz Hein schrieb: (...) I just tried ldglite_1_0_7 and I think it can work for you. Just give it a try. MikeHeide (19 years ago, 9-Jan-06, to lugnet.cad, lugnet.cad.dev)
|
| |
| | Re: LDRAW Package format?
|
|
Steve Bliss schrieb: (...) It seems that you need a viewer for MPD files but also a collector for all file in the MPD. And I mean really all parts. Please try my MPDCenter at www.michael-heidemann.de. It will collect unofficial files according to a (...) (19 years ago, 9-Jan-06, to lugnet.cad, lugnet.cad.dev)
|
| |
| | Re: LDRAW Package format?
|
|
(...) LDLite will do work, but it does bark at you when there's no setting for the LDraw directory. Clicking Cancel gets you past that prompt, and then LDLite draws the file as best it can. (...) I think your idea for a packager is very good. I'd be (...) (19 years ago, 9-Jan-06, to lugnet.cad, lugnet.cad.dev)
|
| |
| | Re: LDRAW Package format?
|
|
(...) I sure wish I knew how to recreate this...... Kev (19 years ago, 9-Jan-06, to lugnet.cad, lugnet.cad.dev)
|
| |
| | Re: LDRAW Package format?
|
|
(...) Sven, What might be better than sending a viewer app each time awould be send a person an LDR/MPD file and a link to a server running a viewer, perhaps an pared-down version of the java app mentioned in this post: (URL) That would definitely (...) (19 years ago, 9-Jan-06, to lugnet.cad, lugnet.cad.dev)
|
| |
| | Re: LDRAW Package format?
|
|
(...) Ldglite wouldn't be a good choice (for a packaged solution) -- it needs glut32.dll along with the main ldglite.exe file. But it would be a good choice for a program someone could just grab, unzip, and run. If you pointed them at the download. (...) (19 years ago, 9-Jan-06, to lugnet.cad, lugnet.cad.dev)
|
| |
| | Re: LDRAW Package format?
|
|
(...) Ldglite is still fairly primitive. For Windows, it's basically just an executable and a dll. If you don't give it an ldraw path, it should just look in the directory containing the model, and in the model file itself (if it's an MPD). Is that (...) (19 years ago, 9-Jan-06, to lugnet.cad, lugnet.cad.dev)
|
| |
| | Re: LDRAW Package format?
|
|
(...) Exactly this is my problem. It is hard to explain all this to someone who has never heard of LDRAW. What I imagine is something like a (*.zip?)package containing the model file, the parts and the viewer. You just have to send this package per (...) (19 years ago, 9-Jan-06, to lugnet.cad, lugnet.cad.dev)
|
| |
| | Re: Proposed new meta-command: !STANDALONE_LDR
|
|
(...) This is a bit of a problem for me too. I've written scripts to import and export ldraw data from Blender, and naturally I built a model in Blender following that.. but now I'm not allowed to share the original Blender model without removing (...) (19 years ago, 9-Jan-06, to lugnet.cad.dev)
|
| |
| | Re: Proposed new meta-command: !STANDALONE_LDR
|
|
(...) They will. We haven't quite decided on what it will be but it will be there. -Orion (19 years ago, 9-Jan-06, to lugnet.cad.dev)
|
| |
| | Proposed new meta-command: !STANDALONE_LDR
|
|
I'd like to propose the creation of a new meta-command. It is as follows: 0 !STANDALONE_LDR The zero at the beginning of this command MUST be the first byte of the model file. LDraw viewing programs can look for the presence of this command at the (...) (19 years ago, 9-Jan-06, to lugnet.cad.dev)
|
| |
| | Re: LDRAW Package format?
|
|
(...) I forgot to mention that the above programs will of course only work if he creates a directory somewhere that contains P and PARTS sub-directories, and then sets that as his LDraw directory in MLCad and/or LDGLite. --Travis (19 years ago, 9-Jan-06, to lugnet.cad, lugnet.cad.dev)
|
| |
| | Re: LDRAW Package format?
|
|
(...) I'd say your best bet for that is likely MLCAD or LDGLite. Not sure if LDGLite likes directories inside MPDs, but there's a reasonably good chance it will work. On a related note, have you tried using LDGLite or LDView as the renderer in LPub? (...) (19 years ago, 8-Jan-06, to lugnet.cad, lugnet.cad.dev)
|
| |
| | Re: ldglite for Solaris 10 Install procedure
|
|
Yes one could do that. But as compilation is a one time thing and they would still have the distribution in case they mauled it, I didn't feel it necessary to do it that way. (...) (19 years ago, 8-Jan-06, to lugnet.cad.dev)
|
| |
| | Re: ldglite for Solaris 10 Install procedure
|
|
(...) You should probably instead create a copy called makefile.solaris and make the changes in that. ROSCO (19 years ago, 8-Jan-06, to lugnet.cad.dev)
|
| |
| | Re: LDRAW Package format?
|
|
Hi Orion, Thank you! So I just need a good viewer for step-by-step instructions! Leg Godt -Sven (19 years ago, 8-Jan-06, to lugnet.cad, lugnet.cad.dev)
|
| |
| | Re: LDRAW Package format?
|
|
(...) Who said that? It's not specifically disallowed in the MPD spec and LDView/MLCad both work fine with s/ and 48/ in the file names. I just tested LDView by changing the LDRAW directory to an empty directory and used a self contained MPD file (...) (19 years ago, 8-Jan-06, to lugnet.cad, lugnet.cad.dev)
|
| |
| | LDRAW Package format?
|
|
Hi everybody, yesterday someone sent me an e-mail and asked for the instructions of one of my models. I asked myself: Shall I render all the steps of the instructions via LPub - which takes a long time? Or shall I just send him the mpd-file and a (...) (19 years ago, 8-Jan-06, to lugnet.cad, lugnet.cad.dev)
|
| |
| | ldglite for Solaris 10 Install procedure
|
|
ldglite for Solaris 10. Download and install OpenGL from the Sun Website :(URL) and install Glut from the Sun Website: (URL) ldglite from (URL) root (or other priveleged user) unzip ldglite in the directory of your choice (I use /opt and have the (...) (19 years ago, 8-Jan-06, to lugnet.cad.dev)
|
| |
| | Re: ldglite Compilation concerns
|
|
(...) I'd say that <GL/osmesa.h> would normally be preferable, but "GL/osmesa.h" works fine, since double quotes in a #include statement search a full superset of the directories searched by angle brackets. So it should certainly not affect its (...) (19 years ago, 6-Jan-06, to lugnet.cad.dev)
|
| |
| | Re: ldglite Compile fail
|
|
(...) Looks like gcc is getting pickier about function prototypes these days. Try adding this line near the top of hoser.c after the #include lines. void hoseout(void); (19 years ago, 5-Jan-06, to lugnet.cad.dev)
|
| |
| | ldglite Compile fail
|
|
Ok, I know UNIX, but to be honest, I'm no programmer by a long shot So This error stopped me. gcc -g -DUNIX -DUSE_OPENGL -DUSE_L3_PARSER -DUSE_BMP8 -DNEED_MIN_MAX -DUSE_PNG -DTILE_RENDER_OPTION -DTEST_MUI_GUI -I./mui/include -c -o hoser.o hoser.c (...) (19 years ago, 5-Jan-06, to lugnet.cad.dev)
|
| |
| | ldglite Compilation concerns
|
|
I seem to have found a typo in ldglpr.c : ---Begin ldglpr.c line 51--- #ifdef OSMESA_OPTION #include "GL/osmesa.h" void *OSbuffer = NULL; OSMesaContext ctx; #endif ---End ldglpr.c line 55--- Shouldn't that be <GL/osmesa.h> I may be submitting some (...) (19 years ago, 5-Jan-06, to lugnet.cad.dev)
|
