KFam Posted February 4, 2023 Posted February 4, 2023 I am trying to associate the AP ver 2 to a file type in another "open with" on another image browser I can see only my older ver 1 in usual "Program Files" Affinity folder. Where is the new exe installed by new MSIX installer when I bought the new ver 2 application package ? I have associated the image type with AP ver 1 all right but locating the execuatable for ver 2 in windows 10 or 11 is a little difficult. How is the new structure organised ? MSIX means new version 2 only appear as a 300+ Mb install as I assume it marks all shared DLL et al files as under ver 1. Quote
walt.farrell Posted February 4, 2023 Posted February 4, 2023 14 minutes ago, KFam said: I can see only my older ver 1 in usual "Program Files" Affinity folder. Where is the new exe installed by new MSIX installer when I bought the new ver 2 application package ? If you've installed the MSIX version then the executable is in a hidden directory that (most likely) other apps won't be able to link to directly. If they require you to specify the path name then they probably won't work with it. Some, though, let you simply specify a program name. If you're using one of those applications, try AffinityPhoto2 or AffinityPhoto2.exe which should work if they support Windows App Execution Aliases. Or, some distinguish between programs and Windows applications. If yours gives you that choice, choose Windows application, which may allow you to find it. Alternatively, you could uninstall the MSIX-based one you have now, and install the EXE/MSI-based version that was released on about January 27. KFam 1 Quote -- 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.3.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
WirlyWirly Posted February 4, 2023 Posted February 4, 2023 On a related note, I have the v2 MSIX installation, however I'd like to replace it with the MSI installers. I don't want to lose any of my studios/settings though, so I'm wondering where these configurations are saved that way I can copy them over to the new MSI location? Quote
walt.farrell Posted February 4, 2023 Posted February 4, 2023 18 minutes ago, WirlyWirly said: On a related note, I have the v2 MSIX installation, however I'd like to replace it with the MSI installers. I don't want to lose any of my studios/settings though, so I'm wondering where these configurations are saved that way I can copy them over to the new MSI location? You don't need to do anything. The MSIX-based and the EXE/MSI-based versions store the settings in the same directory. All you need to do is install the EXE/MSI version and if you want (it's best to do so) uninstall the MSIX-based version. WirlyWirly 1 Quote -- 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.3.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
v_kyr Posted February 4, 2023 Posted February 4, 2023 3 minutes ago, walt.farrell said: The MSIX-based and the EXE/MSI-based versions store the settings in the same directory. If I recall correctly from looking once on a Win box, it was for V2 apps in the users home folder (?). Quote ☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan ☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2
walt.farrell Posted February 4, 2023 Posted February 4, 2023 (edited) 1 hour ago, v_kyr said: If I recall correctly from looking once on a Win box, it was for V2 apps in the users home folder (?). %USERPROFILE%\.affinity Edited February 4, 2023 by walt.farrell Correct erroneous directory name Thanks, v_kyr! v_kyr 1 Quote -- 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.3.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
v_kyr Posted February 4, 2023 Posted February 4, 2023 12 minutes ago, walt.farrell said: %USERPROF%\.affinity %USERPROFILE% ok then I've used the correct ones in OpenCL Disabler for v2. walt.farrell 1 Quote ☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan ☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2
walt.farrell Posted February 4, 2023 Posted February 4, 2023 39 minutes ago, v_kyr said: %USERPROFILE% ok then I've used the correct ones in OpenCL Disabler for v2. Thanks. Fixed. I've been curious: why is OpenCL Disabler still needed? Can't one just use the --no-ocl command-line argument now? Quote -- 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.3.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
v_kyr Posted February 4, 2023 Posted February 4, 2023 6 minutes ago, walt.farrell said: I've been curious: why is OpenCL Disabler still needed? Can't one just use the --no-ocl command-line argument now? Sure should do basically the same, but what if the respective Affinity app cores before performing that operation, or doesn't start that CLI cmd way at all here for you? - My OpenCL Disabler tool isn't dependent on a running Affinity app at all, it works completely independent and doesn't need an Affinity app to run at all. walt.farrell 1 Quote ☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan ☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2
Recommended Posts
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.