Having the same issue. Sometimes crashes after one photo, sometimes it will do 6 (I’ve been doing about 14 at a time). Program just shuts down. Computer specs:
11th Gen Intel(R) Core™ i9-11900 @ 2.50GHz 2.50 GHz
32.0 GB (31.6 GB usable)
64-bit operating system, x64-based processor
Same here: permanent crashes when process arrives at face detection. Windows 11, Nvidia GeForce RTX 3060 TI, latest drivers, Intel Core I7 12700K, 32GB DDR5.
Could no process a single photo yet.
Same here with batch editing.
same issue here.
Using it on 2 4070 based machines, Win10 and Win11.
At first I thought it was related to the new beta color adjustment, but doing many tests its showed it’s not related to it. face recognition seems to be much more likely, especially as it seems to crash much earlier/faster with pictures that contain multiple faces.
Right now it’s sadly unusable as I can barely do a single optimisation and save it (only if I’m fast on some images). Batch processing is completely impossible.
I’m looking forward to a working stable version, especially since the color correction seems to improve some images (mainly portraits) a lot.
Thanks to Topaz, i install the Win11 Nvidia Studio Driver 535.98 from Mai for my 3060 Graphiccard and it works wonderfull. So i wait on an new Nvidia Driver. Also the Autopilot works without crashes.
We released a fix for this issue in v2.0.1. Please update and it should no longer be crashing.
Thanks for the fix seems to remedy the crashing issue.
When are u going to add light and color balance features to work with all photos in batch processing? As of now the very first photo is balanced and others bypassed.
We are adding Adjust Lighting and Balance Color to the Apply Settings to All feature in the release this Thursday.
We are adding default strength for Adjust Lighting and Balance Color to the Preferences > Autopilot menu soon.
I do not have a timeline on allowing Autopilot to turn on these models automatically. They will be manual for now.
Manual mode as ”Apply to all” is very okay. Thanks.
Terveisin /Best regards
It’s been fixed in v2.0.1