• Hey, guest user. Hope you're enjoying NeoGAF! Have you considered registering for an account? Come join us and add your take to the daily discourse.

The NeoGAF Screenshotter's Compendium Thread

Anteater

Member
Anyone know which sweetfx I could use for max payne 3? I tried the newest one (1.51) and the settings just make the screen dark, 1.4 works but it slows my game down by about 15fps (it also slows everything down when I alt tab), and I think it leaves another instance running in the background when I quit the game which might be what contributes to the stuttering.

Edit: guess it's a dx11 thing, works in dx9
 

Leks

Member
Time of day control
Still uses the same CE table. There are 2 scripts and only 1 can be active at a time. It helps if you have the table open on a 2nd monitor so you can keep track of what's active.

F6 - Enable time of day control (this is what most people will want)
Use [ ] keys to change the time of day

F7 - enable sun position control (turning this on disables time of day)
Use [ ] keys to change sun position (useful for changing the direction of shadows)

Can we also change the weather with these scripts?

Thank you for this table by the way, I've quickly tested it today and this is what the game needed for bullshoting.
 

One3rd

Member
These commands work with both Escape from Butchers Bay & Assault on Dark Athena.

Developer Menu

To bring up the developer menu press "Ctrl + Alt + ~". Once up you can input the below commands.

Code:
cl_toggleshowhud  -- toggles the hud.
cmd(godmode)  -- you never die.
cmd(noclip)  -- free camera.
cmd(giveall)  -- give all weapons. This will only provide weapons available on this level.
cmd(selfsummon)  -- spawn a Riddick...or two or three.
cmd(cyclecamera)  -- cycles camera between 1st and 3rd person.
cmd(unlockall)  -- unlocks all Butchers Bay extra content...this didn't work for me.  
vid_blacklevel 0  -- sets to true black.
vid_gamma 0  -- disables gamma...also available in the games menu options.
xr_ssao 3  -- enables ambient occlusion (1-3).


FOV and DoF


I couldn't find a way to change the FOV and it is set pretty high for proper screenshots. One way around this was to use the weapon zoom while in noclip mode (as the weapon is removed from view). This also adds a DoF blur that is set the focal point of where the crosshair is, this can be a pain if you want to focus on something close up and also have a narrow FOV. One solution is to also bring up the weapon radial menu (Z key) while zoomed in, this changes the focus to very near to the camera. If you don't have a gun yet, use the giveall command to provide one, if you have this selected before going into noclip you will be able to use it to interact with the world.

There is also another "fixed" DoF blur that switches on when flying close to some objects or NPC's using noclip. You can enabled it by flying through NPC's or sometimes through the walls. I found that disabling noclip and then reenabling it also resets the DoF.


SSAO

For some reason the SSAO option in the menu does not seem to be able to be enabled at the same time as AA. One way around this is to use the xr_ssao 3 command in the console. This may need to be reapplied whenever video settings are changed, including blacklevel.


Below are some example shots using the above methods.
11641599135_50ee4d8a3b_o.jpg

11641979944_f577f1cf1f_o.jpg


DRM

It should be noted that the original release of this had the Tages copy protection system which can cause problems unless you have the latest Tages drivers installed. If, like me, you find that the game does not work at first, download and install the latest drivers direct from the Tages website.

There are some non-DRM versions available, GOG is one website that I'm aware of that offers this.
 
Free camera, timestop, slow motion, time of day

I get asked this often enough. Here's the table I'm using for Borderlands 2. This cheat engine table is a combination of various community efforts, including my own. It's my hotkey setup though... so if you don't like it, I suggest you familiarize yourself with changing hotkeys in Cheat Engine :)

Borderlands 2.ct

When you open it, you'll see the main script [Enable]. Check that to expand the table.

Inside you'll see a group called "[screenshotting]." This is where I keep everything useful for screenshots.

[Unreal Engine Cheats]
Enable this script for playersonly (numpad 1), fly (numpad 2), ghost (numpad 3), and god mode (numpad 7)

[Day\Night Time and Scale]
Enable this to gain control over the time of day. This is only available on maps where the time of day progresses naturally. Use numpad add and subtract to change. Hold CTRL to move it more.

[FreeCam v4.0]
The free camera. F5 toggles between 3rd person, free camera, fixed camera, and 1st person. I bound numpad 5 to toggle this on and off. The reason is because if you use the free camera on 1 map and then go to another map, the free camera will still be where you left it. Toggling the script on\off allows it to reset to your current position.

Some keys I added while in free camera mode:
Press O to move the camera really fast
Press P to move the camera at the default speed (slow)
Page up - move the camera straight up
Page down - move the camera straight down

[Time Scale Multiplier]
Slow motion. Number keys 7 (2% speed), 8 (10% speed), 9 (50% speed), 0 (normal speed)

