kylejmarsh

Members
  • Posts

    281
  • Joined

  • Last visited

Reputation

32 Excellent

Contact Methods

  • Website URL
    www.kjmdesignstudio.com

Profile Information

  • Gender
    Male
  • Location
    Michigan
  • Interests
    Residential Architecture, Traditional Neighborhood Design, New Urbanism, Town Planning

Recent Profile Visitors

2777 profile views
  1. Here in Michigan you can meet your compliance one of two ways: Prescriptive, or Performance. With the Performance method you have to calculate all surfaces with glass, R-value, etc. just like they do in California. But with Prescriptive you just have to make sure your assemblies meet code insulation values R-21 walls R-38 Roof etc. and windows need to meet a specific U factor - but there's no limit to how much glazing you can have as long as it meets the U-factor. Too bad we don't have any killer mountain views! Guess we have these pretty lakes though
  2. 100% I have been spoiled by TM it's amazing software - For modeling Chief all the way but for rendering I just can't afford to use anything else but TM now it's that good.
  3. Mark I'm sorry to hear about it. I personally have had a great experience with X13 on my mac mini - it runs much smoother than x12 not just in camera views but even floor plan views and layout sheets as well. However check my setup below - I'm running an 8GB Radeon RX 580 which was supposed to be pretty good/stable when I got it. It didn't do anything for X12 because it didn't use the GPU at all. But X13 seems to make pretty good utilization of the graphics card I can fire up the monitor and see it's working pretty hard. I have noticed occasional crashes and I'd say maybe every other day or so. Hoping this new update will have some effect. Anyway I do really like the exterior gpu running over thunberbolt (lightning? whatever the new cord is) except when I kick the cord by accident and it crashes. But the Mini + graphics card seemed the best way to do a cheap 'custom' mac without having to get the imac or the really expensive mac pro. Plus I can get other egpus or exterior hard drives and with the new cord it's like having them plugged right into the board on a tower. My 2¢
  4. Just realized why I missed it - it was also assigned to another hotkey for end to end dimensions. Since that is a plan-only tool, and the perspective crop is a 3d only tool, it had both of them in there under the P. That's why I never caught it.
  5. You genius! Absolute madman. How did I not see that it was a hotkey?! Not only that but I'm on Dvorak layout so my P is located where your R key is so i'm always using literally every other key in that area. Wow. Thank you so much. Nailed it. Kyle
  6. I've noticed this for a while - my exterior camera get's messed up at a certain point so when I try to zoom out with my scroll wheel instead of the camera moving it seems to change the perspective angle - though when I check the camera dialogue box it's still set at 35-degrees. What gives? Not a big deal I just reboot the camera view but still is odd. Anybody solve this or is it a bug?
  7. Also I noticed you have a mac mini - you might look at getting an egpu (external graphics card) for that - with the new x13 update it runs really really well for both raytracing as well as CD/Layouts.
  8. Wow that does look pretty excellent. Did you set-up a transparency layer as well?
  9. I was able to create a new roof label style in text defaults and force it to have a transparent background - this worked well enough so I'm calling it fixed for now. Reminds me of the old 'there I fixed it' blog https://failblog.cheezburger.com/thereifixedit
  10. centered well enough, anyway. you can see it hiding there behind the label
  11. Yeah the trick was to add an extra \n before everything else. Sauce: indx = $tree['roofplanes'].keys.find_index(id) result = "\n" result += areasq.to_s + " sq" +"\n" result += pitch + "\n" result += "\n" result += "Eave: " + eave_fascia_length.to_s + "' " +"\n" result += "Gable: " + gable_fascia_length.to_s + "' " result
  12. Thank you thank you for sending the link to that other conversation - maybe I'll delete this one and jump in over there. I am on a Mac yes - I've been using the \n stack to get it just right - had it before so that the arrow was right smack in the middle of the text! looked so sweet. Ok I will check out that other discussion thanks again
  13. Somewhere along the way here I found a good roof label macro and modified it to fit my use - which was great up till now that there seems to be a roof label fill which is background color (white) but it covers up the arrow for the roof plane itself. Does anybody have this issue yet and how can we control the label background on a roof label? I haven't been able to find it.
  14. Oh another thing - is there a way to make the Automatic Dimensions all be on a single dimension string, instead of all having different offsets? Honestly I end up deleting most of the automatic dimensions so I can get a couple of strings going - guess I really don't use them much after all. Though if I had the ability to set up layer as well as 'keep as single string' I may have a use for them actually
  15. This is going to screw up my workflow a bit, but that's fine. I have been using Automatic dimensions only for locating exterior corners - these are carried over into a number of different drawings like a floor framing plan, roof plan, etc. for plans which only need the overall length of things - then I use the 'manual' for locating interior wall strings and window/opening centerlines, and other stuff that doesn't need to go on the other plans. I also have an 'overall' one which is just the overall lengths or the length of the main building sections. You can see them here on the right - I use these off-sheet guides to help me line things up. I set all four sides up with strings, then it helps me line everything up. The different colors only show up on my @modeling layer and not on my main @plan display layers that show up on my drawings.