Hey Kyle, thanks for the feature request & video explanation! This is something we are planning to add. 🙂

Hey Luis, we currently don't have any of that implemented, though it is a great feature request, and something we are considering.

Hey David, currently, we only rotate in 90-degree increments (via right click on the page), but many users have requested finer control. I'll mention this to the team. 🙂

Hey Elliott, thanks for the feature request! I believe this is a planned feature. 🙂

We have an option to "Print Current View" to achieve this. It only prints the current page, though.

Hey David, thanks for reporting! We'll dig into this and get a patch out.

Hey KevOB, currently no way to switch the property mode in the batch import, but it is something we are planning to address soon.

Hey Conetoe, currently, there is no way to import the measurement type or a parent/child relationship. We are planning to do some updates to the batch import soon to add these capabilities, though.

Hey Tyler! Thank you for the very detailed explanation and associated images. It helps a ton for the DEV team. 🙂

Hey David. With the current formula engine, you can't use tags within tags in the same formula (Example - [Tag 1 [Tag 2]]). I think we plan to address this in the future. For your use case, it m...

Hey Abe, thanks for reporting! I was able to replicate this on my machine, but only if I went over 100+ scale. Going under 100 worked fine for me. I'll mention this to the team to see if we can ...

Hey Chuck, no major updates have happened to overlays since we released them. The latest update added the ability to customize the comparative overlay colors and also to indicate which page was ad...

The traversal via "../" and "./" is similar to the file structure of your computer. "./(takeoff name)" looks for a sibling takeoff/folder, whereas "../" goes to the parent takeoff/folder. '/' on it...

Hey Luis, the formula traversal logic depends on where the takeoff is in relation to the item in the tree. In this example, the formula should be "[Point Count] * [../../../../01 GCs/Unit Count/1 B...

Thank you for the feedback, Tysen! I'll mention this to the team. 🙂

Hey Gary, you can right-click on the page and use "Hide All" or "Show All" to hide/show all takeoffs/digitizers on the page. If you go into the submenu of the hide/show, you can also hide or show ...

Hey Matthew! Right now, we don't have anything built into the software to export this. What you could do in the meantime is use the "Export Project Data to File" and, using AI, build a script tha...

I think Codex may be misinterpreting how zzTakeoff is calculating the sloped area. Right now, the Sloped Area calculated via is Flat Area×Slope Factor. We don't take into consideration which direct...

Hey Lani! Sorry for the late response on this. I may be misunderstanding this, but are you trying to choose the direction that the area slopes, or is this something else? If this is an area, the d...

Ah! You can send this video to support@zztakeoff.com and mention that it is for further context on a community post.

Hey Jes, thanks for pointing that out! I'll see if that's something the dev team can tweak 🙂

Hey Luis! You should be able to use the traversing logic to achieve this - "[Area:SF] * [./Unit Count/Point Count]". Another useful post to look at is Reference Variables From Other Items.

Hey Lani, thanks for the feature request! That would be a pretty cool addition. Do you have a short clip of how this works in OST that you could share?

We don't have a way to reference those values yet, but we are planning to add a computed column to reports that can compute based on those aggregated values. Note: this number would only appear in...

Hey David, this is due to our built-in inheritance from takeoffs down to items. This only happens if the property exists at the takeoff, but not at the item level. Note: applying the custom prope...