[Visibility]
Press V to become invisible to enemies (they won't attack you). Press B to become visible again.

The rest of the table contains a butt-ton of Borderlands 2 hackery.

How to achieve depth of field
If you want this sort of effect:


Pick a weapon with iron sights. Zoom in to enable depth of field. Then use the free camera. You need to do that before enabling PlayersOnly as you'll not be able to zoom in once the game is frozen. While zooming, your FOV will be narrowed. If you set your zoom mode to toggle (options menu), you can use the console to set a larger FOV while zoomed).

The DOF looks nice but it is completely ruined by in-game FXAA. So disable that if you plan on taking shots with DoF. Otherwise, I find in-game FXAA helps smooth out the outlines a bit, so it's nice to have on. Especially if you can't afford a ton of SGSSAA.

Black outlines and downsampling

This game's outlines look a lot better (in my opinion) when you downsample from a high resolution. This is because they are rendered at the same thickness regardless of your resolution. So the downsampling process makes them smaller and therefore makes the game look cleaner. SGSSAA helps make the outlines smoother. In-game FXAA also helps.

Here you can see how the outlines look when downsampled from 5120x2160 (w/4x SGSSAA) to 2560x1080


I realize there is a way to completely disable the outlines in this game, but I think it completely ruins the art style.
 
Also, the OP has a link to the 2013 screenshot thread and bullshot thread. We might want to update or include the 2014 screenshot thread :)

I think bullshots have died :(
 

Thorgal

Member
Also, the OP has a link to the 2013 screenshot thread and bullshot thread. We might want to update or include the 2014 screenshot thread :)

