BenPalmer

Members
  • Posts

    427
  • Joined

  • Last visited

Reputation

32 Excellent

Contact Methods

  • Facebook
    https://www.facebook.com/ArizonaHousePlans/
  • Website URL
    http://www.palmerhomedesign.com/

Profile Information

  • Gender
    Male
  • Location
    Phoenix, AZ

Recent Profile Visitors

1182 profile views
  1. Quick follow up on this: I appreciate everyone's comments and suggestions. Your time is much appreciated. It appears that update 23.2.0.55 has fixed the thick wall connection issues. I appreciate Chief Architect taking care of this. While I wish it didn't take a year, multiple reports/requests to tech support and this thread, I am still grateful it appears to be resolved. Thank you again!
  2. Still no fix for this in the latest update. That lack of Chief's support is extremely disappointing. If I could give Chief's support a ranking, it would get 1 star. I just looked at the 12 tickets I have done over the last 20+ years, and all but one item had an answer something like: I'll pass that on, or sorry for your frustration, but we are unable to fix it, or here is a workaround you can try, that didn't help, etc. Maybe I'm asking too much? Not sure why I'm paying for SSA...sheesh....certainly no Assurance ... aka Priority Tech Support (maybe that just means speed and not service?) (ok, done venting - for now)
  3. Thanks for the report @MoeGia appreciate you submitting a plan so they are seeing the issue from more than just me.
  4. @Renerabbitt was the issue with walls that have the typical wall layers? Or are they non-layer walls like I use in the examples? Trying to narrow it down.
  5. @glennw thanks! I hadn't tried the partition wall on the walls sticking through, I'll give that a go, appreciate you looking at it and giving your feedback. On the shower walls, I forgot that was still in the file, I also discovered, similar to your suggestion, that this can be fixed by making the upper glass wall NOT a partition wall as well. Thanks again for the tip.
  6. Thanks for the feedback and suggestions. I'll try creating new walls and report back. They are very likely walls that have perpetuated over previous versions, so definitely worth trying that out. Some of these issues don't happen right away. They usually appear during the design process, seems to especially happen when cabinets start getting added to the plans, but can't recreate or verify that. But again, this worked just fine all the way until mid-X12, and then after an update started messing up (I have given Chief the exact update that caused it). So this is a Chief created issue for sure, but if I can find a solution, that would be great since Chief doesn't seem willing to fix this or help me with it.
  7. My mistake Robert, I should have clarified that I chatted with Gordon Ray offline and he uses the exact same method, so the plan I posted represents their situation as well. Hope that clarifies. Curious if you have any input or suggestion on the plan I posted for investigation?
  8. @robdyck Please see original post...a plan demonstrating the issue was posted. Also, while I realize chief prefers layers, I've been doing it without layers since Chief 8...been working fine for over 20 years until an X12, mid-cycle update broke it.
  9. @solver really appreciate you taking the time to look at this....you perfectly demonstrate how much effort it takes to correct these problems. I intentionally left the walls broken so everyone could see the issue. I go and fix them exactly as you do, but throughout the design process they just break again. Room definitions are lost, time is taken to fix over and over and plans sometimes go out with wrong definitions...unprofessional. I need them to stay connected! I actually sent this plan into chief over a year ago and they acknowledged the problem and tell me it is on there list to get it taken care of. In hopes that X13 would be the fix, it wasn't. I sent it in again and got the same answer. On our list. It's especially frustrating when it worked before, and has always worked since I've been using the software (Chief 8) and there update broke it and they won't fix it. I've been a long time use of Chief, former beta tester and rarely use support, and this is a big reason why I don't. No purpose in using support if they won't support us. Doesn't seem like it would be hard to fix something they broke?? Again, thanks for sharing the video so others can see it without needing to open the file.
  10. about a year ago, with an X12 updates, thick wall connections (anything over 8" thick) became unstable...especially when 3 walls intersect. I'm attaching an X12 plan that demonstrates several issues I'm having. Curious if others see the same behavior. notes within the plan describing the behaviors I realize that layered walls will likely fix much of this but I do not like layered walls....they have a whole set of issues that I don't want to get into the pros and cons. again, this worked fine before, but broke with an X12 update and is still broken in X13 beta. Appreciate everyone's input. wallConnectionProblems.plan
  11. @MarkMc curious how your experience was with AVA and what kind of delay there was on some of the components.
  12. While I haven't had it happen to me personally, one of my employees has it happen to him once or twice a week in X12...never had it before for anyone on any computer or software version prior to this happening with X12 (20 years+). We have backups and can get it back pretty quick, but an annoyance for sure. We haven't reported it because we can't reproduce it...we haven't been able to find an action that causes it...seems to be random...for us anyway. We'll consider some of the tips listed above and see if that helps.
  13. My wall connections have been horrible since the new update...especially when i have thicker walls (12" or larger) meeting thinner walls (4" or so). Constantly disconnecting and messing room definitions and giving the unconnected wall error...driving me nuts. Anyone else having this? Might need to go back to the previous version..except the dimensions in blocks issue in that version. Ugh.
  14. Thanks Steve, I'll take a look at that on my next import...probably have one later today. I'll report back. Appreciate the input.
  15. Bill, I can confirm that is when I get the same behavior: when importing default sets.