XCOM EU Is there a mod to zoom the camera out?

[NoLifeDGenerate]

What file did you modify? Did you bother to read the "Keybind Commands" article, especially where it cautions you:

 

Also bear in mind that if you have any DLCs installed, copies of various "default" INI files are made in the My Games folder tree, but begin with "XCom" instead of "Default" (as in XComInput.ini instead of DefaultInput.ini). While they normally are updated automatically when you change the "Default" versions, you may need to update these files manually as well if your key bindings don't seem to "take".

 

 

That article has a number of details you need to pay attention to. The DIY article never covers those details, which is why it links to the pertinent key article.

 

I need more detail on what you did (as opposed to what you were instructed to do) to be able to see if you misinterpreted anything. For instance, were you trying to do this for EU or EW? What patch level are you on?

 

-Dubious-

 

I tried putting that s*** in both the config files for EU in the tacticalinput section as the page shows. No effect. I'm using whatever the current version is straight from Steam. Why the hell would anyone use anything less?

Edited October 5, 2016 by NoLifeDGenerate

[dubiousintent]

Please recall that I can't see what you are looking at. I can only go by what you tell me, and saying things like "I tried putting that s*** in both the config files for EU in the tacticalinput section as the page shows" doesn't tell me if you edited the "<Steam install path>\XCom-Enemy-Unknown\XComGame\Config\DefaultInput.ini" and the "XCOMInput.ini" one in <My Games path>\XCOM folder as well, or if you went strictly by the instructions which were written for EW and used the "\XEW" path. (People willing to DIY are assumed to have some familiarity with the differences between versions, and to have read the "Basic Guide".) I assume you have tried to follow instructions, but as something is wrong the most likely cause is a misinterpretation of those instructions. Which in turn means I have to pin down exact details, such as the path and filenames that were edited. Once I know you edited the correct files, then I have to look at exactly what you put into them to see if there is a typo or something. It's a "step-by-step" process of elimination.

 

As to "Why the hell would anyone use anything less" [than the latest version], it would be because some mods (such as the last version of "Long War" for EU) will only work with an older patched version. I try not to make unwarranted assumptions, and determining patch version in use is a pretty standard question with XCOM. Which is why we put instructions on how to determine it in the "Basic Guide".

 

-Dubious-

[NoLifeDGenerate]

I edited the right INIs for EU. I copied the pitch control thing exactly.

 

in the My games...XcomInput.ini under XComGame.XComTacticalInput

 

Bindings=(Name="Pitch1",Command="setoverheadcameraparameters 90 1000 -90 | SetBind F2 Pitch2")
Bindings=(Name="Pitch2",Command="setoverheadcameraparameters 90 1000 -45 | SetBind F2 Pitch3")
Bindings=(Name="Pitch3",Command="setoverheadcameraparameters 90 1000 -30 | SetBind F2 Pitch4")
Bindings=(Name="Pitch4",Command="setoverheadcameraparameters 90 1000 -5 | SetBind F2 Pitch1")
Bindings=(Name="F2" Command="Pitch1")

[dubiousintent]

Fine, but did you also define it in "<Steam install path>\XCom-Enemy-Unknown\XComGame\Config\DefaultInput.ini"?

 

Oops. Just realized I never asked if you have Steam/XCom installed to the default "C:\Program Files" folder tree? If you do, please read the article "Installing Games on Windows Vista+" in my signature and move it. The anti-malware protections on that folder tree will prevent the game from seeing any edits you make to files under the XCom folder. This is an essential "fix" for XCom mods.

 

Do you have <F2> defined elsewhere to do anything else? Have your tried binding to a different key? For a list of valid keys and gamepad buttons that can be bound, see UDN Three - Key Binds article. This also include descriptions and other examples of features such as key bind aliasing, chaining, the onrelease modifier, use of variables, toggles, and binding functions.

 

Just to be clear: That section of key bindings code is defining a "name" of "pitch1" which sets the overhead camera command to look straight down, and then adds the compound command ( | ) that rebinds key <F2> to the name of "pitch2".

The name "pitch2" is similarly defined to a different camera angle, and rebinds key <F2> to "pitch3". And so forth thru "pitch4" and then back to "pitch1".

The last line names the <F2> key (using it's alias string) to the command name "pitch1". So each time you tap key <F2> it will rotate thru the camera pitches.

Lower lines in the file override earlier ones with the same name.

 

Be sure you are using the "vertical" double quotation marks and not the "angled" ones available on some keyboards. It's looks like they are correct in your post, but the forum editor can make substitutions unknown to us.

 

The only other thing would be to show me the entire "[XComGame.XComTacticalInput]" section to make sure you don't have something else in there that could be causing a problem.

 

Finally you can test the "command" portion of the keybind statement in the "Developer Console". This should not be needed for keybinding to work, but is a way to test the camera command is working.

 

-Dubious-

Edited October 6, 2016 by dubiousintent

[NoLifeDGenerate]

Yeah, both INI files. I thought I said that. They're clean files from a clean install, and no the game isn't on C:. I haven't defined anything else.

[dubiousintent]

Then I'm stumped. It should work. Try the command on the Console command line. If it doesn't work then, there is something wrong with the install and you should try "verifying local files" and run through the "Basic Guide" checklist.

 

-Dubious-