Renerabbitt

Not really sure what the benefit would be for having multiple design options in one plan. Have your iterations up on tabs. Ctrl+tab, boom, there's your next design iteration. Want to copy an element over from one to the other, easy. Far more efficient to have design iterations in individual plan files. No special layering or work-arounds needed. Easier to transition to design development, no need to delete anything. Best part of separating design iterations=organization. Iterations are clearly labelled and presented with separate naming conventions. No possible mix-up on which one you are presenting. Have a client that is renting the software and you're okay sharing your work...easier still. Have a draftsperson that you collaborate with..easier still.

@ChiefUserBigRob Have you disabled all AMD radeon overlays, this is a gfx issue, not CPU based. I bet turning off all radeon overlays solves your issues

I use ANSI D specifically so that I can print half scale at 11x17 with my preferences intact

I personally would build a computer and emulate mac if I wanted a Mac for this very reason, too many hardware limitations. An egpu will likely have some bottleneck issues depending on which Mac you have. Nowadays my 107gtx egpu is actually hard wired into my x16 lanes on my desktop. Itll get replaced soon if I can ever get my hands on some new cards.

I've done several searches and can't remember this basic set of characters to create a line break. (also forgot all of the correct terminology for even making this request)Help please! I thought it was "\n" Next q is can I add a macro in label : %(rough_opening_side*2)+width% x % rough_opening_bottom+rough_opening_top+height% RO %automatic_label% such that there is a line break between the RO and the auto label without needing a custom macro?

That image was more for the purpose of showing how chief is handling refraction. That was a live image that had refraction toggled halfway through processing and then screen clipped before it could process the refraction toggle. Kbird1 answered your original question, the 3080 doesn't change anything in terms of refraction and mirror reflections. To note, I didn't down sample your main tile image, I cropped it. Same fidelity with less variation. I often do this on small surface area materials in a low FOV condition where variation is imperceptible. With no caching, baking, or proxies, chief sucks at high res.

