Renerabbitt

Members
  • Posts

    4713
  • Joined

  • Last visited

Everything posted by Renerabbitt

  1. Perfect, thank you that’s what I assumed, happy tday
  2. No idea how alaskan got a full height superscript if this is a screenshot from chief anyone? Custom font? Some ruby vertical alignment method?
  3. See the video for more info # Copyright Rabbitt Design 2023 # Helper method to convert numbers to superscript def to_superscript(num) superscript_map = { '0' => '⁰', '1' => '¹', '2' => '²', '3' => '³', '4' => '⁴', '5' => '⁵', '6' => '⁶', '7' => '⁷', '8' => '⁸', '9' => '⁹' } num.to_s.chars.map { |char| superscript_map[char] }.join end # WINLABEL MACRO WITH CONDITION FOR BLANK NEW LINE def winLabel # MAPPING OF WINDOW TYPES TO THEIR ABBREVIATIONS window_types = { 'Single Hung' => 'SH', 'Double Hung' => 'DH', 'Single Casement' => 'SC', 'Double Casement' => 'DC', 'Triple Casement' => 'TC', 'Left Sliding' => 'LS', 'Right Sliding' => 'RS', 'Fixed Glass' => 'FX', 'Single Awning' => 'AW', 'Louvered Window' => 'LV', 'Glass Louvered' => 'GL', 'Pass-Through' => 'PT' } # CHECK ENERGY VALUES FOR WINDOW LABEL PREFIX window_prefix = if u_factor > 0.3 || shgc > 0.25 '(E)-' else '' end # CHECK IF LAYER_SET INCLUDES "WINDOW LAYOUT" if layer_set.downcase.include?("window layout") if window_prefix == '(E)-' || schedule_number.empty? return "N/A" else return schedule_number end end # CONVERT WIDTH TO FLOAT AND CALCULATE IN FEET AND INCHES width_feet, width_inches = width.to_f.round.divmod(12) width_str = "#{width_feet}#{to_superscript(width_inches.round)}" # CALCULATE HEIGHT IN FEET AND INCHES height_feet, height_inches = height.to_f.round.divmod(12) height_str = "#{height_feet}#{to_superscript(height_inches.round)}" # GET SCHEDULE NUMBER schedule_str = schedule_number # GET TYPE NAME AND REPLACE WITH ABBREVIATION IF EXISTS type_str = window_types[type_name] || type_name # CHECK IF WIDTH IS LESS THAN 30" if width.to_f < 30 # SPLIT TYPE STRING AFTER ANY SPACE type_str = type_str.split(' ').join("\n") # COMBINE VALUES INTO MULTIPLE LINES "#{window_prefix}#{schedule_str}\n#{width_str}#{height_str}\n#{type_str}" else # COMBINE ALL VALUES INTO A SINGLE STRING WITH NEW ORDER AND NEW LINE FOR TYPE "#{window_prefix}#{schedule_str} #{width_str}#{height_str} #{type_str}" end end # CALL THE WINLABEL MACRO winLabel 231123 (4).mp4
  4. You can post a link here to share with anyone or send to renerabbitt@gmail.com and I can post it
  5. Do you have a cloud service like onedrive that you could share a link from?
  6. Sorry I meant please post your .plan file
  7. please post a plan..what version of the software are you on?
  8. Ha! Working through it backwards. As fun as that probably was to experiment with we are missing some core knowledge here. Chief is using a whitted raytrace for RTRT, single light trace, so whereas the results here are easily manipulated, you have to understand whats happening in a scene in order to get the results you want. Which is to say, these aren't repeatable results. the same light in another scene is going to do something different. This ends up getting into a very complex conversation about rendering, truly. Something I usually offer training on. Throw in cuastics and refractions and you have a ton of calcs that are happening in all of the surrounding surfaces of a cabinet box that is lit from the inside. Single surface bounce, so based on the pixel density of your screen, the angle of your cabinets, the color and supporting maps of your materials, the index of refraction on your glass, the backdrop you used and its intensity and so much more, you will get different results from scene to scene. For instance, if you have overhead lights hitting your glass cabinets, and then lights inside of your glass cabinets, chief kinda sorta has to make up the decision on wether the pix of the material inside of the cabinet is lit from those overhead lights or the lights insisde of the cabinet. Move closer to the cabinet, like real close, and chief might make the decision that they are lit from the interior lights. This does get way more complex though, and I wouldn't spend too much time on it until you know what the next version brings
  9. I did notice on another plan you had samples set to 1000 and no cap live samples or denoise. drop that sample rate down to 50 and cap them
  10. Are you doing residential design and plans?
  11. This is an eloborate setup, why are you backing up files to a NAS and to a cloud service and then to a cloud backup service? Why not just the cloud? then periodic system backups to the NAS? Do you use symbolic links? Onedrive saves a version history if you ever need to revert to a previous version...are you versioning your project process as you go? Cool tip about dialpad. I use dropbox for my project files, it doesnt have the same sync issues that onedrive has, (i use onedrive for other things) I recomend it. An old vid of mine- iterative versioning, can always revert back to a previous design iteration, or a previous version of a current design, all through dropbox. Could take any of these folders and share to your sharepoint as well or symbolic link to a NAS or 2nd drive. Sounds like you have your system and it works so Im just sharing info
  12. Actually meant the light source moved outside of the gemoetry of the light itself.(y-offset) Also cut-off angle too steep and fall off WAYYYY too high crank up the lumens til it shows
  13. Hey all, I do not know why all of the workarounds, I didn't mess with anything. Keep your cabinet glass. Make sure your light sources are not inside of the geometry of the light itself. Change them to spot lights, angle them in. This is regular glass on my cabs
  14. No on the a4000. im doing great with an amd6850x which should fall within your budget
  15. You can reach out to Melissa nunes on my discord server, I believe she uses airtable and asana. Pretty sure she has tried them all, buildertrend, canva, designfiles, slack, co-construct, plangrid and more. her handle is MKB there https://discord.gg/tWxurVzw5t
  16. Tons of different methods, simple one, place a cad line, then use the point to point move tool on both Surveys and snap to that CAD line
  17. Hey all, Joe posted this on my discord server. One of his rooms wasnt set to follow floor defaults and had the osb check as framing. Also using X14.
  18. can you post your plan, we are just guessing otherwise. If you need a higher mb cap I think you are in my discord server, you can post it there
  19. are you using a floor overview camera? also post your plan
  20. Im not going to be using the correct terms as I am not a developer, but, even if the hardware was up to snuff, its still running on metal, which from what ive heard, apple doesnt offer dev support like microsoft, metal is hard to work with, their sdk is a moving target, and its all just difficult to code for, and you cant just reach out to apple like you can to nvidia or amd I don't know if you remember this, but M1 was supposed to be a huge game changer for graphics. In fact it was a huge let down. M2 was also supposed to be a huge game changer for graphics. Here's the jist....Microsoft and nvidia and AMD have billions into the gaming industry...in this regard, think of mac as a homebrew application. They dont care to enter this market for the rendering artist or game developers...because frankly, you couldnt convince a game developer to switch pllatforms no way no how. I don't mean to be offensive, but I have never understood the desire to keep trying to make a mac work in our industry, its just not the right tool for the job to me, so after so many years of discussing this, I imagine I am a bit biased at this point. I try to stay subjective, but subjectively mac does not make sense at all to me. I have tried Mac, in fact I've used it as my machine for a full year, and its benefits never outweighed its cons for me...I often times wonder if mac peeps every dip their toe into microsoft. Its better hardware, for less, and open source, and infinetely customizable, and supported by a great deal more engineers and developers and peripherals. security is an old wives tale. Not to oust the devs at Chief, but you should see their actual faces when you push mac...I can't speak for them, but I bet you they wish that everyone would switch to PC as well. I teach a class called Power Users in chief and I was going through a bunch of workflow things I do to create some of my best models and visuals and Kevin Transue had a brand new Mac. I swear I'm a nice guy, I wasn't mac shaming him out of spot but we did do a lot of teasing back and forth, but ultimately he did question his purchase becase we kept finiding limitations in the mac. To be fair though, my workflows are specific, but they are fun and cool and playful , and I know its fun to be around that energy.