LDraw.org Discussion Forums

Full Version: Idea: Highlighting new parts in a step
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3
Maybe I am asking too much at a time, but I really want to share this thought...

Reading the review of the Ghostbusters Firehouse on Eurobricks (http://www.eurobricks.com/forum/index.ph...pic=118783) I saw something interesting I've been wondering about before.

LEGO uses highlighting to show what parts a new in a step.
Like this
[Image: 23570011939_3a3f90efdc_z.jpg]

They've done this occasionally before (in the long past and I think with some monthly minibuilds) and I think it would be nice to be able to do this too?

Would something like this be possible to implement in LPub3D?
Or use some other software to pre-process an LDraw file that creates lines around the parts of a step?

I've done this in some instructions by hand (not every step) where it was really hard to see where parts went in a certain step. This is often the case with a monochrome model or when one uses many black for instance.
For me, this is comparable to changing all but the model's current step to a 'fade' colour - which is already available in LPub3D.

It would be particularly difficult to implement this functionality because I'd have to find a way to signal the render (LDView, ldglite, Pov-ray) to produce an image where the additive parts were highlighted. I'm not even sure either of the renderers I use have the ability to accept a command/signal as such.

Because LPub3D uses static images (produced by the renderer), any highlight not visible would be useless, so the entire functionality would be questionable in achieving it's intent.

However, it would be possible to signal the 3D Viewer but showing highlighted additive parts to the editor does not strike me as the intent of your idea ?

Cheers,
Trevor Sandy Wrote:For me, this is comparable to changing all but the model's current step to a 'fade' colour - which is already available in LPub3D.

True, great feature! But not always practical.

Trevor Sandy Wrote:It would be particularly difficult to implement this functionality because I'd have to find a way to signal the render (LDView, ldglite, Pov-ray) to produce an image where the additive parts were highlighted. I'm not even sure either of the renderers I use have the ability to accept a command/signal as such.

Because LPub3D uses static images (produced by the renderer), any highlight not visible would be useless, so the entire functionality would be questionable in achieving it's intent.

However, it would be possible to signal the 3D Viewer but showing highlighted additive parts to the editor does not strike me as the intent of your idea ?

Cheers,

I imagined this would be difficult to implement.

However, I thought LPub made a temporary LDraw file for every step and render that accordingly as assembly image?
You could compare that to the previous step or create a file with only the parts from every step.
Then process each step file to draw outlines (line types) around visible edges (is that possible?).
And add those parts as as a kind of layer to the previous step and thus creating the new step with new parts with lines and draw that step as assembly image?
Isn't this the way color fade works too?
Jaco van der Molen Wrote:...I thought LPub made a temporary LDraw file for every step and render that accordingly as assembly image?
Yes it does.

Jaco van der Molen Wrote:Isn't this the way color fade works too?
I only change the csi content colour code for previous step's parts.

Jaco van der Molen Wrote:...process each step file to draw outlines (line types) around visible edges (is that possible?).
The fade colour feature does distinguish between previous steps and current but preparation of the additive parts are much more simple than what I understand from reading your suggestion. For fade colour I just change the colour of the step's additive parts. The cis is then fed to the renderer and a faded image is produced.

It sounds like 'drawing outlines' will require significantly more processing to determine which edge lines will need to have it's colour manipulated.

Cheers,
Trevor Sandy Wrote:
Jaco van der Molen Wrote:...process each step file to draw outlines (line types) around visible edges (is that possible?).
The fade colour feature does distinguish between previous steps and current but preparation of the additive parts are much more simple than what I understand from reading your suggestion. For fade colour I just change the colour of the step's additive parts. The cis is then fed to the renderer and a faded image is produced.

It sounds like 'drawing outlines' will require significantly more processing to determine which edge lines will need to have it's colour manipulated.

What about this way? I think there is a pretty easy solution to that that does not require a lot of finding edges etc. let the renderer do it :-)

Render the first Step:
- LDView: All normal
[attachment=1951]

Render the second Step:
- LDView: All normal
[attachment=1952]

Render the second Step ONLY the additional parts:
- LDView: EDGES ONLY, THICKNESS = MAX
- change the color BLACK to a Highlight, e.g. YELLOW or ORANGE
[attachment=1953]

Now merge the original STEP 2 and the Outlines of STEP 2
et voila! :-)
[attachment=1955]


That should be fairly easily to do, the current "fade" feature detects the parts of a step in a similar way. As the control of LDView via the command line is pretty extensive this should be doable.
Hi I am new here and don't know much. How do you update the library?
Did you produce your mockup using LDView command line?
No, he merged the two images. For this to work, both need to be the same size (in pixels), and also both have the same camera settings. Then, drawing the second image over the top of the first yields the merged image. If you look at the second image in an alpha-aware image program, you'll see that everything except the lines is fully transparent (alpha value of 0).
I did use the GUI of LDView to get the pictures and merged them in GIMP.

What I can find in the LDView manual are the following command line parameters for the "edge-highlight" render:

EdgeThickness (Integer, 1-5) -> 5
EdgesOnly (Boolean) -> YES
SaveAlpha (Boolean) -> YES

The rest, camera position, image size, anti-aliasing etc. can stay the same.
Ok, so far so good but it looks like we'll need yet another third-party application to perform the merge. Is this correct ?

I like this approach and I could use the same scheme to improve the quality of the fade part functionality also. In fact, I see a whole range of rendering improvements with this sort of 'multi-image' manipulation.

Does anyone know if there is or I can package GIMP as a distributable - e.g. like I've done with ldglite ?

Cheers,
Pages: 1 2 3