AMDphreak
Community Beginner
AMDphreak
Community Beginner
Activity
‎Apr 17, 2019
10:36 PM
1 Upvote
I discovered the source of the problem. @michalf63166855 said turning off GPU rendering did the trick for him. This is a workaround, not a diagnosis. The real problem is settings within the GPU settings app released by the manufacturer of the GPU architecture. For an nVidia card, modify the 3D settings for Illustrator in the nVidia Control Panel. I had enabled some 3D enhancements for all of my programs and games in the Global Settings. This caused a problem with Illustrator, so I had to specifically disable these for the Illustrator executable. Manage 3D settings > Program Settings > Select a program to customize > Adobe Illustrator (illustrator.exe) -> Change all settings to the default settings for the card. If you changed the "Global Settings", the "Program Settings" must be reverted to what they were prior to your modifications of the Global Settings. Every Program Setting that can be set to "Application Controlled" needs to be set to "Application Controlled". These two changes fixed the problem for me: ~Anti-aliasing mode: Application controlled ~Vertical sync: Use the 3D application setting The "default printer" problem makes zero sense. No programmer would ever check for a printer during a file read. A does not imply B. @Adobe you need to fix your GPU code to handle the error and give a helpful message, instead of crashing the program.
... View more
‎Apr 17, 2019
10:32 PM
I discovered the source of the problem. @michalf63166855 said turning off GPU rendering did the trick for him. This is a workaround, not a diagnosis. The real problem is settings within the GPU settings app released by the manufacturer of the GPU. For an nVidia card, modify the 3D settings for Illustrator in the nVidia Control Panel. I had enabled some 3D enhancements for all of my programs and games in the Global Settings. This caused a problem with Illustrator, so I had to specifically disable these for the Illustrator executable. Manage 3D settings > Program Settings > Select a program to customize > Adobe Illustrator (illustrator.exe) -> Change all settings to the default settings for the card. If you changed the "Global Settings", the "Program Settings" must be reverted to what they were prior to your modifications of the Global Settings. Every Program Setting that can be set to "Application Controlled" needs to be set to "Application Controlled". These two changes fixed the problem for me: ~Anti-aliasing mode: Application controlled ~Vertical sync: Use the 3D application setting The "default printer" problem makes zero sense. No programmer would ever check for a printer during a file read. A does not imply B. @Adobe you need to fix your GPU code to handle the error and give a helpful message, instead of crashing the program.
... View more
‎Sep 24, 2017
04:14 PM
Hi, I noticed on my own that the Effect > Pathfinder > Merge operation does not actually merge anything when I am trying to merge paths. I mean, if it's not the same as the Merge operation in the Pathfinder tool, then why CALL it the same thing? What is Adobe thinking? And what does it even do? The Merge button in the Pathfinder toolbox works just great! There is major ambiguity here. I see no distinction between the two.
... View more
‎Apr 12, 2017
01:32 PM
Dear Adobe, I have used Lightroom on several different computers, and I've noticed that on MacOS, Lightroom prioritizes processes and handles multithreaded operations more fluidly than on Windows. Are there any plans to fix this idiotic discrepancy? I've used Lightroom on an Intel Core i7-6700K overclocked to 4.4 GHz with 4 cores / 8 threads, with 16 GB of DDR4-2666MHz RAM and an nVidia GeForce 650Ti (which scores extremely high on 2D operations on Passmark, but low on 3D operations). Even with this near-industrial level of computing power, Lightroom still performs miserably. My specific complaint is that during exporting or doing ANY background process in Lightroom, the interface is unresponsive. Not only this, but I export my photos 3 different times (for different media platforms with different image size requirements). I can never streamline this process and have to go to the Export thing 3 separate times every time, and after 2 export processes are running, the interface takes 1,000,000% longer to respond to click events. This happens only a little bit on a Mac Pro trashcan with 6 cores. Not only that, but every other app runs very slowly during these export processes. When is Adobe going to do the smart thing and put in a way to control this? There are two ways I can think of. Feature request: Please separate the export thread from the main thread! Let the OS handle the thread CPU time, so that Lightroom and other apps don't become unresponsive. LR has crashed during exports before, because of this thread mismanagement! The second, (and less sophisticated solution): It seems like a pretty brain-dead easy stop-gap solution to introduce a feature in the settings or in the export dialog to limit the number of cores the process uses, so that users can continue to use their computer while a non-urgent export process runs in the background. Feature request: Make it possible to use multiple export profiles in a single run. This should streamline the export process and reduce the number of memory operations required, when the same file is being used between multiple export processes! Thank you, AMDphreak
... View more