I made some major changes to the markup feature based on the feedback I received on my last post. I decided to start a new thread
Here’s what’s new:
Markup is now a mode
This makes adding support for new markup geometry super easy. Additionally editing a markup-in-progress is possible, you can drag, delete or change properties of a markup curve.
Markups get saved as picture frames in the model
As opposed to snapshots, picture frames capture the state of the model exactly as it is. This limits what edits can be made after a markup has been saved into a picture frame but given the temporary nature of markups it didn’t seem like a big trade-off.
New tools in HUD
Eraser
Revision Cloud
Text
Anything else: Technically any command can be run during the markup, objects added during the markup will get deleted after markup is completed or cancelled.
Making a markup
Run the Markup command.
Click inside the viewport you want to markup
The HUD gets locked to that viewport
Markup using tools in the HUD
When finished, click the green check mark to save the markup
Markups saved as picture frames exist in you document, they can be organized into layers as necessary. Double clicking a markup picture frame will restore the markup camera.
It’ll be a lot of work given this workflow of turning them into picture frames. Adding more to an existing markup would be easier but deleting or modifying what’s already turned into pixels is another thing.
Can you help me understand the need for editing a markup?
More often than not I create something and it needs to be changed / modified to suit my clients needs which are hardly ever clear from the beginning.
I get the feeling my wish for editable markups is alien…
Maybe the process of turning geometry into pixels is not the best solution? At least in my very crude first attempt I noticed how a simple rectangle turned into a blurry bunch of pixels which is not something I would want to show in any document.
Exactly. You send the model to client, they mark it up. You change the model. Delete the markup if you want.
I don’t see why the markup itself needs to be editable in that workflow. Am I missing something?
I too feels that the pixilation [into a picture frame] is not the way to go.
even if you double or triple the resolution… for some screens, and at certain zoom it will always be a bunch of blurry square dots… also making them a picture etched into a viewport picture is disappointing direction.
I was very much hoping for a vector based layer for Markup, that will be just a layer in the document .
A couple of days ago i tried to to use it to explain somethings to a client. when i was done, it all turned pixelated and some of it simply disappeared all together.
Sorry and apologizing for the discouraging feedback, but please kindly consider changing direction.
Ok, so what if you save a markup and five minutes later you want to add something to the markup? At the moment you’d have to start from scratch, correct?
Does the state of the model not matter at all? What you’re suggesting can already be done. 1.Make a layer, 2.align the cplane to view, 3.draw with sketch command.
Is that enough for a markup? What happens when the model is moved, or modified?
The sketch command is too limited… I was hoping for a comfortable tool [that has a smoothing level control and use your nice HUD for fast controls.
well one can always simply take a screenshot at whatever state things are in a point in time.
I would love to see the Markup as on a similar class as annotations [basically annotations drawn fast and freely with a pen]
perhaps there can be a smart way to link a specific markup to the object that it is referring to? [and some form of history so when the object is modified there’s a warning [option] for that markup [something like “linked object has been modified”] just thinking while typing…
Rhino can work with SVG images, maybe instead of a raster image, convert it into a vector image ?
But again I would like to point that there are solutions around this for step 242 PMI data, and I believe the approach is aligned with the idea of having annotations on a construction plane around the model part.
Maybe having work in a way that,
Using the markup function could
Create a Cplane from the current view, and saving both the camera and cplane together, offsetting the cplane using the bounding box of the model.
activate projection to the cplane, guaranteeing that the markup will be between the camera and the model.
Create a Markup layer with the markup id and every geometry being stored together with it (similar to the new feature from Rhino 8 the clipping drawings)
Store curves with personalized thickness based on the pen input for those using pens to drawn over the model.
Call the personalized hud for the markup use.
Keep all curves nurbs based to be editable or anything else nurbs related that the user might need.
This way the markup could use existing commands like Layer State, Named Cplanes and Named Views and maybe developt on top of the existing code from the clippingdrawings command.
The first time I heard about Rhino3D was with people saying that Rhino is the swiss knife of cad programs, that can take any badly exported file, import it, fix it and export to be cnc machined.
Having this feature together with all annotation to be aligned with PMI data standard would create so much opportunity for ditching the paper drawings and finally communicating data seamleslly between programs, vendors, suppliers and everything.
Yeah but decrease the timescale to 5 minutes. My markup has a few detailed notes, I make some quick geometry changes and now I need to retype all those notes? At that point I may as well just take a screenshot and do it in Photoshop where I can edit the text etc.
The scope of the markup feature doesn’t include rewriting tools for curve creation. I’m simply using Sketch and other commands in the HUD. However I did add an option to Sketch command to make smoothing optional: RH-85934 Sketch: Added Smooth=Yes/No option
Thank you for looking at this.
Would you consider trying the following suggestion:
ATM, the smooth option creates a degree 3 curve. and the non-smooth create a very dense degree one … What if instead, we would have a degree option in the dialogue?
As a way to control the smoothing? Having curve degree options in the dialogue from 1 to 5 degree.
There are often situations when one would actually need more smoothing then what a Degree 3 curve gives, and a degree 2 might be more useful [with it’s slight smoothing ] then a degree 1 .
