Andy Broomell

This happens to me all the time and I've never been able to figure out why.

I run into this problem as well. Including being unable to select a Section Viewport via clicking on the fill of a sectioned/hatched object.

I'd use this... much easier and faster than current workarounds.

It's probably related to a checkbox called "Update visible out of date viewports before exporting" towards the bottom of the Export PDF dialogue box. (I tend to leave this unchecked.) It shouldn't be random, but it might seem random because it won't re-render if all viewports are considered up-to-date. Try unchecking this setting and see if that fixes your issue.

The "Library" folder that's within the "justin" folder is actually a hidden folder, so to see it you'd have to hit Cmd+Shift+period. Or as Marissa suggests, the easiest way is to just hit the Reveal in Finder button. 🙂

This has happened numerous times to me as well.

If you render without a RW background, and export the image via File<Export Image, choose PNG and check Save Alpha Channel, then you will end up with a transparent background, allowing for even easier compositing in Photoshop.

What's actually needed is a "Greyscale" option when publishing, as the true "B&W" option erases all fills and even makes grey lines black. I seldom want B&W; Greyscale would be much more useful and solve CW76's problem.

Also, every one in a while I've found that you have to Update the viewport before the orange box reflects a change to any of the above.

What are your current 2D graphics like? Are you using Image Fills? If so, are you perhaps asking if there's a way to take an Image Fill resource and automatically make it a RW Texture resource? (There's no automatic way, but when adding an image to a new texture, you can use the "Reuse an Image From Another Resource" option.) Or if you're talking about gradients and things, then definitely not. 3D objects only accept a solid color fill or a RW Texture. Perhaps we're still misinterpreting... If you can post a screenshot or two, that would help too 🙂

Sounds like the same issue as this thread and a few others: It seems via my messages with @Matt Panzer that they have a fix for it, so I'm just waiting for that next SP. I had to revert to 2018 in the meantime.

Unfortunately this isn't currently possible as described, though it'd be an awesome functionality. The closest workaround (outside of marionette) that I can think of for your situation is to have a separate symbol definition for each type of thing you want, and make sure that the Insertion Points align properly across the symbols. Then when you want to switch an instance from one type to another, hit the "Replace" button in the OIP which will switch the Symbol definition while keeping the object object in the same coordinates and (optionally) the class it's assigned to. If you're dealing with records as well, you can utilize Modify<Convert<Replace with Symbol, which is similar the "Replace" button. You can even assign it a hotkey in the workspace editor if you'd like.

Oh and another thought.... You could create a plug-in style for each different Drawing Label set-up by selecting an archetypical Drawing Label and running the Create Symbol command. Then check the "Convert to Plug-In Object" box . Then you'll have a little library of presets that you can drop in by choosing them in the RM. You could even save these to a library or favorite file, presumably. Hope this helps.

Another handy trick if you already have one Drawing Label with the settings you want is to hold Cmd+Opt [Ctrl+Alt] and click the existing Drawing Label - you should get a cursor with a yellow star and eyedropper . This let's you "pick up" those settings then the next one you make should have the same settings (even if you have to navigate to a different viewport first). This works for a quite a few things - dimensions with different font sizes, walls with different walls styles, different symbols to place more of the same, etc. It's the "create similar object" shortcut, which changes the active tool and its settings, the settings in the Attributes Palette, and the active Class as necessary.

Ugh, this just happened to me in 2018 SP6. 😕