brindle

[RESOLVED] - It was definitely 'pilot' error on my end. Explained: I use the WinWing HOTAS F/A-18 throttle start-up panel, along with the landing and combat panels. Unfortunately, having this many 'switches and buttons' at my disposal allows for an increased chance of error. Conclusion: Make sure to have your INTR WING switch on 'norm', not 'inhibit. I vaguely remember reaching down to put my STROBE to BRT (while in VR), about a month ago. Must have hit the wrong switch in the process...

OK - I've read everything here, and it still doesn't add up. I've been flying the F/A-18 for years. Never had issues with refueling until (February 2021). Things I've tried: Purposely jettison all external tanks before landing. I choose 'empty' for loadout and then fuel slider to 100% Stops at 92% every time (with AR door open and closed). Flew Saturday with a few other F/A-18 pilots, and I'm the only one who can't refuel to 100%. Jumped off of mission early because of this bug. None of these 'workarounds' work for me. Bottom line - this is a DCS bug that needs to be fixed, and I hope soon.

What are the steps (procedure) to getting DCS to create a new DCS.openbeta_server? Nevermind, figured it out - simply remove the 'DCS.openbeta_' folder. A new one is created. However, DCS server is still not responsive. Server used to work for quite some time; now it will not. I have to go back to running a server via regular DCS.

Well, I figured this would happen... Just received my HP Reverb G2 (bumped up from G1). Everything ran great for 1.5 days, then problems... SteamVR locks up when I'm in DCS multiplayer. Sometimes, when the G2 doesn't 'black screen' when jumping into the pit, it will 'black screen' when I press F10 for the map. Fortunately, my monitor continues to show what's going on. I can press escape and exit out of DCS. No issues when on single-player. Added: I did some research. It could be a Microsoft power USB setting. 1. Go to 'Power Options' >>> 'Change Advanced power settings'. 2. Scroll down to 'USB settings' > 'USB selective suspending setting' 3. Change from 'Enable' to 'Disable' Let me know if this helps. (I'm on the road; will check on this when I return).

Yes, I do ALL my flying online (openbeta). I'll see about adding my quote to your thread - thanks.

Well, I figured this would happen... Just received my HP Reverb G2 (bumped up from G1). Everything ran great for 1.5 days, then problems... SteamVR locks up when I'm in DCS multiplayer. Sometimes, when the G2 doesn't 'black screen' when jumping into the pit, it will 'black screen' when I press F10 for the map. Fortunately, my monitor continues to show what's going on. I can press escape and exit out of DCS. No issues when on single-player. Put SteamVR on 'beta' mode; didn't work, so I put it back and things ran ok until I hit F10 to view the map, while on multiplayer. This G2 is right off the shelf (new plastic smell)... Hopefully, there will be update(s) to fix this sooner than later. Everything is updated (NVidia, Windows 10, both WMRs of MS & steam). Wish I didn't have to run steam for HP, but oh well.

Thanks for the reply. I am currently using a 'work-around'. Using VVSLV: undesignating the waypoint, then VVSLV will show (press and voila). When doing this, I can re-designate waypoint to 'snap' the FLIR back to the assigned waypoint. **Found this topic afterward, in other forum room >>> DCS: F/A-18C Hornet » Bugs » [WIP] lightning pod uncage/cage command

Thank you! I was searching for a remedy.

I currently have the WIN WING HOTAS F/A-18. Since the last two DCS updates, my cage/uncage button reacts differently: When viewing an target on the ground via the FLIR, all is normal. But when I press the cage/uncage button, the camera is placed directly behind my Hornet (180 degrees of heading) instead of straight ahead like it's suppose to. I received a firmware update for the HOTAS, and went through all the calibrations. Everything is normal on the controllers. **I fly on Open Beta.

Greetings, I currently have a minor issue and not sure if the above will also help me. Am have two PCs, the 'upstairs' PC runs a stand-alone DCS Open-beta server. All that join have no issues talking to each other via voice-chat. I fly with them using my 'downstairs PC', but only my name shows on the voice-chat. It appears to have something to do with the way I am connected to the 'upstairs PC', verses everyone else (outside connections). I would like to mention, that when I use the 'downstairs PC' as the server PC, I can connect with everyone else. How do I connect with the others, when using the 'Upstairs PC' is the separate server?

Thanks a million! I've watched Wags video several times, thinking I missed something.

Same thing happened to me. But what if you only see one .DLL? (message below) "5:37:07 PM - Multiple instances of the 'VAICOM PRO 2.5' plugin found. Only one instance will be used." Also, I have VoiceAttack on my E: drive, and not the standard C:/Program Files (86) folder. Does this matter? Thanks.

