HumbleChief

Members
  • Posts

    6145
  • Joined

  • Last visited

Everything posted by HumbleChief

  1. Here's a comparison between the 10700K and 11900K. https://cpu.userbenchmark.com/Compare/Intel-Core-i9-11900K-vs-Intel-Core-i7-10700K/4110vs4070
  2. If the motherboard noted in the pic above is indeed the one you have than an M.2 drive will have access to (EDIT) PCIe 4.0 and faster speeds. Not true it's only Gen 3 PCIe. Took a while to find the info in the link below, it's a pic towards bottom of page. Click on the tech specs tab for further info. https://www.asus.com/Motherboards-Components/Motherboards/TUF-Gaming/TUF-GAMING-Z490-PLUS-WI-FI/
  3. New gear is always fun but don't expect huge gains from any upgrade at this point in your computer world. Your current computer is very capable and most likely a new CPU and new M.2 drive will be faster but the gains will most likely not be worth the cost. It's fun and can be a bit of a placebo but performance gains from your current system will come in very small, maybe not even noticeable, increments.
  4. Hey Perry, hope you're well! Turned out to be auto framing (roof and floor) that was causing the lag. Turned off auto framing and it was back to normal. Apologies as I should have posted that solution in this thread as well as another I started to address the issue.. I've always been an Intel guy but the AMD processor has been great and don't think it's a factor. The point of the last post was to illustrate that an upgrade to a fast drive might not be a magic bullet to get speed gains in Chief.
  5. Yeah Chop I keep trying to get better performance from upgrades like that new M.2 hard drive but the performance stays pretty much the same, or is a small enough speed increase to be questionable as a purchase and upgrade. Of course that doesn't apply to older way underpowered rigs but if you've got a decent modern rig the upgrades to performance seem incremental and quite small.
  6. REALLY appreciate the feedback and perhaps this was the problem in previous plans as well? I'm going to call it user error but hope this helps someone in the future. Also Joey, Dermot I think some materials/patterns/textures didn't make it from the previous plan and the new install to the new hard drive. I'll explore those as well and make sure they are at least available or replaced for this plan. Again, can't thank you guys enough, that has made me crazy for a while.
  7. I turned off auto framing roof/floor and it's back to workable. THANK YOU! THANK YOU! THANK YOU!
  8. I turned off auto framing roof/floor and it's back to workable. THANK YOU! THANK YOU! THANK YOU!
  9. I've hit this wall many many times in Chief with no solution I've been able to discover. This plan now takes 18 second between any structural operation. Literally unworkable at this stage in the plan's development. I'll post a drop box link if someone's curious enough to open the plan and see what I might be missing. Thank you very much in advance. Drop Box Link https://www.dropbox.com/s/203u2ebda627ny5/UNWORKABLE PLAN.plan?dl=0
  10. A quick update to the new hard drive install. For the most part very, very good and well worth the cost and effort but (you knew there was going to be a but didn't you) when Chief reaches a certain size and complexity no fast hard drive, CPU or fast GPU will fix the 'crawl' that those complex plans revert to. I have a plan now that takes 18 seconds between every change to any component. I'll post another thread seeing if it can be 'fixed' as it has become unworkable, no matter the speed of a hard drive.
  11. I think we're talking a bit of apples and oranges and yes one should always copy (darn near anything you want preserved) a tool bar set instead of modifying an existing one. The point I was trying to make in the previous post was that my toolbar.bak file was dated 2016. I would have thought there would have been a more recent .bak file but perhaps I didn't change anything for 5 years? It's not a concern, only an observation.
  12. Some truth to this Michael. The tool bars should never relocate or reconfigure themselves out of nowhere. It's a simple fix to reload the old tool bars back to sanity but your point is well taken. We should not have to do so.
  13. Smart no doubt. I have never had a problem with toolbars until the other day and it was awful. Mick, I think your advice is better than mine. I'm going to look into backing up the data folder.
  14. Hey Rene, ALWAYS appreciate your posts and information but I just looked in my toolbars folder and the only Larrys.toolbar.bak file was dated 2016. There is now a Larrys.toolbar and a Larrys_copy.toolbar . Do you think that copy version serves the same function as the older .bak files? There's also a Larrys_copy.toolbar.bak dated June 2020. I thought the .bak files were updated as you suggest but I wonder if the _copy.toolbar has replaced that function?
  15. Hey Alan, here's what I did when I installed a new hard drive and it worked to copy old hot keys and tool bars and templates from the previous install to the new install. Go to Documents/Chief Architect Premier X13 Data/ (or wherever your Chief Data is stored) and you'll see all of your current Hotkeys, Templates, Tool Bars etc. If you are happyy with your current tool bar(s) just copy the contents of the tool bar folder (or the folder itself) to a safe location. If (when?) your tool bars blow up you can restore using that older tool bar setting by deleting the current tool bars and copying the old files into that folder. I had backed up that older data folder and reset everything this way when I installed a new version of Chief.
  16. ...or not, and it's not worth the risk to me to rely on Chief to have a back up that 'restores' the old tool bars as it's just as likely that .bak back up tool bar could be a back up of the tool bar that's gone astray.
  17. I've read a couple of threads here about disappearing tool bars and/or quirky tool bar changes and didn't really understand the pain that can cause to one's work flow. I recently experimented with some tool palette tool bars and other way to get my tool bars a bit more functional and before I knew it ALL of the tool bars were messed up. Nothing where it was before. Nothing looked the same in any view. Tools missing. Tools gone. Loaded my custom tool bar, nothing changed. So very disturbing and I finally got all the hub bub around tool bars going missing. It was awful. I was at a complete loss then I remembered that since I just installed a new hard drive that I had saved my old tool bar data from the previous install to a new directory on an old hard drive for backup. Went to the current Chief X13 data folder, deleted all the toolbar data, and copied the old tool bar data in to the new X13 data folder. Tool bars are back to normal and a huge sigh of relief. I no longer trust Chief to not destroy my tool bars and have a back up tool bar file specifically set up in case that happens again. Might be good practice in general. Hope that helps.
  18. WOW, thanks so much, never would have found it there as it has been in the Core Catalog for many, many years. Thank you again!! And...that's a really nice collection and well organized too.
  19. Minor issue but I have been using the Bryant Sconce in plans for years and just went to use it and it's gone from the (my) current Chief Core Catalog. I did just reload Chief and the catalogs so it's the latest version but am wondering if anyone else still has it in their catalog? Am I missing something? Can I download the catalog again? Or is that particular sconce simply not available any longer? Thanks
  20. Another update for those interested. If you've ever done a new install of Windows to a new hard drive you understand the pain that's coming. Loading all programs anew, managing files, locating textures and libraries and hot keys and tool bars and whew. Finally got all that taken care of and the computer was singing along and overall very happy with the upgraded M.2 drive. While working in a not too complex Chief file the computer hit that same old Chief performance wall where it starts to balk between refreshes and plan changes and gets just plain slow with no real improvement over the old SSD drive which is actually expected. Was just going to post how cool this new drive was and that Chief was performing much better but it's pretty much the same. Awesome until it hits that invisible wall where Chief starts to slow down, probably due to file and plan size, but actually unknown to me. Still happy with the upgrade but no real discernable performance gains.
  21. Been there done that. I think it's new for X13? and a great feature. Also it looks like the setting is floor structure/room specific so maybe check/change the defaults for the entire floor?