New 522.25 driver is not fixing it for me
Unfortunately :( I submitted a ticket to techsupport as requested in the post.
-
On Plus Forum several people have said that they have got 2023 working by downgrading to earlier driver 512.15 Game Ready seems to work https://www.nvidia.com/en-us/drivers/results/187304/
0 -
I had 512.96 installed until yesterday and "NoNoise", "TackSharpAI" and "Both" worked with this as well - at least it worked with some images but with some the system seems to stall all of a sudden.
I then upgraded to 517.40 and the "all is black" occurs for denoising.
Then I got back to 512.15 this time and the denoising and sharpening works again.
But there are so many things not working and all is so slow compared to 2022.5 that it is really a blow for every user to bring this software without ANY quality assurance made.
Tried it on both a HP Envy 32 AIO and Z1 workstation with 2080s.0 -
Thanks David & Michael!
I'll hold off on installing 512.15 for the time being then, as there seems to be issues left...I will remain patient :) Just switched to ON1 from PhotoLab as the MaskAI promised to speed up the workflow so much. Can't wait to get started with it :)
0 -
512.15 drivers working for me. I've only had time to test Nonoise/Tack Sharp, and those are now both working at expected speed and responsiveness - but that's all I've tested until later today.
And frankly, my GPU is over 4yrs old. Although I obediently update drivers as they pop up, I'm fairly sure it's not making much difference in terms of gaming etc after all this time. Fingers crossed.
0 -
hi, everyone is talking about problems with the nvidia graphic cards but mine is a ams rx6700xt
and i have a lot od issues too. anyone else with a ams card facing troubles?
0 -
Marc, be sure you have the latest drivers and that they are configured along with the OS graphics settings to allow Photo RAW 2023 to take advantage of them.
"OpenGL 3.3 and Later is Required" - How to Update Video Card Driver (Windows Only) - Photo RAW
0 -
brian,
as i mentioned earlier, i am "THE KING OF UPDATES". you will not find an outdated driver or any software that has not been updated on my system.Unless the Photo Raw 2022.5 because of failure of the new version 2023.
But thanks anyway for at least trying to help people here.
marc
0 -
I set the ON1 2023 exe to "High performance".
This bettered the overall situation but not the Super Select AI issues. I have seen that it is already worked on the SSAI issues.
0 -
512.15 is also working for me! Speeds seems to be fine. But I can imagine an up-to-date driver will be faster overall. But for now I can finally work on things, and wont install anything new unless a bunch of people let us know its working for them...
0 -
I had 522.25 installed and am crashing when attempting to edit any LUMIX RW2 file. No issues with Canon (CRx) or Sony (AWx). I downgraded to 512.15 and still have the issue. I've noticed that the technical requirements for 2023 ON1 PR have been revised to add Vulcan-1.1.dll? I'm going back to 522.25 and wait for the ON1 tech support people to propose something. Seems like I got thru this same BS with almost every major upgrade....
0 -
522.25 was a dud. Moved back to 512.15 as noted above, and made the chagnes noted above. Corrected my issues. Changes noted above include:
ON1 PHOTO RAW 2020 GPU Rendering: Black previews, Export Failures & More – ON1 Support (zendesk.com)
As of now, performance is faster than 2022. Hope this helps.
0 -
I decremented to 512.15. It made no difference.
0 -
Hey Terry, did you perform the other two changes listed above? I have a running a 2070 Super. If you have a different card, that may account for your having the issue post decrement.
0 -
Phillip ....
Yes, I've made (decrementing to 512.15) the two other recommended changes (ON1 executables to high performance and telling my NVIDIA GTX 1050 Ti GPU to do the heavy lifting and adjusting ON1 preferences, etc). I see no changes.... I (edit) crash on LUMIX RW2 RAW files, I do NOT crash on any others (Canon CRx or Sony AWx). HOWEVER, if I load the same RW2 file into ON1 PR 2022.5, do any simple edit, and exit the program, followed by starting ON1 PR 2023 and then loading the previously edited in 2022.5 file, I don't crash and everything is happy. If I then move within 2023 ON1 to another previously unedited RW2 file, and select edit, the program immediately crashes about 65%-70% through the load sequence. Bottom line, I believe my issue is unique to RW2 files and has something to do with creation of the *.on1 sidecar file. But, others have reported no issues so it may be unique to my configuration. Also, if after editing the RW2 file that I initially edited in 2022.5, then again in 2023, I exit the 2023 program and delete the edited RW2's *.on1 sidecare, I can restart 2023 ON1 and successfully load/edit the file. ON1 simply creates a new sidecar file. I've tried every combination of drivers versus settings that I can think of without success. I think what I'll do now is reload the NVIDIA 522.25 drivers and wait for ON1. ON1 says they are working a maintenance fix. If no success after that and I don't seem to see any action on my issue, I'll make the move to ask for my upgrade money back.
0 -
I just updated to the latest NVIDIA drivers 522.25 from a previous version It's my second time running 2023 and aside from the same black screen that I previously got when running no noise and tack sharp, the program appeared to be very very slow starting up and loading files. I will not use the program until something is done to resolve all of these crashing and display issues. I'm just sticking with Lightroom which always works flawlessly and I'll use the 2022 plugins when needed.
System
32b gig ram
and Ryzen 7 8 core
GTX 1650 NVIDIA gtx 1650 4 gig0 -
Terry, you said, "Also, if after editing the RW2 file that I initially edited in 2022.5, then again in 2023, I exit the 2023 program and delete the edited RW2's *.on1 sidecare, I can restart 2023 ON1 and successfully load/edit the file." Have you given this information to tech support? That would be a valuable clue for the engineers.
Charles, you should be able to roll back your drivers to V512.15 Studio to let Photo RAW 2023 run. Many users are reporting this has fixed their problems.
0 -
Brian.... yes, I did....
0 -
Cool
0 -
I downgraded to the March driver (with some reluctance) and now 2023 just seems to be running great in all respects and I’ve gone from grumpy to happy! (I finally got a chance to play with it this afternoon)
0 -
Terry, and others with RW2 crashes. I suspect that the issue is down to problems with how lens corrections are applied to such files, some say it is only particular camera/lens combinations. As 2023 has introduced changes to better handle purple fringing that could well be the problem area.
If you have edited the file in 2022.5 then lens correction information has probably been added to side car and this is read by 2023 rather than having to run the new lens correction from scratch. An edit on that file in 2023 updates the information in PhotoRAW's databases and that then takes precedence over sidecar files, so can carry on editing with new sidecar file created.
That is my guess anyway. If I am correct then this is probably not linked to the NVIDA driver issues and does need an On1 fix rather than an NVIDA driver fix.
1 -
I've been exchanging info with another 2023 ON1 PR user who downloaded RW2 RAW file from an online forum. He loaded and edited without issue. I downloaded the same files and crashed. How would you explain how that could happen? If it were an issue with lens correction, wouldn't it be consistent with other users?
0 -
OK - just a thought.
I downloaded some GH6 RAW files from DPReveiw and tested on my M1 iMac. No crashes but just got corrupted image when opened, Olympus file from same site worked ok, so don't think there was anything wrong with my process. I also sent the files from PhotoRAW to Photoshop and they opened ok in ACR, so not a corrupt file.
Downloaded another file and opened in 2022, this time all I got was a white screen, so for me even 2022 didn't work.
So issues not linked to NVIDA problems, but mystery to me as to why there are these reports of working in some circumstances.
0 -
Hello, When downgrading to V512.15 are you uninstalling all instances of the current NVIDIA driver and the NVIDIA experience program and then reinstalling the old version's exe? Just curious in case you used some other procedure. Thanks
0 -
I simply clicked the box 'Clean Install' and let it do its thing.
0 -
Hi guys, I will unfollow this thread. Too much notification mails which are irrelevant for me. Thanks for all the help and suggestion! I will wait for NVidia and/or ON1 to come with the final fix :)
0
Please sign in to leave a comment.
Comments
25 comments