Hey, Creeper. I've been taking a look at your bindings and at the ME Wiki page on editing ME2's Coalesced.ini, and I'd like put my chosen bindings into [SFXGame.SFXGameModeBase] for taking screenshots as this apparently makes them work in ALL game modes - conversations, cinematics, etc. - rather than just the "Default" where the player is controlling Shepard.
I've been tinkering about and I'm guessing I need to change the InputMode=BIO_INPUT_MODE_NONE part of your listed binding to somehow target SFXGameModeBase, but I've been fiddling about with this for over an hour now and I'm not getting anywhere. They always seem to end up in SFXGameModeDefault. I'd be hugely grateful if you could please enlighten me and save me a lot more guesswork, so I can spend more time making cool screenshots! Thankyou :)
Each control type has its own binding list. You can see all of them clearly in original Coalsced. One of the reasons why I wouldn't recommend using ini editors. Editing it in Notepad gives you far better control and easiness of usage. Just paste your bindings under different header, that's all. Headers are placed in [SquareBrackets]. Use N++ to edit the file. Don't forget to run ME2INIFixer afterwards!
The ini editor interface looks nothing like the one in the description page. When I open the program and then go where? Can you provide more detailed instruction please? Thank you for the good work you've done for ME community!!
Is there a way to move the 'camera' slower? It's probably user error, but I'm using the WASD keys and I'm having a difficult time zooming in without overshooting my mark. Any tips would be greatly appreciated!
Unfortunately that's the one downside I couldn't fix. I recommend strafing to get to the point you want to screenshot. I made a fancy tutorial to help :
As addition to what Creeper said, here's one thing that I used myself to some degree: You can change your FOV to make scene looking a bit closer or further from the camera. It's not perfect, but works. Use console command FOV int. Default FOV in free came is 60. Changing FOV with this command will alter all FOVs - that means, running, aiming, combat, they all will change to given FOV. Use FOV 0 after you've done to reset it to default for them all.
You can also try toggledebugcamera - it's much slower than normal one (I'd even say, painfully slow), but comes with special GUI that you can't get rid of, so it might be bad for cinematic screenshots. Unfortunately you can't use both normal and debug cam - enabling normal cam while being in debug does nothing. Enabling debug while being in normal will swap entirely to debug one, and if you then disable debug, camera position comes back to where you left it in normal cam.
Hmmm maybe I just entered the keybindings wrong (although I made sure it looked like it does in the screenshot in the description) but when I hit G it enters fly cam no problem. However, I tried hitting H (and on another try G again) to try to go back to normal and it did a weird thing. When hitting the 2nd key to leave the fly cam, it very slowly crawls back to Shepard. Like really slow. Then it'll stop where it normally would for 3rd person. But then I can't move Shepard, only the camera via the mouse like I'm still in 3rd person. Hitting G again to go into fly cam works fine though. However the only way to fix this it seems is reloading a save. Not sure if I did something wrong though :/
EDIT: after some messing around it was because H was bound to my holster function by the default game ahaha that's my fault. I just went into the coalesced editor again and changed the G/H for the fly cam to O/P instead!!
Hi! Nice idea, but here are few things from my own experience:
ToggleHUD lefts power bar and many GUIs visible. You can use Show Scaleform instead - it works as toggle and hides everything except selectors. You can toggle selectors by using Show Lensflares. It hides lens flares from sun as well.
Another very useful command that I used when making SS for my mod is Tiledshot int1 int2, which allows you to make screenshots in higher resolution than your own monitor. int1 - how many times screenshot's width and height will be bigger than actual game resolution. Eg. value "3" will make a 3840x2160 photo from 1280x720 resolution. int2 - don't know exactly, but you have to set about 2.5 times less value than game height, or you'll have weird shadows in whole image. General note: You need to disable whole HUD (by Show Scaleform) before using it. Screenshots will be saved in *.BMP format in C:\Users\%USERNAME%\Documents\BioWare\Mass Effect 2\BIOGame\Screenshots and named Highres_Screenshot_00000(number). I then compress them to PNG with Photoshop. If file is too big for Nexus (they have 8MB limit per photo) I choose JPG with max quality instead. I'm really surprised how well such file looks. You can't make photos with GUI with this method. When I needed to do one, I just increased my screen resolution with Nvidia Control Panel.
Slomo 0 doesn't really freeze the time. It only makes everything about 100 times slower. You need to use PlayersOnly instead. Works as toggle.
When making screenshots in combat, I always use God command, so I won't be killed mid-work.
This is great information, thank you ! - What if you use togglehud with show scaleform ? I'd prefer leaving the lens flares as they are. - Good info on the tiledshots. I have a 4K monitor (what I used for the AL0T screenshots), but I'll add this for others. - I know about playersonly, however I prefer how slomo doesn't fully freeze time. It's annoying to have to keep freezing/unfreezing to advance a little in time imo. I'll also add a note about it.
ToggleHUD and Show Scaleform doesn't cancel each other, but looks like hiding takes priority. If you used ToggleHUD, then using Show Scaleform will hide everything that ToggleHUD didn't, but if you then use ToggleHUD again, its hides won't be revoked.
Well, now you can take 8K photos :P
You know, personally, I use both Slomo 0 and Playersonly under different keys, so I can take moments with incredible accuracy.
22 comments
I've been tinkering about and I'm guessing I need to change the InputMode=BIO_INPUT_MODE_NONE part of your listed binding to somehow target SFXGameModeBase, but I've been fiddling about with this for over an hour now and I'm not getting anywhere. They always seem to end up in SFXGameModeDefault. I'd be hugely grateful if you could please enlighten me and save me a lot more guesswork, so I can spend more time making cool screenshots! Thankyou :)
Just paste your bindings under different header, that's all. Headers are placed in [SquareBrackets]. Use N++ to edit the file. Don't forget to run ME2INIFixer afterwards!
It looks like this. I downloaded it from the link in the description which is https://www.nexusmods.com/masseffect2/mods/197
Great mod! (this and your work on a lot!)
You can change your FOV to make scene looking a bit closer or further from the camera. It's not perfect, but works.
Use console command FOV int. Default FOV in free came is 60. Changing FOV with this command will alter all FOVs - that means, running, aiming, combat, they all will change to given FOV. Use FOV 0 after you've done to reset it to default for them all.
You can also try toggledebugcamera - it's much slower than normal one (I'd even say, painfully slow), but comes with special GUI that you can't get rid of, so it might be bad for cinematic screenshots.
Unfortunately you can't use both normal and debug cam - enabling normal cam while being in debug does nothing. Enabling debug while being in normal will swap entirely to debug one, and if you then disable debug, camera position comes back to where you left it in normal cam.
And of course, grat work, and thanks for sharing this mod with us
EDIT: after some messing around it was because H was bound to my holster function by the default game ahaha that's my fault. I just went into the coalesced editor again and changed the G/H for the fly cam to O/P instead!!
ToggleHUD lefts power bar and many GUIs visible. You can use Show Scaleform instead - it works as toggle and hides everything except selectors.
You can toggle selectors by using Show Lensflares. It hides lens flares from sun as well.
Another very useful command that I used when making SS for my mod is Tiledshot int1 int2, which allows you to make screenshots in higher resolution than your own monitor.
int1 - how many times screenshot's width and height will be bigger than actual game resolution. Eg. value "3" will make a 3840x2160 photo from 1280x720 resolution.
int2 - don't know exactly, but you have to set about 2.5 times less value than game height, or you'll have weird shadows in whole image.
General note: You need to disable whole HUD (by Show Scaleform) before using it. Screenshots will be saved in *.BMP format in C:\Users\%USERNAME%\Documents\BioWare\Mass Effect 2\BIOGame\Screenshots and named Highres_Screenshot_00000(number). I then compress them to PNG with Photoshop. If file is too big for Nexus (they have 8MB limit per photo) I choose JPG with max quality instead. I'm really surprised how well such file looks.
You can't make photos with GUI with this method. When I needed to do one, I just increased my screen resolution with Nvidia Control Panel.
Slomo 0 doesn't really freeze the time. It only makes everything about 100 times slower. You need to use PlayersOnly instead. Works as toggle.
When making screenshots in combat, I always use God command, so I won't be killed mid-work.
These commands should work in ME3 as well.
Good luck with all :)
- What if you use togglehud with show scaleform ? I'd prefer leaving the lens flares as they are.
- Good info on the tiledshots. I have a 4K monitor (what I used for the AL0T screenshots), but I'll add this for others.
- I know about playersonly, however I prefer how slomo doesn't fully freeze time. It's annoying to have to keep freezing/unfreezing to advance a little in time imo. I'll also add a note about it.
Well, now you can take 8K photos :P
You know, personally, I use both Slomo 0 and Playersonly under different keys, so I can take moments with incredible accuracy.
Also, 8K screenshots in BMP format ? My hard drive will die :D.
I would make screenshots for AL0T, but I'm pretty sure my 11 years old PC with 4GB RAM and 512 MB VRAM won't even run it.