Quality Test - Planetside 2 and 'Ultra' Settings (1080p Video), Screenshots

Although I am still working on a First Impressions for this game, I am just having waaay too much fun playing and testing out different settings on it. For those who don't know, Planetside 2 is a Free-To-Play MMOFPS (massively multiplayer online first person shooter) and is available on Steam for easy install and login.

Now, when I first tried playing the game, it sometimes got sluggish and choppy, even though my system isn't 'old' yet, with a 6-core AMD CPU and a Radeon HD 6870. So, being a computer technician, I got down to [having fun] troubleshooting..

The first thing I noticed is that larger fights lagged out the game more. Defending a little outpost with a dozen or so people running around, the game flew at 60fps; but in a large Bio-dome 3-faction battle with what must have been a hundred players tearing about, my frames per second dropped below 30 quite often.

What do you do in this case? That's right, lower the graphic settings. In an OPTIONS or SETTINGS menu (as it is in this game) you can usually find Video settings that you can lower or disable, to help the game perform better, by telling your videocard, "don't do this... or that". The funny thing is, putting it on Medium and then Low, made no difference whatsoever.

What does that mean? In case you didn't know, that means that it is not your videocard that is getting overworked. If running on Low settings with no special effects, the game is sluggish and turning everything up to High with all the bells and whistles, the game is just sluggy (yes I make up words), it is not your videocards' fault. Don't send it to it's room just yet.

What is happening then, is that somewhere else there is a limitation of some sort. Loading models/polygons/effects and other things as you move, the hard drive has to feed data to be displayed. My hard drive light wasn't going on much (I defragment often), so it must have been something else. My RAM tested out ok, so what's next? That's right, the CPU. Looking at the performance of my 'main-brain' processor as the game ran, showed it didn't really overuse it either though, only about 20-60% at most. It also didn't use more than about 1.5GB of RAM, so it must be running in 32-bit address space (if your head got 'swimmy' at that last couple sentences, it means the game didn't tire out my computer very much).

Now I don't want to point fingers without really knowing, but the testing suggests that there is possible CPU optimization problems, either within my system, or on the server systems (and possibly some data communication issues). After doing a little research into what I found was a large number of people having problems, I read that the developers have promised some sort of optimization patches over the next while. Great! I see already, whenever I load the game, that there are little hotfixes and patches coming down the pipe. A good sign of good treatment for the game, hopefully.

