New version 14.1 many problems solved by turning off hardware acceleration

Johnny Eriksson

• 2021年03月10日 19:36
• 編集済み

I got many problems after updating to 14.1. Pictures 100% zoomed in. Pictures not showing up in viewer. Exporting picture hangs program and in the end could not do anything at all.

It all went back to normal when i turned off hardware acceleration.

I use a Asus zenbook pro 15 laptop with an Nvidia GTX 1050ti gfx card.

0

• 

  Bill Coley

  • 2021年03月11日 21:22
  • 編集済み

  Prompted by your post in this thread, Johnny, I turned off hardware acceleration in my CO installation, and the result was the same as the one you report: the end of the zoomed-in images problem. In fact, I've since turned hardware acceleration back on without the zoom issue recurring. I don't know about any cause-and-effect, but changing the hardware acceleration setting briefly was enough - in my installation, at least - to resolve the zoom issue permanently. So thank you very much for the tip!

  (FWIW, I've not experienced the export issue you report, so I can't add to that piece of the conversation.)

  0
• 

  Class A

  • 2021年03月13日 14:02

  FWIW, I don't consider turning off hardware acceleration as a solution. In my view, users should still report the issue, even though they found a way to circumnavigate a problem. Hardware acceleration should work and speeds up C1, so if it does not do its job without introducing problems, C1 support should hear about it. 

  0
• 

  Permanently deleted user

  • 2021年03月16日 20:11

  On or off Hardware Acceleration doesn't change Viewer opening images at 100% for me.

  This needs to be fixed. How does technical support hear about this?

  0
• 

  Permanently deleted user

  • 2021年03月18日 21:18

  Excellent response from a Capture 1 Technical Support agent:

  I consider this a bug and I've filed a report with all the details for our R&D team to audit the issue. I will place your ticket on-hold and will get back to you when we have a response from our engineers or if we need any more information for this report.

  We also cannot guarantee that this bug will be in the next service release, but rest assured that it has been reported and will be looked into and our developers will do their best to roll out a fix as soon as possible.

  0

投稿コメントは受け付けていません。