Not sure if you figured it out yet but also if you had any loaders that were specifically daz you should probably reset them and then download the poser/pc version of them.
That’s not really a clear division and risks confusing Mac users, what we have are installers divided by PC and Mac, and within those two categories installers applicable to both studio and poser, and a few to studio alone.
For instance this week’s freebie has the installer “Summertime Grill - 14716_SummerGrill_1.0_dpc.exe - PC”
DPC isn’t ‘poser/PC’, its ‘DAZ Poser Content’ and can be either Poser files alone or a mix.
You also get installers that are DS, those are Studio alone, for instance last week’s freebie had a Studio metadata installer:
Real Tanks & Containers - 14581_RealTanksContainers_1.0_dpc.exe - pc
Real Tanks & Containers - 14581_RealTanksContainersMetaData_1.0_ds.exe - pc
You could decide to ignore them, but I personally would advocate downloading and installing them against the day you decide to give Studio or Carrara a try, or Poser adds a handler for them, or whatever. Quicker to do that now than have to work through anything up to several thousand items later, resetting and redownloading them.
And increasingly you’re just going to be seeing a single zip common to both Mac and PC and both Poser and Studio.
Target application—Daz Studio (this is crucial)
It isn’t, certainly not with recent installers (with the dark blue screen on their icon) and DAZ have been clear in the past that exactly the same files are installed whether you select Poser or Studio in an installer that offers that choice (for example the previous generation bitrock installers with the light blue screen on their icon). For instance I’m just installing the Ballerina Construction Kit (which has a recent DPC installer, a Genesis specific .trx and a metadata installer) into my runtime structure, which is under my old Poser 7 folder.
Double click the DPC Installer,
Accept the License Agreement
Click ‘Customize Installation’
Click ‘Specify an Installation Path’
It comes up with my Studio content directory as the default, which happens to be in the same directory as my runtime. I’ll go with that for the meantime.
Unclick all 3 options
When the installer has finished the poser files are in content/runtime. You can declare this to Poser as an additional runtime, drag and drop it to your existing runtime, or even declare it to poser as your primary runtime and do all Poser installs from whatever source into it.
If I install an older Bitrock installer, or an installer from either of the two installer generations that preceded Bitrock, I can select target application as ‘Poser (All Files)’, tell it to install into any directory I want, and it will quite happily go off and do that, even if there is no existing Poser structure there.
You may also elect the traditional program files route
Content shouldn’t be placed in program files, Windows is getting increasingly picky about this.
if you can’t see it then all you have to do is add the path to your runtime it to the library.
If it hasn’t gone where you expected, better to drag and drop it to an existing runtime.