Fly (free) Camera and settings ?

[Guest]

Hello,

I have noticed two parameters in the settings.ini file of AAF which control the speed of the free camera. But I did not find any easy or automatic way to toggle the free camera when AAF starts an animation. (AAF works fine, animations laod and play nicely but my camera remains stuck, only able to rotate using the mouse).

 

So my question is: is it normal ? Using the console command "tfc" is the only way to use free camera while an animation is played ?

 

Thanks for any advice.

[Indarello]

1 hour ago, LipoCH said:

Hello,

I have noticed two parameters in the settings.ini file of AAF which control the speed of the free camera. But I did not find any easy or automatic way to toggle the free camera when AAF starts an animation. (AAF works fine, animations laod and play nicely but my camera remains stuck, only able to rotate using the mouse).

 

So my question is: is it normal ? Using the console command "tfc" is the only way to use free camera while an animation is played ?

 

Thanks for any advice.

No, when you run aaf scene on player you will have free camera

[Amwatt]

I'm also having this problem. Everything is working except the camera, very strange. 

[Guest]

21 hours ago, Indarello said:

No, when you run aaf scene on player you will have free camera

 

Strange then. I suppose something went wrong during installation (though I followed the steps in the dedicated thread and did not see any other errors or bugs using AAF. One thing though, I have a few errors logs in the Admin tab of AAF, but apparently ones I could ignore (animations timing too short so AAF will set the timing to the minimum one).

[jelloman]

I've been having this problem for a very long time now.  During that time I went through several game re-installs, change of mod manager (NMM -> MO2), different mod setups and different AAF versions. And everytime the same thing happens - everything works fine except the fly cam, I can rotate it around but not move. The only thing left to try is change of OS - I have dual win7/win10 system, maybe it doesn't like win7, I dunno.

[jelloman]

I feel such an idiot now, apparently my problem was using cursor keys for movement instead of WASD, and those are used for AAF control, so I had a conflict, duh.

[Guest]

49 minutes ago, jelloman said:

I feel such an idiot now, apparently my problem was using cursor keys for movement instead of WASD, and those are used for AAF control, so I had a conflict, duh.

 

I also have set up my arrow keys for the character movement. So in order to avoid conflict, I remapped AAF direction keys with AWSD in the setting.ini (works well in the AAF menus for instance). But even that did not help for the free camera. But you might be correct about the source of the issue.

[jelloman]

Yeah, I tried remapping too. Even if I have WASD for both AAF and my movement I can still use camera and setup AAF scene so there is no hard conflict. Probably meaning that arrow keys are hard locked from being used for anything else but their default function. Pitty, I hope dagobaking can do something to fix this.

[Guest]

SOLVED

 

1. Yes, the issue is because I mapped my arrow keys in Fallout 4 options. (such a lame crime, isn't it ?)

2. To solve this and keep using arrow keys WHILE enabling free camera control, I used a "Autohotkey" script to remap my arrow keys to ASWD and also reset control keys to default in Fallout 4 options.

 

Et voilà.

[jelloman]

Didn't know about the AH, thanks. After some trial, error and googling I've ended up with this:

#SingleInstance, Force

#If WinActive("ahk_exe Fallout4.EXE")
Up::w
Down::s
Left::a
Right::d
#if

Is this what you had in mind?

Edit:

my final script result:

Spoiler

#SingleInstance, Force

#If WinActive("ahk_exe Fallout4.EXE")
~`::
ToggleKeys := !ToggleKeys
Return

#If !ToggleKeys && WinActive("ahk_exe Fallout4.EXE")
Up::w
Down::s
Left::a
Right::d
w::Up
s::Down
a::Left
d::Right
#if

 

This way I can have separate keys for movement and workshop navigation and have functioning console.

[padezaw]

hi,

 

I have a problem that is a bit strange. When I enter an AAF scrne the fly camera does not start automatically as mentioned by Indarello.

 

When I am in an AAF scene I can do tfc in console but when I try tp move the camera the scene moves as well.

Say the scene is of Marcy then I do tfc and move camera towards Marcy but when the camera gets to a certain distance, the scene

(Marcy) slides away from the cam. The screne continues playing.

 

What it does is if I am not careful Marcy can end up outside a room.

Can anyone help?

 

 

[supersaiyangoku1944]

this fixed my problem thank you , i remapped my keys back to wasd for the sex scenes and my camera works perfectly now , i appreciate this forum i been looking for a fix for that for months now , i installed this i found below where it forces you into 3rd person view during sex scenes and then remapped my keys back to wasd and works great thanks guys hope this helps yall as well , just copy and paste those into your data folder and overwrite  its for version 1.10.63 it forces the camera  to flycam auto also  but if not just use tfc and itll work for you 

LLFP-v41-20210601.7z

[dr_rsc]

Tried these solutions but none worked. As far as I could tell the LL_FourPlay.psc was identical to the original. Haven't looked into if or how the ll_fourPlay_1_10_163.dll was different or not. The problem, for me, remains the same. The left and right mouse (or trackball) buttons move the camera up and down only. Going from 1st to 3rd person perspective does not seem to change anything and the camera remains fixed on the backside of whatever is doing the deed. TFC does nothing either. It is really too bad as Fall Out 4 would be an interesting game with these specialized mods available. It is really too bad, but this camera problem was likely why the Four-Play system fizzled out. If something doesn't work, most people will just move on and not bother with trying to fix it.