This is taken a bit out of context and I should have been more clear. "The nature of the beast"... of a software that is implementing more than 5 different rendering methods for singular geometry and material/lighting set in a scene. The reason glass doesn't work as you would hope is because glass must still work as intended in a cpu ray-trace as well. We are now trying to get the same results from an unbiased and a biased rendering engine(though I would still argue that Chiefs CPU raytrace is still biased) and then comparing it to a dedicated biased rendering software(of which chief is often at the same price point). This means you can't write it into code the same way a typical physically based rt dedicated rendering software can. Many of those softwares aren't including a true IOR either. Refraction is a big issue that I imagine will take another year to address. I know that most users probably missed it but if you go into the material properties of a glass material what do you see on the preview geometry? The IOR is WAYYYYY too strong(I happen to know the size of the preview objects and they are small enough not to be refracting 4' off center)and also, the flooring at the sidewall is reflected, meaning we dont have a second opposing bounce that is the nature of refraction. This indicates a very clear problem to me. Most architectural fixtures that have glass in OOTB Chief are double pane. Its an extremely complex bit of code to get IOR, Attenuation, antialiasing, caustics and a slew of other even more complex problems inherent in a glass material. The IOR then was built specific to double pane glass, and also, the ior is simply a singular bounce in one direction only. Try putting a single face with a glass material and put it next to your shower glass. Now put a second pane in and see what happens(the refraction effect is compounded in the direction of the refraction instead of attenuating. (not true IOR) Side note-textures are super heavy at 2K and unnecessary for the scene. this scene was rendered with these material replacements: Tagging @MarkMc and @Kbird1 *220505 Deleted Attachments to free up space*

Nice work!

Just to note this is a generic response , not subjective to you. Hoping more people find this. Regarding the quote, I guess therein lie the difference, I don't see these as workarounds at all. The nature of this type of raytrace, which I try to explain in that post, will always have techniques that need be implemented. There is simply no way you can have a scene that will look as intended in both standard and raytrace views, its an impossibility due to the nature of the rendering engine. All of these same theories in realtime raytrace have been around for quite sometime. The Thea render manual for version 1.5 dating back like 7 years I think, goes through all of the reasons that an under-sampled, under or overexposed lighting condition will cause such a problem. I've done support on quite a few scenes now and haven't run into anything that couldn't be fixed with a few tweaks and settings. We have a new tool that can garner fantastic results with a skilled technician. This requires a skillset and a level of understanding that far surpass that needed for standard PBR. . I didn't need to play around for very long to work through similar issues because I have a wealth of understanding in such techniques. Speaking from my experience, this is simply the nature of the beast. I'm sure Chief has an overwhelming number of support calls while people try and figure rt out. The greatest takeaway from this, is that our community is learning the skills to sufficiently use such a rendering engine which can carry over in them being able to pick up other such rendering software's as we get closer to the industry standard. Just wait til we get a denoiser and selection based image sampler amongst 100's more complex rendering techniques and features.

@Kbird1 and @kwhitt Suggest you both read this: Simple solution, change your Shower Glass to a General Material classification. Kbird, the under sampled(aliased) areas of an under-lit room will always occur with an RT type rendering engine for the multiple reasons I list in that thread. There are plenty of simple solutions to that.

You tagged me Scott but I think you meant to quote the OP. X-12 you could include a fixture in a schedule yes. What the OP is referring to is that in X-12, when a sink is inserted into cabinet, we lose the Object Information Panel in the symbols dbx. In X-13 you can access the symbols Object Info after it is inserted into cabinet. Bravo

FYI it does in X-13, upgrade!

Even that will get it to crash. Basically when you do any action outside of file browsing, and forgive me I do not know the proper terminology, but Explorer basically turns into a program executable. So any administrative type action in Explorer will crash Chief if navigating from Chiefs menus.

@Alaskan_Sonand @DMDesignsI've complained about this issue since X-10, only happens on my desktop. Some combination of clearing software cache using a 3rd party software fixes it, but it will return with every update,

Agreed that this should be fixed. There are a few workarounds but this is my favorite: Rabs Auto Label.calibz Snap the top of the bounding box to the bottom of your view, then unblock the tool. It will set an Auto label using reference macros.

I am not using matterport. I am a big fan of open source software with full publishing rights. I use dot3d which is compatible with the l515 camera. I take measurements from the scan in the same way that I would if I were on site. The great part about it is that once trained, an apprentice scantech can scan the site for me with the L515 and an android phone or tablet. Takes them maybe 2 hours to scan and get roof pitch, and setbacks/street width. Biggest problem with canvas is it is stationary, single-station spherical scans. Meaning you will be missing details if the person scanning doesn't recognize the need for proper positioning in the room. Juxtapose to the L515 and Dot3d where the scan is working actively as I walk through a home from any angle or position with some minor limitations. You have to use targets placed on the wall for this.(sounds like a hassle but is quite simple really) My takeaway is very similar to my approach to design. Figure out which tools will offer the most equitable results. I use sketchup for modeling objects I need, not Chief. I use my canvas app for shoebox houses, I use the L515 when Ive got a detailed or high-end home.

I personally prefer the L515 and Dot3d software to matterport. You can still use canvas and measure from the scan. Important to note that when scanning you want line of sight on the faces of all parallel planes. This makes dimension a breeze in canvas as it has an automated parallel plane measurement tool. Everything else is point-to-point and a bit sloppy. Considering I put in standard window sizes in my AB files, this isn't a bother to me. I take extra time getting accurate control measurements in the location of work to be performed.

I have used it and will use it again when I don't have access to my intel LiDar rig. I take a Scan-Tech with me to perform the scanning while I take control measurements of the room as well as street measurements. The scan to CAD service is useless. Hack-job drafter, get what you pay for. I've spent more time fixing Scan-to-CAD sets than I would've drafting it myself from the start. Accuracy is a problem with considering. With my L515, accuracy isn't an issue, but it takes longer in the field.(this will change over time) The rep Ben has an active search for all things that mention Canvas, no doubt he will see this response. I understand that market value of the Scan-to-CAD service, and would suggest the service not try and recreate unique architectural features as more often than not the drafter being used is using sub-standard work-arounds. i.e. using p-solids for stair landings and moldings and not snapping edge to edge or point to point.

X-13 RTRT, A breakdown from another forum in response to growing frustrations with RTRT. (Items that are specific and searchable terms in CA have capitalized first letters) There is nothing "wrong" with the new Astral PBR RTRT option. Better understanding of a modern rendering engine may help alleviate some issues. If you are feeling overwhelmed by this info you can always uncheck the option for the RTRT in your Rendering Techniques Tool. Feel free to contact me for support or advanced training. • In RTRT a low sample rate is used in live camera views. • For exported presentations images similar to a CPU-based RT, set your Maximum Export Samples as low as needed to eliminate fireflies and light leaks. The higher the sample rate in RTRT Rendering Techniques, the better the image(up to a point where benefits are negligible). This only applies to the Export Image Tool. • A sample rate in basic terms is the number of samples from a camera of a given Objects Material ID as it applies to the geometry of an object, including colors, lighting, shadows etc. The more times something is sampled the less aliasing there exists in a final image. • The more light exists in the scene the easier it is to Sample. • You must supply ample light in adjacent rooms for the RTRT engine to properly process and "trace" your scene. Devoid of light, your exterior will be overly exposed, your interior may be underexposed, and you may have fireflies or light leaks. • Ensure that your active Light Set is on and illuminating your scene, which is accessed a number of ways, one being the Edit Active View tool, in the Camera Panel, under the Lighting Section. • With ample lights, an interior scene Rendering Technique Options might have an exposure from .15-.35, a Maximum Sample Rate of 500-1500, a Brightness between -10 to 0, a Backdrop intensity between 100-1000. This is not and never will be a universal setting, each scene needs adjustment according to the amount of light available to that scene. • If your scene is underexposed you may need to adjust your lighting including the lumens of your light fixtures. • Sun settings will do very little to help overexposure, underexposure, light leaks or any other trace related problems. This is the nature of a tracing engine. • Live view will always be of lesser quality than an exported image using the Export Tool(because of the option to change the sample rate.) • Typical problem causing issues: Caustics, Lights near transparent or translucent surfaces, lights of high Lumen values in one room juxtapose to lights of low lumens in an adjacent room. High resolution bump/roughness/normals maps in materials. These issues all cause difficult scenarios for attenuation and aliasing. Some of the fixtures being used are not optimized for this new engine. Consider changing the material properties of any glass that is in close proximity to a light source. Changing the glass material of a light fixture that is turned on in a RTRT camera from Transparent class to General Material with high Transparency can yield much more predictable results. Same goes for situations when inside cabinet lights do not show up in RTRT behind Transparent Class windowed cabinet doors. There is a lot more to this, you can have some success with this info, but barely scratches the surface. For some incredibly good generalized rendering info, read the Thea Render Manual(free online) It has some fantastic info in it that applies to all rendering engines. The following images are a RTRT with zero lights(screen clipped), an RTRT with lots of lights and same settings(screen clipped), and an RTRT export of the same scene The last image has the backdrop turned up since the sun direction is not illuminating the backdrop. Backdrop setting of 1000.

Typical walls

This is a graphics card driver issue most likely. Many similar posts with similar issues over the years.

Just had the same problem present itself in an X-13 plan. Had to pull the thick wall back and reconnect any time that the adjacent walls were modified in any way.

Re-download...I uploaded new versions to the previous post.