.png.e7630a08ee6e1c84d06141c3a5feb319.png)
Frozen Death Knight
-
Posts
1,074 -
Joined
-
Last visited
Posts posted by Frozen Death Knight
-
-
1 hour ago, BertTheDesigner said:
I have a great solution....get rid of the Booleans all together. Replace it with the shape builder and call it a day.
But booleans are the system that runs a shape builder tool in the first place. Asking to remove them is like asking to remove the engine from a car in an attempt to drive. 🙃
- Jowday, Alfred, Raptor Swire and 2 others
-
5
-
Are you on Windows? Did you download 1.8.5 and go into Preferences -> Tools -> Tablet Input Method to change the tablet input? They just changed it so that Low Input (old WinTab behaviour that Affinity has always had) is the default setting. If you use a decent tablet with a computer and OS that can support Windows Ink or High Input (better precision WinTab that got added in 1.8), you should try those settings and see if that improves your situation.
-
@Mark IngramYeah, I am pretty sure they mean a true fullscreen experience like how in Photoshop you can press F and just hide everything, including the Windows and Mac bars that show what programs you are running, etc.
New View in Affinity does hide everything in the program, but you still have to deal with the big Start button and stuff on Windows as well as the scroll bars and header with minimize, fill screen, and close always visible on your open document. So those things take up extra screen space compared to just having a true full screen view.
I really like joeyoshi's suggestion of being able to enable true fullscreen per document window with one window having all the important panels open with the other filling the entire screen to get a full overview of your work.
-
Well, unless you can somehow show people what exactly the problem is, it is hard to help you. Are you able to record a video of the slowdowns? Which effects and filters are giving you trouble? Is there a way for others to replicate the issue as well to confirm the issue of slowdowns?
-
Here is the latest build. For future reference, the latest Beta build is always pinned at the top of the Beta forum for each program and platform.
EDIT: Since I am home now, I can give a more descriptive explanation on how to change the input settings.
To find the tablet input settings, go to Edit -> Preferences -> Tools -> Tablet Input Method. The list has the options Low Precision, High Precision, and Windows Ink.
For fixing your Wacom tablet using Windows Ink, open Wacom Tablet Properties, pick Pro Pen -> Application: Photo -> Calibrate -> Use Windows Ink.
Hope that helps! 🥳
-
Download 1.8.5 and go into Preferences. Somewhere in those options there is a new setting where you can choose precision input for your tablet device; legacy (low precision) WinTab, high precision WinTab, and Windows Ink. I suggest trying them all to see which one works best for you.
P.S. If you use Wacom you need to go into your Wacom settings and enable Windows Ink for your pen in all Affinity programs. Otherwise the Windows Ink option will not work at all.
-
Are you talking about brushes with textures? If so, go to the Brushes panel and click in the upper right corner where you can import brush packages into Affinity. I believe you can also drag and drop directly into the program, but I might be wrong.
-
5 hours ago, Blende21 said:
The logic behind „I have 500 GB of crap on my c- drive, and can’t move ANY of it away“ defies me.
And - haw, haw - I have more than one SSD as well. But 1) on a MacBook Pro there is no easy way to replace or enlarge the primary SSD, 2) it runs at above 2.000 MB/s, so everything that has to do with operations (incl. caches) better runs there / runs better there, 3) very „creative“ program installations sometimes lead to issues, at once or when updating.
IMHO documents can go to a secondary SSD, or even better to a network server. Usually we work on a few files at a time, which is quite ok at 500 MB/s storage speed with an USB3-SSD, or even at 100MB/s LAN speed. Just takes some prior thinking and doing into the own storage deployment.
Being condescending to excuse bad design will not give you any points, I'm afraid.
Also, I don't use Macs while working and I do not care about what your Mac can and can't do. Plus, you talk like you have multiple people working together with you with multiple computers. I am one guy with one PC with very few options but to restructure everything from scratch to make this work. Assuming everyone has the same options as you is just plain arrogant.
-
I agree with @Jowday in spirit. I think it is a cop-out to say that the user has to adapt to the program when the program is a clear outlier among its peers. Not being able to direct the cache in a business where cache data can fill a lot of disk space is just poorly thought out. Having to change your entire infrastructure for handling data for a single program which will take days to restructure is just a lot of unnecessary inconvenience. Pretty much every program I use has solved the cache data issue, so why can't Affinity?
I have been able to adapt to a lot of Affinity's shortcomings and I think the devs have done a pretty decent job at addressing some of the core issues I've had lately with good communication on their end. I am sure they will understand my point and address this eventually. I am however not going to restructure everything on my PC from scratch when I have had no problems in the past. It is not worth the time and effort just to make this single problem go away. Sorry.
-
2 hours ago, Blende21 said:
Usually the primary drive has by far the best performance. On my MacBook Pro the internal SSD runs on appr. 4-5 times the speed of an external USB 3 SSD. Only an external Thunderbolt 3 SSD would be a match, for a prohibitive price.
Because a Cache means swapping data a lot, speed is important. I think it is logical to place the Cache on this drive.
if you can’t upgrade your SSD, can’t you remove stuff from the primary drive ?
I have more than one SSD you know... Affinity is using the smallest one of them as well, since I originally installed Windows on it and then later installed a secondary SSD years later. You honestly think I will completely reinstall Windows and move all important files (over 500 GB) from both SSDs elsewhere just because Affinity can't switch drivers for cache storage? Absolutely not.
-
This problem has been driving me nuts lately. Because of my hard drive only having a couple of GBs at most to work with since I use a lot of programs, I have come to rely on my other hard drives for storage space and only let the essential stuff run from my SSD. However, because I can't for some reason change the cache directory during a work session, I am constantly bombarded with this message since Affinity keeps using up my main SSD.
Because of this I am constantly having to reload my projects. While nothing really gets lost since the program does successfully save, it is still a very, very annoying thing to have to deal with. It also doesn't help that because of lack of memory that my web browser keeps shutting down, so the problem keeps spreading because of the lack of a cache directory feature built into Affinity.
I hope you consider having this as a high priority. Files can get quite big when working, so it would be to most people's benefit.
-
-
@Kochab You can customise your render size by typing the number you want and then add "w" or "h" for width and height respectively. For instance, "1080h" is a full 1080p HD image with 1080 pixels in height. "720h" is 720p, etc., etc.. You can also break the image ratio by typing something like "1080w, 1080h" which produces a 1080x1080 pixels square image, even though the original may have had vastly different proportions.
Agree about half size and third. Would love to be able to just type "0,5x" just to get half the original size when rendering.
-
The latest one I like a lot better. The textures blend nicely together instead of just being laid on top and looking the same across the entire image. Nice work!
-
Wanted to work on something a bit lighter with finished lineart inbetween some heavier projects, so I drew Alita from Alita Battle Angel. Really digging some of the brushes that got added in 1.8, which I used for this piece. ^^
https://www.artstation.com/artwork/8eB8E6
-
P.S. The thing I was taking about was the side buttons that some tablet pens have. The regular drawing with pen pressure works fine, but it's the side buttons that I have had problems with in the past when trying to emulate R click or L click as if using a mouse. The current live iteration (aka High Precision) doesn't allow you to do L click with no pen pressure, but for Windows Ink it works. Hope that clears things up!
-
12 minutes ago, Mark Ingram said:
Do you have Windows Ink enabled in your Wacom Properties? Without it, your pen will just behave as a mouse (hence no pressure).
Yep. I had it deactivated in my Wacom Tablet Properties at first since the Beta and official releases share the same settings, but once I activated Windows Ink there it all worked perfectly fine afterwards.
-
Tried the latest build with the new input precision list that was added. A nice little surprise I found was that Windows Ink allows you to use L click on the side buttons of your tablet pen again, so you are able to produce brush strokes with no pen pressure like you used to with Low Precision. High Precision on the other hand does not work, so it is the only one with this regression. Ctrl+alt+L click works with Windows Ink, so I am overall pretty satisfied with using this method for my tablet input.
A pretty good patch overall. Keep it up! 🥳
-
20 minutes ago, Joachim_L said:
SAVE AS should work too if you write .aftemplate at the end. So maybe just renaming your existing templates could work? Never tested this myself.
Didn't seem to work, but anyway, @Old Bruce solved the problem for me. Was a bit confused where the export template option was at first, but I managed to find it a few rows below the regular export operation.
Thanks for the help both of you!
-
Just now, Old Bruce said:
Are they exported as .aftemplate files?
How do I do that?
-
Been trying to create templates that I can use when working on new projects, but of some reason I can't get them to show up in any Affinity program for some reason. Here's a video showing the problem.
Some help to fix this would be much appreciated. 🥳
-
-
50 minutes ago, MEB said:
Regarding the second point, instead of using the merge selected command, simply rasterise the parent layer. The child layer is not independent from the parent layer thus doesn't count as an independent layer to be merged with other layers unless they are siblings (children of the same parent).
Well, yes, I can do that. However, that also means rasterizing all the layers and masks clipped to the parent layer at the same time, which is not something I want. I want to be able to run merge selected so I can rasterize the parent layer and one clipping layer at a time. I am able to do this when I unclip the clipping layers to run merge selected, but not when they are clipped, since you can't select the clipping layers and parent layer at the same time, as previously mentioned. Fixing the issue of not being able to select both at the same time would make this possible.
-
@MEB Yes, you are right that the masking layers don't get transformed despite being selected in the Layers panel. However, I disagree that not being able to select the clipping layers and parent layers at the same time is consistent. From the user's point of view it looks very weird when you are able to shift/ctrl select everything except the clipping layers, especially when you lose your parent layer selection if you try to select a clipping layer.
Also, I would argue that not being able to liquify a mask layer that is clipped to a parent layer as being weird when it looks like you can select it in the stack. If that's the case, why are you then allowed to liquify both the parent layer and masking layer at the same time when you unclip the latter from the former? If you don't want to liquify the mask as well, then why not just let the user manually deselect the mask from the selection stack or simply lock all edits of said layer through Edit Lock? Still, I may concede on the point that adding this feature to masks might be a feature request rather than a bug.
However, my next point I definitely don't consider as a feature request, but as a bug. Look at this video for example. I can select layers unrelated to the clipping layers themselves and even liquify them at the same time, but when I try to select the parent layer I can't. It is a very odd limitation since you can select everything else at the same time, with the only exception (that I know of) being parent and clipping layers. Not being able to select clipping layers and parent layers at the same time while simultaneously allowing selection of other layers is just really, really awkward.
Shape builder tool
in Pre-V2 Archive of Affinity on Desktop Questions (macOS and Windows)
Posted
Yeah, they really need to fix those. Though, I do hope that a shape builder tool arrives shortly after those are fixed. Would make for a good one-two combo.