NathanC

Hi @jcc5018, It's very likely that you have a mixture of the apps installed using the two different installation methods: MSI (AKA .EXE installer) and the standard MSIX installer. When you mix the two installers for the apps this can cause app conflicts and will continually re-prompt you the activation page and give you the 'please try again' error when you try and run them concurrently. There are ways to distinguish the two install methods for the apps on your PC, however for the sake of simplicity I would recommend uninstalling all three apps and then re-installing them using the same installation method for all three applications. You should be able to uninstall them via Windows Settings > 'Installed Apps'. If you would like to install all three using the MSI(EXE) installer, I've linked a guide below which details how to download the apps via the MSI, if not the MSIX will be available on the Affinity store 'Downloads and product keys' or the 'V2 licenses' page.

Hi @norbinw, As Walt mentioned this is a known issue already logged with the developers, I've bumped it with your report however it's not something I'm able to provide a timeframe on when it will be fixed, apologies.

Hi @cgidesign, This behaviour already exists within the app and requires the Alt modifier key to be used along with the scroll wheel, this will rotate the canvas based on the mouse cursor location. If you hold down Shift and Alt and then scroll this will rotate based on the document view centre. Make sure that you have 'Enable canvas rotation with Alt+ scroll wheel' enabled under Preferences > Tools or this won't work. https://affinity.help/photo2/English.lproj/pages/DesignAids/rotateCanvas.html If you have just assigned the 'Rotate left/right' options shortcuts under the View menu these just rotate the canvas based on the document view centre, as far as I'm aware this has always been the case. I hope this clears things up 🙂

Hi @thegary, There were some general improvements to performance made in 2.1, but I don't think this is an issue we've been able to re-produce likely due to the number of Windows system and Hardware variables involved. I've included some follow up points below so that we can better understand your setup as it's likely to be an issue specific to your environment: - Can you provide a screenshot of your System Information Summary so we can see your specs and OS version? - Can you provide a screenshot of your in app performance preferences? Have you got the same settings as your performance preferences in V1? - At the point at which you begin experiencing the lag within the app after having it open a few hours, could you send us a screenshot of your task manager 'Details' an 'Performance' tabs so we can see the app hardware usages? - You mentioned that it has persisted since V2, have you tried comparing this with V1 on your setup by leaving it open for a few hours? It would also be great to see a comparison recording between V1 and V2's performance after a few hours. - Does it matter what type of document you have open, for example if you were to just leave a blank new document open for a few hours and then come back to it does it then start lagging? ---- I've also included a number of suggestions below to try to see if this helps improve things: - Try turning on Hardware Acceleration (OpenCL) if your GPU supports it, restart the app and then see if the issue persists. Also make sure that you have the latest Graphics card drivers available for your GPU installed, if possible do a clean install of the drivers when updating. - This may sound counterproductive, but try reducing your RAM usage limit in the app performance preferences to half of your installed memory and then restart and monitor, we have had reports of this helping some users under certain circumstances. - If you're using the standard sandboxed MSIX apps, try uninstalling them and switching over to the .MSI/EXE apps as we've had reports of improved performance when using the MSI apps. Many thanks

Hi @4dimage, Looks like this is caused by an existing issue with the layers panel hit area not working correctly when drag and dropping objects between picture frames that are next to one-another in the layer stack, I've now added the details of your report and bumped the issue. 🙂

Hi @IOMendez_10 welcome to the forums, In addition to Walt's question above, could you confirm if this issue occurs on a brand new document? Does the application immediately crash or does it just hang/freeze? If it's an app crash, could you provide us with a few recent crash reports, the forum thread below details how to find these. Many thanks!

Hi @WEHI_Chris welcome to the forums, It is understandable if you do not wish to share the file publicly, though so we can look into this further could you possibly upload the file to the private dropbox link below so we can inspect it's contents? https://www.dropbox.com/request/RSKMlE1Xkso9gzsJfg7f If the images were placed as linked resources (can be checked in the resource manager under 'view'), could these images be included as well? Also, could you advise which version of MacOS your colleague is using? Many thanks

Hi @Hangman, As you've pointed out there is an issue logged under AFD-6216 which details the same issue as what you've shown with CMYK values >50% being imported incorrectly at 50%, the issue missing some specifics which you've outlined here, such as the palette needing both a CMYK and RGB colour definition for the bug to trigger and the 3rd party app requirement. To avoid any confusion by logging the same issue twice i've now updated the existing issue with the details of your report along with your sample files which better demonstrate the issue. I've also since found that this is a regression between 1.10.5 and 1.10.6, if you open any of your .EPS files in 1.10.6 you should encounter the same issue with the .EPS CMYK values being capped at 50%, I'm guessing you're still running 1.10.5 if this is still working for you? Thanks again for the level of detail and sample files. 🙂

Hi @coolpowers welcome to the forums, Many thanks for providing detail, i've replicated your issue on Windows and it has now been logged with the developers. 🙂

