• Posts

  • Joined

  • Last visited


31 Excellent

Profile Information

  • Gender
  • Location

Recent Profile Visitors

1720 profile views
  1. Yes it's a rare system required for a couple of demanding tasks, however further tests show the same high VRAM use with Chief on another more regular PC with a couple of smaller monitors when using layouts with non RTRT PBR views (viewing and printing). I reported this to support a while back and they appear aware and suggest the logical approach of splitting up content over multiple layouts or PDFs. I suspect its probably an optimisation issue with how these are generated on RTX capable systems and potentially the driver, as using GPUs without ray tracing worked fine with the same content and much less VRAM on both the second system and my main one.
  2. My main PC has 6 x 4K monitors (2 GPUs) which needs more VRAM generally but the Chief issue is with layouts and two of those containing a number of PBR views (RTRT disabled). During print to PDF the VRAM use rises and after saving the PDF file it rises again and for several of my layouts then generates a crash in Chief. This is the last capture before it exceeds 12GM VRAM on the applicable GPU: After X13 crashes and the PC recovers it drops back down to 1 to 2 GB. I can replicate this on three PCs and as some of my software related dev work is graphics related I've checked with applicable debug tools and they show the same use and related to Chief. I am not referring to the AMD game related VRAM issues that are hotly debated as they're quite clearly designed to favour AMDs higher VRAM GPUs over Nvidia's and as I am not a gamer that's not an issue for me. If not using an RTX card for Chief then the VRAM usage remains within lower limits so as per my earlier post it could be a driver or Chief related issue. I've been running background diagnostics on two PCs since upgrading them to use at least one 30 series card and both use more VRAM than non RTX cards on several graphics related applications. I've got a lot of work on at present so cannot dig deeper but it does appear VRAM is being (mis)used more in current RTX drivers/software and with larger and higher DPIs monitors becoming ever more prevalent I thought it worth a mention.
  3. I agreed with @Kbird1 on the GPU, this shows the relative performance of some cards mentioned: If you try some of the other 30 series cards in that site you'll find in general the performance gains within the 30 series tails off past the 3070 and you pay a lot more for not much more performance, for example even the 3090Ti scores only 29456. In my case I run a lot of 4K monitors on the one system across two GPUs and wanted to ensure the VRAM wasn't a limitation so decided on the 3080 12GB (not the earlier 10GB variant and mid way between 3080 and 3080Ti in performance). This was the first card other than 3060 that has 12GB and not too much more above the best performance vs cost point. Interestingly one of the GPU issues I've encountered within Chief relates to exhausting VRAM on the GPU, so although this could be an issue with the GPU driver and/or Chief code, the extra VRAM means this happens less frequently than it would with the same monitors and less VRAM.
  4. Although there do need to be improvements to delays when files are missing, I would like the option to keep track of what files (with full paths) are being referenced and not just what's missing to keep things well managed as I suggested here: I can see from using developer diagnostic tools that Chief goes through a lot of locations trying to find referenced files which is great, but it means even with good practices the odd unexpected location can creep in which in turn leads to more cases of missing files when upgrading Chief, new PC etc and then more of these slowdowns.
  5. I always go for the highest DPI I can get for the size monitor I deem most suitable for my work and set text scaling as required for good UI size fonts as this gives the sharpest looking text and details and reduces eye strain. Text scaling on Windows has improved vastly over recent years and support for this font scaling in modern applications is now generally good and even for mixed font scaling across multiple monitors its getting a lot better. It's only older or poorly written applications which will have a fuzzy look when using Windows text scaling, everything else will benefit from more pixels per character/inch. As most 43" are only 4K resolution (102.5 DPI at 4K) I am currently using 3 x 32" 4K and 3 x 27" 4K (recently upgraded from lower res) which are 137.7 DPI and 163.2 DPI respectively. These are at 125% and 150% text scaling which gives near identical real world text size for the same font as 137.7 /125 * 150 = 165.24 and text on both is notable sharper than the 96 DPI monitors used to aim for. I work mostly in software development and appreciate Chief users may benefit from a 43"+ monitor, but sharper text and details is a benefit that's often overlooked. I recommend two or even three 32" 4/5K monitors to friends when asked about higher end setups (three is nice with one in the middle). I have tried 43" and larger but the lower DPI at the moment and large size make multiple monitor setups difficult and impacts off angle colours/brightness even with IPS screens, whereas arranging smaller monitors around you gives higher DPI and a more consistent focal length which is easier on my older eyes.
  6. When using font scaling above 100% characters should be crisper not fuzzy as they're made of more pixels. However sadly some application don't correctly support scaling properly and hence Windows just scales all the existing GUI which gives it the fuzzy appearance. This can be overridden on a per application basis but if the application doesn't allow larger fonts to be used for its GUI then this reverts to the original small fonts issue. I currently run 4 x 32" 4K monitors at 125% scaling plus a couple of 27" 2560x1440 at 100%. This is so I can develop software and easily test for scaling issues. This give a worse case scenario of mixing scaling settings but since I started doing this a couple of years back I've noticed that many modern applications handle non 100% scaling fine and the best manage the mixed scaling (dragging between different monitors with different text scaling) as well. For my other PCs/laptops I always go for all high DPI monitors as the sharpness is so easy on the eye. I've tried 40 - 45" monitors but they were all 4K resolution so for me that size is one for when 8K is a viable option.
  7. I think you need to check today's date
  8. Most terrain parts are missing from Interiors so a toolbar is probably not needed and that could be the difference you are seeing generally. I use Premier so cannot confirm but you can verify with CA Support and also check the product comparison here:
  9. I've developed various software for desktop and web that has had the challenge of rendering rich text within fixed areas without cropping or wrapping at different points when rendered on devices with different screen DPIs, font metrics, browser vs desktop rendering and different OSes. It's true that problems often originate outside of the software presenting the issue, but there are many cases where this is true in software and applications need to work around the problems as I'm sure CA has done for other issues. There are various approaches depending on what is important for the application, such as retaining wrapping locations for multiline text, retaining box size (so shrinking text/spacing) in addition to preventing character cropping. It's a problem that can be solved although it can be harder than it appears depending on the level of low level access to the rendering system/library used. For the software I worked on in most cases text boxes were effectively resized by small amounts automatically to retain wrapping and avoid character cropping but without impacting the saved size unless edited (to avoid needless saves). It was also often useful to have an additional small margin inside the box that wasn't considered part of the calculated sizing after editing, but could be used during rendering as this would avoid overall text box size changes where users wanted them to be accurately positioned or aligned
  10. I always limit Chief to 3 of those monitors all using the same GPU and that's what I've always stated to support but this is always ignored. I see I've been down voted for stating what has happened with my support cases and given I managed the development of complex GPU related software for global corporations and have offered virtual machine images to prove my case with GUI issues (not 3D rendering ) and got a response saying Chief doesn't work in virtual machines. I don't know what else I can do - there seems to be a blinker vision with some issues.
  11. I have 6 monitors and the odd issue with X13 but disconnecting one of my two GPUs isn't an option as each only supports 4 monitors. Interestingly some of the issues aren't related to the dual GPUs (lifetime in software development often using GPU rendering) but support just see the multiple GPU config and that's end of case.
  12. 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 the old save as functionality. Such services also have an interest in avoiding downloading to allow videos to be updated and in some cases adverts included dynamically. The last time I checked CA moved to using Vimeo, but the download issue with such services can be worked around by using one of a number of browser extensions that basically download all the stream and then recreate a full video file which can then be saved to disk.
  13. 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.
  14. 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 work at. I similarly have glasses just for monitor distance to use when not wearing contact lenses. Both options give me sharp vision on my 6 x 32" 4K monitors (so large area and small text) something neither bi-focal glasses with the height issue and just two fixed focal lenses, or varifocal with distortion at the edges could do. I also found a significant drop in eye fatigue with this approach. I buy these various non full correction glasses online at sub $40 (often around $25) a pair as my optometrist said their systems weren't really geared up for anything other than my normal full correction/varifocal glasses and also extremely expensive.
  15. 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.