.png.e7630a08ee6e1c84d06141c3a5feb319.png)
Frozen Death Knight
-
Posts
1,361 -
Joined
-
Last visited
Posts posted by Frozen Death Knight
-
-
-
-
49 minutes ago, PaoloT said:
Looks like the smartest thing to say to someone who just earned one billion overnight.
Indeed. It's one thing to criticise the software, but to say that he has failed after making Affinity a well known and respected brand as the top alternative to Adobe on the image editing front is a bit tone deaf, especially now when he is basically set for life including his family for future generations. Many would kill for that success.
-
On 6/23/2024 at 2:06 PM, Glennsart said:
I agree completely with the need for a larger colour wheel. As a digital artist, I find it very difficult to make small adjustments to my colours using the stock wheel. I'm not sure why it is as it is, but this would be a welcome change. Thanks.
Indeed. That's one thing I think Affinity should take a lot of pointers from Krita as well. Krita is ridiculously stacked with colour features as to make both Photoshop and Affinity Photo blush. If Krita had a better liquify tool, adjustment layers, filters, and image editing tools I would have picked it over Affinity years ago when I was still on the search for a Photoshop alternative.
-
@Wanesty I got some help from a friend who's a coder who helped me go through every step as thoroughly as possible We ended up getting stuck on the final steps with the same errors as I previously posted. From what he said it seems like an issue with newer version of Affinity are using something called "UWP", aka "Universal Windows Platform".
He said that Mono doesn't support it and I needed "Windows.Services.Store.StoreContract.dll" for it to work at all. My friend also mentioned that it is something very Windows specific that no other platform supports and even said that it would be next to impossible to make Affinity run with that requirement.
That's all I managed to find out. I hope that info is of any use, since I don't personally know enough about the subject to make my own assessment.
-
1 hour ago, toddlauzon said:
Ya let's hope Serif is prioritizing it in their pipeline....🤞
The only thing we know is that it is being worked on since last year and that it will be released this year according to the Canva acquisition page. We're already halfway through the year, so we just have to hope it isn't released on New Years. :d
-
6 minutes ago, Bryan Rieger said:
Unfortunately Serif has been hellbent on NOT using the eye for layer general visibility despite using it for layer visibility in the Export persona (Designer and Photo) as well as one or two other places if I recall correctly. While the eye icon is a very well known UI convention for toggling visibility, using a dot (that essentially becomes invisible when hidden) is a hill that Serif seems intent to die on.
Let's see what the new UI developer will decide once that position is filled. My bet is a lot will change UI wise in the coming years (like adding in that eye! :P).
-
11 minutes ago, Luca Ippoliti said:
I just want to have it look good, that's my only priority. The iconography is one of the "least important" points in my mockup - aside from the eye - I agree that it works pretty well as it is. Personally, I think around 80% of Photoshop looks very dated, but not the Layers Panel.
Yeah, agreed. I came back to Photoshop years after I stopped using it and noticed how much the software is starting to show its age. Lots of old limitations that just simply don't exist in more modern programs like Affinity, even if it is more polished in other areas. A typical antiquated tool is building curves in Photoshop that has multiple tools instead of the more streamlined Pen Tool and Node Tool in Affinity that has more contextual shortcuts and baked in options in the top toolbar rather than having multiple tools to do things such as add or remove nodes like in Photoshop and also Illustrator.
Both could learn from the other if you ask me. ^^
-
7 minutes ago, Luca Ippoliti said:
I'll definitely take a look! Thanks for pointing that out!
A tip. Holding down alt while pressing the arrow allows you to open the entire hierarchy or close the entire hiearchy if the parent layer is opened or closed. There is also a shortcut for jumping straight to your selection in the Layers panel, which you can find here (I put it on ctrl+F for muscle memory).
-
20 hours ago, loukash said:
No offense, but as an "ex-Photoshop user" of over 20 years, I definitely wouldn't ever want to go back to that horrible UI again…
I don't hate the Photoshop UI. Besides Adobe being attached to it I actually like Photoshop, or at least old Photoshop until it became way too bloated. I just don't think Affinity needs to look exactly like Photoshop to be good as well. The current UI has issues for sure, but it doesn't need the kind of overhaul to make it look and behave exactly like Photoshop. For instance, Photoshop Adjustment Layers don't have built in masks into their thumbnails like Affinity does. You can't have both icons and mask thumbnails as icons at the same time, so Affinity needs to be different to accommodate for features such as that.
-
I like the pure white icons and text compared to the current UI. The text font is more readable as well, but it still has the issue of the GUI lacking a scaling feature. On anything above 1080p the UI becomes incredibly tiny with limited ways of adjusting it for the screen resolution and size.
I don't particularly care for that redesign of the visibility buttons being moved and replacing the position of the parent-child arrows. The re-arrangement doesn't improve anything functional beyond just making it look exactly like Photoshop. Other software such as Blender and even OS file systems use the current method of putting an arrow for opened and closed parent layers/folders on the left side. There's nothing inherently wrong with the current button placement.
The improved contrast is the main thing I like about this redesign, like having a lighter grey for the layers to contrast the dark panel borders. There is overall a lack of contrast that's been a big issue since V2 when a much darker UI option was added. Replacing the dot with an eye is a good change as well, but a lot of the iconography just looks like a desire to make Affinity an exact clone of Photoshop.
- loukash, walt.farrell, Alfred and 2 others
-
5
-
Personally it's not the fact that layers are being marked as Image/Group/Vector Layers that is an issue. The problem I have is that unless you rasterise them, you can't use a bunch of commands. You can't merge layers of different types together unless you rasterise, which is something that I did all the time in Photoshop. Instead I have to press two commands instead of one to do the same job I used to do.
Cutting something from an image is another good example of where Affinity could just auto-rasterise on command when having a pixel selection. If I wanted the layer to be completely free from edits I would be locking it instead. which is also lacking in Affinity. Adding more locking features and automating the rasterising would do a lot to improve this type of workflow across the board.
-
3 hours ago, Wanesty said:
i think this is something due to mono being missing, you can try to install the wine-mono package (should be named like that on ubuntu)
Does it matter where you put the install?
QuoteRumming /opt/wines/ElementalWarrior-8.14 (wine-7.9-8960-gc12ed146994) in: /home/USER/.wineAffinity
002c:err:wineboot:process_run_key Error running cmd L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (126).
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0024:fixme:mscoree:parse_supported_runtime sku=L".NETFramework,Version=v4.8" not implemented
0024:fixme:mscoree:parse_supported_runtime sku=L".NETFramework,Version=v4.8" not implemented
0024:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
0024:err:kerberos:kerberos_LsaApInitializePackage no Kerberos support, expect problems
0024:err:winediag:ntlm_check_version ntlm_auth was not found. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
0024:err:ntlm:ntlm_LsaApInitializePackage no NTLM support, expect problems
* Assertion at /vagrant/mono/mono/metadata/object.c:4677, condition `is_ok (error)' not met, function:prepare_run_main, Could not set
up parent class, due to: Could not load type of field 'Serif.Affinity.Application:<CurrentMicrosoftStorePrices>k__BackingField' (19)
due to: Could not load file or assembly 'Windows.Services.Store.StoreContract, Version=4.0.0.0, Culture=neutral, PublicKeyToken=null
' or one of its dependencies. assembly:C:\Program Files\Affinity\Photo 2\Serif.Affinity.dll type:Application member:(null) assembly:C
:\Program Files\Affinity\Photo 2\Photo.exe type:Application member:(null)0024:err:mscoree:expect_no_runtimes Process exited with a Mono runtime loaded.
I suppose this is related to win-mono-package since it mentions "Mono" at the end.
-
Well, even if hundreds of thousands switched it wouldn't leave much of a blip on the radar compared to the billions of computer users today. Also, Windows 10 is still very much usable for the foreseeable future, so even the people interested in switching will either learn to dual boot or stay with Windows 10 until it becomes too much of a hassle.
The fact of the matter Is that a lot of people will stay with Windows in some way just because people are used to it. As Linux improves it will become more popular, but it is going to require a significant push and initiative for it to grow exponentially. FOSS have been able to do so sometimes like with Blender, but that took years of planning and dedication to bridge the gap between it and its users to make it user friendly.
After trying Linux Mint I can at least say that I was pleasantly surprised by how user friendly it was, but even then there were pain points along the way like messy audio drivers for audio production and problems finding certain alternatives to software I use daily. It's definitely getting there, but it will take time to make Linux the go to OS for power users. For casual use I would say that Linux Mint is practically there. It did not take long at all to install and download the basic drivers and programs to get a solid base experience.
-
Having every step done separately is good to be able to troubleshoot. I don't think my case would have been solved with full scripts because that final error simply is something wrong with the packaging that the commands can't solve. It is good however to have some scripts as well. I think the first parts could be simplified by having each stage as separate scripts. At least since I know some basic coding I've been able to write scripts on my own that I can reuse for automating certain steps.
Also, I really appreciate the time and work you have put into this project, @Wanesty! Really nice of you to help me out here. I hope it can become a part of normal Wine at some point to be able to make Affinity run easier out of the box!
-
@Martin Klekner The command for changing brush size/hardness is ctrl+alt+L click drag on Windows and cmd+alt+L click drag on on Mac. L clicking while holding down ctrl+alt/cmd+alt will allow you to switch the modes where you can rotate with L click drag instead or change the spacing or shape of your brush tip.
-
@Wanesty Tried your command with --force:
rum ElementalWarrior-8.14 $HOME/.wineAffinity winetricks dotnet48 corefonts vcrun2015 --force
Sadly it doesn't seem to fix the problem.
-
4 minutes ago, Wanesty said:
this has already been discussed here and it happens because the reported wine version is wrong for some reason, this is just a quirk, if you git switched to the right branch then it does not matter and you can do what it says and use --force to force it, like so:
rum ElementalWarrior-8.14 $HOME/.wineAffinity winetricks dotnet48 corefonts vcrun2015 --force
I told it to Git switch earlier during the compiling of Wine. I still get the same error with the package being broken in wine-7.9-etc.
Using "git switch affinity-photo2-wine8.14" gives me this message:
-
Quote
Rumming /opt/wines/ElementalWarrior-8.14 (wine-7.9-8960-gc12ed146994) in: /home/USER/.wineAffinity
Executing mkdir -p /home/USER
------------------------------------------------------
warning: You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.
------------------------------------------------------
Using winetricks 20210206 - sha256sum: 0f21da98811e0bfda16a7d6d6b8e860a9cedbd4e836c7dd9b02f068d3092ee2e with wine-7.9-8960-gc12ed146994 and WINEARCH=win64
Executing w_do_call dotnet48
Executing mkdir -p /home/USER
------------------------------------------------------
warning: You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.
------------------------------------------------------
Executing load_dotnet48
------------------------------------------------------
warning: This package (dotnet48) is broken in wine-7.9-8960-gc12ed146994. Broken since 5.18. See https://bugs.winehq.org/show_bug.cgi?id=49897 for more info. Use --force to try anyway.@Wanesty Above is the full error message when I ran this command:
Quoterum ElementalWarrior-8.14 $HOME/.wineAffinity winetricks dotnet48 corefonts vcrun2015cks dotnet48 corefonts vcrun2015
-
1 minute ago, Wanesty said:
something seems wrong with dotnet, did you have any errors while running winetricks ?
Got this message when trying to open it normally rather than through the terminal just now. Recalled seeing that kind of message earlier when following the Winetricks parts.
-
@Wanesty Okay, so now I am at the stage of trying to run an installer through wine, but I got this error message when trying to launch Affinity Photo 2.5.2:
-
-
14 minutes ago, Wanesty said:
since you have a 32 thread cpu yes! you can increase the parallelization of compiling with the jobs arguments like explained on the guide:
you could set it anywhere from 1 to 33 depending if you want to do something else while it compile(lower number like 4 to 24) or not by maxing it to 33 to saturate the cpu completely
Cool, it worked! Thanks! Now I get the "make install make: *** No rule to make target 'install'. Stop." when trying to do that final part by installing it into the wine-install folder. Do I need to go into the wine-install folder manually before starting this command?
-
8 hours ago, Wanesty said:
it's not all the same text, it's just compiling and you can see it's compiling different things!
first is dib.c next one is font.c then gdiobj.c then icm.c etcas long as you don't get errors or warning then you should just let it running, it took over one hour on my 2014 Thinkpad x240,
on my recent desktop it takes around 10 minutesAll right! I was a bit concerned when it took way longer than 10 min with it constantly rolling with no sign of stopping. I have an AMD Ryzen 5950x so can I do something to speed things up even further you think?
Affinity does not provide quality, it is time to part with Serif.
in Feedback for the Affinity V2 Suite of Products
Posted
I was actively trying to avoid writing in this thread because of this very reason. I could have at least respected bbrother if the thread was just done and over with after a post or two, but still trying to stirr up arguments with people for this long and also refusing to address any of the criticism or questions asked by cherrypicking quotes to "win" arguments is just being ridiculous at this point.