Ok thanks for explaining what they mean. I have a clearer understanding now.

I am not sure if this was covered. But ordering Jester via VaicomPro to go to a selected waypoint is no issue at all. Unfortunately, if there are more that 3 waypoints in a mission, what do I tell him? Will I need to re-activate the wheel just to see what buttons are pressed for more waypoints? Why does the AIRIO program have only 3? Why not at least 8?

If I am on a my multiplayer server, I can not change to the back seat (that was the 1st thing I tried). Looks like I will need to jump in another jet - crap!

I was in a 3 vs. 1 dogfight with AI. I took some strafing, but was able to out maneuver him and eventually splash my targets. (On my multiplayer server). Landed on the Carrier, pulled off to the side, turned off both engines & requested repair. Afterward, I had ground crew turn on ground power and air supply. Jester even voiced that 'it's time to start'... I noticed that Jester did not start the alignment (all 3 displays read '0' heading). My analog read '25', which was correct. Am I doing something wrong or is this a bug? Thanks, Brindle

DCS 'unresponsive' in steamVR Issue started with SteamVR updated - Vive-Pro would not work at all. NVidia released new driver on 10-4-2018 - Vive-Pro works great. Now, Black screen after showing DCS screen - if using SteamVR. Tried to start DCS while SteamVR is active (because I'm using HTC Vive-Pro). Now, DCS.exe is 'unresponsive' in SteamVR. New Nvidia driver released 10-4-2018, which got my SteamVR back online. I have no issues with Oculus running DCS; Vive-Pro has better resolutions, so I prefer Vive-Pro. Not sure what to do. System is: Windows 10 Home (updated) Intel Core i9-7900X CPU @ 3.30G 32. GB Ram RTX 2080 FE (NV-Link)

I have the Oculus CV1, and had to purchase the 'USB 3.0' card that Oculus recommends - it works! I have a 1200 watt, modular power supply and you MUST connect cable from power supply to the back of the USB 3.0 card. This is where you get plenty of 'juice' to power your added USB 3.0. New card has 7. I already have 3 - USB 3.0 ports on my tower, they were not strong enough to run the sensor, just the oculus. Hope this helps.

I have both versions (1.5 & 2.0). Web site says "2.0.1" is released, but my '2.0' still shows "2.0.0" even after purchasing the new A-10C campaign. (I don't have steam versions). I used the 'DCS 2.0 Updater', still shows 'updated to 2.0.0.45...' Am I missing something here?

I may be a little late, entering in on this conversation... I too, wear glasses when I read. Now that I'm 50, I wear glasses when I drive. I purchased the DK2 2-years ago. It came with a pair of "A" lenses (for normal sighted people), and "B" type lenses (for those less fortunate). To this day, I wear no glasses while 'strapped into the rift', and the "A" lenses work perfectly! I just pre-purchased the (consumer's edition) of Oculus due in about March - May of 2016.

I agree with the 'disappointment' of Oculus DK2/1080p. I have the DK2 set aside, while returning to my TrackIR. I'd be flying much more if the higher-def was fixed. I know Oculus is just the developers edition, so I'll need to be patient - loved the 'buzz' I got from the DK2 and the hi-G turns but the HUD reading needs tweaked.

I've got it figured out.. I was going into 'the pit' too fast and not allowing the program & oculus to sync, during the start of Multi-player. I made some adjustments in the 'options' menu; Also, I increased the waypoint font in the F-15 HUD display along with changing the HUD color (R-CNTRL/H). Pixelation is not much of a problem, but can still improve. I'm sure that will be fixed when the consumers edition of oculus is out. This DCS/Oculus is awesome!!!

Well, it appears to me that I'm finally able to fly in DCS multiplayer with the DK2 Rift; without having to disable rift service and without putting Rift at primary monitor. The controls, however, are a little buggy (e.g., taxiing to runway - steering is a bit hectic but clears up). Is there a teak for clearing this up?

Thanks for the reply; I completely understand. I did however, purchase a '12-buttons at the thumb' mouse. Helps ease the pain of not seeing the keyboard at times.

Anyone know how to get Oculus going in Multiplayer? I unchecked the 'auto-detect' box in DCS (as mentioned in the forums), which enabled me to get into the cockpit with Oculus, but the Oculus was not operating (no motion & spit screen). Wondering when DCS will update. An increasing number of people are attaining the DK2, which would be in DCS best interest to keep with the updates. (People will most likely purchase all the aircraft in DCS with Oculus multiplayer working) Thanks.