2circle

I'm interested in downloading DCS 2.9 onto my computer, but am concerned that it may actually be a step backwards in the event all of the bugs aren't worked out yet. It seems like keeping my current version but then also downloading the latest version as described above, may be just the fix. Are there any downsides associated with this approach? I'm thinking in terms of key bindings, aircraft mods, campaign progress, etc... Any insight would be appreciated. Thanks in advance!

2 installs? That would be great - I have plenty of space on my drive. May I ask how to do this without purchasing another copy? My big fear is always that there will be some bug that makes it such that I'd rather go back to the previous version, but not being able to...Is there a link or video that discusses this? Thank you!

I modified the file to "false" and I'm still not able to go through walls using the object external camera view (right CTRL + F2). Works fine with the standard free camera view but then I have the problem of adjusting for the speed of the object (i.e. the super carrier). I'm still using DCS 2.8 - is this a new capability with 2.9? I've been reluctant to update due to reports of various bugs.

As before, thanks Dranconus. The problem was the last step. Even though the Jester menu showed GBU as being selected (and the HUD indicated ORD), unless you command Jester to select the GBU's, he will never give you the talk on needed to release the weapon. On a related note, how do you find using the LANTIRN at night? I find it essentially unusable. The red filter blocks out too much light, and even with the filter removed, I can find no contrast/brightness combination that makes the VDI useful for GBU employment at night. Interestingly, the RIO's scope works fine at night. After I cue the LANTIRN to the target, the target looks great in the RIO's cockpit, but it's completely washed out on the VDI. I'm playing Open Beta DCS MT in VR in case you think that's making a difference.

Thanks Wormeaten, I found a video online on how to get it. Pretty complicated actually.

Are you referring to the control I have highlighted? This one only becomes effective once I select FLY MISSION for me. If not, can you please direct me where to find it? Thank you!

PSA for anyone having issues with the start position when inside the hangar in front of the Su-27. I reset the floor in my PICO headset to be higher than actual when setting up the VR boundary. That way when you get into the hangar, the position is where it should be. A far less elegant solution that worked in the interim was to start a mission, reset the camera view, then exit the mission. When it put me back in the hangar, I was at the appropriate spot. Hope that helps someone... As soon as I can figure out how to request to move this thread, I will!

When it spins once airborne it powers the electronics in the pod. It doesn't provide any thrust (more drag actually!).

Cool pics!

OK thanks - that helped. The main thing though was to add the --force_enable_VR in the command .exe line (which I'm guessing I'll need to remove in order to use it on my monitor - for the mission editor for example). I find the graphics to be superior to my Quest 2 and once I was able to get it to consistently start, it's worth it just to have the cool air blowing on your face while wearing it! One issue though: when I get to the opening screen when I'm in front of the MIG in the hangar, I'm positioned too high and can barely make out the screen. I tried the view reset function on the right controller and although it shifts the angle, it doesn't lower the viewpoint to the correct level. I can click on a mission and then it puts me a few feet above the cockpit (which - fortunately - I can reset using the DCS keyboard command to reset camera view). Does anyone have any insight here? As always, thanks in advance!

Just FYI, the Prowler's ALQ-99 pods jam in all directions. It has steerable antennas inside it. In other words, it is just as effective in jamming while flying towards as away from a SAM site.

