abn5x
-
Posts
40 -
Joined
-
Last visited
Posts posted by abn5x
-
-
WOW, very nice fat update with new features! Hope to see more Live Warp Filters which would definitely help with complex shape mockups!
Cheers!
-
Thanks Matt!
Is it me or the DL speed is very slow?
-
@Andy Somerfield how's the performance of the Apple Silicon DTK version compared to the iPad Pro performance? If you can share that info of course
-
-
-
On 7/2/2020 at 1:19 PM, Sean P said:
Hi abn5x,
Thanks for letting us know - this is something we're aware of and with development to be fixed. It is only the System Palettes that are affected, so you should be OK to re-organize those palettes.okeey thankyou
-
Affinity Designer CRASHes when trying to move around System Swatches Colours in the Swatches Panel.
So I created a System Wide Colour Swatch, added some colours to it and when trying to reorganize them it crashes the entire app 80% times.
-
On 6/29/2020 at 9:53 PM, MattP said:
Definitely something odd happening - I'll look into it, I'm just doing something on iPad for the next couple of days, then I'll get to it, thanks again for the nudge
You're welcome
thank you for your hard work! Also very interested to hear what you're working on for the iPad 👂👂
-
2 hours ago, nik78 said:
I think what is happening is that you have two different node types there: A smooth and corner point.If you make them both smooth the shape should stay the same.
How do you do auto snap close? You drag the points together?the same happens even if the two nodes are smooth.
-
1 hour ago, MattP said:
I can see why it's doing this behaviour then - it's deliberate, but possibly not hugely helpful in the Node Tool?
yes, in the node tool it's not quite helpful
-
4 hours ago, MattP said:
Just off the top of my head, is this because your mouse got near the edge of the view (and hence, we hide the tool as we slightly pan the screen?)
Matt
Yes, it happens when the mouse is near the view's edges, didn't notice that because the stroke was set to 0. When set to something visible, the stroke still moves but the path disappears, though sometimes the blue path freezes while the black stroke still moves.
-
-
On 6/27/2020 at 10:35 PM, AffinityMakesMeSmile said:
I don’t believe Twitter is the best place to report bugs in...
Matt’s twitter account may be his private there, away from only discussion Affinity stuff
He responded and said that he will look into it.
-
Dragging node fast - causes visual glitches and sticking nodes until the speed is slowed down or stopped entirely, then it updates the node's position.
-
oh I see that the issue which I mentioned you in twitter(about joining two nodes with auto-snap ignoring the node handles of the dragged node when welding them) still isn't fixed
-
20 minutes ago, v_kyr said:
Well it's maybe one of those "...quick basic implementations of a feature that were required and only slowly will be polish until it meets user requirements..." then.
But seriously, it's not always the easy way to add some specific functionality, especially if that hasn't be planned and designed to be included before. Meaning here you often may have to change then a bunch of things in code which are related or associated in behavior to that functionality. Which can again lead to new bugs or misbehavior of certain older code which worked fine before. - So it's not always an easy task to change or add certain things in general, especially if no one during the initial design phase thought about to leave room for certain important things, or if essential backend functionaility is missing which is needed for implementing certain frontend functionality ... and so on. The latter then entails a lot of refactorings, code testings and the like until things might work as hoped or expected.
I believe the dev team isn't that overall exhaustive big in man power and since they have nowadays also to work implementation wise on double-three frontiers (MacOS, iOS, Win and then AD, APh and APub) they were maybe pretty busy just with these tasks. - So probably not much time left for implementing much new functionality beside let's say common bug fixing (even there are still enough unsolved and left over).
Basic Boolean Operations doesn't need UI/UX polishing, it's just that, Basic buttons to do operations. ShapeBuilder would be the logical improvement upon Boolean Operations, which we are still waiting for.
Serif is not some new company, it has the Experience and Knowledge to plan its code for the expected features that would be developed, at least that would be the logical assumptions to make. VS added "merge nodes at middle point" in less than one week since I asked for it + other bugs and fixes, Affinity in its 4-5 years still doesn't have a simple proper "merge selected nodes" feature, not even talking about "merge at middle point".
Yes, Affinity Team is not big, comparing it to Adobe or Corel for example, but it surely is bigger than One person. Releasing it on multiple Platforms besides increasing the work which must be done, also increases the revenue, which means they should/could increase the Team to deliver faster, better releases.
-
1 hour ago, ErrkaPetti said:
But, if you are more productive with Vectorstyler Freehand Corel Draw or Adobe Illustrator, why are you here on this forum then?
If Vectorstyler have all the functionality you need just now, why wait here for Affinity Designer?
I don’t understand some of you people here 😞
I use both, AD is more polished, and smoother right now, but clearly lacks features which are covered by VectorStyler for me. I root for both Apps, VS just needs to keep fixing bugs and improve the performance like it has done till now, Affinity needs to fix bugs and add functionality. Whichever does it best wins for me.
Though I have to say, that I LOVE the way Affinity Suite Apps are intertwined, work se well together and speed up the workflow, just wish AD was more feature rich, at least the basic features you'd expect from a MODERN Vector App.
-
18 minutes ago, ErrkaPetti said:
But, in the same time, it’s remind me of Paintstorm Studio - PSP is crammed with painting features, it’s ONE russian developer that does iPad/Win/Mac (!) version...
Incredible, BUT, unstable and TOO many functions...
Paintstorm Studio could beat both Procreate and Clip Studio Paint IF everything worked as planned, but, software developing an app that really works as description takes a lot of effort...
Either Vectorstyler or Paintstorm Studio is near an real version 1.0 even though the latter is v3.x now...
I completely understand your point of view, but sometimes we need to get work done fast and too many functions is better than not having those functions at all.
Affinity could have made some quick basic implementations of all the features that were required and slowly polish them until their Quality Standard, but they chose to starve their base of clients while waiting and waiting... I mean, the Template Window in 1.8 is great and all, but the Warp tools, Blend Tool, Shape Builder, Offset Paths, Cusp Dash lines or Zig Zags, are more important and I think anyone can agree.
Affinity takes pride in its UI/UX and I really agree on that but we still don't have a VISUAL Way to change stroke width at various path points. Something which VectorStyler or even Illustrator understood as something very important for the user...
The BASIC DIVIDE boolean is still broken...
Same circles in a VectorStyle which is a younger and less polished app...:
- Ambang23, Boldlinedesign and Jowday
-
3
-
On 5/31/2020 at 8:42 PM, ErrkaPetti said:
Gave Vectorstyler 30 minutes this afternoon...
Still not impressed by the speed, it crashed three times in 30 minutes, UI is boring etc etc...
Sure, just like Inkscape, it cramed with a lot of features, but, who wants this slow annoying vector apps?
I'm talking directly with the dev(he's a one man-team), he is very responsive and adds features /fixes reported bugs very fast, damn it, he added "merge nodes at middle point" in less than a week while fixing all my reported bugs and also improving dramatically panning/zooming. I think Affinity should hire that guy, he's a monster at developing.
Also was in talks with him to implement the "Pathfinder" Open-source Vector Engine for increased performance, he said it will be a long-term feature when he's done with all the bugs and UI. Also he's VERY RECEPTIVE of critique, you can search in VectorStyler Forums, all my opened threads(same nickname as here) which he fixed in less than one week.
Sure, the app is still quite green, the UI/UX still need lots of work(made some suggestions in the forum, to mimic Affinity in some aspects), and it's drawing engine is a resource hog, but feature-wise is incredible for an ONE-MAN TEAM, give it enough time and maybe we will have a real Illustrator Killer, while Affinity still takes time to implement BASIC Stuff with a bigger dev team...
- Boldlinedesign and Jowday
-
2
-
same issue here, Clip Paint Studio features a GLOBAL PRESSURE settings, affinity should too..
-
On 5/30/2020 at 8:00 PM, Patrick Connor said:
Welcome to the Serif Affinity forums
Nice to see you so soon after your purchase, If it does not suit your needs you are still inside the 14 day money back period, just email AffinityReturns@Serif.com with your order number. However I hope that you find it to be more than satisfactory in other ways and decide to keep Affinity Designer to compliment your Affinity Photo.
Any sneak peak on this function? Is it even worked on?
-
3 minutes ago, ashf said:
I might have seen something like that few times.
Post your environment information.
It cloud be GPU driver problem. so update your GPU driver to the latest one first.
I'm on macOS, we don't have GPU drivers
-
-
8 hours ago, anon2 said:
Sorry to say, but Serif are aware of the problem and yet we've been waiting years for it to be corrected.
well damn... I mean this auto-close features is quite useless in this state...
Sidecar Apple Pencil + Vector Brush BUG
in V1 Bugs found on macOS
Posted
So if I use the vector brush with Apple Pencil, the end and beginning of the stroke will always be 0, even though I press hard or light the first and last node are always set to 0 pressure, the nodes in-between are good. This doesn't happen with Wacom Tablets.
Please fix it, as it's quite annoying...