AiDon

Just a request to include corrections for the Sony FE 200-600 mm F5.6-6.3 G OSS (SEL200600G) to the lens corrections database. 

The problem started after the last update. Since reinstalling an older version of the program did not make any difference, my conclusion was that the bug must sit somewhere in my computer, maybe in the registry, So I used REVO Uninstaller to uninstall the program and really clean up the computer from all  'silly rests'. This worked: after reinstalling 1.8.3 evrything is normal again.
PROBLEM SOLVED!
Thanks for your tips 🙂, I had to try them out  before I concluded that there was an other problem.
Attached:
1.Opening the RAW file in Develop Persona
2. After pushing 'Develop' (without making any ajustments) how it opens in Photo Persona
No diferences, this is how it should be 🙂
 

Chris B
If you have an image that has a ratio of 1440:600, or you crop an image to that ratio, then when you set the long side to 1440px in the export dialog, the short side will automatically change to 600.  How do you wind up with 960 ???

Make sure they are copied to the Default Plugin Folder or the NIK program install folder is included in the Search Folders in the Plugin settings and choose Allow "unknown" plugins to be used ...

Thanks--didn't know if you saw my post a couple of posts up, earlier today, I'm using Adobe DNG.  Also using Bridge as a DAM and metadata tagger.   Between those freebie tools, Darktable for RAW processing, and AP for everything else, pretty good toolset.  
Would love it if now a few more things happened:
AP 1.8 adds the improved metadata editing they're working on.  And in the future, a DAM application, or integration with an existing DAM application.   Darktable adds native support for CR3.  

Hi Joe_cool,
Welcome to Affinity Forums
No eta for v1.8 (retail), sorry. There will be more new features added to v1.8 beta before the final release.

Hi nezumi,
Have you ever saw any new (major) update of the Affinity apps without any new features? Expect both things: new features along with bug fixes & improvements in v1.8 as well

Hi, here is a link to a image that causes a sudden exit when selecting to open in either Production or Beta versions:
DropBox: https://www.dropbox.com/s/hnumcebmm05egco/20190829_152542.jpg?dl=0

I’m guessing you meant to type ‘Sandy Bridge’!

Hey M3rØj,
A lot of these issues are being caused by a compatibility issue with Windows Ink. Unfortunately, Windows Ink and Affinity do not work very well together, but this is something we fully intend on resolving. For now, I would suggest disabling Windows Ink from the Wacom interface. The issues this incompatibility are causing are points 2, 3 and likely 4. It may affect point 1 but we should disable Windows Ink and readdress this to be sure.
As for point 5, I cannot reproduce this at all. It may be worth trying it once Windows Ink is disabled but if that doesn't fix it, we will have to do some more investigating.

Thanks for that. I found a similar report from a year ago so I've tacked this report to that  

Attached Chris ...EOS M50195493.CR3
Note just switch between 100% and Fit ... sometimes only shows in Fit if there are lots of powerlines in the image. I Guess it could also be related to CR3 processing.
EOS_M50195493.CR3

Firstly hold down the Ctrl Key while double clicking the Icon to open the application and keep holding it down until you get the Clear User Data Panel, accept the defaults and click Clear:

if that doesn't help try switching the Render to WARP in the Performance section of Preferences, restart the application and see if you can open the RAW images then.
If you can it means that your Video Driver is out of date, and in this case the latest version is 377.83, download it from the NVIDIA website and install it then switch the Renderer back to the Quadro and try it again. (I'm not sure why you are showing 382.05 as your version)

In the interim you can either use DPP to create TIF images for use in Affinity or Adobe DNG Converter to create DNG files to use in Affinity.

Hi,
Any progress with Canon CR3 support in Affinity Photo on Windows as it has now been 18 months since the format appeared as I believe there are now 6 cameras using this RAW format?
don.

According F1 (Help)  :
 "Locking is useful when you need to prevent a layer from being moved or transformed unintentionally."  = i.e. on the canvas
Though, one can still move it up and down in the stack.
"Layers which are locked show in the Layers panel with a lock symbol next to them. Selected locked layers appear with crosses around the bounding box." 
And  indeed, transform is locked.
But one can still make selections, apply adjustment etc.
 

In the interim you can either use DPP to create TIF images for use in Affinity or Adobe DNG Converter to create DNG files to use in Affinity.

Hi,
Any progress with Canon CR3 support in Affinity Photo on Windows as it has now been 18 months since the format appeared as I believe there are now 6 cameras using this RAW format?
don.

Hi,
Any progress with Canon CR3 support in Affinity Photo on Windows as it has now been 18 months since the format appeared as I believe there are now 6 cameras using this RAW format?
don.

Its something we still don't support I'm afraid however we try to improve RAW support as much as possible with each update.
C

Some of that is still lost.

Hi jargol,
It looks like this may be an issue with Windows 7 Photo Viewer and a colour management setting. Does the image only look inverted once it has been exported through Affinity? Can you go to Control panel > Color management > Advanced Tab and set Device Profile to sRGB IEC1966 and see if it makes a difference.

According to the Help:
 
 

The solution to that is to select the plugins you want, in this case for Studio only, the plugin file tltopazstudiops_x64.8bf from C:\Program Files\Topaz Labs\Topaz Studio\PS_Plugins_x64, copy that to the Affinity Plugins folder at C:\ProgramData\Affinity\Photo\1.0\Plugins and remove the Topaz folders from your list in preferences.
You can do the same for the Adjust AI (update from Adjust 5) plugin.
Please note though that every time the Topaz apps are updated you will have to recopy the plugin files.

@hy13 / @JosephFOtero / @Miromike / @SandM Has anyone in this thread reported the issue to AcdSee? Our thumbnails work within Windows Explorer, so AcdSee must be manually acquiring the thumbnails from our files, i.e. not using our thumbnail provider that we ship with the application (though without speaking to their developers I'm only guessing). Unfortunately it's not our responsibility to fix bugs or update features in other people's software...