CAD Development : 6346


CAD / Development / 6346	6345 \| 6347

Subject:	Re: LDGLite bug report (yes, one more)
Newsgroups:	lugnet.cad.dev
Date:	Tue, 14 Aug 2001 15:53:54 GMT
Viewed:	508 times

Don: > I'm sort of interested in what you get for render times with > both parsers. Using the "l3" parser: $ time ldglite -ms -i1 -s0.2 -l3 town.mpd ... 281.790u 21.700s 8:48.81 57.3% 0+0k 0+0io 2290pf+0w $ A total of 303.49 seconds. The result: http://hugin.ldraw.org/temp/town-parallel-l3_parser.png Using the "ld" parser: $ time ldglite -ms -i1 -s0.2 -ld town.mpd ... 422.900u 19.870s 8:00.28 92.1% 0+0k 0+0io 784pf+0w $ A total of 442.77 seconds. The result: http://hugin.ldraw.org/temp/town-parallel-ld_parser.png As you can see is the "l3" parser both faster _and_ able to parse and render the whole model. Jacob -- http://hugin.ldraw.org/Jacob/edb/digitale_nyheder Om redaktørens opgave på internetnyhedstjenester.

Message has 1 Reply:

		Re: LDGLite bug report (yes, one more)
I did some work on LDLite this weekend. An image of an LDLite rendered town.mpd is at: (URL) image used the -fr option to turn off lines, and has ldlite shading turned on, so it looks a little different than the others. Rendering time was 828 (...) (23 years ago, 27-Aug-01, to lugnet.cad.dev)

Message is in Reply To:

		Re: LDGLite bug report (yes, one more)
(...) You should at least try the "-l3" before you recompile. I'm sort of interested in what you get for render times with both parsers. I only have somewhat underpowered PCs to work with, so I'm curious how they compare in the "real world". Don (23 years ago, 14-Aug-01, to lugnet.cad.dev)

21 Messages in This Thread:

Entire Thread on One Page:: Nested: All | Brief | Compact | Dots
Linear: All | Brief | Compact
This Message and its Replies on One Page:: Nested: All | Brief | Compact | Dots
Linear: All | Brief | Compact

Custom Search