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

Search the Community

Showing results for tags 'incompatibility'.

  • 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 (Serif 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.4 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 3 results

  1. I'm using a PC which I built last year for general purpose use including writing and video work (DaVinci Resolve) under Linux. My book manuscript is almost ready for publication and I wanted to try the Affinity suite to prepare it for prepress. I purchased a new copy of Windows 10 and installed it as a dual-boot system, then installed the 30-day trial of the Affinity products. However, I have not been able to get the Affinity programs to operate properly under Windows. They report successful installation, but never go beyond the initial logo screen and eventually Windows tells me, "Affinity Publisher 2 is not responding" and offers me no choice except to continue to wait or to exit the program. This is frustrating because, before purchasing Windows, I successfully installed and ran the Affinity suite on the Linux side in VirtualBox using an unregistered Windows install for evaluation purposes. It was slow but appeared to be fully functional, and I expected it to work much better with a native and activated Windows OS. Instead, it's unusable. I posted this under the Windows Support forum and another user suggested that I try enabling/disabling hardware acceleration. It didn't make a difference; I received the same results either way. I've also tried with both the .msix and .exe installers, using the latter with "Run as Administrator." No help. The other forum user suggested that my AMD graphics card might be causing the incompatibility. Possible, but I'm not going to jettison a graphics card I'm happy with and which runs all the other software I use because of a problem with this one program. I'm not going to be moving forward with my purchase of the Affinity suite at this time (can you blame me?), but I'm still in need of a good .pdf generator for my book manuscript. If you resolve this issue please let me know and I'll reconsider purchase. In the meantime, I'm trying to learn Scribus. My system information (courtesy TechGuy.org): Tech Support Guy System Info Utility version 1.0.0.9 OS Version: Microsoft Windows 10 Pro, 64 bit, Build 19045, Installed 20230611161523.000000-300 Processor: AMD Ryzen 5 5500, AMD64 Family 25 Model 80 Stepping 0, CPU Count: 12 Total Physical RAM: 32 GB Graphics Card: AMD FirePro W5100 (FireGL V) Graphics Adapter Hard Drives: 😄 931 GB (862 GB Free); Motherboard: ASRock A520M Phantom Gaming 4 System: American Megatrends International, LLC., ver ALASKA - 1072009, s/n To Be Filled By O.E.M. Antivirus: Windows Defender, Enabled and Updated
  2. Hey guys, I worked all morning on a file that was based solely visually on a PDF. After one hour I saved the file and worked on it for another 2 hours. I just wanted to adapt the name of the reference PDF, searched for it in the Save As dialog and selected the file to avoid typing the file name manually (admittedly, I didn't double check, it was supposed to quickly save the file, but yeah I should've known better). I closed the document and left for lunch. When I came back I got an error message trying to open the file because it appeared to be saved in an unknown file format. Specifically as a file that was edited in Publisher but apparently saved as a PDF – when the file was saved, the suffix was also incorporated! Why doesn't the user get an error message or at least a warning dialog? How is it even possible that I could continue working for 2 hours in a seemingly corrupt document and didn't get a single hint of incompatibility due to wrong/double suffixes? Not even when occasionally quick saving (Ctrl + S)! But … luckily I remembered the solution from experience during my "Adobe-era" that by changing the suffix (usually hidden in Windows) manually you can sometimes get the file back to work. Adobe itself has found a solution: when selecting an existing file, somehow only the actual file name (everything preceding the .suffix) is inherited. Nonetheless I think this should be considered a bug! Cheers MrDoodlezz
  3. Hello Affinity Team sadly there is a high number of shortcuts which are not internationally compatible with the UK keyboard. It would be good if,for ease of learning, the shortcuts where chosen to be internationally compatible. UK-Keyboard German keyboard this is an ongoing keylist of incompatibilities with the german keyboard; Size bigger Ctrl+> <- only works with ctrl+shift+> Size Smaller Ctrl+< <- doesn´t work at all Size Precice Bigger <-only works with ctrl+alt+shift+> Size Precise Smaller <-doesnt work at all Spacing tighten More Ctrl+Alt+Left <- seems to move to the beginning of text Spacing Loosen More Ctrl+Alt+right <- seems to move to the end of text Alignment Align Left Ctrl+{ <-doesn´t work Alignment Align Centre Alt+|<- doesnt work Alignment Align Right Ctrl+} <- doesn´t work Alignment Justify Left ctrl+alt+| <-doesn´t work
×
×
  • 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.