Being a Cow (Alternate Version)

[Sinnamonroll66]

6 hours ago, botticelli said:

With bac_blacksmith there are several furniture aliases like furnPillory, furnLesson, etc. The bacFurniture alias is deprecated and no longer used, only those starting wtih "furn..." are relevant. In the case of bac_capturedcow however, those are not the ones in question. Here, it's a property capFurniture_var of quest bac_unowned which should contain the ObjectReference of the milk pump in the cart (xx0171cb, xx = BAC's mod no). with sqv bac_unowned, you should be able to find that property. Check, if there is a vlid ID in there. That ObjectReference points to a zbfMilkOMatic (ZaZ) milk pump. The popup in that quest only shows, when that reference is not valid. One occasion this happens is when installing ZaZ versions mid-game.

 

If you do prid xx0171cb (again xx = BAC's mod no), does the console show a vlid object?

 

When i do prid xx0171cb in both my 2.0.8 and 2.0.10 games it does seem to find a valid object both times just fine, though oddly i don't know if it has something to do with my setup or something but with the 2.0.8 version the xx was a number while with the 2.0.10 it was two letters instead, no clue if that really means much though, just something i found a bit odd.

[bigbasi]

ok I got myself through to the end of Cow's Tears, got captured and now I guess bac_capturedcow2 should start, but it doesn't. setstage to 0 / 10 , resetquest, enablequest don't do anything.

 

As for prid xx0171cb it gives back the milk machine at the camp.

[botticelli]

7 hours ago, Sinnamonroll66 said:

i found a bit odd.

You may run a maximum of 254 mods (and some extra light mods under $FF). the 254 mods are numbered hexadecimal from $00 (Skyrim.esm) through max $FE and those hex numbers make up the first two digits of any object ids from a mod.

 

2 hours ago, bigbasi said:

As for prid xx0171cb it gives back the milk machine at the camp.

If that is a valid reference, the problem sits with quest bac_unowned where that property (not alias!) capFurniture_var probably points to NONE. That can happen when installing a new mod version mid-game. It should however not happen with a new game.:

 

Edited August 4, 2024 by botticelli

[Sinnamonroll66]

39 minutes ago, botticelli said:

You may run a maximum of 254 mods (and some extra light mods under $FF). the 254 mods are numbered hexadecimal from $00 (Skyrim.esm) through max $FE and those hex numbers make up the first two digits of any object ids from a mod.

 

If that is a valid reference, the problem sits with quest bac_unowned where that property (not alias!) capFurniture_var probably points to NONE. That can happen when installing a new mod version mid-game. It should however not happen with a new game.:

 

 

Figured why it was dd on the second try, i just forgot to run LOOT to re-sort my plugins list and out of curiosity i went to check on both the saves in the same situation for the property and both of them appeared to be filled in yet even still the 2.0.10 scene complains about missing furniture and the scene doesn't work while the 2.0.8 scene works fine (even if the changes like the bigger nosering, the cowbell and the brandings don't appear until after she's gotten out of the milker)

 

2.0.10

Spoiler

 

 

2.0.8

Spoiler

 

[Galarorn]

So I finally got around to redoing everything after the december steam update, and everything is running smooth...except when it comes time for any sort of facial alteration.
Any time one of the changes/mutations goes for the face/head, I get a CTD.  I set up everything properly, I'm just wondering if I missed a head mesh somewhere or something?  Playing on SE/AE.

[botticelli]

16 hours ago, Sinnamonroll66 said:

 

Figured why it was dd on the second try, i just forgot to run LOOT to re-sort my plugins list and out of curiosity i went to check on both the saves in the same situation for the property and both of them appeared to be filled in yet even still the 2.0.10 scene complains about missing furniture and the scene doesn't work while the 2.0.8 scene works fine (even if the changes like the bigger nosering, the cowbell and the brandings don't appear until after she's gotten out of the milker)

 

2.0.10

  Reveal hidden contents

 

 

2.0.8

  Reveal hidden contents

 

The quest bac_unowned acts as arepository for the furniture here. The hunter capture quest (bac_capturedcow) gets started at some point by this quest. When it does that, the value of that property gets passed to the capture quest. Now if you had some misaligned load order when starting the capture quest, then save, re-order and load again, the capture quest will still have a broken property. Otherwise, if you eventually got that startetd again after re-ordering, check that via console (sqv bac_capturedcow). Here, there should be a filled alias called bacFurniture also pointing to xx0171cb. That alias is the one causing the message box, if not filled.

 

Anyway, should you end up there again, kill the hunters then go to BAC MCM Debug page and click (a) Skip Story (tats) and (b) Skip Story (items) [*not* Skip Story without any brackets following], then leave MCM and wait for the items and tats to appear. After that, open console and type setstage bac_tears1 10.

Edited August 5, 2024 by botticelli

[Sinnamonroll66]

2 hours ago, botticelli said:

The quest bac_unowned acts as arepository for the furniture here. The hunter capture quest (bac_capturedcow) gets started at some point by this quest. When it does that, the value of that property gets passed to the capture quest. Now if you had some misaligned load order when starting the capture quest, then save, re-order and load again, the capture quest will still have a broken property. Otherwise, if you eventually got that startetd again after re-ordering, check that via console (sqv bac_capturedcow). Here, there should be a filled alias called bacFurniture also pointing to xx0171cb. That alias is the one causing the message box, if not filled.

 

Yeah the misaligned load order wasn't my real issue, it's just what had caused the two examples earlier to have different id's but now in the pics i sent they both had the same id as they were placed in the same spot in the load order this time so this wasn't the cause of the issue and if you took a peek at the two sets of pictures i sent for both the 2.0.8 and the 2.0.10 (with the bac.esp changed to the version made by atheistbigred) it shows that they both still point to the same object and now i went to check the sqv bac_capturedcow on both saves as well and in both games the alias called bacFurniture was pointing to the right valid object so i'm guessing instead of the issue being in the object id now and instead it's probably some issue with the captured cow quest itself since i also ran a quick test where i went into my 2.0.8 save file that was already chased by the hunters and updated it to the 2.0.10 version of bac before getting captured and now suddenly the scene didn't work which leads me to think that some change that was done in 2.0.10 caused the issue but it's hard to really say what

[Galarorn]

4 hours ago, Galarorn said:

So I finally got around to redoing everything after the december steam update, and everything is running smooth...except when it comes time for any sort of facial alteration.
Any time one of the changes/mutations goes for the face/head, I get a CTD.  I set up everything properly, I'm just wondering if I missed a head mesh somewhere or something?  Playing on SE/AE.

Okay, I got them to work after grabbing the LE head mesh's...(That I did miss)...and now it's saying something about 'missing SLIF'.  Would that be sexlab inflation framework?

[oofer23]

25 minutes ago, Galarorn said:

Okay, I got them to work after grabbing the LE head mesh's...(That I did miss)...and now it's saying something about 'missing SLIF'.  Would that be sexlab inflation framework?

So you just downloaded and installed the LE loose files? I’m having an issue with my head turning blue despite having all of the textures, overlay slots and requirements installed and was wondering if this could be the fix.

[Unknown22923]

2 hours ago, oofer23 said:

So you just downloaded and installed the LE loose files? I’m having an issue with my head turning blue despite having all of the textures, overlay slots and requirements installed and was wondering if this could be the fix.

if the head does morph correctly but just turns blue Botticelli made a temporary fix with .pex file for you to put into the script folder of the game, or if you lazy like me using vortex, you can slap it into the bac's script folder.

Edited August 5, 2024 by Unknown22923

[bigbasi]

Oh man, I'm kinda frustrated now (I gave up on 2.10 because I couldn't get capturedcow2 to work). But obviously 2.10 seems to be working for others...

