awakenedbyowls
-
Posts
704 -
Joined
-
Last visited
Posts posted by awakenedbyowls
-
-
I'm having no end of issues with both the Windows and iPad versions
Terrible lag sometimes on both - like on the iPad when I go to the home screen it's blank for a few seconds
On Windows I'm pressing A A A A and it's highlighting the nodes and then immediately unhighlighting them again
All the time I'm going through these irritating procedures to get the software to work
Could be something to do with my new RAM cards that don't seem to be working well with my set up
I also haven't updated to 2.3 on Windows yet because I'm worried it might cause issues when I have a deadline to meet
I hope 2.4 addresses some of these issues because right now I'm not impressed with V2
I'll try to elucidate further when I have time but I'm busy trying to finish a design for a deadline while working and (now) recovering from a bout of flu
-
3 minutes ago, R C-R said:
I don't know, but it may become more obvious if you can post a screenshot showing whatever part of the UI has the focus when you try using CTRL-Z. For instance, is it in a text entry field, a studio panel, etc.?
I'll see what I can do - just feels like before CTRL+Z was a useful shortcut that was used heavily so not sure why I'm hitting dead ends with it sometimes - maybe something I'm doing but still I feel it should just overrule everything
-
4 minutes ago, R C-R said:
Is whatever thing you did that you want to undo shown as a step in the History panel? If not, then it isn't a step that has been completed & thus can't yet be undone.
So why doesn't it just undo the previous step then? Maybe I want to undo several steps too
-
Too many times I'm clicking CTRL+Z - clicking clicking clicking and nothing is happening because I'm stuck in a text box for the opacity or something
VERY frustrating !
Why doesn't CTRL+Z just override anything I'm doing and just go back a step - that's what CTRL+Z is for - if I mistakenly CTRL+Z then I can just Shift+CTRL+Z
A few little things with the V2 I'm finding seem to have introduced some frustration
Another one is CTRL+J when I want to copy a parent group but somehow I always seem to end up duplicating a layer within the group because things don't seem to be registering sometimes when I click on them
I'm on 2.2.1 because I don't want to update to 2.3 until I finish this design project I am on - too scared of new bugs being introduced now
-
8 minutes ago, MEB said:
Hi @awakenedbyowls,
The stuck layer is a glitch in the UI. Does it happens frequently for you or it's just occasionally? Are you able to reproduce it at will? Do you know in what circumstances does it happen/gets stuck? Are you drawing with your fingers or using an Apple Pencil or similar devices? I can't reproduce it at the moment but I will keep trying.
Regarding the pink lines, go to the Snapping Options (the small button on the right of the Magnet icon in the top right of the interface) and change Candidates to Immediate layers or Immediate layers and children (anything but Candidates list).I'll keep an eye out for what might be causing it and get back
I have set the Snapping Options to what you said - see how that affects things but it should matter if Snapping is turned off
-
8 minutes ago, walt.farrell said:
You've posted to the macOS bugs forum, but your topic title says iPadOS which has its own bug forum.
A moderator will probably move this for you.
Yes I realised after I posted here and edited it - I figured it would just get moved - which it has
-
Not sure how else to describe it - keep getting this (see photos)
A semi-transparent Layer from the Layers Panel is stuck there - if I close the file and go back in it gets rid of it (Correction: I have to close the program down to get rid)
Also having problems with pink lines tracing round curves and that only way I get get rid is to refresh the file - not sure if related
5th Gen iPad Air
Sorry if I might have put this in the wrong subforum - please move it if I have
-
6 minutes ago, NathanC said:
In the Snapping settings menu, disable 'Show Snapping Candidates' or change the Candidates dropdown to an option which isn't 'Candidate list'.
https://affinity.help/designer2ipad/English.lproj/pages/DesignAids/snapping.html
What three modes are you referring to? If it's the node snapping options (The magnet icon on the left hand side of the context toolbar) this only ever has 'Snap to Geometry' enabled by default for me, I can turn on the other node snapping modes which will persist as on for the remainder of my app session If I create new documents, and when I restart the app it just defaults to 'Snap to Geometry' again. It doesn't look like the default can be changed currently.
Still figuring out what's causing this - it might be something to do with that but I usually work with all snapping off by default until I want snapping
The other snapping mechanism - I've gone through the tutorials ages ago but it still confuses me a bit - I need to sit down with it one day and just go through all the options again
I'm not sure if some of these glitches are caused by me having lots of layers and cluttering up large files (I'm working to keep things tidy) but in any case I'm having an annoying problem with this file I'm currently working on which is refuses to allow me to select layers with the Pencil - so I have to manually go through all the layers until I find the right one - I've copied and pasted layers into other files to get round this problem and it's still doing it and causing me a lot of frustration as are the following glitches which may be just my drawing gloves hitting a button or something?
- when selecting nodes with the Pencil the app has an annoying habit of un-highlighting all the nodes and I have to then go into Layers to find it the layer
- when deleting single nodes sometimes the app goes into warp drives and deletes a whole selection of layers forcing me to use CTRL+Z to get them all back
-
I don't know what's going with this app or if it's something I'm doing but it seems a little bit glitchy - and it just keeps on tracing pink lines round random objects and the only way to remove them is to come out of the file and go back in
And why is the Node Tool set to have three modes on by default all the time? I'm constantly having to turn the damn settings off because most of the time I don't want to use these feature - surely off by default would make more sense? Or is there a way to set the default I expect there probably is
-
Cheers - that works (sometimes_
Other times not .. ?
Looking into this - it's been some time since I picked up the Affinity suite
-
Must be either a bug or more likely something I'm not doing right?
I've always struggled a bit with getting the iPad app to deselect everything - especially using finger touch it's nearly impossible then (need the pencil for drawing stuff though anyway - just one time I opened a design to show somebody without having the pencil and I could get it to deselect an object
-
I'm working on a design and I can hardly see it for the app tracing round objects - normally I used to be able to get rid of these things by selecting the Move Tool but the only way to get rid seems to involve closing the file and reopening - repeatedly
I'm try to resize a group of objects and it keeps selecting other larger objects round it so I can't see properly !
CTRL+D works on Windows but on the iPad I'm stuck with this mess - how do I get the app to un-highlight all objects?
-
Just opened up AD there to find it inviting me to update to 2.2 again and I was thinking this bug had returned and I hadn't fixed it - only to find this time it is an actual update ! literally the day after I came on to finally figure out this bug to find out there wasn't actually an update
-
4 minutes ago, PaulEC said:
Have you tried going to "%ProgramData%\Affinity\Designer\2.0\" as per Sean's post? (You seem to be looking elsewhere!)
Yes I misread Program Data and Program Files
This has resolved the issue now cheers
-
On 8/3/2023 at 9:15 AM, Sean P said:
Hi earl_grey,
Unfortunately the 2.2 beta release was accidentally released to the wrong group for a short while, which is why you're seeing this message. For EXE users this update was never actually available on the website so thats why its currently available. If you go to %ProgramData%\Affinity\Designer\2.0\ and delete the JSON files that are there, you will not get the prompt on launch of the app for the non-existant update.Not seeing these JSON files - and I've looked in two locations (one of which might be Affinity 1.0 I don't know) ?
-
I expanded a pixel layer so that the pixels were the size of stamps - I guess when you resize a pixel layer slightly it will resample so that it maintains the pixelation of the document and in this instance the pixels happened to be massive
Don't have an issue with that but I would have thought it would have maintained the cubic form rather than going all out blurry ?
-
4 minutes ago, GarryP said:
If you have Photo, the Pixelate Filter should do the job, but it has a permanent effect on the layer you apply it to (no Live version yet).
Yep - that does the job - cheers 👍
-
I'm playing around with effects trying to draw a UFO and I discovered this interested effect just by blowing up the size of the Pixel Layer such that the Pixels are really big - problem is when I Export the File to .jpg the software appears to Blur it thus ruining the effect
Is there a possible workaround for this that allows me to maintain the blocky pixel effect ?
-
53 minutes ago, walt.farrell said:
But even though you try, terminology may be imprecise (e.g. what do you mean in this case by Vector Layer), or you may use it incorrectly.
A picture would have taken you about three minutes, or less, to prepare, and could have saved several days of discussion.
What do Affinity mean by Vector Layer ?
If I create an object the software creates a layer contain vectors so what is that if it isn't a vector layer ?
It would also have been easier if people could just communicate with language rather that constantly complaining about not having pictures - ie. just ask me for more details maybe - if you don't want to help because there's no screenshot or video then don't help
-
1 hour ago, R C-R said:
What specifically do you mean by "underneath"? Nested, not nested, clipped, or maybe something else?
(This is exactly the sort of thing that a screenshot or example file can make 100% clear!!!!)
Whatever happens when I drag the pixel layer into the vector layer or object layer - that kind of underneath
The issue here appears to be inconsistency in how effects from the parent layer affect the child layer underneath
-
13 minutes ago, walt.farrell said:
Shapes (e.g. Rectangles) are vector objects, but they are not Containers. Artboards, Layers (Capital L, identified in the Layers panel as Layer or with the Layer icon in V2), and Groups are Containers.
A Shape cannot "contain" a Pixel layer the same way a Container can. It can Mask the Pixel layer, or it can Clip the Pixel layer, but those are different from "containing" it in the sense that Containers can.
Why the selective application of Effects that are applied to the Shape to the subsequent Pixel Layers underneath then? Why do some apply down and some not?
Consistency is always useful when using complex software applications
-
1 minute ago, R C-R said:
Please keep in mind that when referring to technical matters "plain English" frequently can have several different interpretations or meanings, which is why to avoid confusion & misunderstandings, it is a good idea to use the same terminology that the app uses wherever possible. So for example, plain English words like group, layer, object, & many other terms may have more than one meaning depending on context.
I get that and I always try to use the right terms
-
1 minute ago, R C-R said:
Are you talking about the container type of layer identified with a Capital "L" in the Layers panel or something else?
Also, while it may be clear to you what you mean when you use words like "basic" or "standard," it is often not clear to others, which is why you often get requests for clarifications, screenshots, example files, etc.
What sort of functions are simple vector objects operating when I add pixel layers to them and the effects applied to the vector object also apply to the pixel layer then ? Is the pixel layer not contained within the parent vector object/layer then?
Some effects work on the child layers where others don't ? an oversight in design that has caused a great deal of confusion
I don't know what capital L has to do with it apart from when I add a new Layer it's called Layer 1 with a capital L - I only see some symbol next to Vector Object layers
-
5 minutes ago, Old Bruce said:
These statements are not clear to me at all. I have no idea at all what you are trying to achieve.
Yet here I am having just figured out what the problem is using plain English
I'll work on a series of memes for the grammatically challenged next time maybe then
I can't seem to use CTRL+Z anymore ! (V2 Designer)
in Affinity on Desktop Questions (macOS and Windows)
Posted
I'm going to write down all these irritating design features/oversights/bugs as I find them and get back
Like this one:
Every time I open a file it opens with a default layer selected
Normally at this point when I open a file I'll hold the space bar and move the design canvas around with the left mouse button to position it correctly but the app doesn't recognise the space bar yet/at that point and moves the selected layer instead so I end up going through this same bollox every time I open a file
There are other examples like this that are really doing my head in