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


  • Posts

  • Joined

Everything posted by emmrecs01

  1. Hi Walt. Whilst you were writing I updated my latest reply. It seems the problem is resolved (as detailed in my update) so, fingers crossed!
  2. From C:\Users\myusername\AppData\Roaming\Affinity\Photo\1.0\user to C:\Users\myusername\AppData\Roaming\Affinity\Photo\1.0(Beta)\user Is that not the correct place? assets.propcol in that folder of the release version is 5,346,332 KB; in the Beta folder it's 1 KB. As I wrote before, following the initial copy procedure shows the beta file to be the same size as the release. Opening the beta app, no assets shown, and assets.propcol in the beta\user folder is 1 KB. UPDATE: I decided to try what I considered could be a nuclear option! I moved the whole User folder out of the above Beta directory (saved it to my desktop, in case of disasters!) and then copied the complete User folder form the release to the beta. Result: all assets now available in the Beta. I shall keep the original Beta\User folder, which I have now copied to a different drive, until such time as I am happy that everything in the Beta is "as it should be". So, it seems, problem resolved, hopefully! Jeff
  3. Hi Walt. Many thanks for this response. I think this is something that I really need @Mark Ingram to comment on then. It is entirely possible that few, if any, of the assets in my release version were previously also used in my installation of the betas (I honestly can't remember) but I wonder why copying that assets.propcol file from the user directory in the release to the user directory in the beta seemed to go "without a hitch" (it showed as being approximately 5GB in size) but the assets did not show in the re-opened beta and the file size in that user directory was now 1 KB? Questions, questions... Jeff
  4. @walt.farrell Thanks for the reassurance that it's not just me! Did you also see my post in this forum re the non-appearance of Assets in this beta, even if the whole assets.propcol file is copied from the release "user" folder to the beta "user" folder? Jeff
  5. This is another problem I have encountered in the latest beta, .1079. Opening this version I found that my Assets tab was empty. Not a problem, I simply copied assets.propcol from the latest release to the beta, a total of about 5GB. They showed as present in the correct folder of the beta version. Opened the beta version, no assets! Checked the folder where they had been moved to and the file size now shows as 1KB!!! Repeated the whole exercise, still no joy! They seem to transfer without problem but, on opening the beta version it seems that assets.propcol reverts to being an empty file! Jeff
  6. @walt.farrell Hi Walt, Many thanks for the idea. Looking at the "log.txt" file I see that my Radeon GPU has, apparently, gained "Bonaire" as an additional name, so it seems both GPUs are being used, but the latest beta results (as above) are very disappointingly "low" by comparison with the earlier beta results. 😭😭 Jeff
  7. @Mark Ingram Many thanks for this latest beta release. However, I have noticed one change, when compared with an earlier beta, when running the Benchmark 1920 test. (I will also post this to the the pinned thread about Benchmark 1920 if that would be helpful.) Given the problems that have been encountered with recent releases of AMD Radeon GPU drivers, does this latest beta actually ignore or bypass them? For a benchmark test run under beta I see that both my Intel HD 530 and my Radeon R7 360 GPUs are being used; under this latest beta the Radeon GPU is not listed on the benchmark results and the scores are rather lower. I've copied below a section of both reports: The earlier beta: The latest beta: All ideas/advice very gratefully received. Jeff
  8. @Alfred Thanks for the correction. 👍 However, I wonder then, why PP 10 is not listed in either of the compatibility links I posted? Jeff
  9. @MorganX There is a problem with the AMD drivers which Serif have raised with AMD but so far there has been no resolution, I believe. I have the much lower spec AMD Radeon R7 360 and the two most recent driver releases by AMD have rendered all my Affinity apps totally unusable if Hardware Acceleration is activated. The only way to prevent the apps instantly crashing if using HWA is to use a driver which is, officially, two versions "old". Jeff
  10. @TheMan In addition to what @firstdefence has written: I don't think there ever was a "PagePlus 10", There was a PP 9 and a PP 11, but no 10. If you really do mean "PagePlus 11" then I would have to say whether it will run under Win 10 is rather doubtful, to say the least. The last released version was PagePlus X9, so several versions newer than PP 11. This page is from the Serif web site, showing compatibility of the legacy Plus products with various Windows versions. Or, even better, this updated page for the latest information. HTH Jeff
  11. @JennySwart Great to hear and thanks for the feedback. BTW, all of us were "first time users" at one time! Jeff
  12. @JennySwart Welcome to the Affinity forums. I'm not a Mac user but I think if you simply restart Designer and Publisher the registration screen should reappear. Alternatively, have you tried clicking on Help>My account? Jeff
  13. @Tami Welcome to the Affinity forums. If the apps are not listed in your Serif account it is almost certain you originally bought the apps via the Mac App Store, I think. Simply log into your MAS account, using the same credentials as you used on on your Mac27 and you should be able to download them all to your new laptop. HTH Jeff
  14. @YAR Oracool Actually you can! If you're prepared to install this free utility it will give you (temporary) access to the Windows Apps folder within C:\Program Files, so you can make those checks, I think. Having given yourself access, simply running the utility again will allow you to reverse the permission changes. (Before posting this I ran the utility to test that this would work. I already had it installed, for precisely this kind of situation.) HTH Jeff
  15. @Vepar Thank you for the feedback, and for confirming that the release of the 21.5.1 drivers has not resolved the problem.
  16. @Vepar Further to what @Alfred says, exactly which AMD Radeon driver are you running? The Radeon Adrenaline driver version 21.4.1 produced exactly the same problem for me. Reverting to 21.3.1 resolved the problem. (I see there is now version 21.5.1 but I have not installed that so don't know if AMD have found the problem. I know Serif were in contact with them.) Since you can't actually launch the apps in order to disable Hardware Acceleration this FAQ will show you how to disable it when the apps are closed. HTH Jeff
  17. @Dominique Perchet Affinity Designer does not have the facility to use plugins, so I doubt this will ever be possible, at least for the foreseeable future sorry. Jeff Affinity Designer n'a pas la possibilité d'utiliser des plugins, donc je doute que cela ne soit jamais possible, du moins dans un avenir prévisible, désolé.
  18. @Alan Thornbury Just to add a little to what @John Rostron has written: if you originally purchased APh from the Microsoft Store, simply log into the store using the same credentials as on your old computer and the app will be available to download and install on your new. Jeff
  19. @Nikolai Welcome to the Affinity forums. Serif use the LensFun Library for the lens correction data in APh. Which lens do you have and has it been added to the LensFun library? If it has I think it is likely that a future update of APh will incorporate the updated library and so it will be available to you. This quite lengthy thread includes more information about this. HTH Jeff
  20. @Gregory St. Laurent This thread is about the problems a user was experiencing when attempting to open DNG files in APh and so entirely appropriate in the Affinity forums. On the face of it, your question should really be addressed to DXO, shouldn't it, or have I completely missed the point?
  21. @matt.baker I downloaded and opened your file in both the latest release and the latest beta (1065). No problems in either version. (I have HWA switched on.) Seeing that, in your video you used Drag and Drop on your file, I repeated the exercise using that method, having previously used File>Open; again, no problem. Jeff
  22. @notapodato Welcome to the Affinity forums. Inevitable questions: which Affinity app, and which OS do you run? Jeff
  23. Can I ask why you cannot do this with pdf? Is it because you are concerned that visitors to your website might be able to download these files, rather than buying them? If you are showing only extracts, can you not either create exports of only those extracts, or even make screenshots of some pages from the pdf?
  24. @Mr Lucky I don't have or use Logic but I do have Sibelius Ultimate. Is there any reason why you do not export from Sibelius as .pdf? Jeff
  • 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.