Sorry in advance for the new thread as I know there's a similar one out there already but unfortunately that discussion is above my head. I've been running DCS in VR mode on my Quest 2 headset mostly without problem. Because it disconnects every so often, and based on what I've researched about the Pico 4, I recently purchased one. Living in the USA, I was able to overcome the Virtual Desktop (VD) download problem, and am able to connect the device to my PC. Unfortunately, when I try to launch DCS, it never enters VR mode. Here are my steps: Verify VR mode is enabled in VR settings in DCS then close it out (I'm playing open beta MT), Launch the streamer app on my PC (1.28.1), connect the Pico to the PC, launch VD in the Pico4. I double click the DCS icon on my virtual desktop using the Pico controller and although DCS launches, it's like looking at my monitor through the headset - it's nowhere near a full 360 degree VR experience. It's almost like the headset is just repeating what the monitor displays. The monitor shows the image that I would expect if I were playing in desktop mode (different from what I'm used to seeing with the Oculus where the monitor shows a highly warped image). I've double checked VR mode is still enabled in DCS. I have Steam installed on the desktop, as well as the Oculus app. I do not have Open XR as I've never needed it with my Quest 2 in order for DCS to work in VR mode. I am not a computer science major, just a soon-to-be 50 year old who enjoys VR sims, but also has limited time. Oculus 2 was pretty much just plug and play, and I'm getting close to throwing in the towel with the Pico 4. Any help would be greatly appreciated. Thank you in advance!

Question for the group…I just received my Pico 4 and live in the US. I can’t purchase the VD app in the Pico headset and can’t find it in the App Store. Does anyone have a workaround for those of us that would like to stream DCS from PC onto the Pico 4? Thanks in advance!

I'm having similar issues with Jester and his use of LANTIRN. My scenario is as follows: DCS MT, 4xGBU-16, master arm on, 1688 laser code for the pod and bombs. I find several targets located near an airbase, ingress at 22,000 at 350 kts IAS. Command Jester to cue to the appropriate waypoint (which he does), I see the target aircraft on my VDI on the ramp, I then task him to "find aircraft". After a few seconds he finds the aircraft and states "valid laser ranging". And that is it! He never provides steering cues or time to release. I have him "undesignate" and then I command him to designate using the Jester menu. Once again, he states "valid laser ranging" but again, I never receive and steering cues or TTR, and am therefore unable to release any weapons. I've tried cueing using eyeballs, using head, a variety of targets such as armor or statics, but each time the result is the same. Any help here would be appreciated - I'd rather not have to learn how to be a RIO!

I respect their experience. As I've stated in some other threads, in some ways, DCS is harder than the real thing (in flight refueling is another example IMO). But there are ways to bridge the gap that don't detract from the "purists'" ability to make it happen without some optional help, and actually get us closer to being able to perform the aircraft to its max performance. Until we all have feedback in the stick we're using, or the seat we're sitting in, all we have are visual and audial cues, which unfortunately are not sufficient IMO.

I appreciate the feedback. I'll note a few things - as a pilot who has done quite a bit of air-to-air maneuvering over the years (although it's been over 15 since my last tactical sortie) - it's impossible to overstate the importance of seat of the pants feels and stick feedback (even the F-18 had an artificial feedback system) to determine how the aircraft is performing. All I'm suggesting here is that ED make up for this incredibly impactful deficit by giving us other tools with which to work that would improve playability and individual performance. I guarantee; no one is looking at the ground in the middle of an engagement to help determine speed, nor is anyone listening for the subtle audible noises some described above since the noise of one's own anti-g straining maneuver, sounds of airstream around the canopy, radio comms, guns firing, the ECS pumping air into the cockpit, etc. are way, WAY louder than the subtle noises that could be used in DCS. All I'm suggesting is some technology/a tool to help bridge the gap. This would be akin to displaying flight controls, or seeing a close up of the optical landing system in the super carrier module. For the true "purists" out there, no need to select this option. We just need to be realistic about the artificial nature of sitting in a chair vs. being in a dynamic cockpit with all sorts of non-audible non-visual cues that simply can not be replicated in a flight simulator (although the developers have gotten very close!). As a side note, these aspects are so important that there aren't even any simulator events in any phase of training in US Navy flightschool for any aircraft that focus on within visual range maneuvering. They don't even bother; it's the only training that's done 100% in the jet for the reasons I described above.

