tangofoxtrot

I am running an Oculus Rift VR setup. When I launch DCS, my second monitor displays a VR picture indicating that the headset is being correctly tracked but the itself headset has a black screen. Audio is fine. I am launching DCS Build 2_5_4 (2.54.30386) using DCS Updater / Launcher GUI Utility. The relevant settings are: Rendering Driver Oculus Rift API,Rendering type: Rectilinear Both Eyes,Rendering Size DEFAULT. External Application Oculus VR Client (checked). I launch by pressing the VR/ON button of the GUI. I am assuming that with the settings above, Oculus launches. I would think that what I see on the second monitor confirms this. The Oculus Rift is set to allow unknown apps. DCS is set to use VR headset and the other settings are values recommended on these forums. The Oculus Rifts works fine with Oculus apps (e.g. Elite Dangerous which uses an x55 Hotas, Throttle and Thrustmaster rudder pedals) Somewhere in this complexity, I have failed to dot an i or cross a t. I am out of ideas, so any help would be appreciated.

During the recent sale I purchased several things including an F86. The transaction seemed completely normal, and then I got this message: Order #654847 of 11/29/2018 23:13:55 has been canceled. The order has been canceled because of unpaid within 3 days I paid with a valid credit card, as I have in past transactions. So, I don't get it. The email says to go to my personal section, but there is no trace of the order there. Who and how do I contact someone so I can find out what happened and not repeat the error in the future?

Hawk experience? I'm with trindade and you other guys. The sale sounds like a good deal and the aircraft is awesome. But when I purchased my Hawk, it seemed like a good deal too. Unfortunately the developers seemed to forget about development after the sale and all of the Hawk's numerous warts were frozen permanently( I haven't look recently so perhaps I misjudge). I notice that there have been frequent AV-8B updates this year, but I don't know enough about the aircraft to appreciate what sort of experience one would have if the devs stopped updating, say, at the end of June. What do you guys that know the current state of the product and the actual aircraft think?

Here it is. dcs.zip

I have not run 2.5 in a couple of weeks. Other than that, there have been no major changes to my machine; in particular no hardware changes at all. Yet, now when I try to run 2.5, it checks for updates, and then requests that I activate each of my modules. If I exit from each activation request, I can get into the game, but none of the aircraft are flyable. On the screen that shows icons for the various modules along the bottom, all my modules are colored. So, the sim knows something about what I have. What gives?

Thanks for the quick response Foxfire. I'm concerned about trying to upgrade to 2.5 stable without first getting 1.5.8 off the SSD. Originally, I tried to uptdate 1.5.8 to open beta and 2.2 to the early 2.5 without moving anything. The 1.5.8 update failed, due to lack of room – probably because I have the Normandy and Nevada test site maps and a number of payware acft, combined arms … My goal is to have 2.5 on the SSD (for performance reasons – the other drive is large, but slow) and no 1,5.8 anywhere. I have no objection to just deleting 1.5.8 as long as I don't loose the Caucasus map in the process. That would give me the room to update to 2.5 stable. As long as I end up with 2.5, all the maps and the same number of remaining activations for the payware as when I started, I'll be happy. I just don't want to shoot myself in the foot in the process of getting there.

I am running both 2.2 and I.5.8 on the same SSD drive. I need to move 1.5.8 to another drive on the same PC in order to have room to update 1.5.8 to open beta and 2.2 to 2.5. Couple of questions: In order to move 1.5.8, is it sufficient to just copy the folder to the other drive and delete the original SSD copy? Aside from deleting the original folder, is there any additional cleanup required on the SSD? If I do this, will there be any problem loosing activations for installed payware? Since 2.5 has now been released and given that I have no need for 1.5.8 once the Caucasus map is available in 2.5, is there any point in doing what I described? Is there a more direct path? Thanks for any ideas.

Thanks Frederf for taking a look. The data I posted is slightly dated, I've already moved 777 as you suggest along with everything else of any size. I'm really out of things to move and still I only have freed up a little over 27GB. Some additional factoids: both 1.5.8 and 2.2.0 seem to be intact - I've been able to run missions in both. The Normandy map seems a little jerky, but I have not tried to tweek the system settings. I'm thinking my attempt to update ended when the update process tried to make a copy of the Nevada map and aborted and except for the space occupied by the partial copy, everything else was ok. When all is said and done, all I want is a 2.5 with the Normandy, Nevada, and new Caucasus maps. I have no reason to keep a "final" version of the remains of an openbeta 2.5 derived from 1.5.8. So, maybe I should run what I currently have (without updating anything) and wait for stage 2 when I can dump 1.5.8 and update 2.2.0 to the final 2.5. Following this path will give me 100GB plus space for the final update. Does this seem like a reasonable path to you, or am I missing something obvious? Your advice would be welcome.

Sorry, the disk analysis formatting was screwed up. I'll try without tabs. Disk Savvy Analysis of C: C: usage Major Consumers Program Files: 60% Eagle Dynamics 97.9% of 60% Program Files (x86) 14% 777 35% of 14% Steam 31% of 14% Users 12% Windows 9.5%

Thanks QuiGon for the response. I have the Nevada Test Area and Normandy maps, about 10 study grade acft modules, FC module and combined arms module. The problem I'm trying to solve is to get enough free space to run a repair. Without moving 1.5.8 to another drive I probably can't get more than 28GB of free space for the 2.2.0 repair - thus my interest in reclaiming "debris" produced by the aborted copy. I wasn't sure if this was the correct forum for getting help, so I didn't start my original post with a data dump. Since, as you suggest, details are important, I'll post some of it now. Here are my system stats: Processor: Intel® Core i7-4770K CPU @ 3.50 Ghz 3.50 GHz Installed RAM: 16.0 GB System Type: 64-bit operating system, x64-based processor GPU: Nvidia 770 OS: Windows 10 Home Version: 1709 OS Build 16299.192 Storage: C: SSD 238GB 227GB used (after moving some stuff) D: HD 931 GB 361GB used E: (Backup) HD 931 GB 361GB used DCS World: C: Release Version of 1.5.8 most recent updates C: 2.2.0 most recent version with Nevada and Normandy maps Disk Savvy Analysis of C: C: usage Major Consumers Program Files: 60% Eagle Dynamics 97.9% of 60% Program Files (x86) 14% 777 35% of 14% Steam 31% of 14% Users 12% Windows 9.5% I am hoping that the abort during copy hasn't corrupted anything vital and that I can recover by surgically removing debris from the copy. Whether this is possible, I leave to wiser minds and help would really be appreciated.

Frederf: thanks for the ideas - I'm trying to figure out how to make space. BTW, the abort seemed to leave the 1.5.8 Release untouched. It still works. I haven't tried to run 2.2.0 since the update was copying some of its files when it aborted and I'm worried that something vital has been corrupted.

Two questions for anyone who knows the details of updating: 1. How much free space is required to do a repair of just the 2.2.0 open alpha? 2. When the update detects an out of space condition while copying clip maps does it abort without corrupting the existing open alpha and if so, is it possible to reclaim any space involved in the copying?

A small amount of additional info: I misunderstood the available space requirement and started the update with only 10GB of overhead using the command line: DCS_updater.exe update @openbeta. The process aborted during the update while copying Nevada/Clipmaps leaving zero available space on my ssd. I have the run log if its needed.

Ran out of disk space while updater copying files. Is this forum an appropriate place to ask for help? If so, I have data and can post it.

Thanks, that worked. For some reason I didn't look in the GAMEPLAY tab. Didn't think setting was a global for all aircraft. I expected a local preference for the Su-25T.