Game (cams) STUCK at being tilted at 45-degrees.

So I bought the game on Steam: ran it an hour or so, and gave it a great review: BUT I started the game today, and the camera is persistently stuck at 45-degrees to the right. Like permanently having your right ear resting towards your right shoulder. I cant drive like that.
WHY did it happen (after a recent update)?
HOW do I fix it?
IF I caused it; How did I cause it (e.g. How can I prevent it)?
My other 550 games I have installed do not have this problem.
Rig is...
Haswell i7
GTX780
16Gb Ram
Windows 10 (x64) on SSD
Platinum PSU
Games on WD Black Hard Drives.

I dont recall messing with anything in any part of the file.

I already verified the Integrity of the game Cache.
That did not work.
I put it all to Stock settings.
That did not work.
I COMPLETELY Uninstalled the game (and the part in Documents [the settings?]). Re-booted.
Fully installed the 11+?Gb game again.
Booted it up and the game is STILL STUCK AT 45-degrees to the right.

Is it some Steam Chimp Mod who is messing with my Game?
Or is there a fix I have overlooked?

EDIT
7 hours after the problem was discovered.... (While XBox One controller is being used....)
Turns out that the problem may be that my Thrustmaster Warthog Flight kit my spouse just bought me, has to remain being plugged in to USB3.0 also (as I dont want to crawl around on the floor every time I change a PC game [or its controls]), and In SETTINGS of the Game, I turned off "Steering wheel" and at first it worked. But on re-booting the game, the head angel went to the left.
So; Devs: there is a link between a head angle and a Joystick/Throttle/Pedals combo and your game (and Steering Wheel code) if you have an XBox One controller plugged in.

I also tried a BETA option; but no luck there.

EDIT 2.
May or may not be linked to Steam "CONTROLLER COMPANION" which automatically runs on my system. Will test now..............
Dayn; The Angle of the head is better; but the controls are all shot.
Its now IMPOSSIBLE to SET UP the Controls on the XBox controller in Game; as EVERY SINGLE Input reverts to "Joy3 B20". I cannot change any Input anymore due to this conflict.
Every command changed goes to "Joy3 B20" and to "EMPTY" when I go to map the next button.

I guess that for now, I will have to crawl around under my desk and remove my Joystick USB Plugs from the USB device, and plug them in again every time I stop playing this game only.

Hopefully it will get fixed on day. But I am also sad that Thrustmaster did not put an On/Off Switch on each of the Flight Controllers.

 

Hello, thanks for the feedback.

If any controller is active, plugged in on usb ports, this could cause a problem while mapping. Have you set your inputs to a neutral point on your flight controller when trying to map your joypad / keyboard? This could happen to any other game as well.

Probably, the head rotation (camera) problem was caused by having some input of your flight controller active. Not sure what, to be honest. But probably there is something that the mapping that you were on using on AMS is binding to any input (digital or axis) that was active at the moment.

Maybe you had played any of your flight simulators after trying AMS for the first time and forgot to left your inputs on that controller neutral?

 

You`re correct about the binding issue.
N.B. I usually race using an XBox One controller; unless I am at a different F/F-Wheel-Gaming-Rig I have (not always convenient due to it being in the big-Tv room).

That said; most of my 500+ Steam/Origin/UPlay/Etc games have ZERO problem with leaving them plugged in (although I mostly use fps games). HOWEVER NFS Most Wanted has the Same issue as this game (unable to map with Warthog left plugged in). Thats how I realised it was some non-standard code the (similar?) `game engine` associates to, in mapping (otherwise all games would have difficulties). I also noticed that in NFS that that game does not even `see` the XBox One controller in Game Settings, because the HOTAS Warthog setup & Combat Flight Pedals are "in the way" (higher up the USB ladder [kicking the controller entirely off the game; but the Automobilista settings are approached differently]).
HOPEFULLY ONE DAY HARDWARE/CONTROLLERS CAN HAVE A "CODE" (they have an ID) WHERE A SPECIFIC TYPE OF GAME LINKS TO A SPECIFIC TYPE OF HARDWARE FIRST. Flight sims link to a HOTAS USB first or a Driving game to a Wheel then XBox controller-type 2nd [etc])
Thats a hint for someone to make money.

So, I do have to crawl around under my desk everytime and unplug devices I want to play this or NFS Most Wanted; unless its easily fixable (or I could by a bunch of USB extenders [and physically do it that way each time [but there are issues to do with HOTAS Windows Mapping `priority` each time you unplug them in and out of USB]).
No problems with dozens of other race games I have.
I rpt: "Darn Thrustmaster (and Saitek) for not putting an on/off switch on the Flight controllers."

 

I do understand your situation. When i'm on my free time and not simracing, some games often recognize my pedals as axis, even though the game is on default settings, and the pedals are in neutral positions. So i have to unplug my wheel from the usb to configure my joypad as well.
Anyway, sorry i can't be of more help than that at this moment.