emmrecs01

Thanks Alfred. Good to know it's not just my system!

I downloaded your image and opened it in AP Beta and I see everything as expected, including the tabs you see as "missing". Screenshot attached. Jeff

I suspect this is a rather naive question to ask, but... Following purchase and installation of the full release version a number of brushes were offered, and installed, as "extras". Now the first Customer Beta has been released and installed alongside the "full" version, I can no longer see/use in the Beta many of the brushes that I see installed in the .36 release. (I also installed a few of the brushes available in the Resources section of this forum; again, they do not seem to be present in the current Beta.) Any advice? Thanks, Jeff

Simply select/highlight the whole object, right click, choose Ungroup. Select one of the buttons and delete it. I attach my changed version. test file altered.afdesign

Confirmed here. Also, when it does open in Develop Persona, I see the first screenshot attached; clicking on Develop produces the second!

Just resurrecting this thread to keep it on the boil, as it were! When I saw the list of fixes in 1.5.0.39, the first item on the list (though I didn't understand what on earth the words meant!) gave me some hope that this had been fixed, but, no joy. :( I'm sure it will arrive soon?? Jeff

Hi Jon, Many thanks for this. I have run the utility, opened a .jpg image in AP, made some very quick adjustments and resaved it as an AP file. Checking the folder where it is stored I see a thumbnail for the image. So, for me at least, this seems to be resolved. Slightly OT for this forum, any files I have created using AD (all betas and the final release) do show a thumbnail so the problem seems to have been limited to AP. Thanks again, Jeff

@anonymoustache and MEB. I can confirm it also runs very well in AP for Windows, with the exception of the rotated view that was the reason for this thread.

@Jon W, First, this problem seems to be intermittent on my system. I've attached below a screenshot showing an APhoto file with a thumbnail and an edited version of that same file, showing an AP icon! I then followed the instructions in your post and the icon-only file and the copy of the same file now show the thumbnail, 2nd attachment below. I've also attached the requested logging file. Hope these will be helpful! Jeff Edit: The .log extension to the logging file excludes it from being attached here, apparently! Hence, I'm pasting here its contents (thankfully it's very short): CClassFactory::CreateInstance DllAddRef CClassFactory::QueryInterface DllRelease Found stream, looking for thumbnail... Found thumbnail Loaded thumbnail, size is 276 x 512 Created bitmap: 0000000069053308

Using the image Gregorius posted, this is what I see in the RAW screen. Certainly quite different to the sample .jpg also supplied.

https://forum.affinity.serif.com/index.php?/topic/28190-google-viveza-2-doesnt-work-with-affinity-photo/ , the third post in that thread makes reference to something I am seeing with several plugins: Specifically, that the image displayed in the plugin screen, if the original was taken in Portrait mode, will display landscape, i.e the image is rotated 90 degrees clockwise. This happens with the PhotoWiz plugins I have and also with Topaz (all I have), NeatImage, all constituents of the free NIK collection, MV's Wire Worm and AKVIS Nature Art. I think this was not a problem in the initial beta release, though I may not have had opportunity to test all my available plugins with a Portrait format image. Jeff Running latest available version of beta, 1.5.0.38

You should be able to access them by: Edit>Preferences>Photoshop Plugins and pointing to the folder where your plugins are currently installed, assuming they're not in the default location. As previously stated, you also need to ensure the box "Allow "Unknown" plugins to be used" is also ticked. (For me, all my Topaz plugs show as "Unknown" but can be used.)

Thank you, pauls.

How much hard drive space do you have (that is the one important detail you haven't given!)?

Have not tested this with all drop-down menus but, as shown in the attached screenshot, the Filters panel does open to the right on my system, also set to 1920 x 1080.

Yes, I see the same, but for me, selecting "borderless" on A4 paper makes the left and right margins equal (so not truly "borderless") but with no borders now top and bottom!! Printing to an Epson P50 Stylus Photo.

Geofk, welcome to the Affinity forums A quick Google search on those KB articles, with links to MS Support site, shows nothing that suggests these updates are connected in any way to a future upgrade to Windows 10. Also, now that Win 10 is no longer a "free" upgrade I don't see how you can be forced to make the change anyway. BTW, what is the problem for you with Win 10? Speaking personally, I have to say it has proved to be one of the most stable Windows versions I have used; yes, it has its quirks (not least, the "automatic" updates, but these can be turned off, especially in the Pro version). Jeff

Perhaps because there haven't been any "updates" to the first Beta yet?

Not a problem here, using Canon EOS 600D. All Exif data shown.

I have the betas of both Affinity Designer and Affinity Photo on D:\ and they install and run without problem, so it is possible to do.

Why is this such a problem for you? As Mark says, he has replied to you in the Designer forum and explained why Aero is needed for the Affinity range. As I understand it that is not going to change.

Just to take this topic a little further...! I have a number of plugins, including NeatImage, PhotoWiz collection, Topaz, etc., etc. working in PhotoPlus X8 and I simply added their current folder location to the screen in AP preferences and they all became available in AP. I have not yet had opportunity to test them - quite a number are listed as "unknown" - but so far all seem to work as expected, even at least some of the "unknowns", and considerably faster than they do in PhP X8 64 bit.

Highvoltage, I realise this won't help you but I have just tried to duplicate (no pun intended) this, following the procedure in your earlier gif file: it doesn't happen for me.

Have you tested this in.21, a second build issued today?

Are you running the latest version, 1.5.0.21? I'm pretty certain these were all problems associated with version 1.5.0.19.