Jump to content


  • Content Count

  • Joined

  • Last visited

About grunnvms

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I've been reading this thread with interest, and my first question is what kind of Affinity work would benefit from hardware acceleration. I only do simple work with Affinity products, and I've never come across a moment that It thought, well this is going too slow. Hence my question. And then my second question, isn't hardware acceleration provided by DirectX on Windows, in other words you don't need to know too much about the underlying hardware?
  2. You had that from me as well. So after I send you all that information, I copied the font files from my personal directories to the standard windows font directory (install for all users), removed the registry entries for those personal fonts, and deleted them in the personal directories. I then rebuilt the font cache. After this the standard 1.8 photo worked fine.
  3. So the problem was caused by fonts that were not is the standard Windows font directory. My very personal opinion is that fonts should be in that directory anyway, unless you're using some kind of font manager with its own directory structure. So I'm glad I moved all fonts that were in my personal font directory to the standard Windows font directory.
  4. Publisher 1.8 and Designer 1.8 also start without problems.
  5. I installed 1.8 again, seems to work now !!! I can confirm that after the font operations I described in my previous posting, Photo 1.8 works fine. I've used it, restarted it several times, no problems whatsoever.
  6. No, I don't. So far I did the following: I selected all fonts in the C:\Users\<username>\AppData\Local\Microsoft\Windows\Fonts\ directory, and then right-clicked on "install for all users". With the registry editor , I removed all font entries (except default of course) from “HKCU\Software\Microsoft\Windows NT\CurrentVersion\Fonts”. Rebooted the PC. Deleted all fonts in the C:\Users\<username>\AppData\Local\Microsoft\Windows\Fonts\ directory. Now all the fonts are where they belong. Next step was to rebuild the font cache. With services.msc , stop and disable the "Windows Font Cache Service" , and the "Windows Presentation Foundation Font Cache". (right click - properties) Reboot the PC Make sure you can see Hidden Files and Folders in Explorer ! Go to C:\Windows\ServiceProfiles\LocalService\AppData\Local Delete all .dat files starting with Fontcache Open the Fontcache directory Delete everything in that directory, including the Fonts directory. With services.msc , set the start property of the "Windows Font Cache Service" to automatic and start the service. With services.msc , set the start property of the "Windows Presentation Foundation Font Cache" to manual. There's only one mystery left. In C:\Users\<username>\AppData\Local\ there is a fontconfig directory, with a cache directory, and all kind of cache files. Haven't figured out what they are used for.
  7. I found it. When you select all fonts in the C:\Users\<username>\AppData\Local\Microsoft\Windows\Fonts\ directory, and then click on "install for all users" , they will be copied in the standard fonts directory. Now I have to find a way to remove them from the C:\Users\<username>\AppData\Local\Microsoft\Windows\Fonts\ directory, and perhaps clear those registry keys.
  8. Done. I'm a bit surprised that these fonts are not in the standard font directory where they belong.
  9. Would sending crashdump information help the developers?
  10. If possible, I would like to know if the problem could be reproduced with my fonts directory.
  11. @AnthonyN Did you deinstall Photo before you tried to reinstall it? It seems that deinstalling really cleans everything up, including registry items like the license key.
  12. I also have a problem with the fonts. Is there anything that I can do to provide you with information?
  13. @LeighNo, I did not. I assume the file WindowProfile.xml is needed by Photo, and since I did a fresh install, this file was also fresh. Renaming it to WindowProfile.xml.backup would have caused Photo to produce a new WindowProfile.xml file that should be exactly the same as the one I just renamed.
  14. Thank you so much for pointing me to the event log, I have the same problem: Application: Photo.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.AccessViolationException at <Module>.Kernel.FontCache.GetFontTraitsName(Kernel.StringT<enum Kernel::TEncUtf8>*, Kernel.Font*) at Serif.Interop.Persona.UserInterface.ManagedFontStyle.get_DisplayName() at Serif.Interop.Persona.UserInterface.FontFamilyComboBoxContextBarItem+FamilyComboBoxContextBarItem..ctor(Serif.Interop.Persona.UserInterface.ManagedFont) at Serif.Interop.Persona.UserInterface.FontFamilyComboBoxContextBarItem.BuildFontsList() at Serif.Interop.Persona.UserInterface.FontFamilyComboBoxContextBarItem..ctor() at Serif.Interop.Persona.Data.CharacterDataSource..ctor(Serif.Interop.Persona.Services.IServiceProvider) at Serif.Affinity.UI.Studio.CharacterPage..ctor() Exception Info: System.Reflection.TargetInvocationException at System.RuntimeTypeHandle.CreateInstance(System.RuntimeType, Boolean, Boolean, Boolean ByRef, System.RuntimeMethodHandleInternal ByRef, Boolean ByRef) at System.RuntimeType.CreateInstanceSlow(Boolean, Boolean, Boolean, System.Threading.StackCrawlMark ByRef) at System.Activator.CreateInstance(System.Type, Boolean) at System.Activator.CreateInstance(System.Type) at Serif.Affinity.Services.PageService.EnsurePage(System.Type) at Serif.Affinity.UI.AffinityWindow.AttachPages(Serif.Interop.Persona.Workspaces.IWorkspace, Boolean) at Serif.Affinity.UI.AffinityWindow.set_CurrentWorkspace(Serif.Interop.Persona.Workspaces.IWorkspace) at Serif.Affinity.Services.WindowService.ShowMainWindow() at Serif.Affinity.Application+<>c__DisplayClass53_0.<OnServicesInitialised>b__2() at System.Windows.Threading.DispatcherOperation.InvokeDelegateCore() at System.Windows.Threading.DispatcherOperation.InvokeImpl() at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task) at System.Windows.Threading.DispatcherOperation.Wait(System.TimeSpan) at System.Windows.Threading.Dispatcher.InvokeImpl(System.Windows.Threading.DispatcherOperation, System.Threading.CancellationToken, System.TimeSpan) at System.Windows.Threading.Dispatcher.Invoke(System.Action, System.Windows.Threading.DispatcherPriority, System.Threading.CancellationToken, System.TimeSpan) at System.Windows.Threading.Dispatcher.Invoke(System.Action) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at System.Threading.ThreadHelper.ThreadStart() I had the same problem with 1.8 beta, and it was suggested that it could be my virus scanner. Yesterday I installed 1.8 final, and it crashed again. I completely removed my virus scanner plus all Affinity products, and reinstalled 1.8. It crashed the way you described. I deinstalled it, reinstalled 1.7.3, and now I have a working version of Photo again. It would be wonderful if the developers can come up with a solution, since I need features of 1.8.
  15. Thank you all for your replies and contributions. The document was indeed intended for a professional printer, hence the CMYK setting. The company that is going to print the (A0) document is using EPS as their standard document type. I managed to get the desired output by first changing the document from RGB to CMYK, while using the appropriate profile, ISO coated V2. Then I exported the document to EPS. I then used undo to get the RGB document back, and did the procedure again, but now with the PSO Coated V3 profile. When that was done, I used undo once again. If I understand this correctly, I can use the 16 bit RGB setting combined with the ROMM profile for the maximum colour information. If I export such an image to JPEG and embed the colour profile, then such a picture should show up fine on any PC, assuming the PC has a colour profile setting attached to the monitor. The colour information will be recalculated from the embedded profile to the display profile. Printing is another matter. I have no colour profiles for my printer, and as far as I know I would need to set them up for different paper types and print qualities. The Fuji profiles came from a photo book producer, who publishes them on their web site, so you can use them if you want.
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.