Don't worry about the delay. "Real Life" kept me busy so I've done nothing since posing the questions.
I don't think using ldrawini would add any significant performance delays in ldglite. I never included it before due to laziness, and eventually I simply forgot about it. No matter. It sounds like my plan of incorporating both ldrawini AND the LDSEARCHDIRS additions is the way to go. Perhaps I'll check and remove any duplicate dirs from the search list(s) after the RealDir macro expansion, just in case...
In the meantime, do you have any questions on the solutions I came up with for the rendering issues? You could probably pull the new main.c and ldglpr.c from CVS into your ldglite codebase and try it along with a few small changes to the LPub3D render.cpp code. I'm curious if the resampling filter in ldglpr.c adds any noticeable delays to LPub3D. I'm also still wondering if the LDView scaling fudge factors truly are unnecessary and incorrect.
Don
I don't think using ldrawini would add any significant performance delays in ldglite. I never included it before due to laziness, and eventually I simply forgot about it. No matter. It sounds like my plan of incorporating both ldrawini AND the LDSEARCHDIRS additions is the way to go. Perhaps I'll check and remove any duplicate dirs from the search list(s) after the RealDir macro expansion, just in case...
In the meantime, do you have any questions on the solutions I came up with for the rendering issues? You could probably pull the new main.c and ldglpr.c from CVS into your ldglite codebase and try it along with a few small changes to the LPub3D render.cpp code. I'm curious if the resampling filter in ldglpr.c adds any noticeable delays to LPub3D. I'm also still wondering if the LDView scaling fudge factors truly are unnecessary and incorrect.
Don