SHCanada2

Members
  • Posts

    1490
  • Joined

  • Last visited

Reputation

224 Excellent

1 Follower

Recent Profile Visitors

4105 profile views
  1. above previous thread has some statistics also depends on X16 vs X15( or earlier) for number of samples
  2. is this on a laptop? If so, the laptop will typically constrain the GPU when on battery. What version of CA are you using?
  3. its 5 clicks to get something decent for interior , background intensity, sunlight intensity, exposure, brightness....and make sure to add some lights
  4. also what I do(create on lowest level I am working with). It becomes a bit of a PIA when doing houses on sloped terrain, as the garage is typically on a different level, as are main floor cantilevers. This is where the reference display should be used (or create polylines and duplicate to different floors....I've done it, and don't recommend it). If you do not do either, you can be stuck guessing where to draw the driveway to (because you cannot see the garage on the foundation level)
  5. I did an interesting test yesterday. I measured, I also received the realtor floor plan (which is iguide, which is a lidar scanner/photogrammetry setup in each room. I think realtors pay 3rd parties about $400 for a full house scan using this hardware and software), and cubicasa on my phone (which is a photogrammetry app and cost $10). This is a basement which was interesting because although the exterior concrete wall is not jagged, the interior wood walls next to them differed from nothing by the stairs to 2x4 on flat on the south wall, to 2x4 everywhere else. Plus, there was a supporting 2x6 wall which runs down the middle. Neither of them caught the 2x6 wall down the middle as being 2x6. But the iguids caught the difference in wall width in the bottom, left, and by the stairs. cubicasa also has an incorrect width for the laundry room. Both iguide and cubicasa mistook a light fixture above the toilet for a window. Neither of them tell you about the bulkheads (which I drew in the CA plan) so, for $10 its good if you do not need the accuracy (the use case for me is, customers are doing a basement reno and the city also needs a main floor plan "for their records" and as such does not need to be perfect). For iguide at $400, its better, but because it does not have varying wall widths, it does not calculate the gross floor area correctly (which here is to outside walls). Ironically cubicasa has the more accurate GFA in this case. I'm still on the lookout for an app in which you can actually get the 3d model, in order to double check dimensions, and see anomalies before they (the purveyors of these softwares) create a floor plan...assuming they give you the unadjusted model.
  6. there are tow different types of ray tracing. CPU, and Realtime. open up a floor camera, edit it's settings and change to "physically pabsed
  7. this would be a typical backyard garage suite here. I draw garage on floor 1 and specify stem wall depth. I draw living area on floor 2. I draw terrain on floor 1 I create a site plan that shows roads, sidewalks outside walls etc. and then use a reference plan if I have to show something on a different level
  8. integrate with slices https://math.libretexts.org/Courses/Monroe_Community_College/MTH_211_Calculus_II/Chapter_6%3A_Applications_of_Integration/6.2%3A_Determining_Volumes_by_Slicing ...jk might also be able to put a psolid across the entire terrain and then set its top to be the top of the terrain, with a thickness of whatever will be enough for your cuts. and then model your terrain with the cuts, and then make another psolid, and then use the psolid tools to subtract (might have to cut the bottom to be horizontal). Havent tried it, but might be worth a shot. I'm doing a very sloped lot right now and might try it in the next couple days. I have the undisturbed, current conditions terrain in another .plan file
  9. At some point the O/S or other drivers will no longer work with software. Software companies have to then adapt and test their software with the next O/S/card drivers in perpetuity. In my view, non subscription software has a niche, and that is where something is built that needs no improvements, only future O/S support. The PDF editor I have is in this category. All I need to do is edit the occasional text in a PDF. Do I need to pay adobe $311/yr for that? No, so I will pay a one time fee to others(currently around $75), and when I need to upgrade to the the O/S that breaks it, I will pay another $75. So my annual cost is $15/yr or 5% the cost of Acrobat. A lot of these companies that have these types on non subscription software have multiple pieces of software. So what they do, is have them in "maintenance" mode, where they will make enough money selling a few here and there, and then get a bump when the O/S no longer supports it, or some standard changes, and they make some money off paid support and ads on their websites. But CA is not a simple product, and as far as I can see is in a fast moving market. This means they need to add features every year to keep up with the competition plus all the backlog of requests. And because of the complexity they need a support organization behind it. Perpetual models also work for companies that have a large market to go after, but even they need to plan for what happens once that market saturates. Perhaps that is the way it was when CA started, but is no longer the case
  10. yes, that is more real life, I understood it to be a 3D solid, which is why I commented probably the better option. I dont need a footing, but that is interesting. Did you just pull down the footing (if so I suppose the footing could be set to the same width). Ultimately what I was trying to do was while I was adjusting the terrain, the wall would come along with it, but keep the bottom (below the terrain flat). Ironically in the end for this project, the terrain region was almost flat, so a 3D solid with a terrain break would have worked just fine. But it did get me thinking for the next one how could I do it dynamically. For this one I just put in a CAD box masking the ugly below the terrain terrain retaining wall, and for the moment, have yet to step the bottom. But I had to send it off Thursday so it went like that.. (...the workaround 3rd option..which is not my preference going forward)
  11. It looks when I made the, change to the bottom, only the bottom check box deselects. The top remains checked. If I move the terrain down say 20", the top still moves with the terrain but the bottom does not. see below But is there a better option? A solid would needs its top changed to match the terrain, and in thinking about it maybe that is better as one could step the solid like a real wall, and if the terrrain moved up and down as a whole, the solid would move with it, maintaining the bottom of the wall. ...per usual... a couple options...each with their benefits and drawbacks
  12. also interesting OOTB has footing...good to know
  13. actually if one uses the red handle to move to the right, it can be done in 3 moves