Allen43
-
Posts
26 -
Joined
-
Last visited
-
Now that you mention it, I do think I used one of his macros when making this one. But it has been terribly frankensteined into whatever this is. Haha Not yours, but it is based off of your macro. I couldn't find much info on macros in chief so I used yours as one of my only resources for how all of this worked. This is really smart, and I should take the time to implement this in the new macro I am going to have to make. Great idea! I definitely should have done this. Thanks for letting me know! I'll make that change and then when you analyze type later in the code and maybe add a check for yourself: This is a much more concise approach that I will almost definitely implement this time.
-
I recently updated to X15 and after doing so I have had a few problems. The last one I have to fix is my macro for auto cabinet label generation. I am by no means a programmer and I barely understood ruby when I made this macro. I have been trying to relearn but I still can't figure out what my problem is. I have attached my macro below and this is the error I have been getting: Evaluation Error: Ruby TypeError: no implicit conversion of nil into String Stack Trace: from eval:10:in `eval' from eval:10:in `block (2 levels) in <main>' from eval:4:in `loop' from eval:4:in `block in <main>' Any help is apricated. Thanks in advance! CabinetAutoLabel2.json
-
Okay, I've double checked the system requirements and am still stumped. I'll reach out to support next. Thank you all for your help!
-
I'll read the documentation for X15, but I can't imagine that they would deprecate older cards. They should just run slower, I would think.
-
Yes I am still having the same issue. I also tried everything that you mentioned here and it is still persisting. Also, I should mention I am on a different machine currently, and a far worse one at that. So, I am rocking a RX550 instead of the 1660, meaning no nvidia control panel to set chief to use graphics card in.
-
Hmmmm. Strange. Maybe it is a driver problem with my GPU? Or some other client side problem that is not related to the .plan file.
-
My bad. Here it is. 2023.6.13 Cranmer.plan
-
I recently updated to x15 Premier and have loved the new features. However, I just ran into a problem. The camera tool is kind of busted. Standard view only renders the glass in the windows and light sources. Physically Based is a grey screen. Clay is also a grey screen. And finally, Duotone only renders the glass and light sources again. Is this a problem that other people have ran into? Any suggestions and help are appreciated as I use the camera view a lot in my design process. I have attached to images that show the two main problems.
-
Thanks, I'll have to do that.
-
Thanks, I would love if there was another sizing option in the object specifications page. Either a toggle to include casing in width or a separate number field. But for now taking a dimension of the window including casing will do.
-
I have been trying to find a way to size windows based on the overall window size including the interior/exterior molding. I am mostly sure this isn't possible but last time I thought that someone here showed me a way to do exactly what I wanted. Thanks in advance.
-
Ok, I was kind of afraid of that. I was hoping chief would be smart enough to look past users and use relative paths, because other than the users having different names, all of the items are in the same path. Thanks for your quick response though.
-
I have been working on customizing my toolbar with custom objects from my library to help speed up my design process. However, I work on both my desktop and laptop. And when I tried to move the newly made custom toolbar from one computer to the other every "Place Library Object" tool was reset, and I will have to reassign them all again. When transferring the the toolbar I copied not only the .toolbar file but everything in the Toolbars route file. This is what I see after importing the toolbar. I am sure there is a simple reason that this is happening as always when I run into problems.
-
Thank you both! I ended up using this last week and it worked perfectly. Now I am having different problems with toolbars, but I will make a new thread for that.
-
Perfect! Thank you both! I guess this was a good old case of using the wrong term when searching for a solution, but this is exactly what I was looking for.