Looking around some more, I also found there was an 'Ultra' graphics setting in the Beta (I have been in many but I was not in this game's Beta phase) that was taken out. I assume this is to limit the work put onto players' systems and appeal to a wider audience of older hardware owners. However, it was still somewhat usable now, as long as you didn't mind doing some text editing of a settings file in the game's folder. Of course, I had to test it out!

What was essentially an uploaded text file with no Creditation (it just says Uploaded By: A Guest), what it contained were some settings such as turning up Draw Distance and Lighting Quality, by setting it to a higher number than the game normally does (the game's HIGH setting seems to be '3' and this text file was suggesting '5' in many places). Trying it out, some screenshots of the result are right here:

This wasn't taken with Ultra settings (I was running on High at the time), but 

I liked this shot from the BioLab atrium and wanted to share it, it's my wallpaper at the moment:

The problem was, these Ultra settings didn't really help the lag/sluggish gameplay I was experiencing, although it made it look spectacular. Since the issue of the sluggishness seemed to possibly be tied to CPU optimizations, I further changed the settings on my own, lowering ones that taxed/used the CPU more - and lo' and behold, what I ended up with was a nice, smooth, excitement-adding(!) gameplay performance - from a batch of settings that I now want to share with everyone else!

The [what seems to be] original "Ultra Config" settings are found here:
http://pastebin.com/XFkf8sYJ
^ That is a website where people can upload and share text files and you can simply save it as the text file it is and rename it UserOptions.ini and put it in your
<whatever drive steam is on>//ProgramFiles/Steam/steamapps/common/PlanetSide2
folder. (Make a backup copy of the original if you want)

Since those settings resulted in great-looking graphics, I wanted to keep most of it, but simply changed some of the more CPU-utilizing effects. My changes were all under the section Rendering (you can just copy and paste this 'Rendering' section over your 'Rendering' section in your UserOptions.ini if you want to):

[Rendering]
GraphicsQuality=5
TextureQuality=0
ShadowQuality=3
RenderDistance=2000.000000
Gamma=0.000000
MaximumFPS=60
UseLod0a=0
VSync=0
OverallQuality=-1
LightingQuality=3
FogShadowsEnable=1
EffectsQuality=5
TerrainQuality=3
FloraQuality=3
FloraDistanceScale=2.000000
ModelQuality=5
ParticleQuality=5
ParticleLOD=5
MotionBlur=1
BlurQuality=3
MotionBlurQuality=3
VerticalFOV=74
AO=1
AmbientOcclusionQuality=3
AOQuality=3
GpuPhysics=1

* Update: we have put our own Pastebin text file of the entire UserOptions.ini up here (simply save it/rename it to UserOptions.ini): http://pastebin.com/6j9aHVav

** For even more performance while still looking nice overall, try inserting these settings, most of which release even more CPU demand from the game:

RenderDistance=1000.000000, FogShadowsEnable=0, EffectsQuality=2, ParticleQuality=2, ParticleLOD=2

As you can see, most of the textures, complexity and other effects are up, but I lowered a few things like the terrain and shadows (these seemed to use the CPU quite a bit) and the draw distance, which still looks good at "2000". With these settings, I now had a much smoother, still-pretty result! Recording some gameplay as a test of both the new settings and showing the increase in performance, here is few couple minutes of playing as a Medic and Engineer with the settings above:

Recorded with Bandicam Licensed Version at 1920x1080p, 'Default' setting (MPEG-1 Quality 80 VBR)
playing Planetside 2, a free-to-play MMOFPS

That was just a simple pasting of some short tests together, taken in a time of low light/at night and then during the daytime when I went and found some BioLab fighting (which is usually a site of sluggish performance for most people, I know it was for me) where there are many other soldiers around. It shows an example of  the lighting, effects and clarity of the textures, both inside and outside (except for one or two that seemed to be 'stuck' at low resolution) that you can get with these Ultra settings - as well as the smoothness of gameplay that you can even have with my tweaks to them! If you want to make sure the game doesn't change them back (or you don't by accident), make the file Read-Only.

I'm not the greatest player, but I enjoy playing a Medic and Engineer, helping support my team. In the video, you get to see some Healing and Repairing and the Engineer's Turret that he can construct (and then only he can use it) and my Friendly Fire Warning I got using Claymores (if anyone on your team is too close when it goes off after detecting an enemy they get hurt too). You actually get three or four Warnings, but people were standing in front of my Clays a lot when they took out enemies and then you can see my shooting in the back a little in a firefight at the door there, as we all ran in and around it...don't worry it's not easy to get Weapon Locked. If you get a few warnings, just watch out for other people (sometimes you can't help what they do) or even move to a less busy area or just Repair and Heal people for a while.

Hopefully these tweaks will help some of you out there. It's sad to have such a great game with such a large-feeling scope of battle have so many people upset and frustrated that it's too laggy or sluggish and having those people give up or leave or think the game isn't good at all. Don't forget the promise/rumors of further tweaks and optimizations coming out soon, too. Since I can honestly say it helped my bad performance problem, I can honestly say that it should help you, if you are experiencing low fps in your gameplay - and it will look great! If anyone is still having sluggish gameplay, let me know and I can try tweaking the settings a little more to squeeze more out of it and see what happens. Whether you have to turn everything down, or if you can run it full blast, or with these tweaks, I hope you can enjoy the game eventually, and that these tweaks helped some of you at least a little bit.

*** By the way, for those worried about SOE's stance on modifying game files, etc. their Official Statement on client modification is here:
http://forums.station.sony.com/ps2/index.php?threads/important-client-modifications.54265/ 

Quote:
"The most simple guidance here is do not use third party programs which change the Planetside 2 gameplay in any way unless it has been specifically cleared by SOE.
The above does not apply to user initiated *.INI changes, those are allowed, although setting your own options incorrectly can result in bugs."

So they are mainly talking about hacks like aimbots, memory injectors like Cheat Engine, etc.
Thankfully, merely changing how it is displayed on your own screen (as we are doing here) is O.K. Just don't set any of the settings 'too high' or you can cause problems (they call them bugs) such as corrupted display, really really laggy gameplay, and so on (don't worry, you won't hurt your hardware, the game will just crash or something similar). Thanks for letting us tweak the video options, SOE!

NOTE: When experimenting with these changes, please remember that any problems arising from them should not be added to the already heavy load of Sony Online Entertainment's Technical Support Department. Please 'reset' any modifications by deleting the UserOptions.ini file and then after further troubleshooting, bring PS2 problems to the attention of SOE and their staff. Thanks  

Also.. there seems to be a problem with long play sessions, the game gets more and more sluggish for many people. It has been suggested that is is possibly a Memory Leak problem and for now, to restart (the game and/or your system) after a long battle, so that the next one will possibly have less problems. Hopefully this isn't an issue for everyone.

[Update: Testing these settings with an NVIDIA GTX 560 Ti and then with two GTX 560 Ti's in SLI mode, there was near nil increase in performance when switching to SLI. It seems that the bottleneck truly is within the CPU optimizations.
As a sidenote, I was getting about 30fps on average with the NVIDIA cards in my system (even in SLI) and was getting about 40fps on average with the AMD/ATi card in the same system. This is normal however, as some games perform slightly better with one than the other (as the coders develop the game on one or the other/company optimizations/etc. Something could be said for AMD doing some optimizations between the videocard and the CPU when an AMD GPU is coupled with an AMD CPU in the same system, but as I do not work for the company, I do not know.. it does make sense however).]



Personal Notes/Opinions:

At the time of this posting, the game seems to have a lot of aliasing (in my opinion), even at 1080p or higher resolutions. If you want to enable AA, you can do so by forcing it in your videocard's Control Panel. FXAA (NVIDIA) and MLAA (Morphological, AMD/ATi) are both versions of post-processing that should work and be visible in the game [I tested it with AMD's MLAA, the difference is visible]. 
Note that these post-processing AA techniques may not be able to be captured in screenshots and game recordings (Fraps, Bandicam, Dxtory, Playclaw, etc) although the effects may be visible while playing the game [in some games processing such as SweetFX can be capped, some can't].
As per SOE's Official Statement and replies, use of SweetFX is NOT suggested as it is still in the category of utilities that can result in being banned:
http://forums.station.sony.com/ps2/index.php?threads/important-client-modifications.54265/
http://forums.station.sony.com/ps2/...modifications-announcement.55674/#post-692380




See you in the game!

Tips For Game Recording, Quick Edition (Text-Only Version)

Recording your gameplay, whether it is for sharing with family and friends, uploading tutorials, contest/challenge entries, or just your own archive to watch when you are relaxing, is a great way to share and preserve gaming experiences. There are a handful of game recording applications out there today and while each one has it's ups-and-downs, I want to make a post however, focusing more on the problems people run into when trying to record their games. I wanted to quickly share some Tips that will help no matter which game recording software you have chosen as your own to use, whether your problem is 'it causes lag', 'framerate drops', 'video is choppy' or any other symptom. Here are some ideas to help you out, presented in order of the effect it should have on your game recording, from the most effect to the least:

• Reduce the resolution of the game. That means instead of playing at 1920x1080, set the in-game resolution (usually in "Options") to something smaller like 1280x720 (720p HD) for example.

• Reduce the resolution of the game recording. Not all game software will give you the same amount of choices for this, but reducing the resolution that the game is being recorded at (not the size you are playing at, set in the game, but the size of the frames being recorded, set in the game recording software such as "Half Size" or "75%" or a resolution like "1280x720"/"720p") will help reduce the amount of data your system is dealing with, and will help reduce things like framerate drop and recording lag.

• Reduce or turn off Anti-Aliasing. This is one that can greatly affect recording smoothly but not many people think of it. When AA is on, video data is being 'processed twice' as stair-stepping is being detected on the frame, and then the video frame is being compressed for the recording itself. Do some tests on your system to see how lowering or turning off AA (even FXAA or Morphological/SMAA or 'Fast AA' albeit for reduced gain) has an effect on your game recording. You may need to set it in the video card's Control Panel and/or in the game itself.

• Use the fastest drive on your system. If you have more than one drive in your rig, using something like CrystalDiskMark or Dxtory's built-in disk benchmark/testing tool (usable even in the Trial Version) or Nero's Burning ROM ('copy' using an image file, there is a drive speed tester in there), can help you find which drive recording to will be the smoothest/fastest. Always try to record to your fastest drive and the earliest (firstmost) partition on that drive that you can use for it.

• Change the format you are recording into. By this I mean the recording codec you are using. Some codecs [COmpressor/DECompressors] that are used to handle the video data keep a lot of the detail but take up more space (like FRAPS' codec). Some codecs are 'lossy' and give up some quality in order to take up less space and keep the output file smaller (like Bandicam's MPEG-1 VBR codec). Some are just less taxing on the system or take better advantage of it (like the UT Video Codec's ability to use multiple cores of your CPU). If you have tried other things, try changing the codec and level of quality you are using. Record at 60% quality instead of 90% [Playclaw uses MJPEG set at 90% by Default and Bandicam uses MJPEG set at 80% for it's 'For Editing' Preset] and see if it looks ok to you (especially if you are recording at say, 1920x1080 and going to resize it down to 1280x720 for uploading).

• Reduce the settings in-game. What I mean here is the Special Effects like lighting/shadow detail, graphic detail (complexity of the shapes/models/meshes and sharpness of the textures on them), effect detail (splatters and smoke) and even sound detail. All of these things make the system work harder (especially the CPU) to process them [very simplified; it must take data from the game files, process it, size and shape it and then finally show it on the screen and then buffer it and process it and write it to the recording file]. This will increase your frames per second in the game as well, and more of your system's resources can be put toward recording smoothly.

• Reduce the frame rate of recording. This means, recording at 24 frames-per-second as opposed to say 60fps. There will be literally less frames for the program to deal with, and your system will not have to process so many and push them around, finally writing them to the recorded file. Dealing with less video data means that your system can handle it more smoothly, processing and writing slower to the drive being recorded to.

• Defragment the drive being recorded to. These days, with how Windows7/NTFS and Linux's Journaling System handles files and with Solid State Drives, it is not as needed as in the days of yesteryear; but making as much space as you can and ordering the files as much as you can does still help with game recording overall. 

• Upgrade your system's hardware. I hate seeing and giving this advice, but it really does help with just about anything that you are trying to do with your computer, so I am including it, last (even though the effect a computer upgrade can have can be greater than any of the steps above). Game recording uses not just your video card, but also your motherboard (everything 'talks to each other' through it), your CPU (the traffic cop, dictating how fast everything should go and when), RAM (the holding and transport areas for most things), and finally the hard drive (which receives all of this data and computes writing it to the file). Purchasing anything as an upgrade, whether it is a newer/faster drive, processor or video card, will all help in game recording.
  Lastly, a dedicated Sound Card is always [always] more efficient for a system than using the Built-In/Onboard Audio. Even a good USB soundcard can help alleviate problems like sound stuttering, clicking and popping, static, input lag and other problems, as processing is done without bothering the CPU and using main system resources for audio.

Hopefully, these Tips will help you record your games, no matter what software you've decided to use/try to record with. As always, when having problem with programs, going to the Support portion of the developer's website, even if it is just a Forum there, is a good idea to look for help with a specific program and the problems you are encountering. These general Tips are more concerned with your computer and how it interacts with programs/games in general and should help 'No Matter What'.
Good luck with it and have fun!


See you in the games!

Quality Test - Diablo III and Bandicam's "For Edit" Preset / YouTube Upload Test

With the Bandicam "For Edit" Preset, every frame is an independent Keyframe or I-Frame (Information Frame), which is a type of frame that can be 'cut' or started from in video editing programs (technically, every frame is a JPG picture). Also, the audio is Uncompressed, which means that any video editor should be able to recognize the sound data. Errors in programs like Virtualdub saying "Error initializing audio stream decompression" or Sony's Vegas showing "Stream attributes could not be determined" will not occur and these will open the audio just fine with this setting.

Testing out Bandicam as a game recorder and playing during the launch of Diablo 3 (woot!), I've put together some settings/specifications, uploaded it to YouTube, and collected some results for you all:

The video is short, but I was mainly testing a few things:
1) D3's performance, with all options maxed out
2) Capture quality of Bandicam's 'For Edit Premiere/Sony Vegas' Preset and performance/lag of using it
3) The Logo/Watermark capability of Bandicam
4) YouTube's quality maintainability


