Alaskan_Son

Sorry Johnny, try as I might, I couldn't replicate your problem either. Looks normal on my end.

I can't give you an authoritative answer Cliff, but it was my assumption that Chief always looked at those subcategories as nothing more than a way to get user defined items into schedules and that the reason they were deleted is because the functionality was completely replaced by the new Custom Object Information Fields.

You can also just use 2 doors with zero separation...

I know you were just trying to be helpful but I think these things are absolutely terrible unless MAYBE if you live in the desert. Introducing all that moisture into a house, and at such an extreme rate is a recipe for disaster. We actually had one of those things in a trailer we lived in. I think we lived there about a year and a half. When we moved out, I kid you not, there was black mold behind almost every piece of furniture that lived up against an exterior wall. It may have been coincidence, but my wife and I both inexplicably developed some new health problems around that time as well. Anyway, just to be fair, this was in Alaska where moisture inside the home is a much bigger problem than it is in warmer climates but the same principle holds true in a large part of the country. I would just really encourage anyone seriously considering one of these devices to proceed with EXTREME CAUTION and even then...only if you live in the dryest and warmest of climates or REALLY REALLY understand what you’re doing. That’s a lot of moisture to dump into the air at one time.

Yeah, I did that on one of my own personal houses years ago and I hated it. We almost bought a new dryer one time thinking the dryer had gone out on us till we realized the stupid screen was just totally blocked up with lint. So, we had to climb up on the roof and clean it off every few months. The alternative is to do away with the screen and use a flapper but then you end up with an ugly “lint stain” on your roof just below the vent hood. Anyway, I only go through the roof now as a last LAST resort.

Statement like this would be helpful... ...IF you would send them to Chief and and IF you would somehow qualify your statements. What you said is basically the same thing as saying I wish My Ford worked like my Chevy... What is anyone supposed to do with a statement like that? It would really help if you were to at least specify exactly what you want to be able to do with Ruby that you can do with VBA. The truth is that Ruby (in Chief) already CAN do a lot of what VBA does in Excel. And BTW, don't forget we're talking about 2 entirely different programs and user interfaces though and so there are going to be inherent differences in what is possible. Anyway, I agree that there is a lot that can be done to improve Ruby implementation within Chief but again, if we want to see any changes we have to supply Chief with at least some semblance of specificity or its just noise.

No, still no easy way to use this information directly in a text box. I've used about a half dozen different methods to mimic the behaviour...all of which have their strengths and weaknesses, none of which are nearly as easy or as flexible as what we would like to see, and most of which are only manageable for intermediate to advanced users depending on which one we're talking about. There's the method I posted back in Post #19 There's the method I shared here There's the method I shared here Plus I have a few methods I haven't shared that involve using some special architectural blocks kinda like the block I shared here but with some additional parts and pieces Every single one of the aforementioned methods is relatively convoluted. You probably shouldn't even try them. Please complain to Chief. What we really need as Joe and myself have requested MANY MANY times is access to Chief's global macro values (at a bare minimum) or better yet, a "room context" for text macros. Chief keeps trying to handle room information in such a way that will basically only work for one person. I have yet to see 2 users who want room info. displayed the same way, I believe all the professionals I've dealt with are resorting to adding all the necessary room information manually to each and every room label or just settling for the standard text boxes and turning out plans that don't look as good or are much more difficult to read. The vast majority are doing the first thing and just adding the information manually though. This is just ridiculously time consuming and begging for errors. I really wish Chief would put this higher on their priority list. Of all the requests for help with custom macros I receive I would say the vast majority are relating to room labels. Maybe if we could get a few more of you guys reporting it directly to Chief that would help. You've all been contacting Joe, myself, and others to help you with this stuff but Chief only puts so much weight on what Joe and I have to say, I think maybe they need to hear directly from you guys. The simple fact is that we need access to all the room information values and we need to be able to utilize and modify these values for use in Rich Text boxes. Maybe we should head to Coeur d'Alene and start tipping stuff over.

