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

ChristAlix

Members
  • Posts

    149
  • Joined

  • Last visited

Posts posted by ChristAlix

  1. Also have the same problem with hardware acceleration (OpenCL) in combination with Nvidia GeForce RTX 3070 on my HP OMEN notebook.
    Already invested several days in problem solving including installation of different driver versions and system optimization up to reinstallation of the operating system.  But no solution found :((

    OS: Windows 11 Pro (10.0.22621 Build 22621)
    Computer : HP OMEN 16-b0xxx (current bios F.44)
    Processor: 11th Gen Intel(R) Core(TM) i7-11800H
    RAM: 32GB
    1st GPU: Intel UHD (current driver 30.0.101.2079)
    2nd GPU: Nvidia GeForce RTX 3070 (current driver 535.98)

    What I haven't tried yet is installing the Affinity package as MSI (EXE) version. Until now I have installed only MSIX... But there I hope no improvement , maybe the general Performens, as described in the forum is but not at the OpenCL graphics acceleration....

     

  2. 14 minutes ago, sapstar said:

    Würde das nicht dazu führen, dass mein Laptop-Bildschirm nicht mehr funktioniert? Das NVIDIA-Bedienfeld weist darauf hin, dass mein Laptop-Display daran angeschlossen ist.

    image.png.585c6c7485b43b9bbb110eca22ba8e7f.png

    This NVIDIA setting is only for "PhysX" and this processor interface language only works with special 3D / CAD / Finite Elements or scientific programs. You cannot set "Acceleration" of Affinity here. In addition, Affinity Photo works with OpenCL interface.

    image.png.ef65ff074b6c4677ee26c5ea76a77dce.png


    If you disable the Intel GPU in the BIOS, don't worry, your laptop screen or external monitor will continue to work. There is an "electronic switching" to the video outputs automatically inside the laptop.

     

    Have the guts, it'll work out!!

  3. 4 minutes ago, sapstar said:

    Not sure I understand this. My laptop has 2 graphics cards. The integrated graphics card runs the laptop screen. Do you mean I have to select the same graphics card that is used by the monitor?

    It doesn't matter to Affinity Photo or Dersigner whether they have one or even five graphics cards. You select the "Preferences" menu in Affinity and choose the graphics card that should be responsible for " rendering" the displayed graphics in the Affinity Photo application window.

    Please have a look at the "Affinity Photo Help" under "Preferences".

  4. 15 minutes ago, Subclavius said:

    Which Renderer is APhoto using?  You can check this from Edit > Preferences > Performance.  Does it make any difference if you change from NVIDIA to using Intel Integrated Graphics, or to WARP?

    He has already mentioned this above, or does he mean "In Nvidia control panel" in the system control?1

    [ In Nvidia control panel, I changed my primary graphics card from Nvidia to the integrated Intel GPU. After this change, focus merge works. How can I resolve this problem. I have attached the Affinity Photo crash reports here.]

    Preference.gif.aa7bdd4e1feb5a80a4ef9be7d0abfa65.gif

  5. Hello Greg Wo, 
    it's a known problem, it occurs when smoothing (anti-aliasing) between the exact cut edges. There is some workaround for the problem and that is to click on the "Blend Ranges" (gear icon next to the lock icon) in the "Layers panel", a menu called "Blend Options" will appear. In the pulldown menu "Anti-aliasing:" Select [Force Off] and the edges of the cut will close.

    But beware, there will be strong / ugly stepping effects at the deliberately visible edges.

    See the example below.

  6. I have already noticed this solution, but it was not available "like this" until now. 
    It seems to be related to the "refresh rate" of the editing window, or it only refreshes when you zoom in and out or switch between documents. 
    In addition, the visual artefacts only occur with artboards. No artefacts occur in the normal document, but the bugs of contour tool and expand stroke get worse.

    S_curve_artboard_example.afdesign

    S_curve_doc_example.afdesign

     

  7. I don't know exactly how to classify the following curious behaviour of the "Styles panel", rather as a BUG or as a future feature. That's why I'm listing it here as a BUG and hope it is one!

    1st problem
    When I create the style of an object or shape (grey rectangle with black outline) in the "Styles panel", I only see a black quad under Styles. But if I click on the button "Draw stroke behind" in the panel "Stroke" under "Order:" and create its style in the "Styles panel", I see a light grey gearwheel symbol on a black quad under Styles. 
    I consider this visual behaviour in the Styles panel to be a BUG.

     

    2nd problem
    I can e.g. style an object without changing any parameters infinitely but as soon as I change the parameters (Style, Width, Cap, Join, Align, Mitre, Scale with object, Start, End, Arrow place, Swap) (except "Order:" parameters) in the "Brushes panel" or "Stroke panel" I cannot create a style in the "Styles panel". 
    Only when I change the parameters in the "Stroke panel" (Order:), in the "Color panel" (Line colour, Fill colour, Opacity), in the "Effects panel" (Fill Opacity, Effects) and in the "Layer panel" (Layer Opacity, Blend options, Blend Ranges) can I create a new style.

    For me, the above-mentioned style behaviour or its purpose is not logical and I don't see it as a BUG, but rather as incomplete or ill-conceived programming.


    For understanding:

    The change of the parameters allows the creation of a new style in a category:
    - Create same object style (multiple possible)
    - Change line colour
    - Change fill colour
    - Change opacity
    - Layer Effects (Effects panel & Layers panel)
    - Switch Order
    - Blend Ranges "Blend Options" (Layers panel)
    - Layer Opacity (Layers panel)


    Changing the parameters does "not" allow a style to be added to a category:
    - Layer Adjustments (Layers panel)
    - Assign a Brush
    - Swap Arrow head
    - Stroke Style
    - Change Line Width
    - Change Pressure

     

    Here in the forum I found a few messages on a similar topic!

     

  8. Hi Mithferion, I thought I was the only one with this "graphic bug". In the meantime I don't dare to post anything here in the forum because I have been snubbed by admins a few times.

    For the admins: I know that this "graphics bug" has not yet been fixed in the new beta 1.9.1.971. But nevertheless, "before anyone asks" I have attached a screenshot of the beta version.

     

    Affinity_Designer_1.9.0.932_bug_contour_and_compound_tool.afdesign

     

  9. Hi Mark,
    Hi Sean P,

    As you recommended, I have tested the new beta 1.9.1.963 for freez behaviour. The first time I tried it I was able to play around with Designer (Beta) for about 2 minutes after the system woke up and I was really happy, unfortunately the joy was short-lived. After that, not only Designer (Beta) but almost my entire Windows system froze. 
    It's still there! (Freez)

    It, Horror, Film, Fear, Scary, Strange, Creepy, Scare

     

    I uploaded memory dumps and WinDbg reports to DropBox (Sean P Link).

    PS: I have uploaded the dump image "Affinity Designer Beta 1.9.1.963_open restore.7z" to Dropbox. This was created when I tried to start the Designer (Beta) again after I had killed it. It offered me to open the restore file which I confirmed with OK and it came to the freez.

     

    image.png.e1f8611c475b33f3de2189b7466b0a07.png

     

    ChristAlix

     

     

  10. Hi Mark,

    Found out with my work colleague that on his machine, also HP EliteBook 8560w (2013) but still running Windows 10.0.18363 and the latest and last NVIDIA Quadro 2000M driver 377.83 (2018) the Affinity 1.9.0 and betas 1.9.1 work smoothly without freez.
    It seems that the "freez" problem is caused with the newer Windows builds from 1903 and higher. 

    Is it perhaps possible to disable the Windows "HDR query" behavior in the registry?

  11. Hi Mark, thanks for the effort...
    The phenomenon with updating to latest graphics card drivers is somehow inconclusive and confused for me. The Affinity products with the 1.8.5 versions ran "reasonably" smoothly before the update 1.9.0....
    The current driver version 376.99 (2017) was automatically updated with the latest Windows build (10.0.19042) from Microsoft.
    Before the Windows update, version 341.98 Rev.F (2016) ran smoothly with Affinity products, but caused preview problems with Autodesk Inventor/3DMAX. 
    The newest and latest driver from NVIDIA for the Quadro 2000M is version 377.83 (2018) works (according to benchmark) minimally slower with Autodesk Inventor/3DMAX but additionally brings freez with the Affinity 1.9.0 product line :(
    All three constellations are suboptimal for me :(

    Have now decided to leave the system on the driver version 376.99 (2017) and reset Affinity to 1.8.5 and hope that Affinity team manages to bring the updates to run stable!

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