Jump to content
You must now use your email address to sign in [click for more info] ×

Search the Community

Showing results for tags 'afp-3238'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Staff and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.5 Beta New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests


Member Title

Found 6 results

  1. Affinity Photo Desktop Beta xxx... 780 Windows 10 64 RAM 24g Core Intel i5 Crashed when exporting 6.8 mb .tiff to Explorer file.
  2. Hi! Merge HDR using the GTX 2080 systematically crashes. However, switchting to Intel IRIS is fine. using Windows 10 and latest Affinity 1.85 Nvidia Driver 456.36 GTX RTX 2080 Super Max Q I can send to the team file and any log. Regards
  3. Hi all, My Affinity Photo crashes when I try to create a panorama using TIFF files. It crashes (without any message) instantly when I hit apply after it renders a panorama, or few seconds after I try to see rendered panorama with magnifier. My last attempt was with 5 TIFF (16-bit) files generated in Capture One 20 (Canon 6D). Each file is 114 MB. Before that I tried with few old TIFF files from 2007 (Olympus E-500). It crashes the same way. Everything works well with JPEG files. I tried with 8-bit TIFF files with ZIP compression (~32 Mb each file) as well and it still crashes instantly after I hit apply after the panorama is rendered. I have the latest version of Affinity Photo (1.8.5.703) and bellow are my PC specifications: Windows 10 64-bit PRO with latest updates Intel i-7 4790 3.6 GHz CPU 32 Gb DDR3 RAM GeForce GTX 1050 Ti Samsung EVO 250 Gb SSD disc Asus H97-PLUS MBO My PC is clean from any malware software and works well.
  4. Photo version 1.8.5.703, Intel Core I7 3960X, 32 GB RAM, NVidia RTX 2080 Super with 8GB VRAM Photo will terminate quite unexpectedly and fairly frequently. There are no dmp files created nor recordings of the termination in the windows logs, so I am not able to attach much to this post. I am suing a Canon 70D with CR2 raw files. App termination happens most frequently when developing the raw file, but also happens with a converted afphoto file. Thanks for any help you can give me. Bill Byrnes 3ba01282-8abe-49cc-9c9d-131e35392adf.dmp
  5. Currently using a NVIDIA GTX1050/4GB with driver v456.38 and the Performance settings are this: the previous reported issues with Panorama stitching and HDR merge are still causing immediate exit crashes and opening more than one image at a time still causes crashing if the GTX1050 is used as the renderer If I change to use the HD Graphics as the renderer on a external monitor the immediate close issue doesn't happen, but opening 3 uncompressed ARW images (A7MIII) the second image, or 3rd image on the internal display, wont show a preview and it just looks like this: In some cases there is blocking on the display where the screen redraw doesn't seem to complete:
  6. Hello: I am experiencing random crashes when I try to do panoramas or hdr images. I am using Windows 1903 and Affinity Photo 1.8.4. When I load the images the program starts to work but crashes unexpectedly. I use ARW files. What could be happening?
×
×
  • Create New...

Important Information

Terms of Use | 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.