Alaskan_Son

Email me the file to alaskansons@gmail.com and I can try to see what it does on my end. I suspect that it probably just has to do with the sheer number of faces though.

Just strip it down and remove any proprietary information.

Its being limited by the tab stop limitations which have to be whole numbers.

The .chr at the end is unnecessary and redundant. The chr method will return the first character in the string; however the slice(index) method that you've used will also only return one character, so what you're essentially doing is asking for the character at the -1 index and then asking for the first character of that single character string. I think the most elegant method is the one Eric showed though. Slice works, but simply calling for the index inside brackets is cleaner.

Set up an Orthographic Full Overview camera parallel with or perpendicular to your roof and set it’s Tilt Angle to match your roof pitch.

You have all sorts of problems going on. First things first: That macro is overly complicated and was written by someone at some point prior to Chief implementing the Measurement class. You can get rid of the error as shown below: $_2ExistingBoxSQFT = area rescue $_2ExistingBoxSQFT if $_2ExistingBoxSQFT.to_f == 0 #area is a Measurement with a unit and you're attempting to compare that to a unitless value of zero. You first need to make the Measurement unitless as well. na = "N/A" "#{na}" #These aren't actually breaking the code but they're unnecessarily redundant. else "#{$_2ExistingBoxSQFT.to_f.round(2)} SQ. FT." #Again, this wasn't causing the error, but you're adding some text to show a unit for a Measurement when a unit already exists. You should really either use the automatic unit or first convert to a float and then use your own. end Second: You need to set that global variable before it can be used in a text box. That macro was designed to both define a variable and display a variable value. Your plan attempts to display the value before it has even been defined. To define the value, your macros need to be placed into the label of your polyline object. Now if you ask me: I would suggest an entirely different approach that completely bypasses Text Macro Management. In your polyline object use something like %$my_box = area% In your text box use either %$my_box.round(2).to_s% or %$my_box.to_f.round(2)% SQ. FT. It can really be as simple as that. If you need further formatting or conditional arguments you can either add it right in line or you can go back to writing and maintaining custom text macros, but that stuff isn't necessary for most use cases.

I wrote that several years ago prior to Chief creating the NumberFormatter class, so there are currently more robust ways; however, here's a very special improved version of that same older system you're already using set up in such a way that you can use a single macro anywhere you want for all 3 scenarios plus others. Simply import the attached macro and then in your label, place the following: If you want feet and inches; %macros.my_nf.ft_in(number, rounding precision)% If you want inches only; %macros.my_nf.ft_in(number, rounding precision)% So, for @joey_martin's example, if he wanted the framing member length displayed in feet and inches rounded to the nearest 1/8", he would put %macros.my_nf.ft_in(length, 8)% For @MZLehman's example, he would put %macros.my_nf.ft_in(length, 1)% And for @robdyck's 3 examples he would put %macros.my_nf.ft_in(height, 8)%, %macros.my_nf.ft_in(length, 8)%, and %macros.my_nf.ft_in(width, 8)% Again, the NumberFormatter class is more robust and a similar system could be set up for that class as well, but this is a pretty simple and easy to use solution for simple feet and fractional inch formatting on the fly and it doesn't require placing any initiating macros into your views. I'll leave it here for free for a bit:

To give everyone what they want, the label dialog would have to look identical to the Format tab of the dimension dialog and each and every part of a label would need to have access to those settings as well since any given portion of a label might need to be formatted differently. I think building this type of behavior into the label would be totally unreasonable if not entirely unworkable.

Thanks for the plug Robert. Actually, the first 3 you posted were all created using one of my macros.

You're right, it does happen all the time. If you're really just trying to reinforce something that's already been said though, I think it goes a long if you qualify your statement as such with something like: As so and so already stated... I agree with so and so... To add to what so and so stated... Etc. Or if you don't want to give credit to a specific person and instead just want to build on the idea: To expand upon what was already pointed out... I agree that... I too think that... I second... In order to achieve the aforementioned... Etc. Not only is it courteous, but referencing the original statement also helps tremendously if your goal is to bolster and truly reinforce a common idea/discussion instead of creating what might seem like a whole new one. It just helps keep things a lot more easy to follow when there's a common reference point. There's my 2 cents.

My point is that you've just repeated what I already said. I also thought the extra information you added to your post was unnecessary and a little misleading.

I already mentioned placing the dimension perpendicular. Its not really snapping to the point where you clicked though like you're claiming. It's just that Chief isn't drawing the extension because it's unnecessary. Its easy to prove too. Just dimension to a line and then change the angle of that line.

It doesn't sound like you're missing anything. Dimensions snap to a number of specific points on various model objects but those points are almost if not always either at corners, start/end nodes, break points, or at object centers. What you're trying to do doesn't coincide with any of those. You're trying to snap to a random intersection point along a line. There's nothing for Chief to associate this random location with (which becomes a really issue when moving/resizing the referenced object). You have a few options: Use Point To Point Dimensions which will automatically drop a point marker at your desired location so that Chief has something to associate the dimension with Place the dimension perpendicular to the referenced line so that Chief can just use the end node Place a break in your referenced line so that Chief has something to associate the dimension with

Here's what I recommend: Place an angular dimension that is attached to your desired lot line on one side and to a perfectly horizontal or vertical line on the other Group select your desired objects Click on the dimension and set it to either 0 or 90.

During Import, click on Show Advanced Options and then go to 3D>3D Geometry>Drawing Unit and change the Unit.

I developed a very simple to use, tried and true method for this a while back very specifically for use with Total Stations. The required 2D point data can literally be placed, compiled, and exported in about the same time it took me to type up this response. It just requires a small starter kit and some basic instructions. https://chieftalk.chiefarchitect.com/topic/25158-importing-points-into-a-ascii-format-for-total-station/?do=findComment&comment=202515

It's all in the name of the setting--Subfloor Height Above Terrain. That is, its how far (height) the 1st floor subfloor (absolute zero) is above the terrain zero (sea level).

Its because you haven't defined anywhere on the terrain as anything other than -8'. You need to define somewhere as being 0' so Chief know where to slope to.

You can do as Eric showed above, but for what it’s worth, it looks to me like you probably just failed to check Evaluated for your macro named “x”. Just make sure the macro is set to Evaluated, Context: Owner, and then try again.

Not a dumb comment at all. This is exactly what I suspect is happening as well. The next thing I would suspect is that perhaps Include in Layout Page Table is not checked for any of the other sheets.

You should be able to get attic trusses if you place the required interior walls and set the ceiling height appropriately.

No. not really. You created a backclipped view meaning everything in the background was cut out of the picture. That just leaves you with whatever is between your camera and the clipping plane. Since your Cross Section Lines layer was turned off you weren't getting any lines being drawn in those areas. You're also not seeing any floor framing because the floor hasn't been framed yet (the framing layers aren't turned on either by the way). And lastly, you want see a fill for your foundation wall unless you either manually create one OR use the Auto Detail tool to create one...and again, the appropriate CAD layer needs to be turned on.

This is pretty much exactly what I would expect to see with that camera as you have it set up. The only thing missing really are the Cross Section Lines. Turn that layer on.

Try it again. It should work. You may want to open the cameras one by one and and reposition them by clicking Fill Window Building Only, but I tested it out and once the building is back at 0,0, everything works as I would expect.

I think your problem is being caused by the fact your model is about 2 miles from the origin. I would suggest you used Edit Area (All Floors) to move everything back to 0,0. I think that should fix your problem.