• Content Count

  • Joined

  • Last visited

Community Reputation

28 Excellent

About Smn842

  • Rank

Profile Information

  • Gender
  • Location

Recent Profile Visitors

1232 profile views
  1. Many vendors used to host their videos where the video file was basically read by the browser and played. This allowed the easy save to disk options, but was wasteful if people didn't watch the whole video as part or all of the file was read, and this also added load which could be an issue if lots of users connected at the same time. Hence many videos are now hosted by third parties that specialise in video streaming as they have the resources to cope with variable loads and can more efficiently stream only the content that you actually watch which is the feature that often breaks
  2. From the reviews I've read about real time raytracing with these drivers for a GTX 1080 the performance was terribly poor even compared to the 20xx series which is quite a way behind the 30xx cards. So for some applications (and perhaps Chief?) I could understand companies not wanting to support use of the older cards as it could make features appear unusable and it adds another area of possible driver bugs to contend with.
  3. I second the suggestion of getting glasses specifically for monitor distance. I would also be concerned of neck strain of that stand and the distance difference from top to bottom of the screen increasing eye strain (even people with great eyesight experience eye strain adjusting eye focus so frequently) I have zero ability to adjust focus (surgery not age related) and although I usually wear multifocal contact lenses I have glasses to wear over them to fix any residual astigmatism (affects sharpness and contrast) as well as adjust focal length to be perfect for the distance I wo
  4. This is another reason why 3D mice are so useful as you can just pan and zoom as required with the other hand. Another lesser known benefit is even when in modal dialog boxes the currently active 2D or 3D plan window can still be moved around using a 3D mouse which can be useful if you forget to check something that's not quite in view before opening the dialog.
  5. Perhaps the pole should be 'how many would ray trace with Chief if it was way faster'? Even though I upgrade PC's regularly and try to get the best balance of overclocked core speed vs number of cores, ray trace has not appealed since we've had PBR. As I use a 3D mouse the rendering on the new PBR + Ray trace on X13 didn't look that good to me as I move a lot in 3D views. I am more interested in the consistent lighting model mentioned and hope that will fix the issues of materials looking so different in standard, pbr and ray trace modes as well as the bleed of colours
  6. if only we could control door inset (like windows) so they can be correctly positioned. Covering up cavity gaps gets onerous as does symbol workarounds for the cases where the position is way off where it would be in practice ;-) Before anyone asks - I've submitted this several times as a suggestion which pictures so just hoping it will make an appearance one day!
  7. Do you have the same text scaling on all monitors and what is the resolution of each? I was testing a six monitor setup recently, not for Chief, some other software I use but I wanted to make sure it wouldn't impact other software. I found mixed text scaling settings caused serious issues with Chief and not just the usual blurry font issues on some monitors when using applications that don't support mixed DPI modes, just system wide life Chief.
  8. If you use a 3DConnexion mouse in multiple versions of Chief Architect and notice it loses any custom settings/speeds when running one version then another (on Windows at least) then read on. Background (for the interested, otherwise jump to the workaround) Technically this is a bug / limitation in the way Chief registers/configures itself with the 3DConnexion software but given how few people this probably affects I've not reported it as its less important than others and importantly there is a workaround. The root cause is due to the way Chief lets the 3DConnexi
  9. I often run a mix of resolutions as I have a lot of monitors shared between my two main desktop PCs and I don't see that particular issue. However I do see an issue with mixed DPI scaling modes meaning some applications and parts of Windows that don't support per monitor DPI awareness can look less sharp on the lower DPI monitors (assuming highest DPI is main monitor) due to the default Windows scaling. Sadly this mixed DPI issue is related to the text scaling preference and not the resolution, so even a 27" 4K monitor set to 150% scaling next to a 43" 4K at 100% scaling (which yi
  10. Another thought is do you have a mix of settings for text scaling across the displays? When I've recently tested Chief with a mix of text scaling across three monitors I saw the same issue. Mixed text scaling settings across monitors is still an issue for many applications (and also parts of Windows itself) due to those applications only supporting system wide scaling, not the more recent per monitor support that was added to Windows.
  11. Same here, its a game changer. One additional benefit for me is when modal dialogs are open the 3D mouse can still be used to move and zoom the previously active 2D or 3D view. It may be my less efficient work flow (part time user is my excuse!) but I've had a lot of occasions when in a dialog box that I've wanted to go back and check something on the plan or view that's out of sight or too small. Now I can still use the 3D mouse without exiting the dialog.
  12. For me it depends on the plan complexity and whether Chief is doing a full double plan type save. I had some plans where Chief was creating 500MB undo files on many edits. With a SATA SSD that was causing obvious small stalls during editing but once I moved to NVMe (or RAM drive) that became the lesser issue but I still often noted a chunk of CPU creating those files (around a second but still noticeable). I found a CPU difference when measured with some dev tools across plans evens producing similar size undo files, so obviously the plan content has a significant impact.
  13. Although undo's seem less likely to be your main issue: Chief writes a lot of these as they are created after every operation. Many undo files are basically a full before and after plan file so can be disk and a lesser extent cpu intensive to create. The best way to check for impact is to temporarily disable undos entirely. Try it to asses the impact and then as suggested set to a smaller number. If undos make your workflow laggy when editing then using an NVMe SSD or RAM drive is the way to go. With 32GB RAM a ram drive would probably be the way to go and the fast
  14. I've not tried a recent Safari, but different browser have different capabilities (with or without add-ins) and some videos are made available from web sites in a form all browsers can download. It's just becoming less common without add-ins for the reasons I mentioned earlier. So it's mainly due to CA and their choice of delivery (Vimeo from the videos I've seen) as part of their web design, but I don't think CA are wrong to go this route as its a simple way ensure good video performance globally and its still easy to still download even if an add-in is required.
  15. I've been frustrated by the lack of inset control on doors (like we have with windows) ever since I started using Chief. I raised a detailed suggestion via support two years ago covering various examples where I need to be able to change the inset either to around the middle or the 'wrong' side as Chief see it versus the opening direction. For workarounds all I do is either make it two way to put the door more in the middle if that's near enough or make a symbol out of it. I did experiment with wall layers and even tiny sections of thinner wall but each created their