anonymous
Members-
Posts
17 -
Joined
-
Last visited
Recent Profile Visitors
805 profile views
-
Davidmum reacted to a post in a topic: aero not activated; no startup; 1.5.0.39
-
KevinBet reacted to a post in a topic: aero not activated; no startup; 1.5.0.39
-
We are about 170 spread over 6 different locations. People also switch between locations as the workload requires. And they need "their" software, settings, data etc. wherever they log in to the system. Keeping software, patches, settings, data etc. up-to-date on each single hardware machine was a PITA in the past. So we decided to switch over to a Terminal-Server-VM some years ago where all employees work on one single machine. This was the best decision we could do and we can not revert this because of one software. For the future we plan to put GPUs into the VM-nodes so that VMs also benefit from GPU-powered rendering. But ATM we have none.
-
It would be great if you could add an option to disable the animation. Other Software (GIMP, PS) also provide such a feature. I fully understand that this "problem" is not on top of your list. For the moment it is enough for me to know, that you are willing to implement it in the future. So i keep monitoring the progress of your software. It would be great, if you could leave a post here, if it is done.
-
Ok. So far, so good. But doesn't this huge CPU load point to an error in the implementation of the WARP software emulation? I can't imagine why drawing a dashed line should be this cpu intense - even in software emulated mode. Will you implement the suggested option to change the animated dashed line to a non-animated one in future releases? (This is the last show stopper preventing us from buying the software, as we only have VMs in our company.)
-
1. The step to wait 20 seconds was only to be sure the full CPU useage appears. I did *not* experience a delay. In my case a large increase (to about 30%) appeared instantly. And then a further slow increase to about 50% appeared in the next 10-15 seconds. 2. ATM I can only test via RDP. I'll try to test bare metal as soon as i can and report here.
-
Tested v1.5.0.39 on Windows Server 2008 R2 x64 (via RDP) with 10 cpu cores and >24 GB RAM. Steps to reproduce: 1. create a blank image 2. make sure "View" -> "Show Pixel Selection" is checked (BTW: missing german translation: should be "Auswahl anzeigen") 3. select some area 4. wait 20 seconds 5. see huge CPU load (30% - 50%) in taskmanager 6. uncheck "View" -> "Show Pixel Selection" 7. wait 20 seconds 8. see normal (=0) CPU load May be the issue is not directly related to Affinity Photo and has its root cause in RDP. But even then a CPU load of at least 30% (up to 50%) of a 10-core-machine for only animating lines seems to me like a bug and prevents Affinity Photo from being used remotely. GIMP and Adobe therefore have the option to change the animated selection to a non-animated one. This is what i also suggest for Affinity Photo: It would be nice, if the option "Show Pixel Selection" could be changed to "Animate Pixel Selection" (german: "animierte Auswahl"). This would remove a show-stopper for introducing Photo in our company. (BTW: I doubt that fully hiding the selection can be beneficial at all.)