Jump to content

Aries144

NEW MEMBER
  • Content count

    5
  • Joined

  • Last visited

Everything posted by Aries144

  1. I've got the game running with VorpX! At first, I noticed the game also wouldn't run with flat screen. Not sure what changed. I reset the options.ini to default, set up the graphics for flat screen use using the in game menu, and then started a process of elimination in graphics settings after I found the game would run in VorpX after setting graphics to low. In the end, the only things I changed were setting shadows and effects details from "unlimited" to "high." I found the shadow setting significantly decreased load times, even just running flat screen. I wonder if the super long load time was making things time out? I'm using a Reverb G2. Shadows to high Effect details to high Instant Action works, single missions work, All the official maps work, several different aircraft including 3rd party modules all seem to work. Making a custom resolution like 1920x1920, setting aspect ratio to 1.0, and modifying the default camera position in some aircraft's individual ini files to be farther away from the dash all seem to be beneficial in eliminating that "too zoomed in" feeling without playing around with a bunch of VorpX settings. For me, playing with VorpX settings to resolve that always resulted in fish eye vision near the edges of the screen. I hope this works for you guys too.
  2. New guy question regarding implementing this: with this: [DetectSystem] Name=S-23MLA-II RadarType=AIR_INTERCEPT RadarFamilyName=HighLark RangeUnit=KM RadarAzimuthLimit=56 RadarElevationLimit=42 RadarSearchTime=1.2 RadarSearchRange=75 RadarSearchStrength=100 RadarTrackTime=3.5 RadarTrackRange=60 RadarTrackStrength=100 DopplerLookdown=TRUE RadarSearchFreq=10.5 RadarTrackFreq=10.5 RadarMissileGuidanceFreq=10.5 RadarSearchCW=FALSE RadarTrackCW=FALSE RadarMissileGuidanceCW=TRUE Are you only replacing those lines, keeping some of the additional original lines, or are you pasting that over the entire [DetectSystem] section, deleting everything and leaving only the above? There are some additional lines in the original [DetectSystem] that aren't present in the code snippet.
  3. Ok, I've mostly solved my eyestrain issues. I'm using an Oculus Rift CV1, and using DCS for comparison, since DCS gives me zero eyestrain. Here's what I changed: Vorpx: Pixel: 1:1 Image Zoom: 1.0 3D Reconstruction: Z Adaptive 3D Strength: 0.99 Depth Weighting Near- Far: 0.44 (ETA: I'm still playing with this setting.) Depth of Field: Off Focal Offset: 0.01 (this one was important. I had to set it to 0.01 and then adjust everything else. 0.03 was much too strong for me.) Strike Fighters 2: -Options.ini: DisplayWidth=2400 (This res is effectively super sampling since a Rift CV1 is 1080x1200) DisplayHeight=2400 AspectRatio=1.000000 -Viewlist.ini: FOV=96.0 (I found that the FOV here seems to refer to vertical, not horizontal FOV) MaxFOV=96.0 OffsetDistance=0.001 (This is a universal setting that controls fore and aft camera offset. Positive numbers move the camera in front of the pivot point. Default value has you swinging your head around in VR like a turtle. Nausea inducing.) -[aircraft]_cockpit.ini As mentioned above MaxYaw=360 MinYaw=-360 MaxPitch=360 MinPitchFront=-360 MinPitchRear=-360 Plus adding and tweaking the following value, per [aircraft]_cockpit.ini: Offset=0.0,-0.1,0.0 (This changes the pivot point of the camera, as opposed to the Offset value in Viewlist.ini. I use this value to sit a little further back from the dash in the F-4, for instance.) Now all I need to do is search the forum to find out how to modify view distance so aircraft models in-game aren't going invisible only half a mile away. :) Thanks for finding a way to get Vorpx working with Strike Fighters guys! It's SO hard to go back to Track IR once you've flown in VR. :)
  4. Anyone else having issues with eye strain using Vorpx compared to playing a native VR game like DCS? I've played with the game's FOV, custom resolutions, zoom setting in Vorpx, 3d depth, etc and I can't seem to find a combination of settings that doesn't cause me significant eyestrain after the time a short sortie takes. Any tips?
×

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..