Genesis 8.1 / Victoria 8.1

1464749515259

Comments

  • PerttiAPerttiA Posts: 10,024

    Anim said:

    No lip controls in G 8.1 Base - is that correct or only missing in my install?

    Assuming you are using DS 4.15...

    Remove the 1kb files from "...\Data\DAZ 3D\Genesis 8\Female 8_1\Morphs\Daz 3D\Base Pose Head\" and "...\Data\DAZ 3D\Genesis 8\Female 8_1\Morphs\Daz 3D\Expressions\", ie. empty those folders and the G8.1 will pick up the G8 morphs (For male figure the path is same except Female -> Male)

  • jbowler said:

    s_j_gregory said:

    Maybe a simplistic question.  I think I have noticed that almost always I need to adjust toe spread morph on both feet to get shoes to look nice.  All? the G8 figures seem to load with it set to -50.  This has persisted in G8.1.  Is this a problem for anyone else.  (I think I have also noticed that some odd finger nail aboration that plagued my G8 figures is gone for G8.1 and for that I am thankful . . . .

    Sounds like you have a built in morph which autoloads on everything.  The default G8.1F load comes with two "Mouth Realism" settings and Render SubD set to 3 (which, I guess, is interesting in it's own right but clearly unrelated).  The right and left "Toes Spread" morphs are set to 0.  Most real world heels crush the toes of the wearer; I remember my mother's toes, it does cause a permanent deformity.  -50% seems about right to me.  Standard foot poses for G8F heels often do this (though not always) and it definately looks, well:

    image

    I think it is another example of an auto-loading morph from some, as yet unidentified, product.

    Thanks for your thoughts.  It caused me to look at this more carefully - should have done that first I know. . . .Some corrections are in order.  First, my G8.1 default figure does not load with any toe spread morphs.  They are set to zero.  (To be clear - negative values spread the toes while positive values squish them - which intuitively for me is backward to the naming but that's clearly just me.)  I find, with delicate shoes, I almost always get a better result applying the morph.  The reason I thought the negative settings persisted into G8.1 for me is beacuse I noticed it when I migrated my own character morph (settings) onto G8.1 - I think.  This is another example of where I, or products, or both, have corrupted my G8 base.  I have undertaken lengthy shadow chasing exercises in the past, now pleasantly almost forgotten, that resulted in only partial improvement and me confused.  (I had somehow managed to corrupt my G8 base with a FBM and a variety of other things: something in the fingernail area (morphs being in conflict I fear) and this toe setting remain unresolved.)  Given these efforts, and the number of times updates have been applied and runtimes rebuilt, I am surprised; but, there is something lurking in the long lists of 'data' that is annoying though not a show stopper. 

    Thanks again.  Hope I didn't cause anyone too much angst

  • Serene NightSerene Night Posts: 17,672
    edited January 2021

    My question is why do expressions which do not work load with G8.1? It makes it hard to find ones that do work and clutters up the parameter dials. Is there a way to remove them from g8M.1 and still have them for G8? 

    Post edited by Serene Night on
  • For those of us who haven't updated to Genesis 8.1 yet (but intend to), what would you guys agree is the best, least error-prone way to do so? 

    I'm on a Win10 laptop with the Studio 4.15 beta installed. What files should I uninstall first (and then update), and should these steps be done in any particular order?

  • PerttiAPerttiA Posts: 10,024

    Serene Night said:

    My question is why do expressions which do not work load with G8.1? It makes it hard to find ones that do work and clutters up the parameter dials. Is there a way to remove them from g8M.1 and still have them for G8? 

    Once the placeholder files (see my previous post) have been removed, all the expressions work.

    The reason for some expressions not working is that they are calling the disabled expressions and when they find the placeholder files instead, they do nothing.

  • zombiewhacker said:

    For those of us who haven't updated to Genesis 8.1 yet (but intend to), what would you guys agree is the best, least error-prone way to do so? 

    I'm on a Win10 laptop with the Studio 4.15 beta installed. What files should I uninstall first (and then update), and should these steps be done in any particular order?

    You don't need to uninstall anything. Just update the Genesis 8 Starter Essentials and  Default Resources for DAZ Studio 4.15+. Also make sure you're running the latest build of Daz Studio itself (4.15). 

  • marth_emarth_e Posts: 182

    PerttiA said:

    Serene Night said:

    My question is why do expressions which do not work load with G8.1? It makes it hard to find ones that do work and clutters up the parameter dials. Is there a way to remove them from g8M.1 and still have them for G8? 

    Once the placeholder files (see my previous post) have been removed, all the expressions work.

    The reason for some expressions not working is that they are calling the disabled expressions and when they find the placeholder files instead, they do nothing.

    Thanks for the explanation, PerttiA. Do you know why could be the reason for DAZ to create those placeholders in the first place knowing that it will disable some expressions?

  • algovincianalgovincian Posts: 2,636

    ChangelingChick said:

    zombiewhacker said:

    For those of us who haven't updated to Genesis 8.1 yet (but intend to), what would you guys agree is the best, least error-prone way to do so? 

    I'm on a Win10 laptop with the Studio 4.15 beta installed. What files should I uninstall first (and then update), and should these steps be done in any particular order?

    You don't need to uninstall anything. Just update the Genesis 8 Starter Essentials and  Default Resources for DAZ Studio 4.15+. Also make sure you're running the latest build of Daz Studio itself (4.15). 

    Do you suggest deleting the placeholders that disable the G8 expresions in G8.1? Do these placeholders serve any other purpose other than to disable the G8 expressions?

    - Greg 

  • I moved the placeholders onto a separate drive. (Daz didn't follow the files to the new file location.)

    Reinstalling the Starter Essentials would also repopulate the placeholders, and it's not like the Starter Essentials will disappear from the library.

  • PetraPetra Posts: 1,156

    marth_e said:

    PerttiA said:

    Serene Night said:

    My question is why do expressions which do not work load with G8.1? It makes it hard to find ones that do work and clutters up the parameter dials. Is there a way to remove them from g8M.1 and still have them for G8? 

    Once the placeholder files (see my previous post) have been removed, all the expressions work.

    The reason for some expressions not working is that they are calling the disabled expressions and when they find the placeholder files instead, they do nothing.

    Thanks for the explanation, PerttiA. Do you know why could be the reason for DAZ to create those placeholders in the first place knowing that it will disable some expressions?

    My guess would be to make more money because people will have to buy expressions made for G8.1. 

     

  • PerttiAPerttiA Posts: 10,024

    Petra said:

    marth_e said:

    PerttiA said:

    Serene Night said:

    My question is why do expressions which do not work load with G8.1? It makes it hard to find ones that do work and clutters up the parameter dials. Is there a way to remove them from g8M.1 and still have them for G8? 

    Once the placeholder files (see my previous post) have been removed, all the expressions work.

    The reason for some expressions not working is that they are calling the disabled expressions and when they find the placeholder files instead, they do nothing.

    Thanks for the explanation, PerttiA. Do you know why could be the reason for DAZ to create those placeholders in the first place knowing that it will disable some expressions?

    My guess would be to make more money because people will have to buy expressions made for G8.1. 

     Or maybe someone thought the facerig would be used, not realizing that some PA made expressions were calling the base expressions and wouldn't work.

    Sounds like the opposite of smart, but then again we have "Smart Content" to define what smart is cheeky

  • plasma_ringplasma_ring Posts: 1,025

    Petra said:

    marth_e said:

    PerttiA said:

    Serene Night said:

    My question is why do expressions which do not work load with G8.1? It makes it hard to find ones that do work and clutters up the parameter dials. Is there a way to remove them from g8M.1 and still have them for G8? 

    Once the placeholder files (see my previous post) have been removed, all the expressions work.

    The reason for some expressions not working is that they are calling the disabled expressions and when they find the placeholder files instead, they do nothing.

    Thanks for the explanation, PerttiA. Do you know why could be the reason for DAZ to create those placeholders in the first place knowing that it will disable some expressions?

    My guess would be to make more money because people will have to buy expressions made for G8.1. 

    I understand why people would draw this conclusion, but companies really don't do this kind of thing as a matter of course unless they're extremely shady or too big to suffer any consequences. I'm surprised they did it, but I can almost guarantee it was due to looking at the problem through Developer Glasses; it sounds like they thought customers would expect PAs to go back and support FACS on all of their old content or something similar and felt it was less confusing to make a clean break. I personally would have expected it to be more confusing to users to find that their dials suddenly do nothing on a converted character, but I'm also not part of the specific labyrinthine discussions and product workflow that sometimes leads to weird consensus. 

    The company I work for also sells digital items and we've weathered some catastrophic customer backlash due to well-meant development plans that users interpreted as cynical money grabs because they could not imagine any other reason we would make such a boneheaded choice. It happens. But a company like Daz can't benefit in the slightest from intentionally squeezing users. They have a 30-day return policy, so if they "trick" you into buying things all it does is burden their CS team when you inevitably demand a refund. Their entire business model depends on getting users to invest money in their library, which requires a high degree of trust to provide a return. People will buy 8.1 expressions without having their old library invalidated, and are more likely to do it if they're not super pissed off and reluctant to adopt the upgrade. 

  • fred9803fred9803 Posts: 1,564
    My guess would be to make more money because people will have to buy expressions made for G8.1.

    Dear oh dear I hope that's not the case. It would seem sensible, and to quash speculation, for Daz to provide a technical explanation as to why those placeholders are there. Especially considering that 8.1 is an update rather than a new generational model where one might expact loss of functionality between generations. I look forward to their response.

  • plasma_ringplasma_ring Posts: 1,025
    edited January 2021

    fred9803 said:

    My guess would be to make more money because people will have to buy expressions made for G8.1.

    Dear oh dear I hope that's not the case. It would seem sensible, and to quash speculation, for Daz to provide a technical explanation as to why those placeholders are there. Especially considering that 8.1 is an update rather than a new generational model where one might expact loss of functionality between generations. I look forward to their response.

    Judging from earlier conversation in this thread, the technical explanation is that expressions not designed for FACS support behave unpredictably on 8.1. Nobody who removed the placeholders has seen anything super wonky so far, but I imagine Daz was expecting users to follow a process something like:

    1. Use Babina 8 morphs on 8.1.
    2. Apply an expression from a set that should look a certain way on Babina 8
    3. "Oh no! The expressions I paid for don't look right now! Daz, you have to fix all of the old Genesis 8 expression packs right away! angry"

    From a certain perspective this makes sense, because they have existing evidence to support the idea that users will understand that upgraded features = some content doesn't work and consider that a fair exchange (in fairness they also have evidence that we're fine with things like autofit, which can cause some really bizarre issues with older clothing). But I encounter a lot of situations where creative development folks are dead sure that users will be way more upset or confused by an imperfect/unexpected experience than they will be by having options taken away. 

    On an unrelated note, I wonder when we'll start seeing more character release support for 8.1. 

    Post edited by plasma_ring on
  • LucielLuciel Posts: 475

    Is Powerpose still broken for everyone or is it something I should be trying to fix?

    I mean it's less broken than it was at the launch of 8.1, but it would be strange if the improved Powerpose templates were just the eyes. I have seen companies "improve" things in pretty mysterious ways that make no sense to anyone, but i'm assuming this isn't actually correct... hopefully... cheeky

    fred9803 said:

    My guess would be to make more money because people will have to buy expressions made for G8.1.

    Dear oh dear I hope that's not the case. It would seem sensible, and to quash speculation, for Daz to provide a technical explanation as to why those placeholders are there. Especially considering that 8.1 is an update rather than a new generational model where one might expact loss of functionality between generations. I look forward to their response.

    Maybe so certain things wouldn't trigger a "missing file" error they stuck a bunch same named files in for compatibility?

    Lots of the Genesis 8.1 stuff seems a bit unfinished right now though and lots of it seems a bit placeholdery, so I guess we'll find out at some point..  

  • fred9803fred9803 Posts: 1,564

    You may well be right plasma_ring, but to disable all expression cross-functionality because some expressions may look different seems a bit odd. Users know G8F poses kind of work with G8M but require some tweaking so the same could apply with G8/G8.1 expressions. And that's between two completely different models and not an update to an existing one like 8.1. I'm sure there must be a logical explanation.

  • AnimAnim Posts: 241

    PerttiA said:

    Anim said:

    No lip controls in G 8.1 Base - is that correct or only missing in my install?

    Assuming you are using DS 4.15...

    Remove the 1kb files from "...\Data\DAZ 3D\Genesis 8\Female 8_1\Morphs\Daz 3D\Base Pose Head\" and "...\Data\DAZ 3D\Genesis 8\Female 8_1\Morphs\Daz 3D\Expressions\", ie. empty those folders and the G8.1 will pick up the G8 morphs (For male figure the path is same except Female -> Male)

    Thank you - that did the trick.

  • HylasHylas Posts: 5,070

    Petra said:

    My guess would be to make more money because people will have to buy expressions made for G8.1. 

    If that was the case they would have named the figure G9 and made it way less backwards compatible than it is.

  • Greetings, everyone. I just want to know HOW to update/iupgrade to Genesis 8.1? Will I get it automatically in my library for free? I still have G8 contents within DAZ Studio product and DAZ Studio Beta. If I will not get into my library (in my account), where can I find the Genesis 8.1 products? I looked in DAZ Stduio web page but can not find. By the way, I really love DAZ Studio and what the company offers many free content for free to make default renders. The more I fondle with DAZ Studio the more I learn and love it. Many thanks to DAZ company!

  • HylasHylas Posts: 5,070

    So, I did the thing where I deleted the two folders to get 8.0 expressions to work on 8.1. buuuuuuuuut... is there a way to keep the 8.0 and 8.1 sliders apart? Now they're all jumbled together and I don't love it.

  • LeanaLeana Posts: 11,821

    HenryYrnet said:

    Greetings, everyone. I just want to know HOW to update/iupgrade to Genesis 8.1?

    Reinstall G8 starter essentials and DS default resources.

  • HylasHylas Posts: 5,070

    Hylas said:

    So, I did the thing where I deleted the two folders to get 8.0 expressions to work on 8.1. buuuuuuuuut... is there a way to keep the 8.0 and 8.1 sliders apart? Now they're all jumbled together and I don't love it.

    Ok, so here's a solution to my own question. As always, do at your own risk.

    Use a software that can replace text within multiple files (I used BBEdit).

     

    Replace following: 0.3764706, 0.2784314, 0.3254902

    With: 0.18, 0.18, 0.18
    (or any other colour code, really)

    for all *.dsf files in following folders:
    data/DAZ 3D/Genesis 8/Female/Morphs/DAZ 3D/Base Pose Head
    data/DAZ 3D/Genesis 8/Female/Morphs/DAZ 3D/Expressions
    data/DAZ 3D/Genesis 8/Male/Morphs/DAZ 3D/Base Pose Head
    data/DAZ 3D/Genesis 8/Male/Morphs/DAZ 3D/Expressions

    Now all basic expression morphs associated with 8.0 will appear grey (or whatever colour you chose) instead of the default purple and are visually distinct from the 8.1 morphs.

    You will likely have to do this each time G8 is updated.

     

    Bildschirmfoto 2021-01-30 um 12.24.18.png
    354 x 676 - 95K
  • HylasHylas Posts: 5,070

    Matt_Castle said:

     

    (Also, as noted, there is a minor conflict between the sets, as both sets have controls labelled "Mouth Smile" and "Mouth Frown" that will merge into one slider on default DS settings, although that is not fundamentally something that had to be an issue and can be resolved by editing the files to change the labels, which should not affect presets, as those use the internal naming to set their values).

    Can someone give me a step-by-step for dummies on how to rename the old frown and smile? Thank you!

  • RagazzineRagazzine Posts: 100

    Zilvergrafix said:

    All that 3 nights with no sleep got paid...I've cloned Imma.Gram laugh well, almost, thanks V8.1

     

    By golly, that is well done. She seems just off perfect but really well done. 

  • SaulCsSaulCs Posts: 67

    One question about the PBR shader.

    If i am using Victoria 8.1 the materials already use the PBR shader skin as default or i need to add it?

    Thak you.

  • PerttiAPerttiA Posts: 10,024

    Hylas said:

    So, I did the thing where I deleted the two folders to get 8.0 expressions to work on 8.1. buuuuuuuuut... is there a way to keep the 8.0 and 8.1 sliders apart? Now they're all jumbled together and I don't love it.

    Was this the reason for disabling them in the first place?... wink 

  • Question about Genesis8 and Genesis8.1 crossover:

    So I've downloaded the update to 8.1 and also some facial expressions for her. And I've found that while I can load Genesis8.1 and apply one of my existing Genesis 8 character morphs, what I can't do is load an existing character from the characters library and then use the Genesis 8.1 facial expressions. Which presumably means that when I select a character from the characters tab and load her, it loads to the Genesis8 base figure and not the 8.1 base figure.

    This seems poorly implemented. Is there no way to make it so that a newly loaded figure uses the Genesis 8.1 morphs not the Genesis 8 ones?

     

    Does this also mean that all my pre-saved characters and figures are now obsolete and won't be able to use any of the new Genesis 8.1 expressions or poses without me manually re-making them from scratch using the Genesis 8.1 base which looks functionally identical, apart from being able to access some content that is apparently barred to the older model?

  • Charlie JudgeCharlie Judge Posts: 12,879

    ChallyII said:

    Question about Genesis8 and Genesis8.1 crossover:

    So I've downloaded the update to 8.1 and also some facial expressions for her. And I've found that while I can load Genesis8.1 and apply one of my existing Genesis 8 character morphs, what I can't do is load an existing character from the characters library and then use the Genesis 8.1 facial expressions. Which presumably means that when I select a character from the characters tab and load her, it loads to the Genesis8 base figure and not the 8.1 base figure.

    This seems poorly implemented. Is there no way to make it so that a newly loaded figure uses the Genesis 8.1 morphs not the Genesis 8 ones?

     

    Does this also mean that all my pre-saved characters and figures are now obsolete and won't be able to use any of the new Genesis 8.1 expressions or poses without me manually re-making them from scratch using the Genesis 8.1 base which looks functionally identical, apart from being able to access some content that is apparently barred to the older model?

    What you can do is load the Genesis 8.1 base and then apply the Genesis 8 character to it. That should allow you to use the Genesis 8.1 expressions (but not necessairly the Genisis 8 expressions) 

  • PerttiAPerttiA Posts: 10,024
    edited January 2021

    Hylas said:

    Matt_Castle said:

     

    (Also, as noted, there is a minor conflict between the sets, as both sets have controls labelled "Mouth Smile" and "Mouth Frown" that will merge into one slider on default DS settings, although that is not fundamentally something that had to be an issue and can be resolved by editing the files to change the labels, which should not affect presets, as those use the internal naming to set their values).

    Can someone give me a step-by-step for dummies on how to rename the old frown and smile? Thank you!

    There are two ways to do this;

    1. Find the "Mouth Smile" and "Mouth Frown" morphfiles in Genesis 8 Male/Female morph folders, open the files in Notepad++ and change the "Label" from "Mouth Smile" to "Mouth_Smile" and save, same with the Frown.

    2. Open DS, clear the scene if you have anything loading by default, Load the "Genesis 8 Base Female" or "Genesis 8 Female Dev Load", in parameters tab navigate to the "Mouth Smile" dial, and open the properties (with the gogwheel), change the Label from "Mouth Smile" to "Mouth_Smile" and press "Ok". Do the same with the Frown-dial, then perform File->Save As->Support Asset->Save Modified Assets, which will do essentially the same as option no1. - Repeat the process with the male figure.

    Post edited by PerttiA on
  • DaventakiDaventaki Posts: 1,624

    @Challyll  If you use character presets it will not load in a G8.1 it will load in G8  you can do two things.  (I copied this from another post I made and used BJ Noemi as an example)

    I don't know if your using Smart Content or not so im going to post my steps with both.

    Content Library:
    1. Load G8.1F. Make sure she is selected.
    2. Goto the Character you want to load. Genesis 8 Female/Characters/BJ Noemi/   I dont have Lyra but will go with another Bluejuante character Noemi. Double click the 01 Noemi Head Apply then the 01 Noemi Body    Apply.  Give it a minute should load on G8.1F.

    Smart Content: Pretty close to the same
    1. Load G8.1F. Make sure she is selected.
    2. Goto Figures/People/Female/Noemi HD & Smile HD
    3. In the list on the left (Figures/Hair/Materials/Shaping)  Go to shaping and in there you will find the 01 Noemi Head Apply then the 01 Noemi Body Apply.  Double click to add to G8.1F
    Alternate: Or you can click in Figures and hold down CTRL and double click on the BJ Noemi icon in there and a box pops up with three options All/Materials/Morphs select which you want and click ok.  Using this options takes longer to load for me. When I first did it I thought it was going to load the whole base G8F and everything which it what happens when you just double click on the icon.

Sign In or Register to comment.