IvanCyr

Members
  • Posts

    91
  • Joined

  • Last visited

Reputation

8 Neutral

Profile Information

  • Gender
    Male
  • Location
    St. Lazare, QC, Canada
  • Interests
    Aviation, running, squash, cycling, architectural rendering and 3D virtual home solutions.

Recent Profile Visitors

2025 profile views
  1. Michael...I just sent you an email. It will be from Inteck3d Inc. Thanks. Ivan
  2. Hey Michael....ah...the triple click! Thx for the screen shots. I would have been scratching my head for a while on that! I was looking through the Chief "Help" menu for info on this but what you've presented must be somewhere else from where I was looking! Curious, is your source of info on this within Chief...or outside of Chief 'proper'? I definitely prefer your method and it helps me to better understand how to glean better and more thorough ruby coding back into the mat list. So much appreciated! Thanks!!
  3. Hey Mark...well, that was too easy. I suppose I was thinking that I could add a designated column somehow to the M. List. Sometimes one thinks too hard on this stuff! Ok...thanks so much.
  4. I likely have an advanced question for folks who like to jump into the deeper functions of Chief. I am working with a client to automate his pricing for kitchens. I have almost all the items figured out. However, I'm currently wondering how to "fix" the following: I'm noticing that the cabinet schedule callouts are NOT equivalent to the C#'s found in the materials list. I would need to find a solution to do one of two things: 1. Automatically duplicate the cabinet schedule values (C1, C2, C3...etc) into the same values created in the materials list; or 2. Create a macro that presents the value in the cabinet schedule above AND be able to "present" in on a line in the material's list. Regarding #2 above, I've been able to create a macro...but how can I point back to it from the Materials list and add it in the Materials Master List. Or perhaps there's another solution that I'm missing. Any comments would be well received. Thanks in advance.
  5. Hey thanks Steve. I suppose I need to better understand Chief's ideas of furred vs frame through. Thanks again!!
  6. Fair enough Eric...I'll give it a whirl here...no huge rush... With a handle like "solver" you would think you would just get me an answer or link to the answer!! LOL :-)
  7. While on the topic of furred walls, (could find an answer here on the forum after some searching) does anyone else get the ceiling surface disappearing above the furred wall? I have modelled a split level, with the bottom portion of the basement portion 4' below grade (foundation level), I have defined a 4 foot high 8" thick concrete stem wall on that half the house. The top half is another 48" of exterior Siding 6 wall (so it is defined as a pony wall). I set a furred wall all around the four sides inside up against the 8" concrete stem wall capped at 48" to the top of the concrete stem wall. The furred wall layers are defined as 1" air gap, 2x4, 1/2" drywall. It is set to furred in the Structures panel. I have tried no room definition, no locate etc. but the ceiling in that basement stops at the furred wall (which doesn't go to the ceiling...stops at 48" above floor height). A manual ceiling drawn will also automatically delete itself in that area. What button am I missing!! Likely a rookie question...but this one has evaded me for some time... Thanks in advance! Ivan
  8. Glad you liked the idea. Keeping various design options organized is absolutely critical. I use a lettering system. File management is typically alphabetical on computer systems and this lists the files as such. So a typical project is named, jobA, jobB, jobC as we go along for the versions of the file. Sometimes, say at jobC, the client wants to see three roof options. So at this point, starting from jobC file, I'll create jobC1, jobC2, and jobC3. When we move forward from there, it becomes jobD and so on. Seems like a small thing, but vocabulary becomes important. I use "VERSION" for the letter sequencing and "OPTION" for the number sequencing. In the event of getting to version Z, then the file becomes ZA, ZB, etc. That's only happened twice.... Number and date systems seem to be popular...but they always seem to get messed up between different peoples "way" or even country standards. As well, the time/date stamp is there with the file already so it becomes redundant. Using the letter system then allows for the attached date to be an additional layer of quality control. Organization is the vault to success here....a good system is the key. Again...by humble opinion. Cheers,
  9. Yes, this is VERY important when you showcase as-built and proposed plans...or say 4 different options of a .plan variations of a home onto a single layout. Backing up from the LAYOUT will package ALL associated .plan files (plus all reference files in the layout, and ALL plan files associated) into a single folder. Makes it super easy. One way to make file sharing efficient without having to close programs in order to copy or share, (because the file is "Open" in Chief) is to save the Chief files (plan and layout) in a folder. Save the backup file created in that same folder. In this manner, Chief doesn't really operate by saving into the backup...it just a suitcase to store things as you go along...and you can toss the suitcase to whomever you like and they have everything they need in that suitcase while those same Chief layout and/or plan files are open. When you receive a suitcase of Chief files in a backup folder. First thing, save the files you are going to manipulate outside of the backup folder. Do you thing...and then backup again to another suitcase. Chief will package again ALL resaved and archived files (from the old suitcase) into a new one with again, ALL the associated files with the Layout. Perhaps someone has a better solution, but I work almost always with multiple people using Chief or HD products and so far, this is the best I've come up with. My 2 bits worth... Cheers,
  10. Hi Charles, When you export to Lumion using the Collada file format (.dae) or 3ds, Chief will export what is visible on the camera screen at the time...this would, for example, include all your framing inside the walls that you might NOT want to see and it adds considerable weight to the file size and may push the limits of less powerful computers. What you "see" in Chief, is what you will see in Lumion. If you see a window track in Chief, that is what is will look like in Lumion....it is just a render engine which might improve on the render image quality and control of materials with lighting. Model where you feel is best. About the only thing I import separately into Lumion are animated objects, like opening a door. One thing you may need to consider is material thickness for very large projects, where you have multiple homes spanning 3-4 blocks in a city for example. The under surfaces of faces will expose with Z fighting...this is a computer presentation issue that occurs...there are settings in Lumion to limit this, but sometimes if you're close to one object and far from another, lets say roofs for example, you might get the close ones to look good but the far ones will Z fight or vice versa. Lumion allows each material to be assigned different properties, so you can get around that by using different bitmap names for the same material. One other issue with the export is that Lumion most often applies a random bitmap to all Chief materials which includes ONLY a color (ie no bitmap assigned). Before I export large projects I take the time to adjust all Chief materials (a most terrible menial task) to include a bitmap and differentiate those materials which I might desire to have specific properties in Lumion. This can take a couple hrs in Chief but is a simple one click reload when updating an revision in Chief back into Lumion...a life saver on huge projects. An example of quality of Chief in Lumion can be found at this link: www.inteck3d.com/tour/kennedy/index.html Perhaps this helps.
  11. Showcasing a space can sometimes best be accomplished by showcasing the entire area within an integrated 360 Tour. Video is great for clips, generating interest, investment, and capital campaigns but it drives a user on a set path on a set time frame. Try a 360 Tour! Your users can take all the time they need and really get a feel of a space. Please see one posted at the link below: 360 Tour Tours can be generated easily and quickly. All we need from you is the 2D or 3D floor plan(s) you wish to use, and the spherical images you wish to upload. A company logo, text, and even video can be set into the tour as well. Tours run off our own server and will be active for 18 months upon payment. Very competitive pricing and updates are fast and easy providing the images are resent using the same file names. For more information email ivancyr@inteck3d.com. Ivan Cyr
  12. Hey Chopsaw! You beat me to it...I did find some ideas going back to X10 2018 which helped as well... Thx for offering the link. Mucho gracias. Ivan
  13. Hi Eric, I have been searching all day with that and Ruby codes...likely right under my nose...my brain is fried! But I can go dig a little closer for sure. Thx for letting me know. :-) Ivan
  14. Hello all, Quick question. I have a customer that desires BOTH a window schedule and a window size and top height notation like the window label can display using macros and custom Ruby code. However, I can't get both to show...either the schedule with the callout displays, or the window label displays. I have a workaround, but it would be nice to have it all fall into place automatically. Anyone know the solution on that? Thx. Ivan
  15. Thx Renerabit....I thought of the symbol but wanted it to work a bit more "clean". Btw, nice lips in the aviatar! LOL Joe, you don't have as nice lips, but I like your idea! I do have it now in the schedule, but do you have a way to get the window dimensions into the schedule and a 3D object view for example?? Thx again.