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

Search the Community

Showing results for '"virtual device model profile"'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.4 New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests


Member Title

Found 19 results

  1. Here are some earlier topics that may help. I think you should change your display setting so it's not using the virtual device profile, but standard sRGB. https://forum.affinity.serif.com/index.php?/search/&q="virtual device model profile"&quick=1
  2. Thank you so much! Doing that fixed the issue! For people here who are experiencing the same issue, here is what I followed to fix it: Change the Windows color system defaults (Color management > advanced) from "srgb virtual device model profile" to "srgb IEC61966-2.1 Thanks to all who helped! I greatly appreciate it!
  3. Hi Mark, I went into the Windows color management module. Clicked on the Advanced Tab. Clicked on Change System Defaults. Clicked on the Advanced Tab and changed the Windows default device profile from "scRBG virtual device model profile" to "sRBG IEC61966-2.1". I don't know if "scRBG virtual device model profile" was the originally delivered Windows system default or whether I changed it to that at some point in the distant past. It had probably been that way for years though. I can tell you that it wasn't a problem until I upgraded to Windows 10 Pro release version 2004 from the previous release version of Windows 10 Pro. I can also tell you that "sRBG virtual device model profile" does not work either. Apparently there is something about virtual device model profiles that causes problems now.
  4. I received the following from support. Maybe this will work for you. 1. Try resetting each of the apps, hold down CTRL and open, when the window appears, release the key and click Clear. If this doesn't resolve the issue try 2. 2. We've had reports that our apps no longer start after installing the Windows 10 October 2020 (20H2) update. This update is changing the default Device profile in Colour Management to a Virtual profile. Go to Color Management > Advanced > Windows Color System Defaults and change the Device profile from scRGB virtual device model profile to sRGB IEC61966-2.1. Once changed, the app should run as expected.
  5. UPDATE: This issue is now resolved in the 1.9.0 update which is now available from the Affinity Store and Microsoft Store. We've had reports that our apps no longer start after installing the Windows 10 October 2020 (20H2) update. This update is changing the default Device profile in Colour Management to a Virtual profile. If you see the below information in Application Logs in Event Viewer after trying to start our apps - Description: The process terminated due to an unhandled exception. Exception information: System.ArithmeticException Exception information: System.OverflowException at System.Windows.Media.Imaging.ColorConvertedBitmap.FinalizeCreation () at System.Windows.Media.Imaging.BitmapImage.FinalizeCreation () at System.Windows.Media.Imaging.BitmapImage.EndInit () at Serif.Affinity.ResourceManager.GetBitmapSourceCore (System.String) at Serif.Affinity.UI.AboutDialog..ctor (Boolean) at Serif.Affinity.Application.RunSingleInstance () at Photo.Application.Main (System.String []) Please go to Colour Management > Advanced > Windows Colour System Defaults and change the Device profile from scRGB virtual device model profile to sRGB IEC61966-2.1 Once changed, the app should run as expected.
  6. @johnyelland1234 Once you've set the Device Profile from scRGB virtual device model profile to sRGB IEC61966-2.1 on the Advanced tab. Switch back to the Device tab and also make sure the display is set to use the default sRGB profile.
  7. We convert colours from document profile to screen profile. If you have an sRGB document, and sRGB monitor profile, then no conversion will happen. I have no idea what an "sRGB Virtual Device Model Profile" is, but we would have been converting colours to that profile. Normally your monitor profile should be set to the profile that is compatible with your monitor.
  8. @Alan Shearman Can you check the following for me. 1, Open Colour Management > Advanced > Windows Colour System Defaults and check to see if the Device profile is set to scRGB virtual device model profile if so please change to sRGB IEC61966-2.1. 2, Reset the app, just in case. Hold down CTRL key and open, when the window appears release the key and click Clear. Check to see if a crash report has be created based on the time/date when you are opening the 1.9 version, if one exists please attach here for checking.
  9. Thanks for a quick response and welcome! There was no custom profile - i.e. the box is already unticked. However! I looked on the Advanced tab, and the Device profile said "scRGB virtual device model profile" (It might have been sRGB instead of scRGB, I was too quick to change it I guess). I changed this to "System default (sRGB IEC61966-2.1)" and the installer worked! Now the application also launches fine! I would send you the profile but I'm not sure where to find it. Thank you for your help.
  10. To reproduce: close AD, launch the Color Management control panel (press the Start button, type 'color ma', it should appear in the list), switch to the Advanced tab, in the first options group (Windows Color System Defaults) select: Device profile: scRGB virtual device model profile, start AD Checked on two PCs with AD 1.8.2, 1.7.3, tried clean install, safe mode, etc. This is interesting: if you select the scRGB profile in Windows Settings (Settings - Display - Color profile), but not in the Color Management control panel (keep there 'Adobe RGB 1998' or 'sRGB IEC61966-2.1'), then AD runs well, just with colors shifted to the dark.
  11. Ok bit obscure but worked it out from another post. Basically go to Color Management in Windows 10. Click on Advanced>Device Profile>switch from "scRGB virtual device model profile" to "sRGB IEC 61966-2.1" Then try installers again. I hope that helps someone in the future. Thanks.
  12. Below is a list of common issues affecting the latest Affinity Publisher update for Windows (1.9.0), which are already fixed in the latest beta builds: [If you are seeing one of these problems PLEASE DO NOT REPORT THEM AGAIN] App crashes on Startup (some progress made) Crashing when clicking My Account to register app Fixed scaled text frame changing text size when grouped. App crash when printing document that has multiple (Designer) artboards Fixed PDF passthrough failing to work on multi-page documents. Performance problems when Paragraph Panel is visible App crashes when opening some specific 1.8.x documents Fixed being unable to create custom export presets for PDF export Fixed JPEG and TIFF export filter descriptions (was confusingly "Affinity Files") Fixed "Copy As SVG" option preventing Affinity data being added to the clipboard Fixed Export Preview scaling issues Purple/Magenta outlines after deselecting objects? Read this All of these issues (and other less common ones) have been addressed in the latest 1.9.1 betas and will be released as a patch to customers very soon. You can find links to the latest beta builds in the below links: Affinity Range Windows Beta Release Notifications Problems registering Affinity apps Some users have been getting the message "Error while constructing request of parsing server's response". Some users have been getting the message "schannel: next InitializeSecurityContext failed: Unknown Error". The app is crashing for some users when trying to register the app. There are two possible causes: If you are using a 20H2 machine, you can try changing the default Windows colour profile from scRGB virtual device model profile to sRGB IEC61966-2.1 If you are not using a 20H2 machine, or if the above does not resolve the issue, a simple workaround is to download and install the beta build and sign into your account using the beta build. Once you've done this, you should find that you can sign into the released version without any issues. Feel free to uninstall the beta build once signed into your account.
  13. Below is a list of common issues affecting the latest Affinity Designer update for Windows (1.9.0), which are already fixed in the latest beta builds: [If you are seeing one of these problems PLEASE DO NOT REPORT THEM AGAIN Fixed scaled text frame changing text size when grouped. App crash when printing document that has multiple (Designer) artboards Fixed PDF passthrough failing to work on multi-page documents. Crashing when clicking My Account to register app App crashes on Startup due to broken OpenCL drivers Performance problems when Paragraph Panel is visible App crashes or hangs when opening some specific 1.8.x documents Fixed being unable to create custom export presets for PDF export Fixed JPEG and TIFF export filter descriptions (was confusingly "Affinity Files") Fixed "Copy As SVG" option preventing Affinity data being added to the clipboard Fixed Export Preview scaling issues Purple/Magenta outlines after deselecting objects? Read this Disabled hardware acceleration for AMD Radeon RX 5000 series and later cards (awaiting response to bug filed with AMD) Fixed asset dragging performance for some assets These issues (and other less common ones) have been addressed in the latest 1.9.1 betas and will be released as a patch to customers very soon. You can find links to the latest beta builds in the below links: Affinity Range Windows Beta Release Notifications Problems registering Affinity apps Some users have been getting the message "Error while constructing request of parsing server's response". Some users have been getting the message "schannel: next InitializeSecurityContext failed: Unknown Error". The app is crashing for some users when trying to register the app. There are two possible causes: If you are using a 20H2 machine, you can try changing the default Windows colour profile from scRGB virtual device model profile to sRGB IEC61966-2.1 If you are not using a 20H2 machine, or if the above does not resolve the issue, a simple workaround is to download and install the beta build and sign into your account using the beta build. Once you've done this, you should find that you can sign into the released version without any issues. Feel free to uninstall the beta build once signed into your account.
  14. Thought I would tag this thread with what solved my problem with running Affinity Photo and installing Affinity Photo. This was a response I sent to support when they were helping me solve the problem. <<<<<OK. Went back into Color Management. Clicked on Advanced>Device Profile>switched from "scRGB virtual device model profile" to "sRGB IEC 61966-2.1" Just like that, Bob's your uncle. Affinity Photo installed and so far it seems to be working fine. Thank you for taking the time to work with me on resolving this problem. I'm super happy to have Affinity Photo running. Just in time for the fall colors!! Regards, Bill>>>>>> A big thanks to Gareth at Affinity support!!!
  15. Below is a list of common issues affecting the latest Affinity Photo update for Windows (1.9.0), which are already fixed in the latest beta builds: [If you are seeing one of these problems PLEASE DO NOT REPORT THEM AGAIN] Fixed crash at startup due to broken OpenCL drivers Crashing when clicking My Account to register app Fixed scaled text frame changing text size when grouped. Fixed PDF passthrough failing to work on multi-page documents. (designer/photo) Issues with Focus Merge when hardware acceleration is turned on Performance problems when Paragraph Panel is visible App crashes and hanging when opening some specific 1.8.x documents Fixed JPEG and TIFF export filter descriptions (was confusingly "Affinity Files") Fixed "Copy As SVG" option preventing Affinity data being added to the clipboard Disabled hardware acceleration for AMD Radeon RX 5000 series and later cards (awaiting response to bug filed with AMD) Fixed asset dragging performance for some assets Fixed hardware acceleration performance for Remove Lens Vignette (Develop Persona), Shear Filter, Liquify Turbulence Tool, Haze Removal Filter and Panorama Added .fts extension support All of these issues (and other less common ones) have been addressed in the latest 1.9.1 betas and will be released as a patch to customers very soon. You can find links to the latest beta builds in the below links: Affinity Range Windows Beta Release Notifications Problems registering Affinity apps Some users have been getting the message "Error while constructing request of parsing server's response". Some users have been getting the message "schannel: next InitializeSecurityContext failed: Unknown Error". The app is crashing for some users when trying to register the app. There are two possible causes: If you are using a 20H2 machine, you can try changing the default Windows colour profile from scRGB virtual device model profile to sRGB IEC61966-2.1 If you are not using a 20H2 machine, or if the above does not resolve the issue, a simple workaround is to download and install the beta build and sign into your account using the beta build. Once you've done this, you should find that you can sign into the released version without any issues. Feel free to uninstall the beta build once signed into your account.
  16. @Chris B My "Device Profile" was set to "System Default (sRGB virtual device model profile)". I don't think I have ever changed this. It seems to be the Windows 10 default and I seem to remember it being the same before the version 2004 update. I set it to "sRGB IEC61966-2.1" instead and now both photo/designer installers run without crashing! Both apps launch correctly too. Thanks! This must be a new issue in Windows 10 2004, because I'm pretty sure I had the same settings before the update.
  17. OK, the only other thing I can see in your Devices tab different to mine is that you have a "WCS Device Profile" called sRGB virtual device model profile" associated with your monitor I do not have that or any other "WCS Device Profile" listed there, so you could try highlighting then deleting that. Then try again with the "Use my settings for this device" ticked and unticked (restart affinity and test after any change you do)
  18. I have found the solution I changed the Windows color system defaults (Color management > advanced) from "srgb virtual device model profile" to "srgb IEC61966-2.1" I don't exactly know what the difference between the two is, but it worked. Hope anyone with a similar problem might find this solution.
  19. Your document is set up using the wrong colour profile (scrgb virtual device model profile). When you open a new document, make sure the colour profile is set to 'sRGB IEC61966-2.1' (or 'Adobe RGB 1998' to use aRGB). For the two documents that you have already created with this particular colour profile, go to Document > Assign ICC Profile (Note: Not 'Convert ICC Profile' in this particular case) > Select 'sRGB IEC61966-2.1' from the list > then press the 'Assign' button.
×
×
  • 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.