Jump to content

tokai

Members
  • Content count

    80
  • Joined

  • Last visited

About tokai

  • Rank
    Member

Contact Methods

  • Website URL
    https://tokai.binaryriot.org/

Profile Information

  • Gender
    Not Telling
  • Location
    Europe

Recent Profile Visitors

446 profile views
  1. The FFT Denoise is a awesome function, but its panel is rather awkward to use. on my screen the spectrum doesn't fit entirely inside the window and scrolling around is super slow for some reason. Maybe an option to zoom (50%, 75%, 100%, 200%) could be nice to have a rectangle paint option (I often want straight hard lines in my mask... impossible to do with the current paint brush option) an option to save the current mask (I often have to redo the same mask over and over again) an option to load a mask Alternatively it simply could react to clipboard events via the menu ("Copy" copies the mask to clipboard, so I can create a normal new b/w document from it and edit it with the normal tools in Photo or Designer, "Paste" does the reverse) (I guess, that probably would be the smartest w/o blowing up the UI with more buttons, etc.) maybe a buch of special mask presets (e.g. "smooth vignette", "hard vignette" for filtering the fine details, etc.)
  2. The window for FFT Denoise is slightly transparent/translucent (even the part where the spectrum is displayed). If one has some high-contrast image loaded in Photo and it's displayed below the window the visual result in the spectrum is noticeably altered (image shows through) and therefore can lead to wrong/ unwanted choices when painting the mask (I might try to "mask out" some frequencies from the spectrum that are actually just elements from the image showing through the window from below). Please make the window opaque, or at least make sure the spectrum is opaquely displayed. (Mac OS X)
  3. Indeed, closing the curve (or rather deleting all that mess) fixed the boolean operation (not sure what strange zig-zag curve Designer generated there anyway… the legs where expanded strokes originally. ) The application definitely should inform the user about things like that. I was completely in the dark here about the actual issue. This was just some funny nonsense project I made, but if this would have been an important work project where I depended on a single curve I probably would have cursed like mad at the screen.
  4. tokai

    A Random Blob Became a Funny Animal

    Thanks for the feedback. Glad you like my little funny ones. Making a children book is something that crossed my mind multiple times (not necessarily for those 3 fellows here), only that I always struggle with the right story idea that makes sense from start to finish and can be told in the necessary constraints. Making the actual illustrations is usually the easy/ fun part.
  5. (1) Not sure this is a bug or not, but I'm unable to boolean merge (add) the 2 curves in the attached document. It doesn't work directly and it doesn't work via compound. I simply get an empty result set after an operation (both curves disappear from screen.) For some reason going to the "Layer" menu the "Expand Strokes" option is offered for both curves, even strokes are disabled… feels a bit odd too. I remember that there was/is some issue with the smart nodes, so I made sure to select all points and convert them to the normal ones ("Smooth"), but this didn't solve the problem either. (2) Unrelated to the actual boolean failure: if there's some sort of error Affinity Designer should report them (pop up the assistant and let me know the operation failed or something). Basically it just fails silently. In a more complex situation I might entirely miss the problem and then run in problems later when I notice a graphical element is suddenly missing for some reason. Let the user know there was an error. Bug,1.afdesign
  6. tokai

    A Random Blob Became a Funny Animal

    I know it's somewhat stupid, but I made some quick friends.
  7. Can we have the Zoom functions ("Zoom In/Out", "Zoom to Fit" (especially important), "Zoom to Width", etc.) as optional features to add as buttons to the toolbar? Since all the functions have moved into a submenu ("View > Zoom") with the recent releases I notice I spend a lot of extra time to trigger those options just by having to navigate into that submenu. Personally I'm not a fan of this change (this was more efficient in the older releases). (Note: I'm very bad at learning and using all the strange keyboard shortcuts. I know this would go faster. But I need a quick and direct way to trigger it via a mouse operation. )
  8. Thanks for the information. Makes a little bit more sense now, but it's still a highly confusing feature, IMHO. Feels like it's a tiny bit unfinished in its implementation. I also don't really see the advantage to control the linear gradient that way (do I actually want to skew the gradient too, when I skew the object? Not sure this always makes sense.) But definitely: * it shouldn't activate on pasting the style on a non-skewed object/ if the source object wasn't skewed * there should be a clear way to enter this input mode manually (w/o having to use the paste-bug or having to skew the object) Just… IMHO.
  9. In some situations I get this odd extra rectangular handles (or guides?) for linear gradients in the Transparency or Gradient Tools, see screenshot. E.g. this happens when I copy an object with a "Linear" gradient and then Paste Style it onto another object. I didn't found anything about it in the documentation. What are those things exactly useful for (fill shear?) and how could I trigger their view manually while in the respective tools? Also it shows "Linear" as type for the gradient during this, but it actually doesn't seem to be a "Linear" fill anymore (click again on "Linear" in the selection makes the gradient jump back to the original linear handles and reverts the adjustments/ look too.) It's a little bit confusing. Perhaps a little bit buggy too (shouldn't switch the gradient type/ modus during the copy+paste operation and the UI also properly should reflect the "Fill Shear" gradient type, I guess)
  10. In the Affinity Designer help under Appendix > System Requirements it states that "1.27MB of available hard-disk space" are required. I don't believe that for a second while looking at that 1.16 GiB monster in my application folder!
  11. tokai

    A Random Blob Became a Funny Animal

    Just sharing some random improvements (?) I did. (Yes, I forgot to flip the cacti pot for correct light direction… maybe next time. )
  12. There's an odd and ugly "floating" circular "close" element on some of the info panels in Affinity Designer. Visually it doesn't even seem to belong to the info box (see screenshot, the black thing with the cross behind the window). Personal Opinion: Why are there two separate elements offering the same function on such small panel? Wouldn't the normal and proper "Close" button be enough?
  13. (latest version of Affinity Designer 1.7.1 from the Apple Store, OS X 10.10 with the "latest" updates) After changing the document dimensions with "File > Document Setup…" I experience refresh issues on the background area of the document (doesn't seem to matter if the background is transparent or a color). This especially happens very often after adding extra space to a document by using the "Anchor to Page" option. Perhaps related to the fact if it has to trigger a new zoom level afterwards or not. Usually on the right side of the document parts are missing then or I get bars in the UI background color. See the vertical bar in the screenshot (no such rectangle part of my test document). Moving the document around in the viewport will repaint those areas properly. This is easily reproducible.
  14. Would be nice to have all the tutorials in one downloadable (zip) package (not necessarily has to be in 4K, of course. 720 would be fine, IMHO. ) , so one can fetch them in one go and comfortable watch locally with VLC. My slow network connection struggles with the online streams. Always buffers; one can't quickly pause and seek back in case one missed something, rebuffering, etc. In the end I don't watch the tutorials at all for this reason.
  15. Was just testing some new things in Affinity Designer 1.7.1 and had this random blob (curve) on the screen, and it looked like an animal, so —a tiny bit later— this came out. Tested the new stroke arrow options too (the feet). The vectorised voronoi pattern was generated with CINEMA 4D, rendered out, passed through "potrace", and then imported as curve into Affinity Designer. Not sure that's the best way, but works for me.
×