Recorded with: Bandicam
- v.179204 (Latest at time of this post)
- 'For Edit (Premiere, Sony Vegas)' Preset
- MJPEG, "Full Size", 80%quality (Preset), 30fps, Uncompressed PCM Audio at 48kHz
- Logo option (our GTAM watermark), lower right, 10% opacity


Game: Diablo III (Retail Release) Launch Day
- Witch Doctor, Cathedral Level 3
- Texture Quality: High
- Shadow Quality: High
- Physics: High

- Clutter Density: High

- "Anti-Aliasing" checkbox ticked ON


Resolution: 1680x1050 (1.6AR) recorded at 1680x1050 ("Full Size")**
Filtering: 4xMSAA, 4xAF, set in Control Panel of Videocard
Framerate while not recording: 80-100fps
Framerate while recording: 80-100fps

For people trying out Bandicam and finding your recordings are choppy/laggy on playback (when looking at the original generated/recorded file), you should find that compressing it to a file with a smaller bitrate/size in a format you will keep it permanently in, it will play back that file just fine.

I chose this D3 clip for a Quality Test because it was a good example of both fast movements/action on the screen, as well as slow/non-moving parts, including text. It has dark and light areas, high contrast edges, and tests wide area panning as well.

Bandicam's "For Edit" Preset worked great, with clear text and action in the original recording, while flatter, darker parts were not overly compressed which would create excessive macroblocks or be too smoothed out. There were some Gibbs Effects/Mosquito Noise around text and on some of the button logos in the original recording, but you had to look closely to see it, which is pretty good for not being a 100% Quality setting.

