NXT designers deserve a break
Remember the recent discussion on this blog about whether or not it's legitimate to sell building instructions?
A well-designed model can take days (and weeks) to design, build and rebuild.
Creating CAD models with MLCAD, POV-Ray and LPub (184.108.40.206) is tedious, hard to do right and SLOW, SLOW, SLOW! I'm not sure people understand how much time it takes to create accurate and understandable CAD building instructions. Yesterday, I set LPub running on a rather simple robot and it took over two hours! (I have a 1.66 GHz processor) If I only had to run the program once, it might not be so bad, but every modification requires running the entire file again. It's not uncommon to run the instructions 10-12 times before they come out right. Perhaps, if I could use the newer versions, it might be a bit faster, but I can't. After the instructions are "done", Rick tries them out and then I have to address every problem he finds---some of which require significant changes in my MLCAD files.
After the building instructions are ready, then there are programs to write and test, screen shots to take (and retake). Then you need to explain the program. Don't forget, all the building instructions and programming screen shots then need to cropped and assembled in some kind of desktop publishing format. (I use Photoshop and InDesign.)
It's no wonder we don't find many accurate NXT model directions on the Web. They require a LOT of long tedious hours of work. Anyone who takes the time to create good models with accurate and clear building and programming instructions deserves to be paid well for his or her efforts.
I feel your pain. Some of the CAD models I've made take 6 hours to render on my dual processor laptop.
Why not use the instructions generation capabilities of MLCAD for the checkout phase and only do the final rendering when your sure everything is correct.
ps. Thanks to everyone who has made detailed model instructions which have given me and so many others so much enjoyment with LEGO.
(see how I used all caps, lol)
I imagine most kids didn't buy their NXT with cash so the lack-of-credit-card argument is a little weak.
But I understand what you are asking.
I'm sure Philo knows far more than I do, but if you want to email me your questions, I'd be happy to share my hard-earned experience with you.
Difficult to give definitive answers... The books quoted by Fay are a good start, even if they din't include the latest developments. Most of what I use now was patiently learnt by use. My current flow is this one:
- Build models with LeoCAD (by far my preferred CAD program). Submodels are built as separate files (up to now LeoCAD doesn't support submodels, but that could change soon). Most instruction stepping is done with LeoCAD too
Cable ends and waypoints for LSynth are also inserted, one cable per step to be easily found.
- Export all submodels in LDraw format and create a MPD using MLCad.
- Edit file to add LSynth commands to create cables, run LSynth.
- Render a first BI with LPub and LDGlite renderer.
- Fine tune stepping, and add LPub commands to the file to put several steps per page, add callouts and so on. This is by far the most tedious part (numerous pages generations are needed here).
- Render the final BIs...
That said, LeoCAD can be used to generate very readable and understandable BIs - though not graphically superb (and missing cable synthesis). The process is much faster and easier. You can see such BIs in my older models, for example my RCX brick sorter.
What you see was created as HTML instructions by LeoCAD, with just some editing to match my website graphical chart.
Congratulations, Mirik, these are very good BIs!
You told me that you don't use Lpub for automatically generating building instructions. Does that mean you produce your CAD instructions one-by-one?
If so, that's REALLY labor-intensive.
I didn't use Lpub for generating instructions. I didn't even know about it until you mentioned it to me in your email. I used MLCAD and POV-Ray and rendered each image one at a time! You are right, it was labor intensive.
May be next time I should use LPub?
If you're using LPub, you can select jpg or png for your output. If you're talking about converting an ldr file to a photo, I don't know. My graphic converter doesn't recognize the ldr format.I just render it in LPub, POV-Ray or LDGlite if I want a model or part picture with a standard format.
If you want to save a picture in MLCad...use the "Snapshot" option in the menu File>Save Picture(s). You can also move the 3D image around before you snap the shot. There is also an option to remove the step number.
Or at least some articles for the website?
I'll check out some of the tools folks mentioned. I have the two books that Fay talked about (my wife surprised me with them for Christmas last year).
I am not an graphical artist, but I can use MLCad fairly well... so I'll see what happens with some other tools.
If you want to view the parts added per step use "view mode". This will allow you to step through the building process using the arrow buttons on the toolbar. When this mode is selected only the first few parts will be shown in the screen until you move to the next step (that adds more parts).
All of this is in the toolbars and the menu options of MLCad.
To produce images of each step...the radio button within the File>Save Picture(s) must be checked. Then, pics of each step are produced and saved in a folder you choose.
On to the other Photo/Instruction renderers...It gets a little complicated. But, the same idea is there...but you will always need step callouts in your MLCad files.
Here is the part you're looking for: http://www.ldraw.org/cgi-bin/ptdetail.cgi?f=parts/42003.dat
You need to download it and copy it to your C:\ldraw\parts directory, then install the file with LDraw and MLCad...here's how:
Click Start and then select Run, type C:\ldraw\mklist.exe and click OK. When asked to sort by number or description, type the letter D for description. When the program finishes, close the window.
Next, select File/Scan Parts from the MLCad menu; MLCad should tell you that it has found new parts and ask if you want it to save a new parts.lst file. Click the YES button.
This is a redundant step but safe to perform.
Now, you will have the part in MLCad.