TrimbachDesign

Hey Shane, that's a good idea. Always a work around!

Hello Chief Users, I haven't found a solution to this either here or searching the internet and am curious if any of you have bumped into this. I had an Architect friend of mine redline a set of our drawings for me, reviewing best practices and standards with how our drawings looked. One item that he commented on was not having a little tag end, or tail, to the dimension lines. He said that is a big deviation from standard. Two screenshots are below. One of how are dimension lines look with the "arrow" and one screenshot of his redline (poor quality, scan of a print). I can't find a setting to make his request happen. In looking at other plan sets from Revit users more carefully now, I see the extended dimension line more often than not. Thanks for the help! Austin

Thanks for the feedback!

Apologize if this has been covered in-depth (I couldn't find anything when searching). Is it currently view as best practice to build all new templates in x13? I have a project that I recently finished that began in 12, went through the 13 migration, dealt with a lot of issues (RTX3080 win 11 issues) but now it is pretty stable (in x13). I'd like to use this as a starting point for a new project (in x13). I feel like I read somewhere that when new versions come out, we should be starting fresh and rebuilding all new templates. This seems like a pile of work, and I am hopeful that this isn't the case. What's the current thinking on this? Thanks! Austin

Haven't had any crashes since the latest driver. There were days before the driver update that CA was not workable. Nothing else was changed besides driver, same plan and same layout file.

Good point with 3d views (even if they are cross sections)... I should have understood that before. I'll give the HF a shot, thanks for the link above. I didn't realize this came out after the most recent game-ready driver.

Are those of you that said you are having success with the new driver still feeling that way? I updated my driver to the 511.65 game-ready that rolled out on Feb 2, and initially was thinking all my problems had been solved. The last two days...not so much. Dozens of crashes per day. Right now I get to work on a drawing for about 5 minutes before it again crashes. I'm working through final cabinet drawings on a plan set, and that has me bouncing between layout and plan. Our cabinet sets include a lot of heavily-notated wall elevations and we prefer standard mode (to vector) with lines turned on (so grain direction is clear to the cabinet shop/clients). Of course with standard mode we are sending our plan elevations to layout in "live view". About every other time we jump into layout an internal rendering error occurs or the program gets hung up and requires a force quite. I know I'm asking a lot of the hardware/software but this sort of thing is exactly why we spent a lot of money on a built-up machine. None of my most recent crashes have anything to do with a Camera, full or otherwise. Love to hear latest thoughts...I'm happy to flip to Windows 10, but it just sounds like CA and Nvidia are right on the cusp of solving the issue, and if that's the case I'd prefer not to take more time away from our projects to install 10, then eventually switch back to 11. But right now, this is not functional.

I love the multiple copy tool for placing lights. Such a time saver. I do the math, figure out what spacing I want, set my interval (general object) to that spacing and drag/copy/paste away. I'll do a run like that, then select all and multiple copy a group selection to start to grid out a room of recessed. Then maybe I'll select all and slide them around until I'm satisfied (with my framing layer on) as a unit.

Good evening everyone, I've been cruising along on x13 for awhile now and finally have seemed to achieved some stability with the win11, rtx30 series, x13 issues with the latest driver update...super happy about that! But now I am experiencing this random annoyance. I haven't seen this one before in x13 or prior versions, and have changed nothing on my computer besides the driver update last night. Anyone figured out a solution? I have searched here (and google) and came up with one idea to pull the archive folder of my internal SSD and stick it on dropbox. This didn't change anything for me unfortunately. The forum post I found with this info is below. My CAx13 is installed on my SSD and I have a folder hierarchy on DB for all my project files. This setup has worked flawlessly for a couple years until this afternoon. I'm hoping someone has solved this mystery and can point me in the right direction. Thanks! Austin

Thanks for the update. Happy to hear Nvidia is diving into it too!

Kait, I had the same thing. It was almost repeatable for a while. Working on modifying a cabinet (in the cabinet specification viewer using Standard view) seemed to throw the problem almost every time.

Hey KBird, that's totally what I was doing and couldn't understand why the terrain wasn't building a smooth slope... the underlying problem (above^) was the culprit. I can't believe I forgot that I had the engineer's contour layer data hidden. Appreciate your reply! Austin

This comment helped jog my memory of the underlying terrain information that I had hidden in the plan... Such a simple fix. The contours that came in from our surveyor were hidden and I completely forgot about them. Turning that layer back on allowed me to manipulate (delete) these existing contours that were in the way to allow CA to build a reasonable slope through this area. Thanks for the help ChopSaw!

For me the problem seems to be frequent when I'm in a camera in Standard mode...I don't think it has ever occurred in PB ray trace mode... I'm wondering if the real time ray tracing is talking directly from Chief Architect to GPU and skipping Windows 11 in the middle. Whereas Standard mode is being run through the OS?

Any updates on a fix yet Dermot? The problem seems to be happening more frequently, dozens of times per day. Should we go back to Windows 10? If you guys are getting close on a fix, I'd rather keep my machine on 11.