awakenedbyowls

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

Yes I misread Program Data and Program Files This has resolved the issue now cheers

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 ?

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 ?

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

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

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

I get that and I always try to use the right terms

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

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

When people ask me for videos and screenshots it's often from something I'm working on that I don't wish to put out on the internet yet - until it's finished - so it takes me time to sort something out when often I'm in the middle of something and it's late and I'm tired or whatever - I figured that just explaining in words would have been sufficient in this instance ! I just thought that someone on here who knows the ins and outs of the software might have figured that I was actually adding the pixel layer to an object and not an actual official vector layer and maybe asked that initially ? or maybe if the software was designed in such a way that makes sense then I suppose then nobody would have wasted any time here If I create a simple vector OBJECT or layer as I like to call them since that's also what they are and apply a BASIC transparency to it and then add a pixel layer to it - it applies the transparency also to the Pixel Layer - If I apply a Gaussian Blur to the Vector Object and add the Pixel Layer it also affects the Pixel Layer - Transparency Gradient though - Nope ! That effect does not apply down through the hierarchy So apparently Vector Objects work like Vector Layers apart from when Transparency Gradients applied - I think this is a Design Oversight

I'm not refusing it's just every single time I ask a question the first reply is always asking for a screenshot or video - when often this is not required - adding these takes time which I don't always have So it works if I add a Vector Layer but if I draw a Vector Object the layer it forms isn't a Vector Layer ? What kind of layer is it then - it's either Vector or Pixel If Vector Objects are just Objects then why are they also represented as Layers and function as layers ? It just seems logical to me that if I can apply effects to this layer and add sub layers then the effects would work on the sub layers !

I just had a look at a basic example and no it appears adding Pixel Layers to Vector Layers with Transparency Gradients does not apply the Transparency Gradient to the Pixel Layer - doesn't seem right to me ? If I want to add a Pixel Layer to a Vector Boundary without applying the Transparency Gradient to it that might be applied to this layer then logically I would just think to create a new blank Vector Layer and add it to that ? I need to learn the different between Clipping and Masking too - I never use Masking because I just find it confusing - maybe I will find myself having to use it at some point to create more advanced effects though Sorry I don't quite understand what this diagram is showing but I'm completely exhausted after walking 70 miles in 7 days and trying to finish off a design - I'll come back and have a look later

What is the difference between making the pixel layer into a one child parent group or adding it to a vector layer ? I THOUGHT making the pixel layer into a subset of another layer was EQUIVALENT TO adding a vector layer component over it - and it seems to apply transparency gradients there so why the hell doesn't it when I add a pixel layer to a vector layer with a transparency gradient already applied ? I would have thought that by doing so I would be applying whatever effects are applied to that layer to the pixel layer I am adding as a child layer ! Sorry but I just find basic logic helps sometimes - otherwise what exactly are hierarchies for ?

Must be a bug then Yay for V2

I know This is not the issue

No there's no masking involved - just a standard hierarchy of layering without anything else added If there was masking involved I would have mentioned it

Vector layer with transparency gradient Add previously made Pixel Layer to Vector Layer so it is now the Parent Layer Transparency gradient has no effect on child/pixel layer Is that what it's meant to do or an oversight in the design of the platform or what? Does any one understand what I mean or will I just post all my questions as pictorial representations