SHCanada2

Looks very nice, if you can get 64GB ram for a couple hundred dollars or less, I'd add that if you use MS edge. I use MS edge and it is a memory hog. I'm with Jonathan on the HD storage, go for speed over quantity.

exactly. For instance I get a survey on the email from the customer, I download it to \documents\CA\customer - addresss\ I then import that into my plan because I superimpose my building on it. But videos, pictures, old plans, other docs, I download to the above but dont import into CA's "project". Then when I print(save as PDF) my layout, I save to the above directory, and then when I email, I just drag and drop from that directory to my email. The PM mode is great for keeping all the versions of layouts, and plan files right there in the side pane project browser

I think many of us concluded that the most efficient way to use the new PM mode is to have a hard drive directory structure like we did before. For a couple reasons. 1. If you need to email these layout exported PDFs, then you need to attach them to the email. If they went directly into PM, then you would need to export from PM mode to "somewhere" and then attach it to your email. So more steps, 2. other documents or information which are relevant to the project, but not really relevant to the drawings need to go somewhere. Sometimes I get photos video, etc sent to me. I need some place to store them, so might as well be the hard drive directory structure like I had before X17

i dont use auto build foundation as it then deletes everything in the basement, and I adjust stemwalls frequently to match the basement foundation height Adding +24 to stemwall in floor 0 defaults works on my template plan(which has a basement):. so not sure what the issue is, unfortunately, maybe post the plan. My guess it has something to do with the "no change" that shows for the ceiling (multiple rooms with different heights as John indicated)

that sounds efficient. I find the eater of time is finding the right furniture, colors, carpet

you could try opening up the PDF in another viewer, such as MS edge to see if it actually a PDF problem or an adobe problem

my experience as well

search for "All words" macro feet inches I've seen a few posts on it. I think I saw one by AlaskanSon, so you could also try search by user

couple options 1. draw it on level 0...depending on what it is. Is it a terrain object, or a foundation/wing wall? 2. create a reference plan view for level 0 where the reference plan is level 1 and create a separate layerset with just the layer that the retaining wall is on. CA has a good video on how to do this. I would also suggest saving as a separate saved plan view to avoid confusion. I have to do 2 on occasion to have things that are on level 0 (where I have my terrain) show on level 1. If your retaining wall is the type for terrain, you would have to do 2. or move your terrain to level 0. There is a forum post a few years back on why terrain on level 0 is a good option for those of us that do basements if I am lazy I will just copy ->paste hold position for some things (CAD objects) to show on both levels

merci, worked perfectly

thats what I had done, above it is greyed out in the layout menu

The jurisdiction requires the North arrow to point up on a page. When I rotate the layout to make it be up, the N rotates, or more accurately doesn't rotate. Is there a way to not have it rotate aside from creating my own north arrow?

thats what I suggested in the first post I made on this topic. a special class of text macro to show up in the client form. Then you could create as many as you'd like

That's what I do for detail parameters, but after I saw Rene's point and click system for details, I did realize his is a lot nicer (no typing, and not looking at a long list of macros in the TMM), which is why I thought if we could actually write to the text based macros, with a macro, then it is one and done. But I did forget about the import function. For those that store data outside in files, good question, why not just import directly into the text macro...formatting maybe?

it made it better in some respects, but also not what was intended, as the light comes in thru the blinds and creates a shadow in Rob's, but not the AI. I find CA's light is too "green" (my guess is because of the terrain and sun intensity) , and it does require some fiddling to get rid of the green. I can see the AI advantage that one does not have to presumably do the fiddling

someone said he was over at the home designer forum. His posts here seem to be no longer, as I see posts where he made a post, but they are no longer there. so I'm guessing @solver does not work

This is where I think these things are not really AI, or the I is severely lacking. If almost every human on the planet can spot the driveway problem but it cannot, all it is really doing is pattern matching, and then replacing. Although one has to wonder how it "decides" to add a new window

might want to post the plan.

I would also suggest a rectangular region, for every driveway out there...at least out here

@Renerabbitt thats what I do as well to populate some globals. And then I do not have "do" anything per se, prior to printing. But in the other video you have above, I think you show going somewhere else, and then indicating people have to click it prior to printing. Why do they have to click before printing? I had assumed you needed to populate the globals on that page, but maybe it is just to be sure the globals are for that specific layout/plan, and not another which may be open? .

if you open up X17 and then open a .layout or .plan file, don't you have to go run that macro to read in the CSV, in order to see all the into on the plan/layout, irrespective of printing? I can see the global variable use case for having the option for both layout and plan, you only have to run it once...its just that, I assume, you have to run it every time you open the plan or layout file if you want to see the info. Where if we could write to text macros it only ever need to have to run twice(once for the plan and once for the layout if one needed it on both) . It would not ever have to run it again when I open files, or print...because it would now be stored in the .plan and/or .layout file in the contents of text macros. Me thinks I am not being very convincing.

i do not have that issue. my C drive is at 340 GB which includes files from X14/15/16/17. Although I did not move files from those versions into X17. I have 1842 .plan files

I was suggesting CA give us the ability to write to text(non evaluated) macros instead of global variables when you import data from reading a file. That way the information is stored in the CA file, and the import only has to run once or however often you want to bring in the info, vs writing them into global variables which means, I assume, they constantly have to read from the file and put them into globals. Rene, if you reopen that plan, do you have to go into the project information everytime? I assume so by the text you have: just imagine if you could write to the CA text macro instead of the global variable, you would not have to do that constantly. it would be one and done. I was suggesting this also as a way to populate that form instead of putting a bunch of GUI functions in the form. For example if you wanted a 2 level hierarchy, then give us a category of macro called "user data form", and allow a level structure to be specified, say /client information/address. and then create another text macro with /client information/name etc. and then when you close that form CA just writes to those macros contents.

and please help us all out and put in another suggestion in the suggestion box for a sloping terrain region feature...to avoid all this

or it they just let us add them through the TMM as a category of text macro, then all of the management could just be done there. And the ones of that category would show up on that form. And if they let us write to text macros, then joe could just read his text file and write to the text macro contents And if we were given a function to write to the contents of a text macro, then detail configurators (like the one you have?) could also be persistent, and the values chosen saved with the file's text macros, and be available instead of having to go to CAD details each time the file is open or where ever the configurator is located. And we could then have the global variables written to text macros, essentially storing results of calculations, without having to constantly go to the sheet that has the calculation. It's not world peace and doesnt make me breakfast, but it would certainly avoid the %xxx% that show up on my layout because I didn't go through all the plan views, triggering the calculations and solve the "need more custom fields" at the same time