DreamMastR

@Gabe I'm using FontBase. But I did try loading the fonts directly into Windows and not using FontBase, to no more success. Have you tried changing the Biko font to something else in paragraph style? I was getting more crashes before, but after making a lot of adjustments, that's the only time I get a crash now. I can't remove Biko from my styles. Originally, about 80% of the document used Biko. I replaced it manually in the document which avoided crash on load, but I can't do it through the styles. Thanks again.

All uploaded. Thanks again, @Gabe

@Gabe I managed to open the file for a few hours if I used Affinity Publisher Beta, but then the crashes started again. I was able to narrow the issue down to a couple placeholder fonts that weren't playing nice with Affinity. One font has been removed from the document, but the other (Biko) I can't get rid of, as its part of my paragraph styles. If I open the file with Biko enabled in my font manager, Publisher crashes. If I open the file without Biko available in my system, Publisher opens and gives me the font manager warning. However, upon opening my paragraph style and changing the font from Biko to something else I get another crash. Should I upload the new file to the same place?

@Gabe No worries. Thanks, Gabe!

@Gabe Thank you for your previous response. I was curious if anyone had a chance to review my file yet?

Thanks, Gabe! Uploaded.

Gabe, I have a similar issue. I had a Publisher file crash when I tried to edit the sections. I've been able to get the file up and running a few times as I have an autobackup tool- but every time I try to edit the sections I get the same result. Crash- and the file is now corrupted. Should I also upload the file to dropbox? Edit: Not sure if it's relevant, but this is the first time I'm editing the file since upgrade to 1.8.5.

No disrespect taken. Like I said I'm a student, haven't stepped foot in a professional environment and likely won't for- at the very least- another six months. Until that happens I've worked my whole life in mental health and have no dang clue what standard practices are in a corporate environment. I found that information incredibly valuable and thank you for it.

Thought I'd chime in here. I'm a Front-End developer student and started teaching myself GIMP as a way to adjunct my studies. About six months ago I found myself having a drink without a professional Front-End developer and I asked him if these sorts of programs come in handy. What he told me was this- - Almost all the front-end developers at his workplace have some experience with image editing. For a few employees, they work more on the raster editing side then the coding side. - The majority of Front-End developers use OSX with Linux a close second. - The OS X users were slowly moving away from Adobe because of the cloud license - Some OS X users were using GIMP. Most were using "this new program, Affinity Photo." This, I should mention, is how I heard about Affinity, and now I am a paying customer - The Linux developers were all using GIMP - Almost no one uses Windows I think a point worth mentioning is Linux is a mostly untapped market. The biggest competitor, Adobe, is a non-player. The current market share for Linux OS is estimated to be about 2.5%. That's not huge, but worth considering is that's 2.5% of a market with no commercial competition. I other words, Linux users- as opposed to OSX and Windows users- will more naturally gravitate towards Affinity. Affinity users, in turn, will also be more willing to consider Linux. EDIT: Also, it's worth considering the value of word of mouth. For example the developer I spoke to used OS X. I don't and I never will. I personally find it cumbersome and use a dual boot Linux/Win environment. If a piece of software is OS X only that means I don't use that software. When Affinity came to Windows, that didn't matter. He recommended it, I trusted his opinion, and gave it a shot. And PAID for it. In other words, those Linux users will be another avenue to promote your product, and potentially increase sales in not just Linux, but also OSX and Windows. I love the idea of a kickstarter.

I've had this same issue. I'm pretty new to raster editing so at the time I figured this was normal and it was the result of some color setting I didn't understand. :wacko:

Thank Peter, It does, but with the majority of my files when I export to PSD both GIMP and Krita merge the layers into a single image. The problem is just as likely on GIMP's support of the format as it is on Affinty's export capabilities. An open format would avoid such issues.

I've been learning my way around GIMP and Krita for the last year and have gotten pretty skilled at both. Been looking into more "professional" software but I refuse to pay for a cloud license. Been holding my breath for your Windows Beta and let me tell you it did not disappoint. You folks really have something great here. The only problem is that I still have to use GIMP for a few things, mostly the Gmic plugin- which I realize would be difficult for you to support for licensing reasons. Exporting to PDF has proven tricky. Sometimes it works flawlessly, but other times GIMP/Krita will remove all my layers and just merge everything to a single image. OpenEXR might work, but every time I try to export with layers I get an error message. What would really solve this is if you guys supported an open format, such as the GIMP gcf format or even OpenRaster. So far, this is the only thing that will keep me from happily paying for the program when the Windows Beta ends. You've made an excellent program here.