I got shot down in a head-on before I was close enough to even tell he was that close and coming towards me not flying some other direction. Sometimes I can't even tell the orientation until it's too late. Usually I can't ID a plane type at any reasonable range (a few times I saw the allied plane marker before I could recognize the type). Planes render into full view very late, the dots stay dots very long and it makes the range deceptive. spotting is fine, actually it's better than screen because the dots are huge. I didn't notice any poor performance from 2.0 SS, should I go higher or tweak something else? Am I expecting too much, how well can you guys actually read the instruments? I can still barely read the cockpit instruments, especially on planes where they are small. So far that was my best experience (even managed a kill). ![]() Yesterday I used SS 2.0 from the new linear slider with the lowest game graphics settings from page 1. Been tweaking for a little while and trying to get over feeling sick as well. Hey and thanks for the thread! I got a Vive recently and running a GTX 970. I dont know if that my GPU maxing out or what. Every once in awhile I get a stutter, but experience no FPS drop. My FPS only drops if i were to get shot down and spin out of control. GPU- In order for me to achieve SS 1.6 without losing any FPS I must do the following: The issue with continuous frame drops occurs when these windows in a certain order and state. I pretty much run with everyone off.ĬPU- Max'd the over clock at 4.4 GHZ (done through BIOS.) Just run SteamVR via Steam, run any vr game, minimize steam window or/and get any window and miximize it to overlap all other, wait for 5 seconds. This is map dependent for me because when the glare is ridiculous, stuttering increases for some reason. I recently added the h100i vs liquid cooler for my CPU for my anticipation to upgrading to a I7 7700K. Help is also available if you cant log in, need to reset your password, or recover a hijacked account. For those running a 4790K and a GTX 1080 FE I have been working on overclocking values to allow for consistent supersampling at 2.0. (provided, obviously, that you installed the Oculus software in the default 'Program Files' directory).įor example the Debug Tool on my computer can be found here:Ī full explanation of the most important settings (including supersampling) for the Debug Tool can be found in this video: Program Files\Oculus\Support\oculus-diagnostics It is no longer necessary to download the Oculus Rift SDK to have access to the Debug Tool (the software that allows to change supersampling and other parameters) as the Debug Tool has recently been moved - every Oculus Rift owner can now find the Debug Tool in the Oculus installation on their computer in the folder: Talking about Oculus Rift I wanted to add a couple of comments, (feel free to include them in your guide if you deem them useful): using SteamVR beta general steam beta (gave me compositor error 400
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |