Jump to content

zoomer

Member
  • Posts

    8,844
  • Joined

  • Last visited

Article Comments posted by zoomer

  1. On 7/17/2019 at 3:19 AM, benelmo said:

    I moved my user folder to a Dropbox folder.

     

    I would not do that.

    There may be settings that are machine specific

    (at least the license information in this case)

    which likely provoke problems.

     

    On the other hand, I think VW licensing should recognize the machine

    (code/UUID/....) again and not spread new activations.

     

    What you can do is setting up a Workgroup Folder,

    which when containing "same named" Files as VW App's Library, will

    "overwrite" these with your version.

    (Needs the same Folder Structure as VW App or User Library Folders)

    And put this on Dropbox instead to synchronize between machines.

     

    This will work great to access custom Library Elements and such things.

    (Your Office Standard)

     

     

    With a VW User or VW Workgroup you can easily "overwrite" VW App's Library

    and extend Settings (e.g. accessing your own File Templates and such)

     

    But unfortunately, having a Workgroup Folder will not help to synchronize all your Settings !

     

    As VW does

    a) save all your Settings Changes and things you add, by default into the User Folder only

    b) the "overwriting" of same Settings or library files has a certain priority

    c) Unfortunately that priority goes "overwriting" :

        > User Folder overrides > Workspace Folder overrides > App Library Folder

     

    Generally you may need to feed/maintain your Workspace Folder by manually copying

    things over from User Folder or from scratch.

    And if you would have e.g. a newer custom File Template version in Workgroup Folder,

    but also an older Template with the same name on your machine,

    VW will use/prioritize the older on that machine.

     

     

  2. 10 hours ago, AWDC LAO said:

    Sarcasm .... ?

     

     

    OK, it was bad, sorry.

     

    But I had my Mac Pro 2.1 8 core for 8 years, because nothing

    really noticeably faster came until 2012 with the latest MP 5.1. 

    When I wanted to upgrade, Cheese Graters where no more sold here for

    some electricity security regulations and Apple promised a new much better

    Mac Pro being in Apples pipeline.

    But there came a only a Trash Can which I tried to avoid or hope for an update.

     

    Until I had a project in 2015 that did no more fit in my 512 MB VRAM and was

    terrible lagging. So I was forced to buy a Trash Can. Which I had to run for

    another unexpected 6 years.

     

    As there is still nothing comparable to our cheese graters offered.

    (Mac Studio has the MP price, but is still not the machine that is the

    fastest universal workstation that you can buy for the next 6 months,

    until PC workstations followed, but for a higher price, as it was in 2007)

     

    So i completely understand that you keep your Cheese Grater running.

     

    But if the problem is really AVX, I am not sure if hacking macOS Big Sur

    on it would really help. Or is AVX hardware independent and needs just

    OS support ?

     

     

    But overall, as a (switched) Mac user,

    I realized and accepted that you need to keep everything current,

    Apple Hardware + Apple OS + Software.

     

    As Apple is not as legacy friendly as Windows.

    And I think even late Windows 10s or 11 is no more like Windows was

    in the past in this regard.

  3. Renderworks is the old CPU only Renderer.

    Only Redshift modes may use the GPU by Metal.

     

    And of course your GPU will help with all kind of View Displaying.

     

    I thought Vega cards would be supported for Redshift but I am not sure.

    EDIT : Yes

    macOS Intel:
    8 GB RAM
    AMD "Navi" or "Vega" GPU or later and 8 GB VRAM
     

    So Redshift should use your GPU.

    Only for Systems with non supported GLUs Redshift should switch

    back to CPU instead. But I think even for Redshift there may be some

    tasks that are CPU only, like geometry pre calculation and such.

     

    Are you sure that you will never see any GPU peeks in Activity Manager

    during the whole Redshift rendering ?

     

     

  4. Thanks for the like 🙂

     

    but it is nearly 3 years later.
    VW really got full Metal support and native ARM version ...

    Which I really like.

     

     

    For eGPU in general,

    "external" GPU so far always meant quite a noticeable performance handicap.

     

    For eGPU ever again on Macs, especially ARM Macs, I fear it is pretty unlikely

    to come back, unfortunately anyway. Many still hope.

    I think the only chance would be when they will finally release an ARM Mac Pro

    that is still modular and will somehow offer slots for any AMD GPU at all !?

    Which would still be no guarantee that AMD GPUs would be also available

    by eGPU for other Models.

  5. 2 hours ago, Pat Stanford said:

    If you open the file (or better a copy of the file so you don't mess up the original) in a text editor, somewhere in the first line will be a text string something like. VW17.xx.xx.

     

     

    Is it really the version it was saved with ?

    Or are there 2 VW versions noted ?

     

    AFAIK,

    when I had to enter VW files the last time in an Editor,

    the VW datum in file was pretty outdated - as it seems to

    save the VW version which was used to initially create that

    file. And I had migrated my File Templates over many years

    of VW upgrades ....

×
×
  • Create New...