sbp Posted November 17, 2022 Share Posted November 17, 2022 Adjusting the temperature in the develop persona using the scroll wheel, arrow keys or clicking on the right-side arrows is not working. Quote Link to comment Share on other sites More sharing options...
Staff Chris B Posted November 17, 2022 Staff Share Posted November 17, 2022 Hey sbp, Is this under White Balance? It seems to be working for me if I mouse over the field and then scroll. Quote How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials Link to comment Share on other sites More sharing options...
David in Яuislip Posted November 17, 2022 Share Posted November 17, 2022 For me, the temp. value doesn't change with the wheel and the up/down buttons to the right do nothing, only the slider works. V1 was fine Quote Microsoft Windows 11 Home, Intel i7-1360P 2.20 GHz, 32 GB RAM, 1TB SSD, Intel Iris Xe Affinity Photo - 24/05/20, Affinity Publisher - 06/12/20, KTM Superduke - 27/09/10 Link to comment Share on other sites More sharing options...
Staff Chris B Posted November 17, 2022 Staff Share Posted November 17, 2022 Ah, it's when you are using Kelvin. Once developed, the field uses % which can be scrolled. Quote How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials Link to comment Share on other sites More sharing options...
sbp Posted November 17, 2022 Author Share Posted November 17, 2022 2 hours ago, Chris B said: Hey sbp, Is this under White Balance? It seems to be working for me if I mouse over the field and then scroll. If you open a pixel layer in develop persona the values are in percents and everything works fine. The problem is when you open a RAW file and the values are in Kelvin. Paul Mudditt 1 Quote Link to comment Share on other sites More sharing options...
Staff Affinity Info Bot Posted March 7, 2023 Staff Share Posted March 7, 2023 The issue "Unable to scroll or use the arrows on the White Balance field in Develop Persona" (REF: AFP-5659) has been fixed by the developers in internal build "2.1.0.1720". This fix should soon be available as a customer beta and is planned for inclusion in the next customer release. Customer beta builds are announced here and you can participate by following these instructions. If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.