Jump to content
You must now use your email address to sign in [click for more info] ×

JayW

Members
  • Posts

    7
  • Joined

  • Last visited

  1. Okay Maybe I didn't describe it that well since english is not my native tongue. But maybe with the video and your confirmation the developers get it and canfix it. Thanks for your help.
  2. Made a short video of it. Just reproduced it on a third machine. ScreenRecorderProject1.mkv
  3. It does not make a different. HW accell on or off, it's the same. Also tested on two different machines with different cpu and gpu (both Windows).
  4. Version 1.9.1: Adding a live filter deactivates blend ranges. Reproduced on different machines by the following steps: New document, add a picture (Pixellayer) Duplicate it and set the upper blendmode to something noticable (Screen oder Multiply) Add blend range to the upper image to make a difference (pull down darks e.g.) Now add gaussian blur to the upper image. As soon as you choose a value in the filter (so the filter has an impact) the blend ranges of the image are ignored. Deactivating the filter or (in this example gaussian blur) yetting the filter impact value to zero brings back the blend ranges.
  5. I also have trouble with OpenCL enabled. When zooming in I get halos - zoming one step out or in even more and the halos dissappear or appear on a different part of another layer. Also after some work the brush shows artefacts. Card: NVIDIA GTX 2050TI. When not moving the brush it dissappears after 2-3 seconds and the halos change. The second issue: Zooming all in and working fast results in more and more lags on the mouse/brush movements. Like using a very old computer. I tried using the most stable studio driver 442.92 and the newest stable release 461.40. Does not do a difference. Also tried WARP as render option. Without OpenCL enabled all that problems are gone.
  6. Another solution: I just uninstalled the NVidia driver and software and installed the studio driver version 442.92. With that driver it seems everything is working fine. Using newer drivers than that will cause Affinity Photo to crash here while stacking with hardware acceleration enabled.
  7. Hi, I have the same issues when started stacking astro pictures on my pc. Yesterday I tried it on my laptop just to habe a cross test and it worked. Back on my pc (i7 3200, 32 GB, geforce 1050 TI) it still crashes, Also reinstalled nvidia drivers. When disabling hardware acceleration and setting it to warp it works. My laptop has simple Intel on-board graphics 620. I am sorry not being able to verify if this error is coming up with Win 10 20H2 since I tried stacking the first time last week when my pc was already updated. And now I just tested it on a thir pc here with the same source photos and it also works, Intel HD graphics 4200. On all three (!) machines Capture One is also installed so it seems like it is a problem related to NVidia hardware or their Open-Gl and not to Capture One.
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.