Coming from the F-18C, I was looking forward to the simplicity of the warbirds but am instead confounded by how difficult these airplanes are to fly. I started with the P-51 but found the accelerated stall characteristics made it essentially unusable for me coming from a fly by wire world where I can max perform the jet by pulling the stick into my lap knowing the flight control software will keep me from stalling or departing controlled flight. What would be really nice would be an indicator (like the controls indicator) that the pilot can bring up that somehow shows how close the pilot is to max performing. An indication of G, or AoA would be a start since without seat-of-the-pants feel it's impossible to pick up on the rumble that usually precedes a stall or know how hard one is pulling G's. Even better would be a real time diagram indicating where the airplane is with respect to speed (horizontal axis) and turn rate (vertical axis) with a max performance curve superimposed. This would allow the pilot to know with confidence whether he can pull harder or needs to let off rather than finding out by having the airplane depart controlled flight. Chuck Yeager's Air Combat, a sim I played in the 90's, had this feature and it was incredibly useful and taught me a lot about how to max perform an aircraft.

Thanks guys, I'll try a new cable first. It would be nice to have the headset charge while I'm using it in any case.

I've been playing DCS in VR on my Oculus Q2 for several months now, without any real issues - very smooth graphics. Lately though, it seems the headset just randomly disconnects from my PC (I have a USB 3.0 interface and use the Quest cable). It then takes me back to the VR default view in the headset, but my computer is still showing DCS on the monitor (paused, but not crashed). The Oculus software (which was previously minimized) appears in a window and If I catch it quickly enough, at the top of the Oculus window I see a red banner indicating that my hardware is not compatible. It's odd that it would work and then suddenly stop and disconnect from the PC. It's very annoying as this sometimes occurs mid-mission and it's to the point where I'm considering getting a different headset. Does anyone have any ideas? Any suggestions on an alternative headset that is more stable?

Wonderful! Thanks for sharing....I'll manage my expectations accordingly.

I'm playing DCS ver2.8.6.6.41066.1 OB with Oculus Quest 2 over USB 3 cable. The last few times the Oculus app just randomly appeared on screen mid game and caused DCS to terminate (not crash mind you, it just disappeared from the headset but was still on the monitor with no way to get back into it). I have auto updates turned off in the app (even though I already have the latest version of the software). Has anyone else experienced this problem? If so, any solutions? Obviously it is super frustrating. Thank you.

I'm having similar issues with this functionality in open beta 2.8.6.41066.1. I'm trying to set up a DCA with 2 CAPs; a section of F-14's in the North and a section of F-18's in the South. I select group task of CAP and set up a search and engage zone for the F-14's (the player is on the south CAP so I didn't bother with any AI tasks) that should force it to only engage targets approaching its CAP station. ROE is weapons ONLY DESIGNATED. Despite these parameters, as soon as a bandit group appears from the East, the F-14's from the North race all the way (about 80miles) from their CAP (leaving it undefended) to go after bandits in the south CAPs area of responsibility. Does anyone have any thoughts on to force the North CAP to not engage bandits outside of its AOR? The search and engage function appears to be broken. As a separate issue, they were also engaging targets before arriving on their CAP, which I fixed using a START condition for the search and engage enroute task. Thank you in advance.

Hey that worked perfectly! May I trouble you with an additional question? Now that I have the new section on station, I want them to just set up an orbit until a specified time/BINGO fuel, during which I'd like for them to engage bandits in a specified zone. I found the advanced waypoint actions options and built an orbit over a waypoint in their flightplan, but the AI fighters didn't bother to engage any nearby bandits. I then added an enroute task of "search then engage in zone" and defined a zone that was transgressed by numerous bandits, but they never engaged any of them. Might you have any additional guidance to help me accomplish my goal? Thanks!

Would anyone know how to enable the following scenario in the ME? I'd like to place a couple of F-14's orbiting on a CAP, and when the player (as part of a section of fighters enroute to relieve the off-going CAP of Tomcats) comes within a set distance of the F-14's, have the F-14's RTB, so that the new section of fighters can assume the CAP. In other words, have a group go from CAP/orbit, to fly to the next waypoint in its flightplan based on a trigger? Thanks!

Yes, S/B out is standard. And yes, the tanks were essentially bolted on for all practical purposes. The only time I ever saw jets without them was at the RAG during training.