Jon P
-
Posts
3,307 -
Joined
-
Last visited
Everything posted by Jon P
-
Hi @paolo.limoncelli We've tried this on a couple of Macs running 13.3.1 and haven't been able to reproduce any slowdowns so far. Can you clarify if this happens on both Designer Beta and Photo Beta, and if it happens on the non beta versions of the apps I can see installed on your machine? -
Thanks for the report. I've logged this, but in the future if an issue affects retail please post it in the Bugs forum, this forum is for issues that are specific to the Beta.
- 1 reply
-
- 1
-
-
- 2.1.0.1781
- apu
- (and 2 more)
-
Thanks for the post, this is something we are aware of and it's already been fixed internally
-
Thanks for the post, this is something we are aware of and it's already fixed internally.
-
Can you provide a video demonstrating the issue? It might help me see what step I'm missing
-
Is this a custom profile that has been installed? I've tried switching to the ProPhoto RGB profile we ship and that is remembered on the next app run up. I've also tried installing a custom RGB profile and that is remembered on next app run up, on both Mac and Windows. So not sure what I might be missing to reproduce this issue
-
Thanks, this has been logged
-
Cross References
Jon P replied to Ash's topic in [ARCHIVE] 2.4, 2.3, 2.2 & 2.1 Features and Improvements
Good spot @MikeTO, I've logged that -
Hey @AlainP, Do you happen to remember if you had an object selected at the time you selected a colour via the colour wheel? If so what type of object(s) were selected? I'm struggling to reproduce this right now but will keep an eye out. If it happens again please attach some more crash reports
-
Apologies this got missed, we've got an improvement logged to simulate overprint in the app
-
Apologies if threads sometimes get missed, we are keeping an eye on this forum and responding to most threads, sometimes they may have to be prioritized due to the amount of people reporting an issue/if it's easily reproduced, but we do aim to get around to everything. A couple of us have tried this on different machines and can't reproduce a 4 second delay with some medium/large size documents. Out of curiosity, is this slow down on new blank documents too, or does the slowdown scale with the size/amount of the documents you have open? If so could you let us know what system specs you are using? Can I also confirm if this is a change in behavior in 2.0.4?
-
Hi @NAV777, Are there any crash reports in %userprofile%\.affinity\Publisher\2.0 (Beta)\CrashReports that sync up with some of your random crashes? Or is the app always hanging and not generating reports? If so, right clicking the process in Task Manager when it's hanging and manually creating a dump file may help us pinpoint the crashes. Do you only get this behavior in the beta? Is 2.0.4 ok?
-
Can you ensure that %ProgramData%\Affinity\Publisher\2.0 (Beta) exists and try running the app up again and seeing if you get the same issue? The fact it had to elevate when creating a folder in %ProgramData%\Affinity is interesting and not normal behavior, and could be related to the issue you are seeing. It could be worth ensuring the app is run as admin
-
Thanks, do you mind also confirming you have no issues manually creating a folder within %ProgramData%\Affinity and %Userprofile%\.affinity?
-
Thanks for the event viewer, it seems to be errorr'ing when attempting to create one of the user data folders, which lines up with why there are no folders (including a crash report folder) in there. Do you mind confirming if you are the only user account on that machine and that it is an admin? Can you also open up a run prompt and type in %ProgramData% and let me know if that opens up C:\ProgramData?
-
Also, can you navigate to https://store.serif.com/account/downloads/, where you will have downloaded the 2.1 Beta, and download the EXE for Publisher, and see if after installing the EXE you have any luck running that up, see the attached screenshot if that helps:
-
Ah in which case it may be that it's not getting as far as generating a crash report (looking at your Publisher.zip this does seem to be the case), I assume you have no issues running 2.0.4 up (as there are some crash reports in that folder)? Are you able to go into Windows Event Viewer after a failed run up of 2.1 Beta, and look into the Windows Logs/Application section and see if there are any errors relating to Publisher.exe, and paste what is in there if so?
-
Thanks for that Log, I was hoping there may be something in the CrashReports folder there to look into, see attached:
-
Hi @JosueVivas, could you navigate to %userprofile%\.affinity\Publisher\2.0 (Beta) and upload any crash reports in the Crash Reports folder Thanks
-
Thanks for the report. The wrap outline seems to be being saved in an odd position, if after loading the file you edit the wrap outline you can see it's off the spread. Moving it back into position will also fix the issue until next save. I've reproduced this and logged it
-
Good spot, I've reproduced and logged this
-
Thanks @walt.farrell, Turns out this should be fixed in the latest beta, so if OP is still getting this in 2.1.0.1736 let me know
- 4 replies
-
- 1
-
-
- spellcheck
- spellchecker
- (and 3 more)
-
Hi @TAZ Devil, Welcome to the forums and the beta. Can you clarify if this is a beta only issue, or if you are encountering this in the release (2.0.4) builds? I've just checked this in Publisher Beta and it seems to remember the word on the next run up of the app If you could specify which OS you are on also that would help
-
Thanks for the file and video @siapec. It's simply deselecting the text that's triggering it. We've reproduced and logged it
-
Files fails to open - "features from a later version"
Jon P replied to Dennison's topic in V2 Bugs found on macOS
Hi @Dennison, Thanks a lot for the new crash report, it was very helpful. We've looked into this and we think we know what the issue is, and hopefully will have a fix for this in the next beta. However I think you can fix this now on your end. If you navigate to the Appearance Panel (the one that Paul asked for a screenshot of in the first page of this thread) and change the Apple Highlight Colour to something other than Red, and then back to Red, this should hopefully get the beta running for you. Let me know if that's not the case, either way the next beta should hopefully not crash on run up even without doing the above
