PanthenEye
-
Posts
34 -
Joined
-
Last visited
-
PanthenEye reacted to a post in a topic:
Stroke Width
-
JariH reacted to a post in a topic:
Stroke Width
-
JariH reacted to a post in a topic:
Stroke Width
-
JariH reacted to a post in a topic:
Stroke Width
-
JariH reacted to a post in a topic:
Stroke Width
-
JariH reacted to a post in a topic:
Better stroke width control for Designer v2
-
JariH reacted to a post in a topic:
Better stroke width control for Designer v2
-
PanthenEye reacted to a post in a topic:
Better stroke width control for Designer v2
-
Bri-Toon reacted to a post in a topic:
Better stroke width control for Designer v2
-
Aammppaa reacted to a post in a topic:
Better stroke width control for Designer v2
-
DDesignDude reacted to a post in a topic:
Set stroke thickness/width per point/node.
-
DDesignDude reacted to a post in a topic:
Better stroke width control for Designer v2
-
Yearly bump.
-
Yea, I did that. That's why 0,0 is right where rulers meet, but it does not import into Spine at 0,0.
- 655 replies
-
- 1
-
-
- automation
- scripting
- (and 3 more)
-
It's very basic. Transfers single PNG images in correct (EDIT: Actually, it's not correct order, perhaps something with Slice order?) layer order but doesn't retain the Layer blending mode such as Multiply. There's also no way of correctly positioning the art. I want rulers to define the origin: But no such functionality exists and art is offset in Spine since it's placed using the bottom left corner of the document: I can, of course, move the art in Spine in place, but this introduces issues when updating art later via JSON import. And PhotoshopToSpine script can set a custom ruler origin before export. For animation purposes, I need 1-2px alpha whitespace at a minimum, which the PhotoshopToSpine script adds to each individual image exported. In Designer I have to do this by hand manually with export slices. Too much manual work for complex projects, which can easily exceed several dozen slices for a single character. It just doesn't scale. And finally, the built in Spine exporter doesn't support any of the Spine specific features such as defining Skins, defining bones, placing multiple images under the same Spine slot, auto converting images to mesh, exporting into subfolders which spine will export as separate texture atlas, etc. All of this is very Spine specific, so it's not really Affinity's job to cover this. But API should be robust enough to handle all this and it should do so without manually defining export slices. Or if slicing can't be worked around, at least it should be able to automatically define slices per rules defined, such as auto slice only visible groups and add X px alpha white space to each slice.
-
I just want this to be possible in Designer: https://github.com/EsotericSoftware/spine-scripts/tree/master/photoshop Creating new tools is all swell and good, but I just need a basic export pipeline for Spine 2D animation software, which is the industry standard for 2D animation in video games. The linked script saves literally hours of work and is the single biggest reason I'm still subbed to Adobe. Hopefully, the API will cover things like merging layers, parsing layer names then do operation X if the name contains some string, change exported layer name, add alpha padding to each exported image, trim alpha whitespace, set and read designer document ruler origin, read layer mode, scale layers before exporting and write relevant data to a JSON file, which Spine can then import and rebuild the exact layer order, layer position, layer mode and everything else that's relevant. This should be possible without manually defining export slices, ain't nobody got time for that.
-
Stroke Width
PanthenEye replied to nametag's topic in Feedback for the Affinity V2 Suite of Products
Yearly bumb a bit early this year. -
As far as I can tell stroke with control options have not improved from v1. Please add stroke width tool. Some examples:
-
Looks like the newly released Affinity Designer 2 hasn't improved anything in this regard. Unfortunate.
-
Yearly bump.
-
Stroke Width
PanthenEye replied to nametag's topic in Feedback for the Affinity V2 Suite of Products
Yearly bump. -
Stroke Width
PanthenEye replied to nametag's topic in Feedback for the Affinity V2 Suite of Products
Yearly bumb. -
Add Stroke Width Control tool to the list. Like an ex-user of the forums once said, using the pressure graph is like driving a car with a calculator.
-
Yearly bumb, it's been 3 years with no advancements in line width control. Still can't use AD.
- 15 replies
-
- 1
-
-
- stroke width
- art
- (and 2 more)
-
I'd like to see that happen too. Since all their revenue only comes from attracting new users, that's where all their development efforts are focused. And hence why long standing, fundamental issues are never addressed - fixing them won't generate new sales so they're forever in the backlog. A change of business model is probably needed like you described, otherwise I can't see AD ever becoming a true professional tool. I bet the refocus on Publisher and slow AD updates is because AD has probably reached a certain degree of market saturation and is not generating the sales it used to. So they create a new product and invest most resources in that until it also ends up in the same situation at which point it'll enter maintenance mode and they'll develop a new product. Is this really better than Adobe? Not for me at least.
-
I believe the situation we're in is largely caused by Affinity's business model everyone likes to praise. Since the software is a one time purchase for a rather cheap price (when compared to similar commercial software), their revenue is largely dependent on gaining new customers indefinitely. To do that they periodically release new versions that introduce a bunch of big, marketable features at the cost of the ever crumbling and deficient foundation of the software. Once the new features are introduced, they might get some bug fixes later but rarely are they fundamentally improved even if they are effectively unusable in a professional setting. The team then focuses on the next set of big, marketable features or new products to sustain the company. And with every new product their resources grow thinner and thinner. I absolutely hate Adobe's subscription but this is no alternative, never has been and it seems it never will be either. Or devs just like to work on something new and don't care about basic vector features like per node stroke width control. EDIT: Just tried VectorStyler mentioned in this thread. In 30 seconds I found stroke width tool so it's already superior to Affinity Designer in my eyes. This basic tool has been requested in multiple threads here as far 6/7 years ago. Affinity have made 0 improvements in all that time to stroke width control. Pressure graph is as janky as it has always been, creates ugly results and in no way it's even comparable to manual per node stroke width control.