I have absolutely noticed the same thing. I'm relatively certain its an unintended consequence of the new Ray Casted Sun Shadows affecting all the dialog previews. I am confident this is on Chief's radar but it would be a good idea if you were to send in a report as well.

Its working. You just can't really see it with the texture you're using. The texture has a plank pattern in it so the border doesn't show up very well...

Either that or maybe get an engineer to sign off on one going through the roof if you can prove enough stack effect. This would be pretty easy for us to do in Alaska I imagine. Maybe not so much in California. Downside of course is cleaning the screen on the roof or the lint on the roof. Yeah, that's not a good idea. Forget I said it.

In line booster is the only way I know of. Here's one example... https://www.amazon.com/Fantech-DBF-110-Dryer-Booster/dp/B000GXF7KO I've never actually ended up having to use one but we've been close and so that's how I know about them.

Seriously...PLEASE don't do that for my sake. I honestly don't need to see one and I don't need to see any proof. I only asked for a quick rendering because I knew I wouldn't get one that fast. As you well know, you've found time to submit posts on all sorts of things (some of them rather long) but somehow the time it takes to "open, load, and push the button" is a bit much for you right now . I've just noticed you ripping on Chief a lot lately and so I decided to go ahead and take a shot at your obvious and blatant hyperbole is all.

I don't doubt that but to be fair, you have also been using it since AT LEAST version 6. To be clear, there is no doubt in my mind that Lumion is easy to use, intuitive, and a better rendering program than Chief. I mean for $1,800-$3,600 it freakin' better be. My comments were just a jab at the " Open, Load, and push the button" type comments. If it was that easy we wouldn't need guys like you or Jintu now would we?

Ooop. I missed that part. My advice re: opening the box and cleaning it out may not apply.

Sounds like an overheating problem. I would recommend you open your box up and clean it out real well.

PLEASE report it anyway. Just because someone else reports it is not enough. I'd venture to guess this attitude and thought process is reason numero uno that things don't get fixed. Not only will Chief leave it on the back burner in favor of items that have been reported by more users, but just because another user has similar problem doesn't mean its caused by the same thing. Please please please...for your sake, for my sake, for the sake of all users...if you care enough about the problem you're having that you would like to see it fixed...report it.

Also, just a side note and I know its a little off subject now, but you can also adjust the number of cores allocated to Chief by going through these 3 steps... If the low CPU usage WAS your problem (which it seems now was a bad assumption on my part) then you could also check here to make sure this had not been changed.

Why does your screenshot only show it running at 27% then? I assumed that's what you were trying to address. If your CPU is indeed running at 90-100% on all cores than Mick is right. Its something about your model. More likely than not it has to do with the number of faces, number of lights, or screen size but there are a number of other settings that come into play too as Mick already pointed out.

Click on that performance tab and then click on Open Resource Monitor. Then over on the right you can see which cores are being used. Also, check Preferences>Ray Trace and make sure its set to use all available cores.

Good catch. I'm gonna guess a little bit of inadvertent Object Eyedropper usage was to blame.

Many ways, but just try using railing sent to no room definition

That's what these are for...

No, not necessarily. You can just click on the Open Symbol tool after you drop the object into the plan if you want to.

Just FYI, the problem occurs because the symbol is set as a switch. Uncheck that option and the problem goes away...

Yep. Kinda what I thought. Its all super easy and super amazing and soooooo much better than Chief, and soooo much more intuitive, but so far no quick examples demonstrating how easy it is. It should only take a couple minutes right? I'm gonna go ahead and call BS. Lumion is just like every other piece of software, it costs money, it takes time, and it always seems super easy till you dig into it. I have no doubt that it turns out a better end product than Chief but to be fair, you're definitely paying for it, both in time (learning and modeling) and money. P.S. I've seen plenty of Lumion examples from seasoned users. Those ones don't count. What I would like to see is the "Open, load, and push the button". I won't hold my breath.