I just started a new game with 2.0.8 installed and facing the same issues I had with 2.10 with bac_capturedcow. (capFurniture_var is filled correctly and I don't get any errors at all)

I get put into the milking machine and the Hunters are just walking away.

So there must something wrong with my installation.

 

I can't run LOOT because I'm on a Wabbajack List ( Nefaram 12 ).

 

Can somebody with a working configuration tell me the load order with MO2 with all the dependencies? And the priority on the right side? More to the Top or rather on the Bottom.... I don't know, I'm really out of Ideas. I really would like this to work, I started to like those fluffy ears 😉

 

PS: RAINER! Zu Hülf! 😉

 

Edited August 5, 2024 by bigbasi

[Unknown22923]

19 minutes ago, bigbasi said:

Oh man, I'm kinda frustrated now (I gave up on 2.10 because I couldn't get capturedcow2 to work). But obviously 2.10 seems to be working for others...

I just started a new game with 2.0.8 installed and facing the same issues I had with 2.10 with bac_capturedcow. (capFurniture_var is filled correctly and I don't get any errors at all)

I get put into the milking machine and the Hunters are just walking away.

So there must something wrong with my installation.

 

I can't run LOOT because I'm on a Wabbajack List ( Nefaram 12 ).

 

Can somebody with a working configuration tell me the load order with MO2 with all the dependencies? And the priority on the right side? More to the Top or rather on the Bottom.... I don't know, I'm really out of Ideas. I really would like this to work, I started to like those fluffy ears 😉

 

PS: RAINER! Zu Hülf! 😉

 

there is still some people reporting 2.10 as working except the capture quest (me including) and a blueface on SE that has a fix already, the capture quest its being looked at as far as i can tell. :]

