ComputerMaster86

You can run Chief Architect on Core i7 and Ryzen 7 Processors just fine. I actively do on both an Intel Core i7-10700K and AMD Ryzen 7-7700X. Both are 8-Core 16-Thread CPU's. The Intel processor has a base frequency of 3.8 Ghz and the AMD 4.5 Ghz. The i9's and Ryzen 9's depending on model have a few more core's and/or a bit faster clock speed but many i7 and Ryzen 7's are still decent work horse processors. I try to shoot for 8-core processors with around 4.0 Ghz speed as a baseline for a processor for a computer that is going to run Chief. If you are going to do ray-trace renderings get a good graphics card. I've been using a RTX 3070 super on my semi-portable open air desktop quite a bit this week. My big ole desktop PC in a more traditional case has a RTX 4080 super on the inside. I honestly haven't used the 4080 super much but, others on here actively use RTX 4080 supers for raytrace renders.

Its not a laptop but, I picked out the components and had a local computer shop put this machine together for me. It's a mini ITX computer built on a OCPC frame. After it was built, I added the RTX 4070 super graphics card. Almost doesn't fit. I call it a semi-portable computer. It has a... + OCPC Mini ITX Case + GIGABYTE B650I AORUS Ultra Mini-ITX AM5 Motherboard + AMD Ryzen 7700X Zen 4 Processor 8 Cores, 16 Threads @ 4.5 Ghz Base Processor Frequency + 32 GB's of DDR 5-6000 (3000 Mhz) Memory (2 DIMM's @ 16 GB's) + 1 TB Samsung 990 PRO NVME M.2 SSD + GIGABYTE GeForce RTX 4070 Super Eagle OC 12G Graphics Card After my 8 year old laptop gave up the ghost on me, I had thought about another laptop. Hearing people having problems with brand new laptops, I decided to go this route. I am so happy I did. I even cart the machine back and forth to my daytime employer.

I think the easiest thing would be for Chief to implement and allow two customizable hot keys. The hotkeys would be dedicated to each option. One for Angles/Corners and the other for horizontal / vertical. I actually use the corner snap with "Reflect About" a lot and would hate to see that go away but, I also have experienced the issue shown in the video.

Thank you so much for the tid-bits.

My window schedule has a custom object field that is linked to a column of the schedule. In the custom object field I have typed the following... %@rouSil[1][4,0,0]% My macro works and does what I intended it to do but, I am having trouble getting the macro to execute automatically for all items in schedule. I have to click on "Open Row Object" and then close out the dialogue box for the macro to execute. Then it will execute for just one window. I have to keep repeating the process of clicking on a line item, clicking on "Open Row Object" and then close out of dialogue a number of times equal to how many windows I have in my schedule. There must be something about how ruby works I am not understanding. How do I trigger the macro to run automatically for every window in the schedule? My knowledge of ruby is limited. Here is my macro... @sill = (owner.bottom_elevation - owner.rough_opening_clearance_gap_bottom).to_f.round(4) @rouSil = [ -> (thickA, thickB, height) {(owner.bottom_elevation - owner.rough_opening_clearance_gap_bottom).to_f.round(4)}, -> (thickA, thickB, height) {( owner.bottom_elevation - owner.rough_opening_clearance_gap_bottom).to_f.round(4) + thickA + thickB + height}, ] puts = @rouSil[1][4,0,0] Schedule Issue.zip

I revised my code (see below) and got it working to a point. It still is creating a seperate line item and runiing the macro for the first instance. I can open up that line item and then close the dialogue box and will force the macro two run. But I have to do that multiple times. Maybe I can get video footage of that. @sill = owner.bottom_elevation - owner.rough_opening_clearance_gap_bottom @rouSil = [ -> (thickA, thickB, height) { ( owner.bottom_elevation - owner.rough_opening_clearance_gap_bottom).to_f.round(4)}, -> (thickA, thickB, height) { ( owner.bottom_elevation - owner.rough_opening_clearance_gap_bottom).to_f.round(4) + thickA + thickB + height}, ] puts = @rouSil[1][4,0,0]

With my limited knowledge of ruby I am running into another issue I can't understand. Let's say I have 6 quantity of windows listed as one line item on a window schedule. Currently, it will run the instance macro and do the math formula calculation for the the first window of the line item but, create a second line item and not perform the macro calculation for the remaining 5 windows. In the end, it theoretically should still result in one line item. The result of the macro is going to be the same for all six windows. Very baffling. @rouSil = [ -> (thickA, thickB, height) {owner.bottom_elevation - owner.rough_opening_clearance_gap_bottom.round(1) + thickA.to_f.round(1) + thickB.to_f.round(1) + height.to_f.round(1)}, -> (thickA, thickB, height) {owner.bottom_elevation - owner.rough_opening_clearance_gap_bottom.round(4) + thickA.to_f.round(4) + thickB.to_f.round(4) + height.to_f.round(4)}, ] All 6 instances of the window are at the same rough sill height. My macro just does a simple math calculation where I can manually type in the concrete thickness and it adds that value to the rough sill distance. It spits out a vertical distance from bottom of grade board to top of rough sill. A value the builders can reference for framing the window openings.. For upper story windows, I manually type in three values. The lower floor concrete thickness, the lower level ceiling height and the upper level floor assembly thickness. It will do the same calculation and spit out a value. I just don't know why its creating another line item when the result of the macro is going to be the same for all six windows listed in the original single line item.

Thank you for this piece of information. I will have to try to remember this for similar future scenarios.

I was almost certain I tried that combination sometime earlier in the day and it wasn't working. Now I can't even remember. Anyways, it seems to want to work. Now tomorrow I will be doing something and it will be messed up again.

Lower wall type if split by butting roof wont generate. This scenarioalways gets to be a royal big PITA. What's the secret sauce to getting "Lower Wall Type If Split by Butting Roof" to actually work? Roof Project.zip

Individual Mod Pools Mod Pool 4.skp Mod Pool 3.skp Mod Pool 2.skp Mod Pool 1.skp

I am up to date on my SSA.

it's probably because I whine about stuff they think is trivial. Just like my idea of being able to copy and paste angular dimensions and reassociate them to things just like we can do for linear dimension strings. Being able to rotate dimension text for angular dimensions. Being able to add to or override dimension text for angular dimensions. Being able to modify material defaults list similar to the room types dialogue. They probably know I would complain about not having 3D angular dimensions. Just Joking!

I didn't know private beta started yet? I asked to join the private beta and never got a response, so I just figured private beta had not started.