Jump to content

Mark Ingram

Moderators
  • Posts

    5,245
  • Joined

  • Last visited

Everything posted by Mark Ingram

  1. I'm one of those engineers that you're insulting, and I'm also the only engineer to reply to the posts on this thread, trying to help out the community. My time is valuable, and I don't want to waste it reading comments like that.
  2. Technically you could say "the one to blame for no Linux support is actually the lack of Linux desktop users, which would make the product commercially unviable" https://gs.statcounter.com/os-market-share/desktop/worldwide Windows: 75% macOS: 15% Linux: 2.75%
  3. The WPF UI is rendered (by default) in Direct3D9. The --no-hw-ui flag disables WPF's hardware rendering and switches it into software mode. The document view is always drawn with Direct3D11 and Direct2D.
  4. RE: canvas flickering. We use Direct3D11 for rendering the document to the screen, and Direct2D for rendering the tool.
  5. We only use that version of .NET for the installer itself. The actual app uses .NET 4.7.2. You could extract the internal MSI from the outer installer exe by using "app_name.exe /extract" - though you'd still need .NET 3.5 to do that (you could run Windows in a VM first to extract the MSI).
  6. This is off-topic for the "Share your work" forum. https://duckduckgo.com/?q=NFTs
  7. It's not up to us to get it working on Linux - as far as we're concerned, it's an unsupported platform, regardless of whether that's native, or via WINE or anything else. With regards to the canvas flickering, it uses Direct3D11 to present the document to the screen (separate to the UI rendering in hardware, which is done by WPF/Microsoft). You may have more luck by changing the renderer to WARP in the Preferences, if that is detected (WARP is a software rasteriser for Direct3D).
  8. The UI is rendered via WPF, which by default uses Direct3D9. You can try disabling this, and rendering the UI via software instead with the --no-hw-ui command line parameter... (noting the double hyphen at the start).
  9. We don't need multiple threads all discussing the same topic, so I'll close this thread down in favour of the larger, older, more active one:
  10. I'm closing this thread as this forum is meant to contain work created within the Affinity applications and to gather feedback on the work. It is not intended as a catch-all location for off-topic conversations to take place.
  11. @Tolucacan you show Task Manager in the Details view, sorted by CPU usage? I just want to confirm that it's actually Photo that is using the CPU after the image has closed.
  12. Their OpenCL kernel compiler is much slower than it used to be. I have a sample repo demonstrating the problem here: https://github.com/MarkIngramUK/ocl-compile-benchmark Pinching the results from that repo: AMD Radeon PRO W6800 (OpenCL 2.0 AMD-APP (3354.13)): 143ms AMD Radeon RX 5700 XT (OpenCL 2.0 AMD-APP (3188.4)): 1400ms AMD Radeon (TM) R9 390 Series (OpenCL 2.0 AMD-APP (3110.7)): 53ms The top result is what I've just tried now, with the latest drivers. The middle result is what I originally filed the bug with AMD. The last result is a non RDNA GPU (i.e. unaffected by the slow compilation bug). Driver 3354.13 appears to be 10X faster than 3188.4, but that's still 3X slower than it was originally.
  13. I'm in regular contact with AMD, and I haven't been told that, so I would suggest that the AMD support person isn't being entirely truthful there.
  14. Please use the 1.10.5 release build there is no later beta Click here to download the latest beta <download link removed by mod> Status: Customer Beta Purpose: Fixes Requirements: A valid product key (for Affinity Store purchases), or an installation of the full retail version from the Microsoft Store As this is a beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity that may be adversely affected by the application failing, including the total loss of any documents. We hope you enjoy the latest build, and as always, if you've got any problems, please don't hesitate to post a new thread in this forum and we'll get back to you as soon as we can. Thanks once again for your continued feedback. If you have a general question about the software, please head over to the Questions Forum, or if you have any suggestions, please head over to the Feature Requests forum. Changes Fixed sporadic issue with images incorrectly rendering depending on their alpha outline Fixed crash in export of EPS and WMF when there were missing resources Previous release notes
  15. Please use the 1.10.5 release build there is no later beta Click here to download the latest beta <expired link removed by mod> Status: Customer Beta (Release Candidate) Purpose: Fixes Requirements: A valid product key (for Affinity Store purchases), or an installation of the full retail version from the Microsoft Store As this is a beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity that may be adversely affected by the application failing, including the total loss of any documents. We hope you enjoy the latest build, and as always, if you've got any problems, please don't hesitate to post a new thread in this forum and we'll get back to you as soon as we can. Thanks once again for your continued feedback. If you have a general question about the software, please head over to the Questions Forum, or if you have any suggestions, please head over to the Feature Requests forum. Fixed sporadic issue with images incorrectly rendering depending on their alpha outline Fixed crash in export of EPS and WMF when there were missing resources Previous release notes
  16. Click here to download the latest beta Status: Customer Beta Purpose: Fixes Requirements: A valid product key (for Affinity Store purchases), or an installation of the full retail version from the Microsoft Store As this is a beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity that may be adversely affected by the application failing, including the total loss of any documents. We hope you enjoy the latest build, and as always, if you've got any problems, please don't hesitate to post a new thread in this forum and we'll get back to you as soon as we can. Thanks once again for your continued feedback. If you have a general question about the software, please head over to the Questions Forum, or if you have any suggestions, please head over to the Feature Requests forum. Changes Fixed registration failure (will now use the browser to complete registration, rather than attempt it in-app) Updated help Previous release notes
  17. Click here to download the latest beta Status: Customer Beta (Release Candidate) Purpose: Fixes Requirements: A valid product key (for Affinity Store purchases), or an installation of the full retail version from the Microsoft Store As this is a beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity that may be adversely affected by the application failing, including the total loss of any documents. We hope you enjoy the latest build, and as always, if you've got any problems, please don't hesitate to post a new thread in this forum and we'll get back to you as soon as we can. Thanks once again for your continued feedback. If you have a general question about the software, please head over to the Questions Forum, or if you have any suggestions, please head over to the Feature Requests forum. Fixed registration failure (will now use the browser to complete registration, rather than attempt it in-app) Fixed corrupt images when entering Photoshop plugins, with hardware acceleration enabled Updated help Previous release notes
  18. I've just checked AMD's site, and 21.5.2 (21st June 2021) does appear to be the latest driver for your card. I would suggest contacting AMD's support, or filing a bug report with them. It looks like they have a tool for this - https://www.amd.com/en/support/kb/faq/amdbrt
  19. Thanks! Are you still experiencing crashes? The log file indicates the app started and closed OK - did you disable hardware acceleration to prevent the crashes? Or is this log file from after you reverted your drivers?
  20. Thanks @GWitchy - I can confirm that your AMD OpenCL driver (amdocl64.dll) is crashing. Could you attach your log file from %APPDATA%\Affinity\Photo\1.0\Log.txt too please?
×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.