Search the Community
Showing results for tags 'sandbox'.
This was discussed in another related thread and tested by a number of users using the “unzip to desktop” unofficial install method for the MSIX package in order to negate sandbox. It was learned that there is a significant performance increase when using the same package un-sandboxed versus sandboxed. (i.e. sandboxed == slower) It seems to impact higher end hardware more, but it isn’t clear for sure without more machines being tested. I tested an AMD card in the other thread and it showed a hit, but that card is not that powerful compared to the others. (Feel free to add your own tests below with higher end AMD cards) These tests are using the official 126.96.36.1991 MSIX installation vs MSI installations. 230127_188.8.131.521_Sanded-vs-Unsanded-Benchmarks_ALL-MACHINES.zip I tested with 3 machines using 3x benchmarks for averaging each installation method: Machine 1 (Main): Microsoft Windows 10 Home (Build 19045) AMD Ryzen 7 5800X @ 3.8Ghz (-30 all core +200mhz PBO); Mobo: Asus X470 Prime Pro 32GB DDR4 (3600Mhz) EVGA NVIDIA GeForce GTX 3080 X3C Ultra 12GB Monitor 1&2 4K @ 150% Perf Variance: 16 ~ 20% Sanded: Unsanded: Machine 2 (Hub’s): Microsoft Windows 10 Home (Build 19044) AMD Ryzen 5 5600X 6 core @ 3.7Ghz Asus ROG Strix B450-F Gaming 16GB DDR4 (3200Mhz) Gigabyte RTX 3070 Gaming OC 8GB Rev 2.0 Monitor 1 1440p @ 225% Perf Variance: 15 ~ 21% Sanded: Unsanded: Machine 3 (Living Room): Microsoft Windows 10 Home (Build 19045) AMD Ryzen 7 3600 6-core @ 3.8Ghz (-30 all core +200mhz PBO) ASRock A520M-HDV 32GB DDR4 (3000Mhz) Asus TUF GTX 1660 TI Monitor 1 4K @ 225% Perf Variance: 12 ~ 14% Sanded: Unsanded:
I have an issue with a font manager called FontAgent Pro. It has a font auto activator, which is very handy because I use many different fonts and don't want to have these activated all the time. I run into the issue where the auto-activation works very well for the Beta versions, but not for the app store release versions. How can this be? Is the way the app store version is sandboxed a limitation for this to work? If this is the case, is it possible to update to the non-app store version of Affinity Designer (sold in the Affinity Store) as I believe this does not have the sandboxing?
A question just occurred to me when thinking about how iCloud will work with the suite. Affinity shares the same file format across all the apps right? So in other words I will be able to open my Affinity Designer files in Affinity Photo? If that is the case then how does sandboxed iCloud storage work? If I save one of my Affinity Designer files in the iCloud sandbox then when I go to Affinity Photo it won't be in the Affinity Photo sandbox.