Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Warning Capture One Directory Structure has Changed in CO20.

Comments

7 comments

  • Paul Steunebrink
    That is correct. On macOS, there is a similar change since CO20.
    0
  • SFA
    Is this after the most recent update?

    My still original V20 installation does not have an ImageCore folder in Appdata (Running Win 7).


    Grant
    0
  • Paul Steunebrink
    SFA wrote:
    Is this after the most recent update?

    My still original V20 installation does not have an ImageCore folder in Appdata (Running Win 7).

    The change is since the CO20 beta, if I recall correctly.
    0
  • Dave R
    SFA wrote:
    Is this after the most recent update?

    My still original V20 installation does not have an ImageCore folder in Appdata (Running Win 7).


    Grant

    I am running Windows 10. It is interesting that with this change you can have CO12 and CO20 on the same machine and switch between them without the ImageCore folder rebuilding.

    Dave
    0
  • SFA
    David532 wrote:
    SFA wrote:
    Is this after the most recent update?

    My still original V20 installation does not have an ImageCore folder in Appdata (Running Win 7).


    Grant

    I am running Windows 10. It is interesting that with this change you can have CO12 and CO20 on the same machine and switch between them without the ImageCore folder rebuilding.

    Dave


    Hmm.

    I spotted that at some point (probably during the beta?) but can find no evidence of it now.

    Maybe I should fire up V12 to see what happens.


    Grant
    0
  • Dave R
    SFA wrote:
    David532 wrote:
    SFA wrote:
    Is this after the most recent update?

    My still original V20 installation does not have an ImageCore folder in Appdata (Running Win 7).


    Grant

    I am running Windows 10. It is interesting that with this change you can have CO12 and CO20 on the same machine and switch between them without the ImageCore folder rebuilding.

    Dave


    Hmm.

    I spotted that at some point (probably during the beta?) but can find no evidence of it now.

    Maybe I should fire up V12 to see what happens.


    Grant


    This change could have come with 20.0.2, in my usual disorganised manner I did not note when I first noticed I could switch between 12 and 20 without imgcore rebuilding. In the long list of bug fixes in 20.0.2 there is one “ Fixed an issue with hardware acceleration in a multi-user environment.†which could be a clue. One way of fixing this issue might be to give each user their own ImgCore by putting it in c:/users/user name/appdata.

    Dave
    0
  • SFA
    David532 wrote:


    This change could have come with 20.0.2, in my usual disorganised manner I did not note when I first noticed I could switch between 12 and 20 without imgcore rebuilding. In the long list of bug fixes in 20.0.2 there is one “ Fixed an issue with hardware acceleration in a multi-user environment.†which could be a clue. One way of fixing this issue might be to give each user their own ImgCore by putting it in c:/users/user name/appdata.

    Dave


    That's true.

    The Version split would work at the App version level but not per user.

    If per user was required then version AND user split in User Appdata makes some sense - possibly.


    Grant
    0

Post is closed for comments.