quantos

Thanks Jon. I have about 20 from the period (May 12th) and a couple of older ones in there (that are bigger and might not be relevant. The last 3 .dmp file attached - with thanks. Q. 1f978de9-8d0a-4c06-91a0-8cef6704d6ae.dmp 3c35be51-924f-4255-8ae0-00b0cefd4705.dmp 4ab97622-68e3-438f-b76b-c27d9439f1c6.dmp

Interesting. Extra feedback for you. I've just found out that: 1. if I click on a file directly, the file opens without any issues. 2. If I then open the/any file from within the open app then there don't seem to be any problems; but 3. If I try and open the app itself from my pinned shortcut, it fails (closes after 2-3 seconds); and 4. If I try and open any file from my pinned shortcut lists, they also fail to open (same error); and 5. If I try and open from the short-cut alias (on the desktop), it also fails (same error); and 6. Same error if try from the standard Windows start menu 7. Which is also true if I try and open Publisher.exe file directly. Seems strange to me (as a non application programmer) but at least I seem to be able to consistently open files directly.

Unfortunately, updating to .Net Framework 4.8 seems to have made no difference so any tips/clues would be highly appreciated. Let me know if there's anything I can do to surface any actual events (logs?) that I can get to you. Many thanks.

The latest version of .Net Framework would appear to be 4.8 which for Windows is available here: https://dotnet.microsoft.com/download/thank-you/net48 I'm testing that now/as soon as it finishes updating.

Cross-referencing another thread for this, if that's not considered bad etiquette: Where the reply is: "Can you please make sure you have the latest (4.7.2) .Net Framework installed?" I don't yet know if that's what my problem is but will check that and report back here if it fixes it.

Hi guys. Late post on this one but this was the first/best thread I found when googling 'affinity publisher not opening' - which for me is a brand new problem. Have just updated to the latest version too (after the previous recent version didn't open). New version is 1.7.0.312. The "only" change since I last opened Publisher (within the last few days) was I update my NVIDIA Geforce graphics drivers (for the first time in 2 years) to GeForce Game Ready Driver - which is v 430.64 released May 9th 2019. I'll check other posts and update this one if I find any but the problem/bug is quite simple (on Windows 10 64bit): 1. Click to open Publisher. 2. Initial loading graphic runs/loading the programme 3. The programme starts to open as usual (at least the outline shell of it does) 4. IE the menus don't load, just the outline + the close button etc 5. Within roughly 2-3 seconds (5 at the most) the progamme shell window just silently closes. 6. Closes with no warning, no message, no error, nothing. It just closes. Running as Adminstrator makes no difference. PS Affinity Designer seems unaffected (if this is an NVIDIA GeForce driver error). I haven't updated that for a week or three and that version number is 1.6.5.123. I'll look around now and see if I can find a more specific/recent thread on this. Thanks guys.

Wow, this looks great guys, except that I can not find any "Pinning Panel" or any help text referring to it and the current version (1.7.0.293 / Windows). Has been tested and removed or am I somehow looking in the wrong place? See grab attached for for full View / Studio UI options... Many thanks.

+1 I just found this having started using AP in earnest now to produce client documents and reports etc. Many kinds of pictures or 'picture boxes' will need to flow with the text to stay useful. On the other hand, I absolutely love having design/creative tools built into the AP at nearly Affinity Designer levels. Just great - but those lovely little extras will need to go with the flow sometimes!

Oops. I didn't spot that. He's replying on the wrong thread then. :-)

This isn't on opacity issue. It's all to do with ICC color profiling. Something I didn't understand at all when I first replied here. I haven't checked recently but you excellent guys at Affinity do still need to explain this better and I were you I would do it as part on the initial set-up steps. Basically if you're using a modern HDR-style (10bit colour) or any professional-grade colour monitor (above 8bit colour) you need to make sure, on Windows at least, that your Windows colour space matches you colour space inside Affinity - otherwise colours appear washed-out/desaturated, etc. There's a lot more to it than that and all it's to do with ICC. Google it. But as of 2017-18 the best (most flexible) approach is to use a good 8bit colour profile such as sRGB IEC61966-2.1 and have Affinity automatically convert imported images to that colour spec. 8bit colour is 16.7million colours so it's still very, very good for most graphics and certainly most web/tablet graphics work and then save/export your graphics with the 'include ICC profile' included - which tells any wider-gamut (HRD/10bit colour devices) how to display the colours properly. Devices that don't understander ICC profiling then ignore the ICC profile data anyway and you're good to go. That's an incredibly simplified explanation probably only useful to 10bit/HDR Windows users and who, like me, are predominently most concerned with correct colour matching on a wide range of digital devices that may or may not support ICC. If you Google it you'll find a lot more on this. Affinity: Great product guys. I'm a huge fan so keep up the great work - but do get on top of the explanations for this when onboarding new users.

Oops. @MEB. I just realised that feature works differently to expected (and Fireworks where I'm coming from) after I re-read Andy Somerfields' post "Select this slice, then at the top, choose "PNG" and choose a "Matte" colour - your file will then export with the colour as the background"... I was expecting to be able choose the transparency colour (from the colour index) using that tool as I needed to alias out to particular colour. With Fireworks you can select which of your index colours to use for the transparency (which is what I need) and so it seems that might not be possible (after taking another look). Apologies for the confusion - although I still would like to be able select the colour to index out. Q.

Thanks @MEB. Current version (1.5.3.69) of AD on Windows 10 Pro/64bit. I'll test AP too. @Geowil, yep, a straight transparent background export works great for PNG 24 and PNG 8 but sometimes you do want/need to matte out a particular colour to properly alias out/blend into any given background colour - being the query. Thanks guys. Q.

Connected to this, I can't get the 'matte' selection tool to work either. The scenario, a common one, is that I have various objects including cropped bitmaps sitting on a coloured background (shape object). I want the object aliasing to continue to the same background colour as the final export, stripping out the background colour in the export. IE This is a very common requirement. However, I can't get the selected matte colour to render as transparent. It outputs the background colour every time - seemingly ignoring the matte setting. What's the trick I'm missing? Q.

Guys/team Affinity. With a little testing I've just realised that, in my case, I need to use a different Colour Profile to the recommended/default sRGB IEC61966-2.1 for web/digital work. IE using sRGB IEC61966-2.1 seems to desaturate the colours (all colours) of every image I bring into Affinity Designer's workspace. If I switch to Adobe RGB (1998) the colour match (from any other app/browser to Affinity) is much better whereas it's only if I switch to use the colour profile of my DELL U27313H monitor that the colours match perfectly (as far as I can tell). I'm on a Windows 10/64bit workstation here. Request: Can this 'feature' or a good explanation of what's going on here be added to your Help section, tutorials and anywhere you can mention it. I don't have this issue with any other professional design/art programme I use and whereas I'm sure the option must be there some very good reasons that perhaps don't apply to anyone, like me, that only work in the web/digital sphere - unless I've missed a very important tutorial somewhere in my 20+ years working as a digital designer. PS Your otherwise excellent Affinity Designer WorkBook (book) doesn't mention any of this either. IE there's nothing in it at all about colour calibration and the tools/presets that might be needed to work with colour in AD (or AP).

Guys/team Affinity. With a little testing I've just realised that, in my case, I need to use a different Colour Profile to the recommended/default sRGB IEC61966-2.1 for web/digital work. IE using sRGB IEC61966-2.1 seems to desaturate the colours (all colours) of every image I bring into Affinity Designer's workspace. If I switch to Adobe RGB (1998) the colour match (from any other app/browser to Affinity) is much better whereas it's only if I switch to use the colour profile of my DELL U27313H monitor that the colours match perfectly (as far as I can tell). I'm on a Windows 10/64bit workstation here. Request: Can this 'feature' or a good explanation of what's going on here be added to your Help section, tutorials and anywhere you can mention it. I don't have this issue with any other professional design/art programme I use and whereas I'm sure the option must be there some very good reasons that perhaps don't apply to anyone, like me, that only work in the web/digital sphere - unless I've missed a very important tutorial somewhere in my 20+ years working as a digital designer. PS Your otherwise excellent Affinity Designer WorkBook (book) doesn't mention any of this either. IE there's nothing in it at all about colour calibration and the tools/presets that might be needed to work with colour in AD (or AP).