0 of 0

File information

Last updated

Original upload

Created by

me smileyface

Uploaded by

mkhihi

Virus scan

Safe to use

8 comments

  1. atdhehypnedhe
    atdhehypnedhe
    • premium
    • 0 kudos
    Doesnt work at all crashes the Frosty mod manager as soon as you load the mod and try to run the game
    1. Valorin
      Valorin
      • member
      • 4 kudos
      Same here. So far with every mod that comes without an archive file. 
      Any ideas?
    2. MasterAcer
      MasterAcer
      • premium
      • 0 kudos
      Used Frosty Mod Manager 1.0.6.0 (Alpha 5)
      Had to unzip and select the .fbmod file when adding the mod 

      Worked perfectly.
  2. MasterAcer
    MasterAcer
    • premium
    • 0 kudos
    Used Frosty Mod Manager 1.0.6.0 (Alpha 5)
    Had to unzip and select the .fbmod file when adding the mod 

    Worked perfectly. The only solution to the atrocity that is the different x and y sensitivity, that I've found so far. Thanks.
  3. wetom67
    wetom67
    • member
    • 0 kudos
    Okay I can confirm that there is a difference. Y axis has different coef. Even x axis has different coef for a scanner camera.
  4. wetom67
    wetom67
    • member
    • 0 kudos
    Why do you think there is a difference between X and Y axis? I don't feel it.
  5. kevikev
    kevikev
    • supporter
    • 5 kudos
    According to Frosty Mod Manager, this conflicts with the UltimateCombatCameraFOV.

    I don't know if I can use both or not; only started modding MEA today.
    1. mkhihi
      mkhihi
      • member
      • 0 kudos
      Couldn't get them to work together so I made an optional file with some camera adjustments for combat. I really like the "Camera Mod - FOV (Field of View) and Camera Position Adjustments" shame that it wasn't easy to pair them. I don't know if I could clean up the excess off so it would only apply the one setting per camera profile. Just started modding.

      "Game/Cameras/Rigs/" contains the camera profiles that change according to what you do in game.

      ContactCamera.InputControllerData/Strategies/0/PitchAxisInputData/Speedratio "1". For the sensitivity.
      Yaw is mostly already set to 1 but pitch is out of wack in every "profile" (PlayerCombatCameraRig, PlayerAimCameraRig, PlayerAimSniperCameraRig, playerjumpaimcamerarig..etc). 

      The field of view side of things seems to take a lot of work to get it unified and seamless.