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

Mark Ingram

(Ex) Staff
 View Profile  See their activity

  • Posts

    5,358

  • Joined

  • Last visited

 Content Type 

Posts posted by Mark Ingram

    Extremely disappointed that this installs as an "App" and not regular software program

    in Pre-V2 Archive of Affinity on Desktop Questions (macOS and Windows)

    Posted

    Just now, SpiffinJay said:

    Isnt there currently some sort of issues with those aliases. I hope you can fix those issues some people seem to be having with those aliases currently.

    Windows creates these aliases on our behalf, so I believe the issues are with the applications attempting to launch them. RawTherapee, for example, works fine with the aliases, along with many other applications that we tried.

    Extremely disappointed that this installs as an "App" and not regular software program

    in Pre-V2 Archive of Affinity on Desktop Questions (macOS and Windows)

    Posted

    20 hours ago, François R said:

    Major blunder by Serif. What they can do, however, is to install launcher apps with a static path somehere outside this Windowsapps folder. I hope.

    We already have app execution aliases installed to:

    C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityDesigner2.exe

    C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityPhoto2.exe

    C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityPublisher2.exe

    Please replace username with your Windows username. Also, those paths are already in your %PATH% variable so you can launch them without even specifying the full path, e.g. AffinityPhoto2.exe.

    Affinity V2 on Linux

    in Feedback for the Affinity V2 Suite of Products

    Posted

    It's nothing to do with Apple. We haven't implemented a Linux version because there simply isn't enough support for it. I realise that's not a satisfying answer for Linux fans (which I count myself as one), but take a look at the thread linked above, 136 votes of support for Affinity on Linux. It means we would never recover our engineering costs from developing a Linux version.

    Affinity products for Linux

    in Feedback for the V1 Affinity Suite of Products

    Posted

    On 8/14/2022 at 12:49 PM, 1stn00b said:

    i find it funny they can't afford better developers if the one they have are unfit to develop on other platforms like Android or Linux

    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.

    Affinity products for Linux

    in Feedback for the V1 Affinity Suite of Products

    Posted

    1 hour ago, 1stn00b said:

    the only one to blame for no Linux support is actually Serif not others

    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%

     

    Affinity products for Linux

    in Feedback for the V1 Affinity Suite of Products

    Posted

    4 hours ago, chiddekel said:

    Thanks for this tip - equivalent on bottles is VKD3D and DXVK - for now app in bottles work with switch --no-hw-ui 
    If Direct3D11 is for rendering document so on bottles (wine) is time to search which patch for VKD3D and or DXVK is use to run app without switch --no-hw-ui.
    On winehq and proton site there is many solved issue with flickering on D3D (VKD3D) after apply certain patch.



     

    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.

    Affinity products for Linux

    in Feedback for the V1 Affinity Suite of Products

    Posted

    14 hours ago, Kajac said:

    I have exactly the problem of .NET 3.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).

    Affinity products for Linux

    in Feedback for the V1 Affinity Suite of Products

    Posted

    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).

    Affinity products for Linux

    in Feedback for the V1 Affinity Suite of Products

    Posted

    9 hours ago, Renzatic said:

    So we're 3/4ths of the way there. Underneath it all, there's a working program. We just need to wait until a fix comes by that stabilizes the UI.

    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).

    A .notdef glyph in oil

    in Share your work

    Posted

    From Alfred's link:

    Quote

    It is recommended that the shape of the .notdef glyph be either an empty rectangle, a rectangle with a question mark inside of it, or a rectangle with an “X”. Creative shapes, like swirls or other symbols, may not be recognized by users as indicating that a glyph is missing from the font and is not being displayed at that location.

     

    It is spring. - A language-independent glyph to convey that meaning

    in Share your work

    Posted

    On 3/21/2022 at 7:02 PM, William Overington said:

    How is the meaning of the glyph expressed in the languages that you know please?

    William

     

    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.

    AMD Radeon RX Hardware Acceleration

    in V1 Bugs found on Windows

    Posted

    2 hours ago, ziplock9000 said:

    Would it be possible for you to go into specifics about the issue as people like myself are software engineers.

    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.

×
×
  • 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.

 Accept Cookies  Reject Cookies