The very small amount of color banding present in the original recording was somewhat generated by the Game Engine (seen in the lower-right quadrant of this video, and in the Diablo3 login screen around the moon, etc.), and there shouldn't be much, due to using MJPEG as a recording codec.

If you are having problems with Color Banding that is not in the game itself, try MJPEG as your recording codec




Average bitrate of the original was about 40Mbps, which meant a writing stream to the disk of about 5MB/s, which any hard drive can handle (recorded onto a drive capable of 150MB/s).
Framerate during recording was maintained at 80-100fps (same framerate as not recording).
The original 1 minute generated file is about 300MB in size with these settings. The recompressed MPEG-4, resized to 1080p file, has an average bitrate of 20Mbps and is about 140MB in size.

While this Preset in Bandicam is designed for compatibility with editing programs, the original recording was uploaded directly from the Bandicam-generated file anyway, to test the effects of uploading to YouTube from an original recording.

** The video at the top was Lanzcos3 resized from the original 1680x1050 capture to a 1728x1080 (1.6 AR) [MPEG-4 H.264 AVC/AAC file with a bitrate of 20000kbps (audio at 384kbps) using a Deblocking Filter setting of +0+0] because the original upload was down-sized to 1280x720 by YouTube and looked much worse, see here below:

The Result:
Recorded at 1680x1050, YouTube had downsized that one to 720 vertical lines. The Gibbs Effects were no longer present because of this, but excessive smoothing and other compression artifacts were introduced. Text was far less readable and nothing on the screen was as crisp as the original 1050p recording. Aliasing was also introduced. This was unfortunate but understandable however, as YouTube can no doubt not keep 'everything' at 'very high bitrates' on their servers, and since it was not 1080p, it simply scaled it down.

A single frame taken from each video for comparison (Frame 813, zoomed section) from the original Bandicam recording, YouTube's version of the 1080p upload and YouTube's 720p version of the 1680x1050 upload. Click to see Full Size.

The resized-from-1050p-to-1080p version maintained much of its detail after uploading to YouTube. The text is closer to the crispness of the original recording, and there is only some smoothing and deblocking being done. There are some macroblock artifacts and color banding accentuation in the darker areas however (for instance, the lower-right quadrant much of the time) but other than that, it is a decent quality version of the 1080p upload.


For those recording at 1680x1050, I recommend upsizing it to 1728x1080 so that YouTube keeps most of the detail of your recordings

  Well done, Bandicam (and YouTube).

Hopefully this information will help out any gamers that are looking to start recording their experiences, or even the already numerous people who are recording and sharing their great videos. Thank you all for sharing and your efforts.



Please note dear reader, that I am not saying "This codec is the best one to record with" or "use this one only". I am merely showing that it is possible or how to tweak it for quality or file size, as to your own personal tastes. There are many codecs out there to choose from when game recording and although some are more apt for certain types of games than others, overall it is your own choice to do with as you will.


See you in the games!