Jump to content

Fcunhaster

Members
 View Profile  See their activity

  • Posts

    29

  • Joined

  • Last visited

Reputation

3 Neutral

See reputation activity

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1.    Fcunhaster reacted to a post in a topic: Bug on latest version 2.6.3 on windows
  2.    Fcunhaster reacted to a post in a topic: Bug on latest version 2.6.3 on windows
  3.    Fcunhaster reacted to a post in a topic: Bug on latest version 2.6.3 on windows
  4.    walt.farrell reacted to a post in a topic: Affinity Suite 2.6.2 folders and contents weren't removed after successfully updated to 2.6.3 on Windows 11 24H2 (OS Build 26100.4061)
  5. Fcunhaster
    Yes, they were both fully installed. Windows 11 Home 24H2 (OS build 26100.4061) would read only the last install (2.6.3), but NVIDIA APP would read both (2.6.3 and 2.6.2). Removing the older version manually didn't cause any trouble and 2.6.3 had been successfully updated, just didn't clear the previous version as it usually does.
  6. Fcunhaster
    Check the WindowsApps folder which is invisible under Pograms Folder and see if you have both installed and it's acting up, going for the older version.
  7. Fcunhaster
    I always use the auto update, so if there was a mix of installers was not on my end. But they did update and install on the proper location.
  8. Fcunhaster started following Importing an Affinity Designer Background with Bleed into Affinity Publisher , Affinity Suite 2.6.2 folders and contents weren't removed after successfully updated to 2.6.3 on Windows 11 24H2 (OS Build 26100.4061) , Bug on latest version 2.6.3 on windows and 1 other
  9.    Fcunhaster reacted to a post in a topic: Bug on latest version 2.6.3 on windows
  10. Fcunhaster
    Maureen, I did notice that the 2.6.3 update left behind the entire last version of all Apps, so you might have 2.6.2 still installed and be generating a conflict. I had to manually remove the 2.6.2 install from the WindowsApps folder, which is invisible by nature. Windows itself wouldn't detect the install duplication, but NVIDIA APP would, that's how I spotted it early before I had a major issue. I just reported that as a bug in the Forum.
  11. Fcunhaster
    Fcunhaster changed their profile photo
  12. Fcunhaster
    Affinity Suite 2.6.2 folders and contents weren't automatically removed as usual after successfully updated to 2.6.3 on Windows 11 24H2 (OS Build 26100.4061). I had to go to WindowsApps Folder, because on Installed Apps was showing with no duplication but on NVIDIA App was showing as a double install as both versions were fully present and that's how I noticed. I did remove manually the 2.6.2 Folders for the 3 Apps, Designer, Photo and Publisher. All is working normally, but that would eventually get in the way and create some conflict. Some users may be having the same issue without knowing and Windows shows only ONE installation when they're really both fully active. I'm not sure this is a Windows issue or is an Affinity Install issue as Windows had it's Monthly Security Update on the Tuesday before the Affinity update kick in on the same week's Thursday. Note: I did notice on Designer that some brushes behavior wasn't as I remember, sometimes it does drawing live and auto-apply but not always as usually is and it requires to be applied as a style and setting line's Stroke after drawing it. I used both Pencil Tool and Vector Brush Tool to test that, Vector Brush seems to allow Live Drawing with a Pre-Selected Brush, but Pencil requires it to be applied after and adjust Stroke weight. Maybe this is an intended feature and I just didn't had noticed it before. I have no error messages and won't ask me to reinstall or anything strange and all the Brushes and other Assets Installed do show and seem to work correctly.
  13. Fcunhaster
    Those 3D features that were removed from Photoshop, I could use them for some projects, specially for 3D Game related content. Will we have have them implemented, or at least a plug in that does that (If there's one, I'm oblivious of it). Tysm.
  14.    Dan C reacted to a post in a topic: Affinity Suit Apps assuming the wrong Graphic Card for Hardware Acceleration
  15. Fcunhaster
    Time to Upgrade then lol. Tysm for the answer.
  16. Fcunhaster
    Well, for what I understand, for NVIDIA Graphic Cards latest supported version is OpenCL 1.2 while other Graphic Cards like Intel HD have OpenCL 3.0. I'm having a compatibility issue right now where allowing the Graphic Card manual choice for Hardware Acelleration would be a life saver, I got a run around that also works, but probably not the ideal result on the image I'm working. My NVIDIA has 2VRAM of Dedicaded Memory while the Intel HD is a basic Graphic Card. Well, it's a mess right now for NVIDIA users. I have it all FORCED to Affinity Apps to use NVIDIA GeForce 930M, it shows on Render GPU, but on Hardware Acceleration it still reads Intel HD Graphics 520 because it's OpenCL version shows as higher version, when it really isn't. For what's I've read, officially it's 3.0, but 3.0 is just a renaming of 1.2, and the supported OpenCL C language standard is still 1.2. I've learned a little more about this issue because until recently all was set up to NVIDIA by default and I never had to worry about that.
  17. Fcunhaster
    Thank you very much. I knew I was doing something wrong 😆
  18.    Fcunhaster reacted to a post in a topic: Importing an Affinity Designer Background with Bleed into Affinity Publisher
  19. Fcunhaster
    I'm not doing something right, it's maybe a bug or a preference I need to activate, but when I make a background on Affinity Designer with Bleed, it does export fine to a Print Format showing the bleed area, but when directly imported the Designer File to Affinity Publisher, it imports it trimmed to the page format and disregards the bleed area. Anything else I can do differently to fix this? I'm on V2. Thank you so much in advance.
  20. Fcunhaster
    It helped, thank you.
  21.    Fcunhaster reacted to a post in a topic: Missing dictionary for language [warning] in Publisher
  22. Fcunhaster
    The "Awesome" has more advantages, but that would be precious for sure.
  23. Fcunhaster
    Maybe Serif could make a 1st contact, would be in mutual benefit and Fontbase devs are willing and they know it already, could be a solution.
  24. Fcunhaster
    I read that too on their Forum, because I do use Fontbase. It's up to Serif to get back to them now on that matter because it would be extra helpful to be able to have Font auto-activation working properly with Affinity Suite, specially if you're "Awesome" and take adantage of the full access to Google Fonts through them.
  25.    Fcunhaster reacted to a post in a topic: FontBase | Font Auto-Activation
  26. Fcunhaster
    Tysm, I was going insane. lol
×
×
  • 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.