Hi @beardedcraig, Happy to hear that you've found a way to resolve the issue if you do encounter it again in the future. I'll see if I can replicate the issue based on your recipe and get it logged, many thanks for taking the time. 🙂

Hi @Bob Rastall welcome to the forums, Thanks for providing additional info, I'll see if I can get an OM Systems camera to try and replicate this issue with as it looks like the OI.Share app requires it to wirelessly tether.

Hey @walt.farrell, I've now logged this inconsistent regex behaviour with the developers, many thanks. 🙂

Hi @JavierBecana, Many thanks for the detailed recording and steps, i've been able to replicate this issue and it has now been logged with the developers. It looks like the trigger for the issue is moving the freehand selection area after initially drawing it, if this is not done the redraw issue does not occur (for me).

Many thanks for the files, as expected they have opened without any issues on my side, so i've gone ahead and swapped them to being linked resources, I'll DM you a dropbox link to the .Zip of both files containing the linked resources and doc shortly, let me know if you're now able to open the files. Although it shouldn't really matter since it's resources embedded into the document one thing that stood out to me was the location the images were originally placed from being on ICloud (see below path of the embedded resource). I'm wondering since you mention you can replicate this issue on any document with an embedded resource, what if you were to create a brand new document and File > place a resource from a local location instead of ICloud and then save & close the file and see if the issue occurs when you next load the same file (make sure the placed doc is embedded).

Hi @resunoiz, Although it prompts the shortcut conflict warning it should still function, If I assign 'Move to front' or 'Move to Background' the CTRL + Alt + C shortcut and then use it within the layers panel, it does re-arrange my layer when using the shortcut as expected. However, it shouldn't be giving a warning when there isn't a conflict in the first place with 'Align Centre' being unassigned, so i'll log this with the developers. 🙂

Hi @Corgi, This is a known issue currently logged with the developers, i've updated the existing issue and bumped it with your report. The tag for this issue is slightly different to afp-3062, but it is the same issue. 🙂

Hi @beardedcraig welcome to the forums, If you could send me a copy of your file(s) to the below dropbox link i'll then confirm if this is the same problem as OP had and then see if the files can be opened on your side if I swap the resources over to linked and go from there 🙂 https://www.dropbox.com/request/G4ZADRLm0HsPSaHbU7X2

If there is an external storage location that uses the same file path on both of your machines there shouldn't be a problem with using shared storage, but if you do notice the files no longer load after exchanging them, try changing the linked resource(s) location to local storage and then send the external linked resources when you exchange the files to confirm if the shared storage is the problem.

Hi @renisdead welcome to the forums, It might just be me, but it looks as if the content on your linked .afphoto file is blurred because the .afphoto file contains missing resources, in addition to checking what hangman's mentioned above could you possibly upload the files used in your above screenshot? Many thanks

Hi @FoxyCornelieus, As an idea, why not have an original 'source' document where you can edit and re-position content accordingly and then on a separate document where you need different scaling proportions/layouts File > Place (Or use the image place tool) the source document in as a linked resource. You can then duplicate the linked resource which exists as a single object in the layers panel and re-position and scale it accordingly. You can then freely edit the content of the source file and save it, which will update all instances of the linked resource. You could create the source file in any of the three apps before placing it into your Publisher doc. Make sure that the placement policy of your document is set to 'Prefer linked' in document setup before placing it and 'Automatically update linked resources' is checked in the app Preferences > General.

I've been able to replicate the issue and it has now been logged, many thanks

Thanks for sending the file over, I’ve been able to open it successfully and can see it contains mostly embedded resources with two missing linked resources which storage location was on Onedrive, this might be the problem if it’s actively trying to link back to this location but can’t. I’ve PM’d you a dropbox link to a version of your file where I have removed the two missing linked resources, could you confirm if you’re able to open the file now? If you are, see if embedding images in your other files and then opening them allows you to exchange them without running into this issue.

It really depends on what you want to trace over but you can find different workflow examples available online, the majority of the video tutorials online are for desktop but that doesn't necessarily mean they can't be followed on iPad, I did find one for iPad below but this is an example of tracing a pixel image to create a vector silhouette.

Hi @Mainecoon364, On both Designer V1 and V2 you can manually trace over a a pixel image using the vector tools available within the app (E.G Pen Tool, Vector Brush tool, pencil tool), Designer V1/V2 doesn't currently have an auto trace function currently as previously mentioned. See v_kyr's post below where he has also included a list of 3rd party apps available on iPad which can perform this function.

Hi @Radosław, The colour panel defaults to 'Tint' when an object with a global colour is applied as the tint property can be altered without the object losing it's global colour assignment on that particular object, you can edit the global colour from this panel using the respective button that will bring up the wheel/sliders etc. As far as I'm aware there isn't a way to change this behaviour currently. However, If you no longer want the object to be assigned to a global colour you can change the fill along the context toolbar which will in turn swap the colour panel back. 🙂