[oofer23]

4 hours ago, Unknown22923 said:

if the head does morph correctly but just turns blue Botticelli made a temporary fix with .pex file for you to put into the script folder of the game, or if you lazy like me using vortex, you can slap it into the bac's script folder.

First off, thank you. The blue face issue went away, but my game is still crashing with any head morph. I downloaded the LE meshes like the other user did and it still crashes.

[Unknown22923]

15 minutes ago, oofer23 said:

First off, thank you. The blue face issue went away, but my game is still crashing with any head morph. I downloaded the LE meshes like the other user did and it still crashes.

what version of skyrim are you running?

 

If its SE 1170 then im using this head mesh

Edited August 5, 2024 by Unknown22923

[oofer23]

1 hour ago, Unknown22923 said:

what version of skyrim are you running?

 

If its SE 1170 then im using this head mesh

Alright thanks for the help man.

[botticelli]

10 hours ago, bigbasi said:

an somebody with a working configuration tell me the load order with MO2 with all the dependencies?

MO2 tends to know things better than you storing those in its "overwrites". Sometimes, you have to delete those, too. That's the reason, I use Vortex.

[Galarorn]

15 hours ago, Galarorn said:

Okay, I got them to work after grabbing the LE head mesh's...(That I did miss)...and now it's saying something about 'missing SLIF'.  Would that be sexlab inflation framework?

Alright, the head mesh's stopped the game crashing, and I got past the blue face...but the mesh's aren't really working?  Like the head doesn't really change shape at all, it just get's slightly bigger each time.

[SilentOption]

Blue Mesh Issue how do I fix this @botticelli it's from the new game... when I started mid game it doesn't have the blue mesh

Edited August 6, 2024 by SilentOption

[botticelli]

21 minutes ago, SilentOption said:

ue Mesh Issue how do I fix this

*not* mesh issue, this is a *texture* issue. Install missing textures (tats pack)

Edited August 6, 2024 by botticelli

[SilentOption]

31 minutes ago, botticelli said:

*not* mesh issue, this is a *texture* issue. Install missing textures (tats pack)

I tried installing it with mod manager and playing the texture pack for tats manually it's still appearing blue. I even setup the overlay on the nioveride

Edited August 6, 2024 by SilentOption

[Unknown22923]

26 minutes ago, SilentOption said:

I tried installing it with mod manager and playing the texture pack for tats manually it's still appearing blue. I even setup the overlay on the nioveride

try go into racemenu and body layer and see if you can see what name of the body layer its supposed to be.

[SilentOption]

1 minute ago, Unknown22923 said:

try go into racemenu and body layer and see if you can see what name of the body layer its supposed to be.

what am I suppose to look in the race menu

[Unknown22923]

3 minutes ago, SilentOption said:

what am I suppose to look in the race menu

Body Paint on the top fanes shows what layers is being displayed etc see if there is a black phase "X" or whatever colour you where going for.

[SilentOption]

3 minutes ago, Unknown22923 said:

Body Paint on the top fanes shows what layers is being displayed etc see if there is a black phase "X" or whatever colour you where going for.

I use the brown color but I tried the other colors as well and they all turn out blue

[Unknown22923]

3 minutes ago, SilentOption said:

I use the brown color but I tried the other colors as well and they all turn out blue

Ok, try go to slave tats and see if there is a bac option there.

If not then as botticelli says that you must have installed something wrong with the tats file.