Alaskan_Son

Its not a Mac vs. PC thing. Its based on what macros you have in your current plan. Chief's latest object properties macro is %object_properties% and reports not only standard name:value pairs but also expanded NVPublisher name:value pairs. It also works in both owner and referenced contexts. Many people are using old templates with old macros that used different naming convention and/or had different functionalities. In addition, some people have both Chief's macros and macros written by other users (which again might be named differently and have different behaviors).

I think what you're doing is presenting an XY Problem (click to read up on it). That is you're needing to solve problem X and you're trying to do so by asking how to achieve Y. The problem is that Y is simply an inappropriate solution. In other words, you're asking the wrong question. The simple fact is that Chief works entirely different than the software you're currently using. I suggest you stop trying to use the same approaches you used with your previous software. You're just wasting a lot of time and energy. The solution you're looking for simply doesn't exist in Chief because its a different tool set built around on an entirely different paradigm. You'll just need to adopt a different system. Here's a little additional food for thought: One of the main benefits of using a true 3D modeling application like Chief Architect is that you can model your structures in 3 dimensions exactly like they'll be built in real life. That means when you generate a cross section or take an elevation view, its going to display exactly what you've modeled and not a generic representation. Some of the process takes a bit more work, but the payoff can be enormous. Model the building once and you can generate as many views and details as you want at any angle and from any desired reference point. You can analyze all sorts of things that would otherwise be impossible to analyze. By trying to generate a bunch of generic details and sections you're largely defeating the purpose of using a 3d modeling software and in doing so missing out on many if not all of the real benefits.

My previously posted workaround solution works with this plan as well:

This is EXACTLY what I suspect is happening as well.

No

Not sure about ascii but I believe the the JavaScript key code is 93. You can also try Shift+F10 or Control+Shift+F10. I can't make either of those work on my system. but I also have a menu key, so I'm not sure if that's affecting things or not.

I use Jitbit Macro Recorder in which I can set the delay between keystrokes to whatever I want. A sequence of 20 or 30 keystrokes can be carried out in a split second. This of course isn't always the case. Some operations require setting longer delays, but if you're currently limited to the built in delays, then I would suggest you consider using a different macro recording software. I'm sure you could still assign the macros to you radial menus as well.

If you're using a macro/keystroke recorder and intending to share with other users, I would suggest the exact approach I spelled out. The one you seem to be suggesting is not very dependable. It's the approach I originally started with, but I found it only consistently works if the library browser is its own window. If the Library Browser is docked along with ALDO and/or the Project Browser like many of us do, and something other than the Library Browser was the last activated window, then that window is the one that stay active. The Library browser will close and reopen, but you won't be able to get to it.

It's possible, but I have NOT found a way that doesn't involve closing and re-opening the Library Browser. I posted the most effective sequence that I've come up with here:

I always forget about that feature. Pretty cool, but I'm always curious how many people actually made use of it.

Look closer at the image I posted.

There are 2 different approaches you could potentially take for this one. Scale down ALL your various components before you start modeling (walls, roof structure, floor structure, window sizes, door sizes, molding sizes, etc.) and actually build the model to true scale. Create your own Units and use those instead. You can do this by going into Preferences>General>Unit Conversions and then adding a new Unit. The unit might look like this...

That just looks like an Opening to me. See if maybe a Doorway or Pass-Through does what you're looking for.

No. That would be a far more complicated process and not one I have time to spell out. Its possible, but requires some ridiculously convoluted methods that I don't currently have the time or inclination to try and spell out. I don't think you'll find them anywhere else either. Your best bet is to just try and get it close enough OR use a different software to make the symbol OR hire someone to model it for you OR see if you can find one that's close enough on 3D warehouse or on one of the other various 3D symbol/model repositories like Turbosquid.

In X12 you’ll need to be in a 3D view.

There are quite a few methods but most are more complex than this one. Here. I threw together an X12 version of the tool for you... Symbol Curving Tool (X12).calibz

Not a bad approach. There's a reason thousands and thousands of companies are still using Windows XP. Its exactly this situation. They either can't get newer software that does what they need, or upgrading would be too cost prohibitive.

I have a special "tool" set up specifically for this purpose. The basic concept is that you convert your desired object(s) to a cabinet door symbol and then use a Bow Front cabinet to get your desired size and shape. Just download the attached symbol and follow these basic instructions: Download the attached object. Its really just a Bow Front Cabinet set to a Filler and with every element turned off except for a single Door Front. Select the object(s) you would like to curve, and click the Convert Selected to Symbol tool. Choose Symbol Category>Cabinet Door/Drawer, check Add to Library, and check Show Advanced Options. Click Okay. When the Symbol Specification dialog opens up, change the Y Position Origin Offset to 1/16" (this will cause the door symbol to hug the cabinet front with no gap between the door and the cabinet) Drop the previously downloaded "Symbol Arching Tool" cabinet into your plan Select your previously created Door/Drawer and hover over your "Symbol Arching Tool" cabinet. You should see the Replace From Library indicator. Click to replace. Change the width and height of the cabinet to adjust the overall width and height of the newly curved object and change the Bow Front Depth to adjust the radius of the curve. NOTE: It really helps visualize things a bit better if you at least temporarily turn on Show Closed Doors/Drawers in Plan View in your General Cabinet Defaults. When you get the shape you want, simply select the cabinet, Convert Selected to Symbol, and select Symbol Category>Fixture Symbol Arching Tool.calibz Using the tool above, I was able to grab a simple curtain from the core catalog and create this new symbol in just over a minute.

A couple things: 1. You don't actually need 2 offsets. Setting one or the other to 30" works just fine and does NOT result in casing with the little flat spot on the top. 2. You can also simply use a Tudor Arch with the radius set to zero.

I’m pretty heavily invested in Chief at this point but if I was just getting started, I would almost certainly be looking at either Softplan ot Archicad. Both of which offer an outright purchase option, one of which is notably more robust in quite a few ways, and one of which is notably cheaper. Chief has it’s own unique strengths, but I’m not sure any of that would matter since the subscription only model is a deal breaker for me and so I wouldn’t be digging that deep.

Here are my basic definitions: 2D = Lines, polylines, and fills drawn along X/Y axis 3D = Faces that exist on X/Y/Z axiis/planes Modeling = the act of actually creating the 3D objects Renderings = the production of simulated camera views of the 3D model

it’s not a problem with dimension strings. It’s a problem with the dimensions that are reporting to the schedule.

Yes. This is a pretty big deal as well. I feel like a policy needs to be adopted right up front that ties SSA to a fair and equitable percentage of the subscription license cost to ensure a consistent, measurable, and reasonably predictable value of our legacy licenses as they compare to the subscription licenses. Outside of this approach, I think it’s going to be far too easy to ostracize legacy users and make us feel like we’re not being treated fairly or that we’re getting hard armed into the subscription based system.

Be aware that Architectural Blocks may or may not show the desired width and depth values. It’s the biggest downside of going that route in my opinion. Architectural Blocks report the bounding box width along the plan’s X axis and they report the bounding box depth along the plan’s Y axis. That means you’ll get the desired dimensions in one specific orientation, you’ll get inverse dimensions in a perpendicular orientation, and you’ll get completely different dimension in a horizontal orientation.