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

Mark Ingram

(Ex) Staff
  • Posts

    5,358
  • Joined

  • Last visited

Everything posted by Mark Ingram

  1. For a long time I've tried to acquire a colour profile that displays whites as yellow (I've seen a lot of reports over the years...), but never succeeded, every file provided by a customers has worked as intended... However, the AMD profile does incorrectly show whites as yellow. Here's Designer: And here's Photoshop: The only interesting difference is that the document background in Designer is correctly drawn as white, which means the background colour is bypassing the colour profile conversion (normally not much of an issue, but a useful debugging feature now I guess)! It would be good for us to try to detect these kinds of broken monitor profiles, and disable colour profile conversion, and give a message to the user.
  2. Excellent detective work @- S - , thanks very much. I'm going to give that AMD profile a try, and see what happens here...
  3. @Throne777, is that the default profile (SurfacesRGB.icm) that came with your Surface Pro 3 laptop?
  4. Hi @Aileen Russell, as I mentioned in the post above yours, we have a fix for this now, available in a beta build, that we hope to roll out soon.
  5. Thanks @BeansAcquired, the "Low Precision Mode" in the beta is the same as the "--legacy-wintab" command line option in the retail build.
  6. Do you have a licence.xml file in the Designer folder? We identified a problem with the installer that it would fail to install if that file was in there. To work around it, you can move that file out of the directory, do the install, then put the file back into that directory.
  7. What are you doing at the time in order to cause the system to hang? What CPU do you have?
  8. Hi @Mezcapp, I missed the fact you said Surface Book in OP. I don't think that's using the WinTab driver (and will instead use the new Pointer API, aka Windows Ink), so you shouldn't have been affected by the --legacy-wintab switch. Unless you have a Wacom too?
  9. Normally when users are experiencing crashes when opening / creating documents it's because their graphics driver is crashing. An uninstall and reinstall of their GPU drivers normally solves it.
  10. For now, you can use the --legacy-wintab command line option (in 1.8.4). When 1.8.5 is released (hopefully in next week or two - it's only a small hotfix for 1.8.4), that command line option will be ignored, and will use the new Preference item instead. When using the Windows Ink method in Affinity it's important to note that your Wacom driver must also be configured to use Windows Ink (else your pen will just behave like a mouse).
  11. Do you have Windows Ink enabled in your Wacom Properties? Without it, your pen will just behave as a mouse (hence no pressure).
  12. They've not been forgotten, they're just not being addressed in 1.8.5 as this is a bit of a 'hotfix' to address the most commonly reported issues that people have been facing since 1.8.4 was released 🙂
  13. If you can't open an existing document, or create a new document it sounds like your graphics drivers may need reinstalling. Have you recently installed a Windows update?
  14. Thanks for checking, it's possibly that the High Precision mode is generating lots of extra input points, which is causing the app to do more work. Perhaps in the future we could investigate a "High Precision for Brushes Only" mode... as that's where it's most important.
  15. Looks like it was the High Precision input (you could try enabling that option in the latest beta to confirm it).
  16. Hi everyone, thanks for your patience. In the latest customer beta (1.8.5.703) we have changed the default tablet input method to be the Low Precision mode, the same as in 1.8.3, and added a new Preferences option that allows users to opt-in to High Precision or Windows Ink modes. If you would like to check it out, the details are here:
  17. Hi everyone, thanks for your patience. In the latest customer beta (1.8.5.703) we have changed the default tablet input method to be the Low Precision mode, the same as in 1.8.3, and added a new Preferences option that allows users to opt-in to High Precision or Windows Ink modes. If you would like to check it out, the details are here:
  18. Hi everyone, thanks for your patience. In the latest customer beta (1.8.5.703) we have changed the default tablet input method to be the Low Precision mode, the same as in 1.8.3, and added a new Preferences option that allows users to opt-in to High Precision or Windows Ink modes. If you would like to check it out, the details are here:
  19. Hi everyone, thanks for your patience. If anyone would like to try the latest customer beta (1.8.5.703) we have a fix available for this.
  20. Click here to download the latest beta Status: Customer Beta Purpose: Features, Improvements, Fixes Requirements: A valid product key (for Affinity Store purchases), or an installation of the full retail version from the Microsoft Store As this is a beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity that may be adversely affected by the application failing, including the total loss of any documents. We hope you enjoy the latest build, and as always, if you've got any problems, please don't hesitate to post a new thread in this forum and we'll get back to you as soon as we can. Thanks once again for your continued feedback. If you have a general question about the software, please head over to the Questions Forum, or if you have any suggestions, please head over to the Feature Requests forum. Fixes Fixed tablet input problems by reverting the default input method to be Low Precision mode, the same as in 1.8.3. Added tablet input preference (in Tools section) to opt-in to High Precision mode, or Windows Ink mode (previous command line options --legacy-wintab and --disable-wintab are now ignored). Fixed cursor disappearing following keyboard shortcuts that display dialogs, while using a brush tool 1.8.4.693 release notes
  21. Click here to download the latest beta Status: Customer Beta Purpose: Fixes Requirements: A valid product key (for Affinity Store purchases), or an installation of the full retail version from the Microsoft Store As this is a beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity that may be adversely affected by the application failing, including the total loss of any documents. We hope you enjoy the latest build, and as always, if you've got any problems, please don't hesitate to post a new thread in this forum and we'll get back to you as soon as we can. Thanks once again for your continued feedback. If you have a general question about the software, please head over to the Questions Forum, or if you have any suggestions, please head over to the Feature Requests forum. Fixes Fixed tablet input problems by reverting the default input method to be Low Precision mode, the same as in 1.8.3. Added tablet input preference (in Tools section) to opt-in to High Precision mode, or Windows Ink mode (previous command line options --legacy-wintab and --disable-wintab are now ignored). Fixed cursor disappearing following keyboard shortcuts that display dialogs, while using a brush tool Fixed raster Crop Tool units multiplying incorrectly on the context toolbar 1.8.4.693 release notes
  22. The resolution shouldn't be an issue - what display scale have you got set (in Windows)?
×
×
  • 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.