Jump to content

Frank Jonen

Members
  • Content Count

    330
  • Joined

  • Last visited

Everything posted by Frank Jonen

  1. Indeed. Like a nested document layer. Doing this via a live layer would also open up the possibility of easy versioning within a document. The output then creates the layer to be used in the layer stack. Node tree recipe files are tiny. You could easily stack a few up and send the file to your TD or supervisor for selection. I kinda like the idea. Have all your items in the layer stack and reference them from the comp = portable project file. Or only have one comp layer and reference outside files from there. Best of both worlds. Typography items could be embedded Designer files that have their output as an input in the comp even.
  2. I don't recall who it was, but someone from the Affinity team once posted here that under the hood it's a node-based architecture that is exposed to the user as a layer stack. A Compositing Persona would be amazing and is definitely possible but I don't really have high hopes for that. At least not near-term. It would be great to have it with the 3D texture map preview and a few more generative nodes to create surface details. Maybe that could be a step towards getting nodes.
  3. When painting on a mask we shouldn't need to manually set the colours to greyscale, masks are greyscale by definition. When clicking on a mask layer it should automatically switching to black and white colours in the tool palettes. Also it would be helpful if we could preview the selections normally with an overlay colour. Right now the mask preview doesn't work for existing layers only to create new masks. That feels like a bug.
  4. On Designer I was able to get around it by using TIFF as an export. To replicate it in Designer, make copies of the artboard and export to JPEG directly. That's when it happens here, sometimes even in TIFF export.
  5. It seems to be intermittent. With Designer I get it sometimes, with Photo always. In the original document I have 12 Artboards, "whole document" exports them all as one image for some reason instead of all Artboards at once.
  6. Didn't get a notification about this, so I missed it. But uploaded it now.
  7. 😮😲 I hope you don't go full kitchen sink on this but keep it basic and focused. We have great evolving tools with Quixel Mixer, ArmorPaint and Mari. What none of these do well, not even Mari is decals. Anything artwork related excessively sucks to do in all texture painting apps. You always have to leave the app. With your approach I'm getting some hope that I can design the decals in place as vector art, keep it nimble. That way we can either just export the albedo/base with the decals and load them into Quixel to include in a WIP material or work on finished textures to paint decals into. Right now a workflow like that (that is reliable and respects OCIO) doesn't exist. Photoshop only works well up to 16-bit integer. Affinity doesn't have that problem. I can just roundtrip without sacrifice for the first time ever. And with an in-context texture preview, now that's really something. A "dumb" bump map support would be great. That way we can see light effects of the displacement without tesselation slowing us down. Maybe a toggle between bump and displacement view? Old school bump maps are almost forgotten these days, but for fast previews of displacement features they're very useful.
  8. The integer vs float is causing so many problems in the whole suite. How about two buttons in the transform panel "make whole pixels" to set the dimensions and/or the position to integer values?
  9. I just built the file back with much of the key assets removed. Do you have a place where I can upload it?
  10. Here's a quick way in Photo to illustrate the problem in a very binary way. The clean looking one is NN. What you're looking at is a single pixel column selected on the artboard edge. When that pixel column is filled, it automatically blurs and bleeds into adjacent colours. Yes, feathering and anti-aliasing are off. This is not a vector shape but a pure pixel marquee. The bug is only in Photo. In Designer the setting sticks until I reboot the system. In Photo it's until I restart the app.
  11. Error is in the JPEG exporter. I just exported to TIFF. That one still works. For now I wrote a script to batch it through ImageMagick, so it gets converted for the web automatically in that folder. Here it is in case someone else needs it: https://pastebin.com/32W6ZHBm Setting it up to a folder goes nicely through Automator.
  12. And now it's in both apps. I just duplicated an Artboard in Designer and now that one exports erroneously while the predecessors export normally (from Designer. In Photo they're all crapping out).
  13. You keep bringing that "feature" back for some reason. Bilinear just means I get inaccurate rendering towards object edges and have no idea what the alignments are based on as they constantly change. I now have to turn it off for each session. I'm not allowed to have it set permanently.
  14. They export normally from Designer. Photo messes up by adding a white border. Setting "include bleed" in Photo's export cuts away the white border and leaves the now smaller image. Exporting 1:1 is not possible in Photo when Artboards are used. This extra area roughly matches the frames once set in export persona (the very first thing I deleted, EP is clean). This is through normal export, I don't use export persona anymore as it's too fickle and error prone.
  15. Sometimes (like 98% of the time) moving Artboards around creates floating point pixel values in their position and dimensions. This always results in rendering errors (white gaps, wrong export sizes, distortions). The problem has not been addressed since Artboards got introduced. There's no benefit to having sub-pixel accuracy when moving Artboards around on an infinite canvas. It only creates problems.
  16. There is an easy one like that on the Mac btw: https://www.swiftpublisher.com On Windows there's BarTender, great connectivity and features, design of a pedestrian Word document: https://www.seagullscientific.com/software/professional/ Swift seems like a nicer looking PagePlusX when I compare your screenshots with their site.
  17. For the simple reason that InDesign XML doesn't require InDesign, it's XML. You can create and modify it in any text editor. This means you can create hundreds of different XML documents based on your data set. These just have to be parsed by Affinity Publisher. I never said this is a great route, but it's the only one we have with Publisher.
  18. I think at this point our best / only bet is to do it ourselves via the InDesign XML import. A python script that repeats over a certain pattern over and over is not hard to find, even if you’re new to scripting. Someone can probably make a dedicated one and put it on gumroad.
  19. Element used for testing: Circle with Gaussian Blur fx. Edit: This was for Designer, please move if needed (same in Photo though).
  20. Nice idea with the minimised top menu. However the execution is a bit buggy. Then you have the waste of space that you refuse to care about at all: The Optical Alignment panel that for some unfathomable reason has a fixed height, like you never thought people would actually use it.
  21. I'm bringing it up again since this has never worked properly. Slice tool only sees "current vector layer boundary" and "canvas" boundaries. Which makes it pretty much useless since the only way to do it is to screenshot the positions in regular mode and make a stickie from it to type them into the transform panel in export mode.
  22. Also this is forced upon me. I don't care for wasting cycles. Don't force options on the users that they do not want. I want Nearest Neighbour filtering, not bilinear!It constantly keeps resetting itself. Very frustrating.
  23. Just created one for you. Also Metal on or off doesn't make a difference. All rendering options are messed up. Can't we just get version 1.6 with a compatibility mode for 1.7 files until you've sorted this out so the apps are usable again? Affinity Compatibility Errors.afphoto
  24. BTW… the workaround for not being able to sharpen layers anymore is: Sharpen your layer Get selection from layer (in new layer) Fill selection with white (in new layer below) Fill entire layer with Black merge the two layers Sharpen with the same parameters as before Rasterise to Mask Assign mask to layer you wanted to sharpen previously Nine steps for something that takes 1 click everywhere else. Now that's what I call progress.
×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.