Michael_Gia

Don’t use auto-dormers. It’s mainly; - hole in roof - place walls - use the “lower wall type if split by butting roof” in the roof tab of the wall dbx. - use the “ballon through ceiling above” in the structure tab of the wall dbx. - manually draw your roof planes.

Way back when I wanted to switch to Archicad, I had reached out to an architect Archicad user and asked him if I could come to his office and watch him put together construction documents form concept, to 3d model to, floor plans and finally to a full set of construction documents on a small enough project that would take less than 1 day to complete. He agreed, I spent the day with him and saw the whole process from start to finish. I learned that I should stick with Chief but that's beside the point. I would suggest you try and do the same with a local Chiefer in your neck of the woods.

Oh god, I noticed that but I thought that it was just something that occurred because the original view was not sent as Plot Lines. Don't tell me this is a thing?...

OK! I changed all elevations to Plot Lines Color Fill = 30 seconds total to print to PDF Then chose Plot Lines Color fill for all 3D Camera Views (as well as all elevations) = 10 seconds total to print to PDF If I delete all my 3D Camera views = 3 seconds or less to print to PDF TL:DR PC and Mac both print to PDF in under 3 seconds unless you start adding live link standard render views to your layout. I guess a good tradeoff is to keep the live 3D views but at least make sure your elevations and cross sections should be Plot Lines (30 seconds to print vs over a minute)

The 3D views are just Standard Render mode which are updated on the Layout on demand, is what I meant to say. The reason is simply so that they reflect the latest change in the plan. That is I don't have to constantly take screenshots and replacing 3D images on the Layout. I guess I will try to print to pdf without all those Camera Views and see what happens. Thanks a million for the feedback.

I can confirm that the Bachelor View Layout takes around 3 seconds to print to PDF on my Mac. Haven't tried it on the PC but I'm sure it will be similar. Therefore there is definitely something gravely wrong with what I'm doing in my layout files to take so long to print. and I've had this issue since X14. I'm doing something wrong. I did notice that in the Bachelor View Layout, every 3D image is a png, every elevation is "Plot Lines" and the rest is Cad Details, Text boxes or Saved Plan Views. In my Layouts, every 3D image is a Full Cavera Live View, and every elevation is a Live View and not Plot Lines. plus of course, the usual text and cad details. So, are my Live Views causing the delay in pdf printing? Or my Live elevation views?

No pdf's. I usually convert to png by way of screen shot of pdf as @Joe_Carrick mentioned. I'm anxious to test out the Bachelor View layout to compare.

I will test that out and post the results. thanks for the comparison.

Yes I compared the same plan. I use 144 dpi which is not too high. 68 seconds vs 138 seconds.

Hey all. I’ve been praising my new switch to Windows 11 from macOS with respect to PBR but printing a set of plans to PDF is excruciatingly slow on a pc compared to a Mac. The Mac is at least twice as fast. is there some trick to this? I have used both the Chief pdf print option and the windows pdf option. Am I missing something?

For anyone seeing this in the future who is still contemplating pc vs macOS… The RTX4060 (considered modest) vs the 2023 MacBook Pro with the M3 Pro chip, 36G of ram, here is the result. PBR exterior render 100 samples: RTX = less than 3 seconds. M3 Pro = 110 seconds. At 50 samples I can actually move around in realtime on the PC. 50 Samples gives a very good final image in my opinion. I was led to believe that realtime PBR navigation was not possible on any 4060. The reason for this is that the pc community has a very high bar in what they consider performance.

I guess I got a good price then.

I went ahead and ordered the Legion 5i. The bestbuy dude said that if the price goes down within 30 days or so I’ll get the discount as well. When I get it I will post a M3 MacBook vs a modest RTX4060 machine PBR render time comparison. Should be amusing. If it’s not I will return the piece of crap. kidding

I will be picking one of these up. chief seems to like Lenovo. Any objections? For the same money, that is? That’s CAD $2000 = $1430 USD

1) watch the video posted by Gawdzira - rendering in Chief is basically photography 101 2) your materials on the building are not high enough quality. 3) Your main image is about selling the design. You don’t have to include every square inch of the facade, that’s what the plans and elevations are for. Try to follow a perspective like the attached image… (maybe not relevant to the post, but your building violates every fire code in the book)

I'll raise ya, 2500 years...

Trust me, you still don’t, unless you watch this….

Holy cow! Thanks for the detailed construction documents! I will start construction as soon as I use them to apply for permits (kidding) I doubt this was your intention. I would delete it asap and reload an image of your problem and maybe a plan file.

Thanks for saying that. I just checked and the plan was indeed saved with the most recent changes despite the error message. I restarted and it seems to work so far. I did have to deactivate and reactivate the product key.

Hey, anyone else getting this? I keep getting this error even after I verify, make available, and whatever else to my product key.

I had this at first. I lowered the sunlight to 7000 from the 70,000 I used to have it at before X16. I also use a less bright background now as well.

Don’t use roads unless the road you want is real simple. Instead use terrain features or 3D solids or counters or slabs. Create those 3D object by first drawing out the perimeter of your road. Then make a copy of those lines so you can use them later to create 3D mouldings which will be your curbs, (Before!) you create the road. Later if plans change and you need to adjust roads and curbs you can always convert them back to lines, readjust and reconvert to curbs and roads.

I'm no expert but I was looking at this recently. For the money I think you'll have great realtime raytrace results, which is the litmus test on how well any machine does. https://www.xidax.com/ready-to-roll-gaming-pcs/14830-x-2-rtx-4060-vf-0792105640600.html

I just go to their YouTube channel. You can see the video list by date uploaded and narrow in on specific playlists.

Haze is almost always caused by using way too bright sunlight. Use PBR and set samples to 50 until you get the result you're looking for. (it's quicker) Here are my PBR settings... This is a screen shot of the result. Took a little less than a minute for the PBR to go through 50 samples. (pretty sad, but that's a Mac for ya)