 | | Re: LPub and Lsynth page for tracking enhancement requests and bug fixes
|
|
(...) Looking into other renderers was just a thought of mine. Your requests for pause controls is indicitive of the cost of high quality rendering. For those who do not want to pay that price they have to lay out BIs by hand. I don't have a desire (...) (22 years ago, 30-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: LPub and Lsynth page for tracking enhancement requests and bug fixes
|
|
(...) I missed this bit before. I thought Jake was asking about why I didn't use MLCad for rendering. (...) I agree with this approach, I don't think you should write your own renderer, we don't need YARenderer at this point. Just link them in as (...) (22 years ago, 30-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: LPub and Lsynth page for tracking enhancement requests and bug fixes
|
|
(...) If you want an example of the quality you can get with this technique, take a peek at the Family Car instructions on this page. (URL) almost positive it was done with the edge thickening and scaling method described by Larry. Don (22 years ago, 30-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: LPub and Lsynth page for tracking enhancement requests and bug fixes
|
|
"Kevin L. Clague" <kevin_clague@yahoo.com> wrote in message news:HCKpqw.1x7x@lugnet.com... [ ... snipped ... ] (...) for (...) hand. (...) [ ... snipped ... ] I am chasing an issue that failed halfway through a render right now. Fortunately I am (...) (22 years ago, 2-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LPub and Lsynth page for tracking enhancement requests and bug fixes
|
|
(...) Hi Mike, I've added it to the list. Minimally I could see it affecting construction image size, and possibly some quality and anti-aliasing controls, but I'm not sure it makes sense to affect rendering of parts for part list images and BOMs, (...) (22 years ago, 2-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LPub and Lsynth page for tracking enhancement requests and bug fixes
|
|
"Kevin L. Clague" <kevin_clague@yahoo.com> wrote in message news:HCqIBJ.12tn@lugnet.com... (...) [ ... snipped ... ] (...) current (...) build (...) construction (...) not (...) BOMs, (...) For this type of LPub run I am not concerned about image (...) (22 years ago, 2-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LPub and Lsynth page for tracking enhancement requests and bug fixes
|
|
(...) I think this is a great idea, and can provide another recent example of why this would be wonderful to have. Using LPub, I recently ran a large model with about 6 submodels. I kicked it off before I went to bed, and it had completed by mid-day (...) (22 years ago, 3-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LPub and Lsynth page for tracking enhancement requests and bug fixes
|
|
(...) My solution to the above is to give you explicit control over construction image render window size and PLI render window size. You can set these sizes small for test runs. Is this acceptable? It will be available in the next LPub release. (...) (20 years ago, 4-Oct-04, to lugnet.cad.dev)
|
| |
| | Re: LPub and Lsynth page for tracking enhancement requests and bug fixes
|
|
"Kevin L. Clague" <kevin_clague@yahoo.com> wrote in message news:I52p4z.1xwI@lugnet.com... [ ... snipped ... ] (...) construction (...) sizes (...) LPub (...) I believe that will do. Thanks, Mike (20 years ago, 7-Oct-04, to lugnet.cad.dev)
|
