Don Samuels

As an example, I turned on debugview.exe and when I hit ctrl-s, I got this: 00000017 296.88165283 [2776] Error 12 in function AudioDeviceProperties::GetNahimicFormFactorOverride: Unexpected type 00000018 296.88168335 [2776] Error 12 in function AudioDeviceProperties::GetNahimicFormFactorOverride: Unexpected type 00000019 296.88241577 [2776] Error 14 in function DataSystem::GetProductDesc: Product infos not found 00000020 296.88244629 [2776] Error 14 in function DataSystem::GetProductDesc: Product infos not found 00000021 296.88714600 [2776] Error 12 in function AudioDeviceProperties::GetNahimicFormFactorOverride: Unexpected type 00000022 296.88717651 [2776] Error 12 in function AudioDeviceProperties::GetNahimicFormFactorOverride: Unexpected type 00000023 296.88775635 [2776] Error 14 in function DataSystem::GetProductDesc: Product infos not found 00000024 296.88778687 [2776] Error 14 in function DataSystem::GetProductDesc: Product infos not found 00000025 362.01596069 [2776] Error 12 in function AudioDeviceProperties::GetNahimicFormFactorOverride: Unexpected type 00000026 362.01638794 [2776] Error 12 in function AudioDeviceProperties::GetNahimicFormFactorOverride: Unexpected type 00000027 362.01699829 [2776] Error 14 in function DataSystem::GetProductDesc: Product infos not found 00000028 362.01751709 [2776] Error 14 in function DataSystem::GetProductDesc: Product infos not found 00000029 362.51550293 [2776] Error 12 in function AudioDeviceProperties::GetNahimicFormFactorOverride: Unexpected type 00000030 362.51605225 [2776] Error 12 in function AudioDeviceProperties::GetNahimicFormFactorOverride: Unexpected type 00000031 362.51800537 [2776] Error 14 in function DataSystem::GetProductDesc: Product infos not found 00000032 362.51907349 [2776] Error 14 in function DataSystem::GetProductDesc: Product infos not found

I am having issues with Affinity Photo crashing or hanging on my windows 11 machine. This is happening when I save or close a window. Is there a way I can invoke Affinity with some sort of debug flags to send to you to help debug? I am on 1.10.5.1342

Because one of the main drivers on buying a laptop with an Nvidia Gforce was to get the hardware acceleration for Affinity.

While the laptop is less than a month old, and was customized by Xoticpc, so that presumably they got the latest drivers on themselves (as opposed to letting Windows do it), I am going through to make sure there are no updates since the laptop shipped. I hope this works, otherwise I have to ask if Affinity does not have bugs in the classes they use for hardware accel.

I moved the file to my old Windows 10 Laptop and did the merge visible and no artifacts were created.

I bought a gaming laptop with an Nvidia gpu to speed up my affinity work. Unfortunately it is Windows 11. My affinity version is 1.10.5.1342. When I do a Layer->Merge Visible, I get artifacts created like this: This renders my use of the new laptop for processing useless. Please help.

I am trying to understand the adjustment curve layer that the built in astrophoto stack feature generates. When the stacking is done, there are two adjustment layers. First is a levels adjustment, and then a curves adjustment. When I click in the little white box on the curves adjustment, I get this: The histogram is barely visible at the bottom. Then when I click on the box next to where it says master: and choose one of the selections (by the way what is that box called?) This now lost all of the adjustments and you can not get them back. Behavior is the same on Windows 10 and Mac OS. Windows 10 is at 1.10.5.1342 A few questions 1) if I want to take the curve as Affinity thinks is best, why is the histogram on the curve box so low as to not be useful 2) the box where I clicked grey, how come that kills the adjustments that Affinity applied? 3) what is that box called? When I hovered on it I did not get a pop up? 4) is there a technical documentation that explains each of the windows like adjustment curves? Meanwhile, what I was doing is capturing M51 (Whirlpool galaxy) with a 200 mm lens and a equatorial mount. Did not spend much time after stack but quickly got something that tells me it will be usable as I learn more: Thanks Don

taking off the hardware accel did it for me. Lap top is old and no new driver updates.

I would like an option to undo rotation if you take pictures with just a dslr without an equatorial mount. For now I will try deepskytracker, but I trust affinity and know nothing about the group that has wrote the other software. And I am thinking of buying sky-tracker for xmas. Thanks Don

The color is also based on which way you drag Turning off the hardware acceleration seems to do it. Hopefully I won't see too much degradation in performance.

I have switched over to my wife's mac and am doing the exact same curve procedures without issue

curve001 is before I drag, and curve002 is after. You can see the whole picture starts to turn magenta.

here is my system info: OS Name Microsoft Windows 10 Home Version 10.0.19042 Build 19042 OS Manufacturer Microsoft Corporation System Manufacturer HP System Model HP Pavilion x360 Convertible 15-br0xx System Type x64-based PC System SKU 1KT69UA#ABA Processor Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz, 2712 Mhz, 2 Core(s), 4 Logical Processor(s) BIOS Version/Date Insyde F.45, 5/20/2019

Back in September I posted I must have some default set which is making curves mis-behave. I am on Windows, and my wife is on Mac. We are both at 1.10.1. When she does layers->curves, the popout window that comes up on the Mac shows rgb and grey on the histogram, and with the settings at rgb and master, when she drags the curves or uses picker, it drags all the colors, i.e. grey. When I bring up the same image on Windows, the popout window only shows the grey histogram but when I drag, I seem to drag either the R, G, or B color. I was notified it was a bug. I am now at 1.10.4.1198 and no fix. As I am trying to follow one of your youtube tutorials that make extensive use of curves for astrophotography, I am unable to do this on my windows laptop. Help!!

I am now at update 1.10.4.1198 and it is still there.