I think bullshots have died :(

The screenshot thread absorbed that one .

There was never any rule that stated that the screenshot should be at a playable res.
only size restriction rules to not make peoples webpage expand to ridiculous sizes but that issue got solved with the face lift the site got re sizing pictures automatically .

Technically the bullshot thread died because there was no longer a reason for it to exist as all of it could be done in the screenshot thread .

That and personally. i find it better and convenient to have everything unified into one thread .
 
Technically the bullshot thread died because there was no longer a reason for it to exist as all of it could be done in the screenshot thread .
I don't disagree with any of that, really. I always saw the bullshot thread as more of a selective place to submit the best\well-composed screenshots. But the quality of the screenshot thread has gone up so much that I don't really think a separate thread is necessary.

I wasn't really serious about the sad face. I'm definitely more sad over Sethos getting himself banned and Neogaf missing out on his crazy high quality screenshots.
 

Spazznid

Member
I don't disagree with any of that, really. I always saw the bullshot thread as more of a selective place to submit the best\well-composed screenshots. But the quality of the screenshot thread has gone up so much that I don't really think a separate thread is necessary.

I wasn't really serious about the sad face. I'm definitely more sad over Sethos getting himself banned and Neogaf missing out on his crazy high quality screenshots.

I never found out, was it Perma?
 
Wanted to leave this here for archiving purposes.

While this cheat engine table could use some improvement, it's better than nothing. It's pretty similar to the DMC table except this is controlling only the camera.

Free Camera

Enslaved - camera coordinates table

Only works with PlayersOnly active (add that to the input config file) and probably won't work when the camera is fixed in some places. I also couldn't do anything about the vertical view angle limitations. Lastly, pointers are unreliable so it may not work 100% of the time.

Numpad 2 & 8 - Camera Y coordinate
Numpad 4 & 6 - Camera X coordinate
Numpad 3 & 9 - Camera Z coordinate

Here are a few screenshot examples courtesy of Midhras

 
So you're creating custom resolutions for downsampling and you have to use a low refresh rate to get your monitor to accept it. For example, you might have a 60hz montior but wind up successfully creating a resolution such as this:

11524640405_1796f311c8_o.png


(The refresh rate is too low for games to see that resolution. You'll need to do a couple things to make that 30hz resolution acceptable.)

1. Get the custom resolution utility (download, extract and run)
2. Make sure your active monitor is selected from the drop-down and then click the "add" button under "Detailed Resolutions."
3. Create another native resolution with the same refresh rate as your custom resolution (30 hz for this example).
4. Repeat for any other refresh rates you want to show up in-games. For reference, here's what my CRU looks like:

11811131114_23332e5011_o.png


Here are my custom resolutions:

11507036556_f469b68dc0_o.png


5. When you're finished, close CRU and restart your computer. When you're back in Windows, try to change your desktop resolution. If you can see your custom resolutions like this, you should be good.
 

GutsCrush3R

Neo Member
Well that dog just aint gonna hunt.
Meaning it won't worked when clicking on the test button? Or it won't be listed in the ingame resolution menu?

I have a Acer QD245HQ (1080p@120Hz) monitor. I can go up to 3840x2160@60Hz (maybe even a higher refresh rate is possible, I didn't try) without any trouble and without any manual settings ajustments. Yet I can't create anything higher than the 2160p custom res whatever the refresh rate I try. When I click on the test button I get the "Custom resolution is not supported by your display" error.

While I'm at it. Is there a special manipulation for 21:9 aspect ratio resolutions?
I tried a while back creating several 21:9 resolutions, none of them worked. I didn't have any pop up error. When I clicked on the test button, the screen would just became completely black for the test period until it switched back to native res. Just one of them gave me on the test period something like a 1920x15 pixels equivalent resolution.
 
Meaning it won't worked when clicking on the test button? Or it won't be listed in the ingame resolution menu?

I made a few edits to my post but that first screenshot is the resolution I ended up creating successfully. The point was to show that:

1. It tests and saves just fine
2. Games won't see it

Yet I can't create anything higher than the 2160p custom res whatever the refresh rate I try. When I click on the test button I get the "Custom resolution is not supported by your display" error.

Typically you can only create a maximum custom resolution that's 2x your native. I have a 2560x1440 monitor. I can not go a pixel higher than 5120x2880. I've seen a few folks claim to achieve resolutions a bit higher than that on a 1920x1080 monitor but it's very rare. 3840x2160 being your max is very normal.

While I'm at it. Is there a special manipulation for 21:9 aspect ratio resolutions?

Nothing special. Usually the same timings that work for a 16:9 resolution will work for a 21:9 resolution. For example, whatever I use for 5120x2880 will work for 5120x2160. What I use for 3840x2160 will work for 3840x1620. I can not say that it will work in every game. All monitors are different.
 
Hud Hide, Free Camera, Timestop, FOV, etc etc

To unlock the dev menu, download the following zip and extract the DLL contained into the game's install folder. You'll then have developer controls during gameplay and the dev menu when you press escape.

Dev Menu DLL

Controls:
F8 - high quality mode (toggles a larger view distance and higher details)
F9 - timestop
F10 - toggle HUD
Pause key - toggles on/off FreeCam
NumLock - slow motion (very useful for free camera)
Numeric / - accelerates game time
ScrollLock key - toggles 1st/3rd person views (3rd person animations are very janky)
+ and - keys (number row) - modify FOV
9 and 0 keys (number row) - tilt camera

Additional tweaks, fixes, etc

Dead Island Helper is also pretty useful for tweaking the game a bit more. Here are some things you can do with it:

* disable the game's dust effects
* disable the game's bloom shader (it's a little overdone)
* disable the game's desaturation shader (game becomes much more colorful)
* fix the micro-stuttering bug (I've never experienced this though)
* force a custom FOV (for gameplay. you can change this on the fly in freecam mode)
* enable overcast weather
 
ABSOLUTELY ESSENTIAL - DSFIX
You probably know what this is if you've ever thought about taking a screenshot of Dark Souls that doesn't look like mush.
DSFix can....
* Force a higher rendering resolution
* Enable SSAO
* Unlock 30 FPS limit
* Enable custom textures (find texture mods here)
* Toggle the HUD
* Pause the game (timestop)
* Make you beautiful and rich beyond your wildest dreams

Stop by the GAF thread for troubleshooting. Or just to pay homage to Durante.


Free Camera - Cheat Engine table for latest steam version
(FOR USE ONLY IN OFFLINE MODE, you cheating sad-sack)

1. Run the game. Get to the main menu.
2. Open the table and click "yes" when asked to run the LUA script (or click "no" and manually point to DATA.exe)
3. Click the box next to "DISABLE Xlive Cheat Detection" and wait for the X to appear (will take a second or two)
4. Click [Enable Main Table]
5. Go back to the game

Using the free camera:

Page up \ Page Down = Enable \ Disable
Numpad 8 and 2 = Increase \ Decrease Y coordinate
Numpad 6 and 4 = Increase \ Decrease X coordinate
Numpad 9 and 3 = Increase \ Decrease Z coordinate

Coordinates can be tricky since they're not based on where you're facing.
-> When the game is not paused, your character can run around. Camera rotation can be handled via joystick or mouse (yuck)
-> When the game is timestopped, you must use arrow keys to rotate the camera. You'll get used to it.

FOV
Numpad 0 = Enable FOV override
Numpad (+) and (-) = Increase \ Decrease

Other stuff
* The CE table is full of just about everything under the sun. To make things easier, you can enable a ton of different cheats.
* Expand [Hero's Stats] to modify.... your stats. You can give yourself a floppityjillion souls, too.
* Expand [Misc Stuff] to force Human state (change hollow visual to 0, hollow state to 1)
* You can change your bonfire location (where you spawn after you die) too. Find the values by enabling [Toggle Table Info Window]
* You can change your equipped items to anything in the game. To swap out gear, expand [Equipped Item values] and replace the Value for the slot you want replaced with the ID of the item you want. Here is a spreadsheet that has all the IDs of every piece of gear in the game.

There's a ton in there and I haven't seen\used it all. Look around. Experiment. Assign hotkeys to things you use more frequently.

Handy DSfix commands to make screenshotting easier
These are the hotkeys I use when playing\screenshotting DSfix. They go in DSfixKeys.ini
toggleAA VK_F2
toggleDofGauss VK_F3
toggleVSSAO VK_F4
reloadGAUSSEffect VK_F5
reloadSSAOEffect VK_F6
toggleBorderlessFullscreen VK_F8
togglePaused VK_F9
toggleCursorVisibility VK_F12
takeHudlessScreenshot VK_0
toggleHUD VK_RCONTROL

togglePaused - Pauses the game. You can stop the action and get a really neat, dynamic combat shot... or just explore a frozen word via freecam without fear of certain death.
toggleHUD - HUD toggle. Very complex, this feature. It toggles the HUD on and off.
reloadSSAOEffect - Turning this off during gameplay improves performance a TON. So I find it best to leave it off and enable it for screenshots. I'd love to have it on all the time but with a rendering resolution of 6400x3600...... yeah no.
toggleAA - If somehow SMAA actually impacts your performance at all, disable this for a few extra frames. But turn it back on for the mind-boggling difference SMAA makes. I can't make this any more sarcastic sounding so I'll leave it at that.
reloadGAUSSEffect - If you decide to play with the gauss shader in DSfix (see below), you can use this to reload your changes.


Playing with the gauss shader
Open "dsfix\GAUSS.fx"
What you want to tweak is
static const float sampleWeights[3]
static const float sampleOffsets[3]

sampleWeights determines the strength of the DoF and it's somehow connected with the ingame hdr power so when you raise the values you can get bright DoF.
sampleOffsets controls the DoF "spread" so when you raise the values you get more a blurry background.

You should raise them (all 3 values) minimally though so as to avoid overbights and artifacts. Also raise / lower them proportionally more or less, no need to be super precise.

Capturing screenshots with SweetFX in their original resolution
Example capture straight from SweetFX (converted to JPG)

This is tricky. Normally SweetFX captures screenshots at whatever resolution you set for presentWidth \ presentHeight. To capture the render resolution with SweetFX, you to set up your config files like such:

DSFix.ini
Code:
renderWidth 7680
renderHeight 4320

presentWidth 0
presentHeight 0

borderlessFullscreen 0
forceWindowed 1

DarkSouls.ini
Code:
[DisplaySetting]
WindowMode = 1
[DisplaySettingWindow]
Width = 7680
Height = 4320

Obviously you don't need to use the same resolution I am.

How to get fancy with aspect ratios
Crop your screenshots. This game hates you.
 

Alo81

Low Poly Gynecologist
You can change your bonfire location (where you spawn after you die) too. Find the values in the table info window.

Here's another interesting tip that might be useful for others.

You can set your bonfire to one of the boss locations that you haven't beaten. Then if you teleport into the boss area the boss will just stand there and not be hostile. It allows for interesting screenshot opportunities. (I've only tested this with Gwyn but I would think it would work for others as well.)

 
Here's another interesting tip that might be useful for others.

You can set your bonfire to one of the boss locations that you haven't beaten. Then if you teleport into the boss area the boss will just stand there and not be hostile. It allows for interesting screenshot opportunities. (I've only tested this with Gwyn but I would think it would work for others as well.)

You can also change your gear in Cheat Engine while the game is timestopped. So if you have a scene setup but you think another piece of gear would be more appropriate, you can open the item spreadsheet, find the ID of the item you want, and enter that in the value for the particular equipped item slot.

I'll add a link to the item spreadsheet above.
 
Yeah, btw, thanks a ton Neo!

Pfffft. If you want to thank people, thank...

Durante, for DSFIx and timestop
Technojacker (CE forums) for compiling all the various scripts from the community and combining them into a really slick table
Hell, Dark Byte for creating Cheat Engine, which ironically happens to be the best screenshotting tool in the world.

Kicking myself because I could have created this freecam when Durante first implemented his pause key... but I didn't really know about it until now.
 

Leks

Member
Help GAF! I'm playing Brothers: a Tale of Two Sons and Unreal Engine commands don't properly work. I first applied differents bindings (neoenigma and K-Putt), it worked fine but they no longer do, I don't know why. Then I set commands to other keys, without any success. No problem with the console, though it is annoying to type all commands, and tiledshot also takes the black screen.
I tried to set the .ini in "read only", without any changes. I even checked the cache integrity, deleted the Config file so the game creates a fresh one.

If I made a mistake, I don't know where. What should I do to fix this issue? Thanks for the answers, this game wonderful.
 

One3rd

Member
Help... Brothers: a Tale of Two Sons
Try the items mentioned in this post.

[Edit:]
Oh...you've already tried this. Make sure that you are adding the commands to the C:\Documents\My Games\UnrealEngine3\P13\Config\P13Input.ini file and that they are added under BOTH the [Engine.PlayerInput] and the [Engine.DebugCameraInput] sections in that file.

I don't think the game has recently been updated but I'll try booting it up and see if these binds are still working in my game as well.

[Edit 2:]

I just tried this and found that my old bindings had been removed from the ini file, I copied them back in and found that they all still work. I've uploaded the P13Input.ini file with these binds in here, you can either copy this over top of yours (backup first) or add the bindings yourself. See if this works for you.
 

Xavin

Neo Member
Do you guys have any tips on lumasharpening?
Im having troubles to see if a shot is oversharped or not.

Here are some examples using the lumasharpen in sweetfx with the clamp at default 0.035

Original
1.0
2.0
3.0
 

One3rd

Member
Do you guys have any tips on lumasharpening?
Im having troubles to see if a shot is oversharped or not.

Here are some examples using the lumasharpen in sweetfx with the clamp at default 0.035

Original
1.0
2.0
3.0

IMO, with lumasharpen, less is more. With the resolution you've used I like the 1.0 option in your examples.

Although, one thing I have learned about lumasharpen (other than it being very subjective) is that it is a double edged sword. Even when minimal amounts are used, at higher resolutions it can introduce or increase "banding" in your image when downsampling. These larger resolutions though, do negate the need for added sharpening, especially if you are going to be downsampling the image.
 

Xavin

Neo Member
IMO, with lumasharpen, less is more. With the resolution you've used I like the 1.0 option in your examples.

Although, one thing I have learned about lumasharpen (other than it being very subjective) is that it is a double edged sword. Even when minimal amounts are used, at higher resolutions it can introduce or increase "banding" in your image when downsampling. These larger resolutions though, do negate the need for added sharpening, especially if you are going to be downsampling the image.

I always setup in 1080p and just switched to 3200x1800 when im gonna snap the screenshot without thinking about the crisp downsampling adds.
Thank you for this info, i've learned alot today that will be very helpful :)
 

Leks

Member
I've uploaded the P13Input.ini file with these binds in here, you can either copy this over top of yours (backup first) or add the bindings yourself. See if this works for you.

It works now! Thanks for your help, I hope I won't meet any trouble again.
 

Xavin

Neo Member
FastStone doesn't seems to recognize my 19200x10800 images, they show as 1x1 images. Been trying to google but to no avail.
 

gunderic

Neo Member
Hey Neo! You may remember me, we were chatting on Flickr earlier about your Dark Souls screens. First off, I want to sincerely thank you for all your work with all these tables (I've used several of them but don't consider any of my screens to be worthy of posting here) ESPECIALLY this new Dark Souls table. It's really a dream come true and I can't wait to get in there and try my hand at it.

One question I have, though: I've got DSFix and the table running and they seem to be working fine EXCEPT when I press PageDown to disable the freecam my camera goes completely crazy, shaking around uncontrollably. Any ideas as to why that may be, what I may be doing wrong, or how it can be fixed?

Apologies if this isn't the appropriate place to post this question, I'm new to the forum.

Thanks!
-Gunderic
 
Can't think of a better place to ask that question. But I'm not sure why that might happen. Can't say I've experienced that myself and I haven't seen any other reports.

You can always try the table I just uploaded.

Page Down disables both the freecam script and the locked rotation script. Maybe one of them didn't get disabled properly. Try pressing Page Down a few times?
 

gunderic

Neo Member
OK, thanks! I'll try that.

What exactly should Locked Rotation do, by the way? Maybe this is also acting up, but I couldn't really notice a difference between it being enabled vs. disabled.
 
OK, thanks! I'll try that.

What exactly should Locked Rotation do, by the way? Maybe this is also acting up, but I couldn't really notice a difference between it being enabled vs. disabled.

Locked rotation is enabled automatically when you enable freecam. It's what allows you to rotate the camera during timestop.

Basically, the script locks down the rotation so the game no longer has control over it. This way Cheat Engine can take over. I don't know what else to call it. I'm terrible at naming shit.
 

One3rd

Member
Thanks to the DET Flickr group postings for most of the info on binds and methods used. I thought I'd compile them here for easy access.

UE3 Bindings

Go to \Documents\My Games\UnrealEngine3\RememberMeGame\Config\ExampleInput.ini and add the following bind under the [ExampleGame.ExamplePlayerInput] section.

Code:
Bindings=(Name="Add",Command="Pause",Control=False,Shift=False,Alt=False,bIgnoreCtrl=False,bIgnoreShift=False,bIgnoreAlt=False)
Bindings=(Name="Subtract",Command="PlayersOnly",Control=False,Shift=False,Alt=False,bIgnoreCtrl=False,bIgnoreShift=False,bIgnoreAlt=False)
Bindings=(Name="NumPadZero",Command="freecammode",Control=False,Shift=False,Alt=False,bIgnoreCtrl=False,bIgnoreShift=False,bIgnoreAlt=False)
Bindings=(Name="Decimal",Command="Ghost",Control=False,Shift=False,Alt=False,bIgnoreCtrl=False,bIgnoreShift=False,bIgnoreAlt=False)
Bindings=(Name="Decimal",Command="Walk",Control=False,Shift=False,Alt=True,bIgnoreCtrl=False,bIgnoreShift=False,bIgnoreAlt=False)
Bindings=(Name="Multiply",Command="Tiledshot 5 128",Control=False,Shift=False,Alt=False,bIgnoreCtrl=False,bIgnoreShift=False,bIgnoreAlt=False)
Bindings=(Name="Divide",Command="ToggleHUD",Control=False,Shift=False,Alt=False,bIgnoreCtrl=False,bIgnoreShift=False,bIgnoreAlt=False)
Bindings=(Name="Divide",Command="ShowHUD",Control=False,Shift=False,Alt=True,bIgnoreCtrl=False,bIgnoreShift=False,bIgnoreAlt=False)
Bindings=(Name="NumPadOne",Command="FOV 10",Control=False,Shift=False,Alt=False,bIgnoreCtrl=False,bIgnoreShift=False,bIgnoreAlt=False)
Bindings=(Name="NumPadTwo",Command="FOV 20",Control=False,Shift=False,Alt=False,bIgnoreCtrl=False,bIgnoreShift=False,bIgnoreAlt=False)
Bindings=(Name="NumPadThree",Command="FOV 30",Control=False,Shift=False,Alt=False,bIgnoreCtrl=False,bIgnoreShift=False,bIgnoreAlt=False)
Bindings=(Name="NumPadFour",Command="FOV 40",Control=False,Shift=False,Alt=False,bIgnoreCtrl=False,bIgnoreShift=False,bIgnoreAlt=False)
Bindings=(Name="NumPadFive",Command="FOV 50",Control=False,Shift=False,Alt=False,bIgnoreCtrl=False,bIgnoreShift=False,bIgnoreAlt=False)
Bindings=(Name="NumPadSix",Command="FOV 60",Control=False,Shift=False,Alt=False,bIgnoreCtrl=False,bIgnoreShift=False,bIgnoreAlt=False)
Bindings=(Name="NumPadSeven",Command="FOV 70",Control=False,Shift=False,Alt=False,bIgnoreCtrl=False,bIgnoreShift=False,bIgnoreAlt=False)
Bindings=(Name="NumPadEight",Command="FOV 75",Control=False,Shift=False,Alt=False,bIgnoreCtrl=False,bIgnoreShift=False,bIgnoreAlt=False)
Bindings=(Name="NumPadNine",Command="FOV 0",Control=False,Shift=False,Alt=False,bIgnoreCtrl=False,bIgnoreShift=False,bIgnoreAlt=False)
Bindings=(Name="N",Command="Slomo 0.3",Control=False,Shift=False,Alt=False,bIgnoreCtrl=False,bIgnoreShift=False,bIgnoreAlt=False)
Bindings=(Name="N",Command="Slomo 1.0",Control=False,Shift=False,Alt=True,bIgnoreCtrl=False,bIgnoreShift=False,bIgnoreAlt=False)
Bindings=(Name="M",Command="Slomo 0.1",Control=False,Shift=False,Alt=False,bIgnoreCtrl=False,bIgnoreShift=False,bIgnoreAlt=False)
Bindings=(Name="F1",Command="Slomo 0.3",Control=False,Shift=False,Alt=False,bIgnoreCtrl=False,bIgnoreShift=False,bIgnoreAlt=False)
Bindings=(Name="F1",Command="Slomo 1.0",Control=False,Shift=False,Alt=True,bIgnoreCtrl=False,bIgnoreShift=False,bIgnoreAlt=False)
Bindings=(Name="F2",Command="Peace",Control=False,Shift=False,Alt=False,bIgnoreCtrl=False,bIgnoreShift=False,bIgnoreAlt=False)
Bindings=(Name="F2",Command="War",Control=False,Shift=False,Alt=True,bIgnoreCtrl=False,bIgnoreShift=False,bIgnoreAlt=False)
Note: tiledshot does not work.


Remove Film Grain with TexMod

Thanks to JonasBeckman you can find the fix here.


Texture LOD Streaming

Similar to all (most?) UE3 games, you can stop the engine from changing the Texture LOD streaming by adding "NumStreamedMips=0" to the end of each TextureGroup setting. In the \Documents\My Games\UnrealEngine3\RememberMeGame\Config\ExampleEngine.ini file and under the [SystemSettings] section add this to each as below.

Code:
TEXTUREGROUP_World=(MinLODSize=1,MaxLODSize=1024,	LODBias=0,MinMagFilter=aniso,	MipFilter=point,	MipGenSettings=TMGS_Sharpen5,NumStreamedMips=0)
TEXTUREGROUP_WorldNormalMap=(MinLODSize=1,MaxLODSize=1024,	LODBias=0,MinMagFilter=aniso,	MipFilter=point,	MipGenSettings=TMGS_Sharpen0,NumStreamedMips=0)
TEXTUREGROUP_WorldSpecular=(MinLODSize=1,MaxLODSize=1024,	LODBias=0,MinMagFilter=linear,	MipFilter=point,	MipGenSettings=TMGS_Sharpen0,NumStreamedMips=0)
TEXTUREGROUP_Character=(MinLODSize=1,MaxLODSize=2048,	LODBias=0,MinMagFilter=aniso,	MipFilter=point,	MipGenSettings=TMGS_Sharpen5,NumStreamedMips=0)
TEXTUREGROUP_CharacterNormalMap=(MinLODSize=1,MaxLODSize=2048,	LODBias=0,MinMagFilter=aniso,	MipFilter=point,	MipGenSettings=TMGS_Sharpen0,NumStreamedMips=0)
TEXTUREGROUP_CharacterSpecular=(MinLODSize=1,MaxLODSize=2048,	LODBias=0,MinMagFilter=linear,	MipFilter=point,	MipGenSettings=TMGS_Sharpen0,NumStreamedMips=0)
TEXTUREGROUP_Weapon=(MinLODSize=1,MaxLODSize=1024,	LODBias=0,MinMagFilter=aniso,	MipFilter=point,	MipGenSettings=TMGS_Sharpen5,NumStreamedMips=0)
TEXTUREGROUP_WeaponNormalMap=(MinLODSize=1,MaxLODSize=1024,	LODBias=0,MinMagFilter=aniso,	MipFilter=point,	MipGenSettings=TMGS_Sharpen0,NumStreamedMips=0)
TEXTUREGROUP_WeaponSpecular=(MinLODSize=1,MaxLODSize=1024,	LODBias=0,MinMagFilter=linear,	MipFilter=point,	MipGenSettings=TMGS_Sharpen0,NumStreamedMips=0)
TEXTUREGROUP_Vehicle=(MinLODSize=1,MaxLODSize=1024,	LODBias=0,MinMagFilter=aniso,	MipFilter=point,	MipGenSettings=TMGS_Sharpen5,NumStreamedMips=0)
TEXTUREGROUP_VehicleNormalMap=(MinLODSize=1,MaxLODSize=1024,	LODBias=0,MinMagFilter=aniso,	MipFilter=point,	MipGenSettings=TMGS_Sharpen0,NumStreamedMips=0)
TEXTUREGROUP_VehicleSpecular=(MinLODSize=1,MaxLODSize=1024,	LODBias=0,MinMagFilter=linear,	MipFilter=point,	MipGenSettings=TMGS_Sharpen0,NumStreamedMips=0)
TEXTUREGROUP_Cinematic=(MinLODSize=1,MaxLODSize=4096,	LODBias=0,MinMagFilter=aniso,	MipFilter=point,	MipGenSettings=TMGS_Sharpen5,NumStreamedMips=0)
TEXTUREGROUP_Effects=(MinLODSize=1,MaxLODSize=512,	LODBias=0,MinMagFilter=linear,	MipFilter=point,	MipGenSettings=TMGS_Sharpen3,NumStreamedMips=0)
TEXTUREGROUP_EffectsNotFiltered=(MinLODSize=1,MaxLODSize=512,	LODBias=0,MinMagFilter=aniso,	MipFilter=point,	MipGenSettings=TMGS_Sharpen3,NumStreamedMips=0)
TEXTUREGROUP_Skybox=(MinLODSize=1,MaxLODSize=2048,	LODBias=0,MinMagFilter=linear,	MipFilter=point,	MipGenSettings=TMGS_NoMipmaps,NumStreamedMips=0)
TEXTUREGROUP_UI=(MinLODSize=1,MaxLODSize=2048,	LODBias=0,MinMagFilter=linear,	MipFilter=point);QLOC
TEXTUREGROUP_Lightmap=(MinLODSize=1,MaxLODSize=4096,	LODBias=0,MinMagFilter=aniso,	MipFilter=point,	MipGenSettings=TMGS_Sharpen1,NumStreamedMips=0)
TEXTUREGROUP_Shadowmap=(MinLODSize=1,MaxLODSize=4096,	LODBias=0,MinMagFilter=aniso,	MipFilter=point,	MipGenSettings=TMGS_Sharpen1,	NumStreamedMips=0)
TEXTUREGROUP_RenderTarget=(MinLODSize=1,MaxLODSize=4096,	LODBias=0,MinMagFilter=aniso,	MipFilter=point,NumStreamedMips=0)
TEXTUREGROUP_MobileFlattened=(MinLODSize=1,MaxLODSize=256,	LODBias=0,MinMagFilter=aniso,	MipFilter=point,NumStreamedMips=0)
TEXTUREGROUP_ProcBuilding_Face=(MinLODSize=1,MaxLODSize=1024,LODBias=0,MinMagFilter=aniso,MipFilter=point,NumStreamedMips=0)
TEXTUREGROUP_ProcBuilding_LightMap=(MinLODSize=1,MaxLODSize=256,LODBias=0,MinMagFilter=aniso,MipFilter=point,NumStreamedMips=0)
TEXTUREGROUP_Terrain_Heightmap=(MinLODSize=1,MaxLODSize=4096,LODBias=0,MinMagFilter=aniso,MipFilter=point,NumStreamedMips=0)
TEXTUREGROUP_Terrain_Weightmap=(MinLODSize=1,MaxLODSize=4096,LODBias=0,MinMagFilter=aniso,MipFilter=point,NumStreamedMips=0)
TEXTUREGROUP_ImageBasedReflection=(MinLODSize=256,MaxLODSize=4096,LODBias=0,MinMagFilter=aniso,MipFilter=linear,MipGenSettings=TMGS_Blur5,NumStreamedMips=0)
TEXTUREGROUP_Bokeh=(MinLODSize=1,MaxLODSize=256,LODBias=0,MinMagFilter=linear,MipFilter=linear,NumStreamedMips=0)


Methods for camera movement / placement

jim2point0 says:
Duncan explained to me how this works. But for the life of me, I can't get the same results he does. I'll try my best to relay my own experiences....

Ghost is no-clip, as you know. It goes REALLY fast. Hold CTRL (walk key) + movement to go slower in ghost.

When you use ghost, you can not fix the camera. I'll spare you the technical reasons I've discovered while playing around in the code. When you're flying with ghost, you have to use PlayersOnly to freeze your character in the air.

Then use Walk to exist ghost. If you quickly fix camera after using Walk, SOMETIMES the camera will be fixed where you were looking with ghost... though sometimes it won't at all.

THEN, with the camera fixed, you need to use ghost again to move her around. Sometimes you can safely land her and then walk to where you want to go. Sometimes you can't. I also don't think you can move up and down this way. Only along the X,Y axis.

Stein3x says:
I would like to add also that you can move in the Z axis while you use Ghost with an Xbox360 controller i tried using the Triggers.It's much easier to make a good composition since you also control the camera speed with the analog sticks and the Z axis with the triggers, but overall it's such a pain in the ass to get good shots -_-

Godspazz says:
For trickier shots, it gets a bit complicated. For my "Lineage", "Diktat Future", and "Stillborn Broadcast" shots, I had to get the camera into places it normally wouldn't fit. What I did was press the ghost button, move the camera into position (It's probably going to move a bit in the process so give a little leeway), then I press my Slomo 0.1 button to make the game go VERY slow. Then, you're going to press "Walk" and then "Fix Camera" very fast, one after the other. Then IMMEDIATELY press Ghost. With a little luck, your camera won't have moved much. If it did, then try again, maybe moving the initial position a bit from where it was last. I find that doing Top-Down shots is nearly impossible. Shots where you're on the edge of the stage are really annoying, because Nilin trying to find the ground seems to make your camera go nuts. Sometimes it's a good idea to hit "Players Only" before "Walk" and "Fix Camera".

Remember to hit "Ghost" afterwards to make sure Nilin doesn't fall through the level. That's likely what's causing your reloads. Hope I helped. It's really confusing, but the game is worth the effort.


Remove Combat HUD During Combat
As mentioned by jim2point0 , you need to toggle between ghost and walk a couple of times to get this to disappear. I found that pressing walk first, in my case this was "ALT Decimal", then ghost "Decimal" seemed to work almost ever time. Note that you will not get back the combat HUD until new combat is started and you may not be able to trigger some scripted events with the "use" key. Oh, and you will not be able to attack until you aim and shoot something...then you can punch and kick to your hearts content!


Rewind Savepoints and freecam cut-scenes.

After a bunch of pissing around with ghost and fixed camera to change the savegame point to just before the cut-scene (place fixed camera in save point location and then "walk" Nilin off the map to reload), I was then able to use playersonly/walk/ghost after immediately entering the area to skip the cut-scene completely and have the actors in a different (default?) position than was in the original cutscene...with the added ability to move the camera around.

I need to test this in a couple more scenarios but it looks like if you go into playersonly then ghost/walk/ghost just before a scripted event, you can break the camera out of the event.
 
As I pointed out, it may causes crashes when enabling during gameplay. What I do when I'm at the main game menu is disable cheat protection, enable the main table, and then enable the FOV override script. Then I just leave it on. Seems more stable that way.

I've been thinking of ways to improve it but it will have to wait until after work (where they pay me to code less interesting stuff).
 
@Neoenigma

I don't want to bring up old stuff but i can't figure out how to get a free camera in Dishonored? You did get it to work right? (or rather how to fly?)
 
Quick update to the Dark Souls table. It now outputs the actual FOV (default 43). And when you change it, it transitions smoothly. Ooooooooh

@Neoenigma

I don't want to bring up old stuff but i can't figure out how to get a free camera in Dishonored? You did get it to work right? (or rather how to fly?)

Dishonored has Fly, PlayersOnly, notarget. Pretty solid table.

Here it is.

[enable] -> [scripts] -> [cheat handler]

Numpad 1 = PlayersOnly (pauses the game and lets you move around)
Numpad 2 = Fly
Numpad 3 = Ghost
Numpad 5 = God

V = Invisible to enemies (they wont attack you)
Alt + V = Visible
 

Xavin

Neo Member
So i've been trying some commands in Lost Planet 3.
SetRes, Fov, ToggleHud, Tiledshot and fixed camera seems to work.
The issue though is to get the camera back to the default state after i used fixed camera.
I tried several commands, thirdplayer, behindview etc but those sets the camera to first person(ish)
The commands aren't put in the Lostplanetinput.ini which had me scratching my head but rather in KeyMappings.ini and the code looks like this:

<Strings:LostPlanetGame.Commands.Custom_Command_14>=Camera Fixed,Multiply,,False,False,False,False

No idea what purpose the false has though.

Anyone have any ideas on the default thirdperson camera?

Since png is lossless, i assume max compression is the preferred way?
 
Better late than never,

Timestop, Free Camera, and Stealth

Cheat Engine table download link

1. Attach the CE table to your game.
2. Click [enable]
3. Expand [scripts]
4. Click the [cheat handler] script
5. Use the hotkeys below

Numpad 1 = PlayersOnly (pauses the game and lets you move around)
Numpad 2 = Fly
Numpad 3 = Ghost
Numpad 5 = God
V = Invisible to enemies (they wont attack you)
Alt + V = Visible again

Hud Toggle and FOV

Input file for bindings: "..\Documents\My Games\Dishonored\DishonoredGame\Config"

Code:
m_PCBindings=(Name="F12",Command="showhud",Control=False,Shift=False,Alt=False)
m_PCBindings=(Name="F1",Command="FOV 10",Control=False,Shift=False,Alt=False)
m_PCBindings=(Name="F2",Command="FOV 20",Control=False,Shift=False,Alt=False)
m_PCBindings=(Name="F3",Command="FOV 30",Control=False,Shift=False,Alt=False)
m_PCBindings=(Name="F4",Command="FOV 40",Control=False,Shift=False,Alt=False)
m_PCBindings=(Name="F5",Command="FOV 50",Control=False,Shift=False,Alt=False)
m_PCBindings=(Name="F6",Command="FOV 60",Control=False,Shift=False,Alt=False)
m_PCBindings=(Name="F7",Command="FOV 70",Control=False,Shift=False,Alt=False)
m_PCBindings=(Name="F8",Command="FOV 80",Control=False,Shift=False,Alt=False)
m_PCBindings=(Name="F9",Command="FOV 90",Control=False,Shift=False,Alt=False)
m_PCBindings=(Name="F10",Command="FOV 100",Control=False,Shift=False,Alt=False)
 
Top Bottom