Dentedend10

Hi, I've been able to set this option on my Pimax Controller buttons, which is really handy. However, it doesn't quite work as I hoped it would. I can press the buttons on the controllers to disable them as intended. However, pressing the buttons again doesn't enable the controller. Ideally I would like to enable and disable the VR controllers with the same button on the VR controller itself. It seems currently once the controller is disabled, no input is taken from it and I need to set up a different button combination to enable the controllers. Is it possible to have both enable and disable on the controller buttons? Thanks

Thanks that makes sense! I'll be more patient with startup next time Yes I think we are saying the same thing, that I have to 'abort refuel' before I can tell Paco to tank with the F10 menu

Hi, I'm reflying the campaign and so had a vague memory of this mission. After flying to Waypoint 1, which was 30NM south of Pagan, had to track back to Pagan to find the ships. Looks like an INS issue maybe? I did not overG my INS and didn't interrupt startup. If you think it's an F14 INS issue I can submit a bug there. Attached is my log. Another thing, simply the F10 menu did not allow Paco to refuel in the end. I also had to 'abort my refuel' to allow him to get there. Thanks! Tacview-20240805-164106-DCS-Speed and Angels - 12b.zip.acmi

Pimax Crystal user, Quadviews is essential. I am also disappointed that this was not caught, as it is obvious right as you load up the game with Quadviews installed. Not willing to go back to lower graphics settings and disable eye-tracking which is the single most important feature of high resolution headsets. This magic software by mbucchia made DCS not only look incredible but also perform reasonably for VR users. Please fix this ED

Thank you! With the F-14 for sure, haven’t tried F18 in while, but if I do I’ll report back

Thank you so much for this! I spent 4 hours trying to get it to work before I stumbled upon your solution. This should definitely be part of the manual for TX-Link and SRS integration! Thanks

Make sure you’re not hopping from one plane to another within one DCS session , even make sure you restart the FFB device between DCS restarts. I’ve had issue similar to that when jumping from let’s say the F4 to the F14 without all those restarts. Apparently it has been a DCS issue forever

The motion software has a key for turning the motion off. However, that also cuts power basically to the motion rig and the rig just moves to a gravity-directed position (nose down in my case). I haven’t tried recentering after that if that works. However, being on the catapult and having this nose down attitude would break the immersion

Unfortunately turning smoothening sway up to 90% or turning it off completely still results in a kick of the motion rig. Please fix this bugged telemetry

Yes this can't be good for the motion platform. Makes me not want to do carrier lunches even though it is the most fun part. Another problem I am having is anytime I get shot down, the crash telemetry carries on to the next session. That is when I sit in a new plane, the session starts with a huge kick of the motion platform, like the telemetry from the previous session's crash got carried through. This also happens even after a DCS restart. That is I dogfight, get shot down. Restart DCS. New session, and it will still start with the kick. This is not only bad for my motion platform but also for the heart Any idea what is causing this and if there is a fix? Thank you

Yep, I also noticed the difference in that instant action in that I can actually fly now with both engines out. although I still haven’t made it to the divert field

Yep, that was it. Just need to hold the horses and not rush to get up in the air

Thanks I’ll give it another try, maybe I was rushing it too much. I’ll report back

Hi, I've been learning the start-up and have been running into an issue during flight controls test. I seem to only be able to do one side of the ARI check, where the crew chief tells me that the rudder is back to neutral after engaging yaw stab and pulling the lever on the stick. When I do the same sequence on the other side (stick all the way to the side, yaw stab on (hear rudder kick)), when I pull the lever on the stick I do not get the ' rudder neutral' by the crew chief on this second side. Looking from the outside, the rudder does neutralize. It also does not seem to matter which side I test first, it's always the second side that doesn't work. Thanks for looking into this. I've tested on different maps during cold start instant action missions. By the way, I also absolutely love how the plane has all the REMOVE tags without the helmet on. Thanks for all these details

Can confirm. Tried it as part of start-up, but cannot disengage with abrupt movements

yes with the Rhino, 1 disconnect. I find it pretty stable initially, and once it gets heavy it starts to woobble, or maybe I should just retrim. I find it hard reaching for the trim though when I'm flying with tips of fingers for AAR

I haven’t been able to hear Jester either, was also on Nevada instant action mission

Hi, This happened twice in a row now. Cold starting the phantom in Persian Gulf or the Marianas quick missions results in abnormal hydraulic pressure on the right side. Left side is within normal. This doesn't seem to affect flight characteristics as far as I could tell, but it stayed high for the duration of the flight. On the ground, a repair was not possible to correct this. It seems to have occurred since last patch, although I can't say for sure (not sure if I cold started the jet on these specific maps before). Bug maybe?

Hi, id also like to add the perspective of a VR user who also uses controllers instead of a mouse. both the bombing table and the manual are really hard to navigate with the controllers. The reason is that both those windows can be moved around with the controllers freely . At times I want to adjust the values, but instead just grab the window and move it around. The scroll bar in the manual is unusable with controllers at the moment. It would be nice if they could be scrolled with the thumb sticks of the controllers. Currently the scroll bar on the right cannot be grabbed with the controllers, it just grabs the whole window and again moves it around. therefore, the manual is not very usable in VR with controllers at the moment. I prefer to use apps like Open Kneeboard. However, with the manual hyperlinks being bugged that’s not an option at the moment either. So please, fix at least one of these sooner than later so I can study the manual in flight thanks for this amazing piece of work!

Hi! id just like to add that FFB in the Tomcat feels awesome, and thanks for the development! I do have a question about it - once engines are shut down, on the ground, I was draining the hydraulics pressure by moving the stick all around. I was expecting a change in the feel of the stick, potentially requiring more force as the hydraulic pressure is gone. I did not feel a difference though. It’s more of a question, since I don’t have experience with real stick and hydraulics. Should there be a change in the force needed to move the flight surfaces? thanks!

Hi, After flying the Phantom, I switched to the F14 within the same DCS session. The force feedback implementation in the F14 completely went out of whack (pitch trim not working, forces acting very differently, such as no forces were felt around the centre at all). I restarted DCS only. Sat in the F14 right away, and FFB was working flawlessly again. My first flight within the same session affected my second flight in a new plane when it comes to FFB. I don't know if this is a DCS bug or whatnot, but if somebody is experiencing this weirdness, a DCS restart seemed to take care of it. This is on a Rhino base.

I wasn't at any extremes. probably around angels 10 and 3-400 knots

Hi, I've tried to tune in to the ILS for runway 31. I hear the morse code playing in the audio. I have the Bearing/Distance indicator on TAC, while the mode selector on ILS/VOR. The flag does not come on for the glideslope (with FD on). I'm not sure if it's a bug, but I was able to get ILS working on other maps before. Attached is tacview. Trackfile is too big to attach (80MB), but available as needed. Thanks! Tacview-20240602-183248-DCS-F-4E_IA_PG_Cold Start.zip.acmi

"Out deploys the Slats to their fully deployed position. Should the landing gear be deployed, both the Slats and Flaps will deploy. Out and Down fully deploys both the Slats and the Flaps. Should the landing gear not be down, the Wheels Light on the telelight Panel will illuminate and flash." There is no pure slats position. With gears down, flaps and slats come down in the middle position

I had this once and I believe it occurred during the MiG-29 instant action mission