Renerabbitt

hauske is another service wich is basically Stable Diffusion with Controlnet using Realistic Vision as a model which is free if you can set it up yourself. I use a custom chatbot I wrote thats in my forums for scripting ruby Some times I do some idea starting from apps but really the good old pinterest search is usually faster for me

really should be doing with with a custom material and custom wall definition

Preface to say what you are asking for requires very advanced methods which is why you may not have found much on the subject. Some people build a simple tool for a solution which only handles particular use cases. Might be more useful to just use a calculator For a holistic approach that covers most if not all aspects of a programmatic result for nfa requirements, I think there would be some sacrifices somewhere down the line. In a perfect world we don't need global macros, but you likely do for this task to be done and working for all scenarios. Here are a few things to note: A roof plane can report ridge_vent_length so long as ridge vent is checked in the Supply section of the Options Panel of your roof plane or Build Roof. Otherwise A roof plane can report projected overhang area A roof plane can report projected area A fixture class of symbol can be set to flush mount on a roof and report the room that it is placed "in" as well as its width, depth, height and custom_fields which can be formatted to report values from macros A fixture can have an offset that can work to keep an object in a room when its geometry is outside of the room...such as inside of eave blocks for instance A custom_field with a numerical value can have its sums totaled and those sums could be produced from an equation Now for the bad parts. A triangle shaped hip roof will not have a ridge vent to report so it could prove challenging to adjust your equation between 1/150 to 1/300 requirements without some conditional situation. A fixture can report area of the room it is placed in, it but that would not be helpful if the room was only partially covered by a roof A roof plane does not know what room is below it You'd have to get real clever about representing eave vents or soffit vents There is no OIP for the Build Roof has_ridge_vent doesn't exist as a reporting value from Roof Planes there is no easy way to calc attic area with a roof overframe condition The real challenge is determining what attic space is, whether or not a roof plane satisfies the rule for 1/300 or 1/150 depending on the presence of a ridge vent. A system you could use is a simple trigger such as the presence of some term in the comments section of the roof Or you could make the trigger be based on say the prefix of the schedule number where R04 means the roof plane ha a ridge vent and calc from that. Then the last problem is either using polylines or fixtures to create the nfa value of your vent. I think my version of a perfect system might be that I have fixtures. Here is a ridge vent fixture I created that reports nfa as a custom field formatted as a number, derived from its width. Followed by a fixture that represent an eave vent that derives nfa from its widthxheight. Pls roof planes that take projected area minus projected overhang This does not solve for an overframe condition

try using twinmotion cloud presenter instead. PBR and full walkthrough capabilities

See video 240628.mp4

did you update your software?

not sure I like that...then we have to delete the source item, if we remember to, if we dont want the source item where it once existed

yeah I just sent this in. I see the add a link tool...don't see much documentation on that and how it correlates with exporting a catalog

i would clarify, this isnt the same, because if you had a door or window in the wall then that door or window would be in new location if you rotated the wall in place. also would clarify this is in plan view, one could confuse "vertically" for top elevation to bottom elevation

do share..I thought you might say this :

Hands downs: OIP in rooms and floor defaults xy position updates for layout row totals and custom field number formatting those 3 alone net 20% improvement in drawing efficiency for me

install and it will re-write. this is called an in-place update. your files remain intact

update from beta doesn't require a migration so you should be able to install and just run the program again

reverse your interior wall direction

same question

LOL, was this for a 1:1000 miniature model?

Pyramid Tool 240625 (2).mp4

Just as a general FYI about Google Earths accuracy, and in regards to this post, it's not going to be nearly as accurate as the survey that he has, though he certainly could use a combination of the survey and what you would provide. Google Earth interpolates from section to section where a section is a resolution of 30 meters by 90 meters. It will miss things hidden by trees or incorrectly interpret retaining walls etc. It can be off as much as 2M at times. Google gets my lot way off, and in general doesnt do well with dense forest hills for instance. I use it as well but not when it comes to anything important regarding terrain

post the pdf here please

report it as a bug, I will too

but thats aligning to outer surface. They want sheathing layer

This video works, just change your floor structure to masonry:

You could make a custom symbol, but in the end, its faster to manually place these items as we don't have enough directly editable parameters in treatment/millwork/shutters etc. for all of the various configurations you may come up with

So this is part of a full transfer of my existing template to an OOTB x16 template. easiest and seemingly fastest way.. in default OOTB template: delete all SPV delete all layer sets that aren’t camera defaults delete all text styles that aren’t defaulted. rename all remaining text styles then import SPV/layersets. delete renamed text styles. ugh.

even for duplicate text styles?