artbymaddesign.com

Mark, Your response is very much appreciated. After performing a clean install of the new video driver (471.41), it does appear to have solved my issue. Was the Capture One listing a newer development, or did I totally miss it the first time I posted my problem? My temporary fix, prior to today, was to use an old NVIDIA driver all the way down in the 446.xx versions. That played well with Affinity and Capture One, but eventually caused problems in newer programs installed on my system. Glad they were able to fix it in the new driver. I opened over 20 TIF files at once, and edited through all of them, with no issue in Affinity Photo. Thanks again for alerting me to the driver update. -Michael

Would like to add that I have used the DDU tool to uninstall and reinstall the drivers in safe mode. Tried a older version of drivers, as well as the latest driver. Tried reinstalling Affinity Photo. I get the crash if I try to open an image in Affinity Designer as well. Publisher seemed to run okay. I could create a new document and place an image file. CaptureOne trial runs okay, illustration apps like Krita run okay. GIMP has some issue where I can't export the TIF files, so that's a no-go. There are various web reports on forums of people having an issue where a game would crash from the nvwgf2umx.dll file, and I try whatever they suggest to no avail. If anyone has any suggestions short of seppuku, I'm all ears. I was really counting on Affinity products for my image editing and occasional graphics/layout work.

Mark, I appreciate your time. I did a 2nd clean install of the graphics drivers, and I'm still experiencing the Affinity Photo crash. Attached latest crash report. -Michael 1f0e1ea8-f5c7-4650-bb9e-f8534e98982a.dmp

Mark, Thank you for your reply. I have attached the 3 latest crash reports. I'll go ahead and perform a clean install of the nvidia drivers. Now that you mention graphics drivers, something i did differently on this fresh install of Windows was to select the "studio" drivers instead of the "game ready" drivers that I usually install. Let me know if that's a known issue. Thanks again for your help. -Michael fe7f4e34-cdfb-4fa8-a121-20ad5246dd7b.dmp 7f3e5ec5-3b04-4f21-8173-97b84c8ce750.dmp 10536ed4-3ddc-42c0-b039-932fed996dba.dmp

--- I am NOT using the 3rd party software mentioned in the "Issues caused by third party software" thread. While I am using a 1060 6gb Nvidia card, I am NOT experiencing render issues as suggested in that thread. No 3rd party clipboard manager is installed. --- I recently got off the Adobe train, and decided to do a fresh install of Windows on a clean drive (Adobe leaves so many residual files). System is Windows 10 64bit Pro (build 19041.388), first-gen i7 950 processor, 12 gb ram. Since performing the re-installation of the OS, Affinity Photo is unstable. Issues: Photo closes/crashes with no consistent cause. Sometimes it closes after I have just opened an image, or while trying to open an image. Sometimes it closes after I work a few seconds, and on rare occasion I can edit and save an image. It will then crash within 1 or 2 of the next images I try to edit. I've tested to make sure I can repeat the crash if I open images from different drive locations. The issue occurs whether I am opening/editing a .tif or .nef (Nikon raw) file. The abrupt closing/crashing happens during cropping, moving file with hand tool, creating/editing adjustment layer, etc. So there does not seem to be a consistent and repeatable action causing the crash/close. Affinity Photo worked fine on the previous installation of Windows, and I'm not experiencing errors in other programs, or imaging programs. For example, I can run several images through GIMP, CaptureOne trial, and Topaz Denoise without issue. What I've tried: Opening different file formats to repeat the crash, making sure the files open in other programs, and trying to open the same file from a different drive location. Possible corrupt color profiles --- Reading the attachments in the crash report folder at "C:\Users\...\AppData\Roaming\Affinity\Photo\1.0\CrashReports\attachments" showed Affinity Photo was skipping some color profiles, which were under 5 kb size. I took ownership of the folder at "C:\Windows\System32\spool\drivers\color," and moved the skipped color profiles to a different folder. But the crashes/closings persist. "Let apps run in the background" is globally disabled. Windows font cache service is disabled to allow for speedy font scanning in Nexusfont (not just stopped, disabled). I had this process stopped in the previous Windows installation, and Affinity programs worked fine. No third party fonts are in the system folder, and all fonts in the system folder render in Nexusfont. So corrupt font seems unlikely. Any help would be appreciated, as I was really looking forward to being Adobe-free. -Michael

Well now I feel like a dork for posting it, if it's old news. My bad, but thanks for letting me know, Mike. Do you know if they have been working on a fix for this, or at least addressed it? I know we need to be patient about "new" features they may add to the program, but this is a pretty fundamental issue of page flow. If it isn't fixed by the end of the beta period, I'd never be able to use Publisher in any workflow.

I feel like I've found a bug in the way Publisher handles adding pages to a document that has been populated with auto-flow text boxes (the shift-click option). Curious to know if it's just my system. The Setup: New single-page document with inner and bottom margins of 1.25 inches, outer and top margins of 1 inch, and page numbering has been added on master page spread. Create a text box on Page 1. Right-click on the text box to “Insert text from file” in that text box. Shift-click the bottom right text flow arrow to create as many pages as necessary to auto-flow the text. For my test file, this makes the document a total of 6 pages. The text boxes created are the same size, and conform to the margins set in the document properties, as expected. The Possible Bug: At this point, I add an odd number of pages to the document somewhere in the middle of the text auto-flowed pages. For example, I'm on Page 3, and add 1 page after Page 3. The text boxes on all following pages are shifted. So after my new blank Page 4, the text boxes on all subsequent pages (starting at Page 5) do not automatically adjust to conform to the margins set in the document properties. Page 5 still thinks it is the left page in a spread, so the text box does not conform to the document margins. This would present a problem in something like magazine layout, where you are sometimes placing a single-page ad in the middle of the document, and re-flowing your article around it. Any time you would add a page in your layout, you'd have to manually move all your text boxes in the document! Obviously not an issue if your left and right margins are the same, but I tend to leave a larger inner margin to account for the binding. Can anyone else confirm that they experience this issue?

StuartRc, Thanks for offering to help with this topic. I did some more experimenting, and was getting frustrated. I could repeat the error that Mr. C and I were encountering, in spite of following both the video tutorial and your well-explained directions. Then I tried to save my file after creating custom paragraph styles, but before inserting the TOC in a text frame. That resolved the issue. Just offering that as a suggestion in case anyone else had trouble creating a TOC with custom paragraph style names.

It's not just you, Mr. C. I'm able to duplicate your problem. I can get a TOC to work just like the tutorial if I do the following: highlight my heading in the document select "Heading 1" paragraph style edit the parameters of the "Heading 1" style (font, size, color) apply "Heading 1" paragraph style to future headings in my document If I try to make a custom heading, or if I try to rename "Heading 1" paragraph style, the TOC will not work.