Jump to content
You must now use your email address to sign in [click for more info] ×

Michael A. Lowry

  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. That was indeed the problem. The layer was marked invisible even though the buttons indicated that it should be visible. In the Layers panel of the Export persona, I tapped on the layer visibility button next to the layer that was not showing up in the export. Even though nothing changed in the Layers panel, once I switched to the Slices panel, I could see that the layer had been enabled. Then, exporting worked as expected. I look forward to the fix for this bug. Thanks for your help.
  2. The visibility of the layers makes no difference. I’ll contact you directly to send the file.
  3. I have a document with two almost identical artboards. In the Export persona, I created a slice for each artboard. When I export the slices, one of them is exported correctly, but the other one results in a blank (white) file. The Layers view of the Export persona shows the content as it should be. However, the thumbnails in the Slices view reveal what will actually be exported: a blank white slice instead of the expected content. This is Affinity Designer v2.4.2.2371 on iPad OS 17.4.1 running on an 11-inch iPad Pro (model A1980).
  4. @Ben: Is it fair to say that bugs specific to Symbols are not the top priority? (I recall that it took years to fix the Copy-and-Paste Symbols bug.)
  5. Any news on this topic? Has this problem been accepted as a bug? Is there a public bug tracker somewhere?
  6. As you can see in the file, I used symbols to keep the shape bilaterally symmetrical. Detaching all of the symbols appears to have to resolved the problem. So perhaps Shape Builder has a problem with constituent shapes based on symbols.
  7. This morning I tried to use the new Shape Builder tool for the first time. After several attempts, I gave up. I have not been able to create a shape yet. The app has crashed several times — once when I accidentally typed Command-Delete while selecting areas, and every time I tried to commit the selection and create the shape. I’m using Affinity Designer 2.0.0 on macOS 13.0.1.
  8. On my iPad, iCloud backup has not been working for a long time. I opened a ticket with Apple Support several months ago. This past week, Apple developers finally narrowed the problem to a file or files created by Affinity Designer. According to Apple, there’s at least one file over 100 GB on the iPad that belongs to Affinity Designer. And because iCloud Backup does not support backing up files larger than 100 GB, this large file is preventing backups from completing. (iCloud Backup misleading reports that there is “not enough storage available” even though there is plenty of space available in my storage plan.) If I disable backing up files from Affinity Designer, iCloud Backup works fine. I was unable to find any such large files on my iPad by using the Files app or by browsing the iPad’s content from the Finder on my Mac. However, using a third-party file system browser, I was able to see some additional details, such as file creation/modification dates and folder sizes. Based on this information, it seems the Designer folder on the iPad is taking up more than 300 GB even though the files under the folder add up to just 228.81 MB. Evidently Affinity Designer is using more than a thousand times more storage than can be explained by the listed files. Apple developers were able to read some metadata about the >100 GB file that is preventing the iCloud Backup from working correctly. In these metadata, they found what looks like a date & time stamp: 20190516103049. (It might be part of a file name, but I’m not certain.) I have read several older threads about similar problems. It seems a work-around might be to move all Affinity Designer files to other locations (e.g., iCloud Drive or a computer), and then remove & reinstall the app. I would prefer not to do this unless absolutely necessary. I would also like Serif to help investigate this problem so that a permanent fix can be found.
  9. Aaaaand it happened again. It seems that when AD was forced to quit by other foreground applications it failed to save the current state. This time, I lost about an hour’s worth of work — painstaking drawing I had started to redo the two hours’ work lost last week. This is getting a bit discouraging.
  10. Just encountered another data loss problem. Perhaps two hours’ work on a file that I did last week are just gone today. This time, there was no crash that I’m aware of.
  11. I recently discovered a document in the club archives that has another version of the coat of arms. I presume this version was in use before the 1893 design. The later 1978 version is clearly based on this one, but this small blue reproduction is the only copy I’ve found. My modern version has plain rather than colored oar blades, and incorporates an NRF monogram closer in style to the 1978 version.
  12. Here’s another update. For the flags, I completely redrew the shading layers that simulate the draped folds using a new approach. Each of these shapes contains both a gradient and a gouache brush stroke. I think this adds a bit more of a sense of physical realism. I also added a sort of undulating gradient to the each flag, subtly implying gradual waves perpendicular to the more prominent folds.
  13. Here’s another update. Some purists had noted that the flags looked to sterile and lifeless. So I went back and redrew the flags from scratch, based closely on the flags of the old design. I’ve moved the cantons of the flags more to the top hoist side to make the identity of each flag easier to discern. For the fringes, I used two overlaid strokes — a rope brush stroke with a subtle 3D filter atop a solid color stroke. I think the fringes look pretty good, but they’re not perfect. I like the flexibility offered by a custom brush but I haven’t found a brush that looks exactly like the fringes in the original design. I might just end up creating my own custom brush. I haven't done this before but it looks pretty straightforward. Just one question: Is it true that so-called ‘vector’ brushes are based on bitmap (PNG) graphic files? I also tweaked the floral elements, and now use a variable stroke width (custom pressure profile) for these strokes. I think this gives them more natural & elegant look. I’m still not satisfied with gradient shape overlays meant to simulate draping and folding of the flags. What I’d really like is to be able to define a gradient along a custom path, and not to be limited to linear, elliptical, or conical gradient shapes.
  • Create New...

Important Information

Terms of Use | 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.