

whitav8
Members-
Posts
188 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by whitav8
-
Just curious - were you able to easily spot targets without zoom on your monitor? What resolution did you run your monitor at?
-
@SkateZilla, Most of us are amazed at the new quality experience with the latest 2.0.2 - the smoothness of the VR experience is what we have been hoping for in the flying world. I've been in the pilot training simulator business for 40 years and haven't had as much fun as this. Since you have made this a sticky - thanks - could you possibly make a summary list at the top of this thread of the reported issues/bugs so newbies don't open another thread to report them (right now, chiefly just the problem with ending a mission). Also, maybe a list of desired key improvements - not so much for the game, but just for the VR interface (mouse versus laserhead). If this is impractical, it's OK - this thread is wonderful as is. I'm not sure when to open a new thread (like I did for the Night Environment issue) or just tack on to the last page of this thread. Thanks for your effort!! Dave
-
OK - I solved the size of stars issue. Just use Notepad++ to edit the following: C:\wherever\DCS World 2 OpenAlpha\Bazar\shaders filename = Star.fx line 21 : static float starSize = 1500.0; I changed it to 500.0, could even be less for personal preference. I set up a simple mission with a UH-1 at low altitude near the North end of the strip - looks great in the neighborhood areas. Turn on your landing light (which looks just a little strange in stereo at very low altitude) and land in a parking lot - or on top of a building. Late twilight is nice.
-
- 1
-
-
Congratulations to ED for the 1.3 runtime support in 2.0.2 and that ATW works so well! Yes, the menu bugs are annoying but we are seeing great strides being taken. Night Environment 1. The problem that several of us noted before was that the lighting from point sources onto the terrain was different for each eye (and really headache causing) has been fixed!! Flying in downtown Las Vegas in a UH-1 at night is a real treat. By the way, I saw some CTD crashes with starting at McCarran in the UH-1 (brand new simple mission) but if I start near the Stratosphere and come into town from there, no crashes?? 2. The stars are way too big - everything is a Supernova! I hope I can find an editable file that reduces that. 3. I see a lot of banding in the sky coloring at late dusk (a little twilight left) - I'm not sure if that is DCS, my DK2, Oculus 1.3, or what Anyway, I am enjoying the night scene now. Hoping for some of the bugs to be fixed soon but will be patient! Please report your own findings - maybe the CV1 is better.
-
Couple of wishes after maidenfligth in VR (Vive)
whitav8 replied to Kirin's topic in Virtual Reality
For cockpit "seat" movement, I use my POV hat to set Cockpit Camera Move Back, forward, left,right,up,down in the View Cockpit assignments. I use the POV upper right(UR) for "UP" and lower left(DL) for "Down". I like to sit pretty far forward so I can read most of the instruments without much "lean in" - I also use the Bigger HUD font for the A-10C in the User Files. -
Thanks very much for the VR subforum creation!! Dave
-
@Frusheen, Thanks for the expert opinion on ReShade/SweetFX. I expected it was something like that. I've asked Dan Church (author of FlyInside for FSX/P3D) about it and he seemed to think that he could add the "hooks" interface to his code. I wonder if ED could do the same - certainly there are post-processing passes being made using shaders somewhere. If that could be exposed somehow (not using dxgi.dll) to the user as addon shaders, it would be great. There is some evidence that screen door, vibrance, luma sharpen and other such effects could be used to improve the VR image. Thanks for your expertise Dave
-
Sorry, Only 1.5 openbeta is 1.3 runtimes compatible.
-
If you are having trouble reading the A-10C HUD, if you haven't already, make sure you load in the following: https://www.digitalcombatsimulator.com/en/files/374967/ Also, For eyepoint/seat movement, I use the Joystick POV HAT and set them up as follows: View Cockpit->Cockpit Camera Move Back JOY_BTN_POV1_D View Cockpit->Cockpit Camera Move Down JOY_BTN_POV1_DL View Cockpit->Cockpit Camera Move Up JOY_BTN_POV1_UR etc Finally, I use Voice control for the formation commands and radios - maybe not all you want to do. Dave
-
@ED, Many, many thanks for providing early Oculus 1.3 support - fast head movement is now a delight and the overall smoothness is great even for us DK2 users. If we could somehow insert ReShade/SweetFX effects into the post processing, I might be able to reduce the effects of screen door, and not have to purchase the CV1 and also sharpen the instrument panel. I joined the Virtual Aerobatics multiplayer site yesterday as a TF-51D and flew in loose formation with a solo aerobatics p-51 (smoke on)and what an experience! We are able to fly in situations where we never could in real life but feel like we are (minus the G's). Thanks again ED Dave
-
I would really like to be able to use Reshade/SweetFX with VR so effects like vibrance and luma sharpen could be utilized to help the appearance of the VR image. I have it loaded in the latest openbeta update and you can see the effects on the monitor screen but not inside the goggles. Thanks Dave
-
To all, If you need to switch back and forth from Runtimes 1.3 (Cv1) to 0.8 or less: https://www.reddit.com/r/oculus/comm...0813_with_gui/ Note: I had to make some small changes for the 0.8 cmd file - some sort of hidden character problem with file paths NOTE: The above link was incorrect! Maybe it changes as more replies are added - search for: Oculus Runtime Switcher V2 (supports win 7\8\8.1\10) OR maybe: http://www.xsimulator.net/community/threads/oculus-runtime-switcher-v2-supports-win-7-8-8-1-10.8155/
-
Switching from newest 1.3 Oculus runtimes back to 0.8 for DCS World -until cv1 update To all, If you need to switch back and forth from Runtimes 1.3 (Cv1) to 0.8 or less: Note: I had to make some small changes for the 0.8 cmd file - some sort of hidden character problem with file paths.
-
Reshade 2.0 SweetFX / FlyMaker Preset - DCS 1.5 Beta
whitav8 replied to FlyMaker's topic in DCS Modding
Has anyone had any success installing ReShade for DCS 1.5/2.0 with the Oculus DK2. I read about install the ReShade dxgi.dll and the Reshade folder in the OVRServer_x64.exe directory (Oculus\Service) but I can't get it to work. It works fine with nonDk2 mode. Thanks Dave -
Has anyone had any success installing ReShade for DCS 1.5/2.0 with the Oculus DK2. I read about install the ReShade dxgi.dll and the Reshade folder in the OVRServer_x64.exe directory (Oculus\Service) but I can't get it to work. It works fine with nonDk2 mode. Thanks Dave
-
AG-51_Razor, So is your version available only to your teammates? Are you using both 1.5.2 openbeta and openalpha2.0? Thanks Dave
-
@SCPGrinder66 Are you saying that you see them as AI (which I do already) or that you can be the "player" and fly inside their cockpit? (which I can do with the A-7E after a small fix) Even Morkva says he hasn't updated them for then latest openbeta/openalpha. I have what I downloaded from the Stinger site last week - FA-18_113_2.0 and SLUFOCT112015 Thanks Dave
-
I would like to use the Fa-18C and A-7E mods with the DCS World OpenBeta 1.5.2 and also with 2.0 OpenAlpha. I am flying with the Oculus Dk2 and the carrier environment seems very interesting. When I first tried them both from their ZIPs on the VFA-113 STINGERS website, I could make a mission with them but they would only appear as AI - not flyable by Player. It appears that the A-7E is closest to being usable - I had to make a minor modification (names?? - A-7ECorsair) to the "entry.lua" file in the A-7E Corsair directory to get it to be flyable by "Player". The cockpit model is in EDM format. I am having some issues connecting my TM HOTAS X joystick to the tailhook and some cockpit view adjustments - maybe there is a "lua" file that needs additions? The FA-18 Model doesn't seem to have an EDM model - just a lods version - and I haven't been able to make it flyable by player. I am wondering if this limitation is to be expected at the present time, or is there something I have missed. I have been able to take off and touchdown on the USS Bush deck but not catch a wire - maybe because I can't get the tailhook to come down!! (I know that it is "Lalt+G" ). I can see it go down just fine with the AI Pilot. Thanks for the great carrier environment Dave