NAF Bridge

[dosfox]

15 hours ago, Here4SlootyMods said:

I'm glad I could help but to be honest it's really weird that F4z Ro D'oh's installation fixed that for you.

 

It's VERY strange, it was definitely the last thing i expected to happen. I've been annoyed by this problem for weeks now, but haven't installed any other mods, made no major changes to NAF or automomy settings. Immediately after installing Ro D'oh the settler NPCs' sex scenes were noticably more frequent and remain so till now. It's like when i found that altering the Bridge "script delay" setting altered the mating frequency of NPCs, Panda could see no reason why that should happen either (btw, that doesn't work any more with Bridge v.78 for some reason). I guess we are all dealing with something new, and Autonomy is throwing some unique stuff at NAF/Bridge with results that i can only report, but not explain.
 

[dosfox]

Hey @Evi1Panda,

Thank your for that console command. Unfortunately it doesn't really work. Sometimes it will change the NPC's voice back to male, but it seems that every time Autonomy scans (every 20 seconds or so) it redistributes the quest alias or whatever it is, and the same problem, again. So not really a fix.

 

[Evi1Panda]

18 minutes ago, dosfox said:

Hey @Evi1Panda,

Thank your for that console command. Unfortunately it doesn't really work. Sometimes it will change the NPC's voice back to male, but it seems that every time Autonomy scans (every 20 seconds or so) it redistributes the quest alias or whatever it is, and the same problem, again. So not really a fix.

 

You have some strange trouble with autonomy, it doesn't work for me this way. If autonomy filled alias - it should start scene. It work for me this way. And after scene you should just free alias because bethesda promissed that it will be after quest stops, but it is not. That is why autonomy has such trouble. It stops quest after scene, believing Todd, that he will free quest aliases, but Todd is cheating...

 

Female voices is a side effect of this bug. As I said before...

Edited October 22, 2024 by Evi1Panda

[dosfox]

@Evi1Panda

OK, i'm using Autonomy v2.8, it's the only version that works for me, even in AAF. It sounds like you might be using a later beta version (with broken blacklist function). I won't bother you any more with Autonomy problems. Thanks for all your help so far, sorry to distract you from more important things.

[Evi1Panda]

32 minutes ago, dosfox said:

@Evi1Panda

OK, i'm using Autonomy v2.8, it's the only version that works for me, even in AAF. It sounds like you might be using a later beta version (with broken blacklist function). I won't bother you any more with Autonomy problems. Thanks for all your help so far, sorry to distract you from more important things.

I have had autonomy for a long time, and I rarely update it. In my opinion, I missed 2.8, I had 2.7 or even less installed until the last one. In general, it has always worked this way. But group animations appeared only in the latest update. But this problem, with aliases, is 100 years old. Never remember Authonomy without it.

 

But I am not 100% sure, maybe it because I updated Bridge.

Edited October 22, 2024 by Evi1Panda

[VilLynne]

I agree with the above sentiment about the scenes with two women in these animations are mostly repurposed M-F scenes with a strap-on; although, there are some women who actually prefer to wear a strap-on and 'do not want to be penetrated by anything resembling a d', so then I felt the need to to study their natures, which still felt somewhere in between, though obvi' I kept that to myself.

Anyway, if someone wishes to compose real scenes of two women in love (and/or lust) with each other, both being stimulated simultaneously, then I attached a picture link of just one example of a better "aid" for F-F love (curved double-sided rabbit-style vibe with remote control)...

https://e.pcloud.link/publink/show?code=XZpQECZu4iiAAV1BV7PGxIJJFc2cQtgq9CX

FYI, I will also search for the aforementioned "fufa?" animations; I'm not quite sure what it is.

Edited October 25, 2024 by VilLynne

[Evi1Panda]

Quote

https://e.pcloud.link/publink/show?code=XZpQECZu4iiAAV1BV7PGxIJJFc2cQtgq9CX

 

 

Wanna see this data is in processing...

[WaterRabbit]

So I have been trying NAF, but so far in most of the scenes the PC is invisible.  Is there something that I am missing here?

[Evi1Panda]

If you're using Custom Camera replace it with Camera Tweak. Or try with it if you don't use camera mod.

 

[WaterRabbit]

3 hours ago, Evi1Panda said:

If you're using Custom Camera replace it with Camera Tweak. Or try with it if you don't use camera mod.

 

 

Camera Tweaks seems to have fixed the problem, Custom Camera did not.

Thanks,

 

EDIT: Update, that didn't fix the problem.  It is back.

 

Edited October 23, 2024 by WaterRabbit

[VilLynne]

On 10/22/2024 at 8:55 PM, WaterRabbit said:

Camera Tweaks seems to have fixed the problem, Custom Camera did not.

Thanks,

Camera Tweaks definitely needs to be in the future NAF Manual; it's virtually required...?  I did have to fiddle with some settings for an hour to get it to play nicely with See Through Scopes's 3rd-person to 1st person aiming; now they are working together very well.

Edited October 26, 2024 by VilLynne

[dosfox]

8 hours ago, Evi1Panda said:

In my opinion, I missed 2.8, I had 2.7 or even less installed until the last one. In general, it has always worked this way. But group animations appeared only in the latest update.

 

I have been using Autonomy v2.6/AAF v.164-0 since August 2021, with no updates of anything. (I took a voluntary 3yr sabbatical from internet modding scene because of AAF's snobbery and lack of development, and the Nexus IP Crisis!) The last playthrough with that mod list lasted 2500 hours. That game was very stable and Autonomy worked reliably from beginning to end.

 

• With v2.6 there are definitely 3-6P animations happening regularly, but 4P+ are pretty buggy and rarely end well. There is an option for "Threesomes" in the v2.6 MCM settings which enables 3P+ animations. I never noticed the femaleVoice problem with v2.6.

 

Three years later I updated to Autonomy v2.8/AAFv1.71,  just a few weeks before trying NAFBridge v.529.  Autonomy v2.8 was working with AAF the same as v2.6, but with a couple of great new features with hotkey functionality including a blacklist that actually works. I tried every beta of the Autonomy 3.0 series, with AAF and with NAF, but none worked as well as v2.8, if they worked at all. And you know the story from there ...

 

Edited October 23, 2024 by dosfox

[Evi1Panda]

Update, that didn't fix the problem.  It is back.

 

 

Then I dont know. I have it in very rare cases. Somebody wrote Camera Tweaks fixes it for him. I never played without CT, so... Body disappearing is caused too close camera position before scene start, so I believed that CT can fix it.

 

Edited October 23, 2024 by Evi1Panda

[Evi1Panda]

Own blacklist for authonomy was the first I did for myself. I never used autonomy blacklist, so this bug is something what I missed.

Because it is too fun when Marcie fucks with somebody in Concord museum.

Edited October 23, 2024 by Evi1Panda

[dosfox]

5 hours ago, Evi1Panda said:

I never used autonomy blacklist, so this bug is something what I missed.

 

Autonomy v2.8 doesn't use a predefined blacklist. It uses an attribute called the "Autonomous Perk" which is distributed by Robco Patcher to NPCs. The Autonomous Perk can be defined as "NPC can have sex" or "NPC can't have sex" in MCM. The perk can then be assigned to any faction of your choice by MCM settings, or to individual NPCs with a hotkey. So if you choose the Autonomous Perk to be "NPC can't have sex" you have an automatic blacklist which you can add (or remove) individual NPCs to with the hotkey, or whole factions with MCM settings. This is a great system which works perfectly only in v2.6 and v2.8.

 

Edited October 23, 2024 by dosfox

[izzyknows]

14 hours ago, VilLynne said:

Camera Tweaks definitely needs to be in the future NAF Manual; it's virtually required. 

Actually, us old school folks are way ahead of you. We use a custom ini tweak and no mods required. And making CT a hard requirement is just silly. Making it a strongly suggested (this will help IF you have this issue) mod would be a good idea. If it actually does fix the issue of course.

The point is, the less "required" mods the better.

[izzyknows]

9 hours ago, Evi1Panda said:

Body disappearing is caused too close camera position before scene start

There's an ini camera zoom fix, I think it was a fix for the barber chair at the time. But when put into 3rd person you are by default zoomed out about twice as far as vanilla. Which fixes that issue. But you can also zoom waaay out, which is handy at times. 😜

So is it possible to do something similar when the scene starts?

Edited October 23, 2024 by izzyknows

[Evi1Panda]

@izzyknows actually have some ideas, but had no time to test it. What exactly ini setting do you mean, old man?

[izzyknows]

2 hours ago, Evi1Panda said:

@izzyknows actually have some ideas, but had no time to test it. What exactly ini setting do you mean, old man?

Hell if I know! It's been almost 10 years. 😜

The only time I've had missing bodies is when either the camera was to close to a wall, for example, or the actors wasn't moved together correctly. Like one being dead and de-spawning before being moved. In other words, never had "camera" issues.

This is what I've been using for God knows how long.

 

Spoiler

[Camera]
f3rdPersonAimFOV=70
f1stHorzDampeningVelocityDampening=0.1
f1stHorzDampeningSpringConstant=0.0001
f1stVertDampeningVelocityDampening=0.1
f1stVertDampeningSpringConstant=0.0010
fCameraCasterMinTargetHeight=30.0000
fTweenCamZoomSpeed=50.0000
fTweenCamZoomFOVMod=90.0000
fTweenCamRotClosingSpeed=10.0000
fTweenCamRotSpeed=4.0000
fTweenCamRotAngle=0.0500
f3rdPersonAimDollySpeed=6.0000
f3rdPersonAimDist=20.0000
f3rdPersonAimFOVAnimateSec=0.0000
f3rdPersonAimFOV=75.0000
fVanityModeMaxDist=800.0000
fVanityModeMinDist=30.0000
fPitchZoomOutMaxDist=300.0000
fMinCurrentZoom=0.0000
fMouseWheelZoomSpeed=3.0000
f3rdPersonPowerArmorCameraAdjust=0.0000
fOverShoulderMeleeCombatAddY=0.0000
fOverShoulderMeleeCombatPosZ=-10.0000
fOverShoulderMeleeCombatPosX=12.0000
fOverShoulderCombatAddY=0.0000
fOverShoulderCombatPosZ=13.0000
fOverShoulderCombatPosX=28.0000
fOverShoulderPosZ=0.0000
fOverShoulderPosX=0.0000
f1stPitchOffsetMouseMaxLag=2.0000
f1stPitchOffsetMouseFollowSpeed=15.0000
f1stPitchOffsetMultOffMaxSpeed=1.0000
f1stPitchOffsetMultOffAccel=1.0000
f1stPitchOffsetMultOnMaxSpeed=0.6000
f1stPitchOffsetMultOnAccel=0.5000
f1stPitchOffsetTarget=0.7500
f1st3rdSwitchDelay=0.0000
bApplyCameraNodeAnimations=0
bUseFuzzyPicking=1

 

[WaterRabbit]

2 hours ago, izzyknows said:

Hell if I know! It's been almost 10 years. 😜

The only time I've had missing bodies is when either the camera was to close to a wall, for example, or the actors wasn't moved together correctly. Like one being dead and de-spawning before being moved. In other words, never had "camera" issues.

This is what I've been using for God knows how long.

 

  Reveal hidden contents

[Camera]
f3rdPersonAimFOV=70
f1stHorzDampeningVelocityDampening=0.1
f1stHorzDampeningSpringConstant=0.0001
f1stVertDampeningVelocityDampening=0.1
f1stVertDampeningSpringConstant=0.0010
fCameraCasterMinTargetHeight=30.0000
fTweenCamZoomSpeed=50.0000
fTweenCamZoomFOVMod=90.0000
fTweenCamRotClosingSpeed=10.0000
fTweenCamRotSpeed=4.0000
fTweenCamRotAngle=0.0500
f3rdPersonAimDollySpeed=6.0000
f3rdPersonAimDist=20.0000
f3rdPersonAimFOVAnimateSec=0.0000
f3rdPersonAimFOV=75.0000
fVanityModeMaxDist=800.0000
fVanityModeMinDist=30.0000
fPitchZoomOutMaxDist=300.0000
fMinCurrentZoom=0.0000
fMouseWheelZoomSpeed=3.0000
f3rdPersonPowerArmorCameraAdjust=0.0000
fOverShoulderMeleeCombatAddY=0.0000
fOverShoulderMeleeCombatPosZ=-10.0000
fOverShoulderMeleeCombatPosX=12.0000
fOverShoulderCombatAddY=0.0000
fOverShoulderCombatPosZ=13.0000
fOverShoulderCombatPosX=28.0000
fOverShoulderPosZ=0.0000
fOverShoulderPosX=0.0000
f1stPitchOffsetMouseMaxLag=2.0000
f1stPitchOffsetMouseFollowSpeed=15.0000
f1stPitchOffsetMultOffMaxSpeed=1.0000
f1stPitchOffsetMultOffAccel=1.0000
f1stPitchOffsetMultOnMaxSpeed=0.6000
f1stPitchOffsetMultOnAccel=0.5000
f1stPitchOffsetTarget=0.7500
f1st3rdSwitchDelay=0.0000
bApplyCameraNodeAnimations=0
bUseFuzzyPicking=1

 

 

It the scenes I mentioned, the camera started about 10 feet away and there were not any walls nearby.  In one of the scenes it was two males air humping and it was clear where the PC was supposed to be.  It didn't seem to be a camera thing to me since everything was visible except for the PC.

Since there wasn't a clear fix, I just went back to AAF.  This was my second attempt to get NAF to work and so far it has been a bust both times.  If seems to be missing several feature like moving the scene forward.  It is faster and doesn't have the stutters that AAF has.

 

Overall, though both NAF and AAF seem primitive compared to SexLab for Skyrim. One of the biggest features is the ability to move the scene when it starts in an awkward place -- this doesn't seem to be something in either framework.  Or maybe I just cannot figure out how to do it.

 

Either way, it seems NAF still has some bugs to work out.  The NAFicator was a big step forward, but there is not point in using it if the PC is invisible in 75% of the scenes.

[Dlinny_Lag]

9 hours ago, izzyknows said:

Hell if I know! It's been almost 10 years.

Do you mean "fMinCurrentZoom:Camera"?

[Evi1Panda]

@WaterRabbit agree this trouble is, but I have it very very rarely. I guess you have some specific in your modlist or settings that provide this to be often. But have no idea what is it. As everything else, one day it will be fixed.

Edited October 24, 2024 by Evi1Panda

[dosfox]

@Evi1Panda   A couple of questions about the NAF.log:

 

1.  On every load of the game this line appears:

 

     [10/24/2024 - 20:01:54] [info] Cache invalid, rebuilding (startup may take longer than usual)...

 

2. What is going on here?

 

    [10/24/2024 - 20:02:30] [info] Ready!
    [10/24/2024 - 20:04:14] [warning] Ref ID from co-save is not valid. Empty handle will be used.
    [10/24/2024 - 20:04:14] [warning] Ref ID from co-save is not valid. Empty handle will be used.
    [10/24/2024 - 20:04:14] [warning] Ref ID from co-save is not valid. Empty handle will be used.
    [10/24/2024 - 20:04:14] [info] Finished deserialization in 0.747ms   

 

NAF.log

[Evi1Panda]

1 hour ago, dosfox said:

@Evi1Panda   A couple of questions about the NAF.log:

 

1.  On every load of the game this line appears:

 

     [10/24/2024 - 20:01:54] [info] Cache invalid, rebuilding (startup may take longer than usual)...

 

2. What is going on here?

 

    [10/24/2024 - 20:02:30] [info] Ready!
    [10/24/2024 - 20:04:14] [warning] Ref ID from co-save is not valid. Empty handle will be used.
    [10/24/2024 - 20:04:14] [warning] Ref ID from co-save is not valid. Empty handle will be used.
    [10/24/2024 - 20:04:14] [warning] Ref ID from co-save is not valid. Empty handle will be used.
    [10/24/2024 - 20:04:14] [info] Finished deserialization in 0.747ms   

 

NAF.log 19.99 kB · 0 downloads

 

Some reference is invalid. Idk reason, need to search in code what is it about. I dont think this is critical.

 

upd. I guess it can be provided by changing load order. NAF lost pointers to some objects. Not seems as something critical. I guess it should reparse archive. Try to clear NAF archive, then start new game and see if it will be there or not. And also try to clear and see on existing save.

Also probably hotreload from NAF UI can fix it.

 

Can try ask Snapdragon, I guess he remember in what cases this will show.

Edited October 24, 2024 by Evi1Panda

[Evi1Panda]

Forgot to answer for the first part... I will answer later, when I'll look at code. I guess it can provided by some fixes like ghoul heads fix, that must been applied everytime game loads... But also probably it is just update archive, because you've been change some xml creation data. Anyway I don't think will be any troubles from there.

Edited October 24, 2024 by Evi1Panda