Jump to content

Potzo

Members
  • Content count

    16
  • Joined

  • Last visited

About Potzo

  • Rank
    Newbie
  • Birthday 03/04/1990

Contact Methods

  • Website URL
    http://potzo.net

Profile Information

  • Gender
    Male
  • Location
    VaraĹždin, Croatia

Recent Profile Visitors

251 profile views
  1. Potzo

    Crashing

    Sorry, I forgot to check replies. I am loading files from local drive that's synced to OneDrive. I will try disabling 'Show' options. I do have to use Guides though, so I will leave that on. I would have to record video all the time, because it really happens on no particular action. I've attached another crash log, but most of the time it crashes it leaves no bug report. def1e086-c02e-4209-b581-ae3ff7f38fee.dmp
  2. Designer would randomly close on no particular action, could be just zoom in or moving element. I've attached some crash reports that are generated. I'd say 50% are not even generated. 4b655d4a-db81-402e-92df-fc23bedb9366.dmp 5ad1389b-369c-4721-b0cf-f0cb64ca2b26.dmp 875a027f-7e69-4fcc-b996-c28ee788a4c3.dmp
  3. Moved to new topic.
  4. Done! I also have seperate artboards saved from the this main source, if you need. But bitmaps are glitched because of lack of storage I guess. The thing is, we cant revert back to 1.6.5. now once its saved in 1.7
  5. Well duh. I know how pagefile works. I just didn't expect for Affinity and Windows to go beyond all limits. I took that screenshot when I had that document opened in Affinity to show what happened. My PC had paging file set to automatic. My C drive had 20GB of free storage before that and pagefile took all of it. I manually changed it now so it doesn't happen in the future. But the problem is still there. How are we supposed to use that source file now if it does this? Even when I open it it's glitching all over place. PC specs: i7 6700k, 16gb ram, 1080ti EDIT: Tried loading that source again with lower pagefile and got BSOD.
  6. So we use Affinity Designer professionally for UI work at the company. A designer colleague just saved his 1.6.5 source of some web design in new affinity 1.7 and it became a literal mess. I had to open it on my personal PC which has more RAM, but it managed to BSOD my PC on first try. On second try it opened but pagefile was filled up like crazy and bitmaps in source had glitches (maybe from no more memory) I can provide source files privately to the developers if needed. When I was opening that source file: When I noticed it took over all my C drive storage. I somehow managed to save each page as new affinity source file though. You really need to have a beefy desktop i7, 16GB of ram and proper GPU to actually work on real projects with lots of artboards. Even then it's prone to crash and lag a lot. It's frustrating. I really hope pages instead of artboards will fix this issue. Thanks.
  7. Here are the crash logs. 0c28b20b-8179-43f0-a68b-677709de4c44.dmp 87418e74-89b8-4064-951a-4b8dffe81165.dmp
  8. I haven't figured out what causes it, it's totally random. Didn't have this issue before this version, I believe. Sometimes random click closes it instantly or when PC wakes up from sleep I notice Affinity is closed. No crash dialog, just disappears from processes. Maybe it's due to source file I am working on. I can send a source file to developers if needed.
  9. FIXED! In short, it was a Windows problem on this PC. After Creators Update they handle fonts really weird. If you try to manually view fonts installed on your system, it will open up default preview mode. Even with explorer. I managed to actually view the fonts files installed by using %systemroot%/fonts via start. It turns out I installed fa fonts (ttfs) on this PC way before I did newer font files on the laptop (otf). And Windows keeps all the versions along with the new ones for some reason. That's why I had problems with some other fonts being duplicated and showing up that way in Affinity. These were being used: So, in order to fix it is to remove all your duplicates (search for _0, _1, _2 etc.) and old Font Awesome fonts. After that you have to follow these steps to rebuild the font cache. So, this is some issue going on with Windows and lets hope Microsoft is aware of it. Hopefully this helps someone.
  10. I use the same OTFs on both PCs. That's why I am confused on how it generates the PDF
  11. Here's example on how PDF looks generated on one PC (broken) And here's on the second one:
  12. Hello, I've been having some weird issue of fonts duplicating in the list and showing up as an old version when exporting to PDF. Specifically I've been having issue with Font Awesome font. They constantly update it, but it seems like Affinity Designer PDF export takes the older version? Even stranger is that only my home PC has this issue, it works fine on my laptop. I used the same source file on both machines and only the PC produces this issue. I also took the same font files from laptop and installed on the PC. Nope, same issue. Don't tell me to use 'Text to Curves' because this is not the solution, it works fine on other Windows machine This is font info in Acrobat, exported via Affinity on laptop: And this is with PC: Something strange is happening here. Also Montserrat font has duplicated weights all though I removed/installed the latest font from Google Fonts several times. You guessed it, it works fine on laptop. I tried reinstalling Affinity Designer and also removing user settings, but none of it helped. Thanks in advance.
  13. You're wrong, we used Fireworks for production a lot. You could easily make slices and export them all. There was extension for svg export. We also had custom js script that exported text styles to xml or plist format. It would be really nice if we had text styles panel in Export persona where we could define custom output. That's the only thing I am missing actually.
  14. Right now we can only export slice into one path, but it would be nice if we could specify different folder for each format.
  15. States are used mainly in animations and it would really nice if we could have that. Integration could work in similar way as in Adobe Fireworks It would probably also need separed animated GIF export option
×