Jump to content

Recommended Posts

Posted

Since upgrading to 2.1.1 Designer 2 doesn't fully open anymore. It gets stuck in "non-responding" state while loading the user interface but there are no menus or other interface stuff visibile. This seems past the "initializing fonts" and "initializing data" messages, the splashscreen is still open.

I've tried waiting for like 5m and it goes nowhere, all I can see is a crashpad_handler.exe subprocess, other than that there doesn't seem to exist any sort of activity.

Is there any way to debug exactly what's happening? It was working properly before 2.1.1.

Thanks in advance..

Designer2.1.1-splashcreen.png

Designer2.1.1-UI.png

Posted

If you start Task Manager, you can expand the entry for Affinity Designer 2, right-click on the first expanded entry, and choose Create Dump File.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.2.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

  • Staff
Posted

Welcome to the forums @Alexandre Paes,

If you're encountering an app hang on startup, I would initially suggest trying a basic CTRL run up to do a basic reset of the user defaults and most recent documents by following the below:

  1. Close all Affinity apps
  2. Hold down CTRL and launch Photo 2 whilst still holding CTRL
  3. This will prompt a 'Clear user data' menu with three boxes ticked, in addition to these tick 'Reset Most Recent Documents'
  4. Press 'Clear' and the app will now hopefully launch.

If that fails, I wouldn't expect this to be the cause if the app launched prior to updating to 2.1, but it would be worth ruling out Hardware Acceleration being the problem by running the app with the --no-ocl flag which will disable the setting from outside the application, i've linked the full FAQ below.

 

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

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