Turkey_Baster

Problem solved, Oculus updated to V68 and I had to disable OpenXR toolkit.

Hello, Tried a repair, reinstalled and no matter what it will not run in VR. Can someone please advise me based on the log file? dcs.20240717-022040.log

@Victory205 Thanks for the reply, What type of seat-of-the-pants feel did Pilots use to help them make Power adjustments to maintain Glideslope? Was it a heave or a settle type feedback? I assume watching the FPM or VSI was secondary to experience and feel? I remember you even mentioning that Pilots rarely used the HUD on the Tomcat. I'm trying to build a Motion Simulator to provide some of that feel so that us basement Flight Jockeys can add a little more realism and authenticity. Thoughts?

@Victory205 How often did pilots use Auto-Throttle on the Tomcat? If power corrections are so critical for glideslope, especially in CV landings (LSO literally calls it) I would assume most pilots didn't use it at all? Was there a time when it was required?

@fat creason While it is frustrating to relearn things, I'm still grateful for what you and Heatblur have recreated here. I'd rather it be accurate than easy. Thanks for all you do.

If its accurate, I can learn to work with it. It's still frustrating when you achieve a satisfying level of competence flying the airplane, only to have it change and become difficult again. The original Burble was extreme and very difficult to manage and they refined it. I have a feeling that this will be the case here too. The A model in particular behaves exceptionally different on speed than it did a week ago.

I fly VR exclusively with an Oculus Rift S, my "Light Bloom" setting is off and Gamma is set to 2.2. To echo what others have said: -The Flight deck is way too dark. Its incredibly difficult to line up correctly, even if you hit the groove at 0.5 in the middle of the day. -The IFLOS Datum lights are extremely bright. Super Carriers are already hard to read, but I can read the Meatball from about 0.7 NM out. With these ones, I get about 2 seconds of useful ball indication as I come over the ramp. -Night lighting on the deck at this time makes the module unusable in in the dark. I understand that VR users see things differently compared to people using a Flatscreen, I wonder if there is a happy medium like the Supercarrier currently has?

I bought a DOF Reality H2 this past month. I have successfully gotten it to operate on the Sim Tools App, but it will not pick up Telemetry from DCS. I've followed the trouble shooting guide on the Sim Racing Tools Website and I can't get it to work. I am using UDP 9800. I have disabled my Firewall and unblocked my UDP Ports, I have reinstalled multiple times. I put the Export.lua file from the Simtools folder into the DCS Saved Games File as the instructions indicate. I'm at a loss and have no idea what to do at this point. Has anyone else dealt with these issues? Any guidance? Thanks,

I’ll tell my lead IronMike says he sucks at formation flying :) Seriously though, thanks for the info.

Mike, Surely 2 identically configured F14A’s should fly at roughly the same speed with minor throttle corrections to maintain a formation rather than the wingman always needing to hit the speed brake to keep from surging ahead when both are at idle? The B does this without issue. The A doesn’t, in my experience. Anyone else having issues keeping the A in formation with another Human controlled A?

I also want to chime in regarding the flight behavior of the F14A flight model vs the B, especially at low power settings in subsonic flight. When doing the landing pattern with my lead (live person, not AI). I can't for the life of me stay in formation, particularly when descending when my lead is at idle and so am I. I always surge ahead, he can even push up the throttle to 3000 PPH Fuel flow and I still pass him repeatedly. (Both aircraft have the same fuel state and stores/wing sweep auto etc..) I will speed brake, start slowing down but once I retract it, I will start to shoot past him again. Even if I am in a lower throttle setting. 'In the B its silky smooth. Its also much harder to keep in position while in formation at any speed. I'm used to the nose in the B dropping and raising when moving the throttle. The A doesn't seem to do this. I also find it really likes to coast and won't react as suddenly to the power settings as the B does. This is especially apparent like another member mentioned when doing the overheard break at the boat. It does not want to slow down without engaging the speed brake. I tried a SHB at 600 KIAS and by the time I was in the groove, I wasn't anywhere close to On Speed. With the B its perfect. I'm not an aeronautical engineer but with the engines at idle shouldn't both airframes slow down at a similar rate when banking at 60 Degrees and pulling back on the stick? I look forward to the continued refinement of the Heatblur F14, I just wanted to add what I have been experiencing. I can't thank both Heatblur and the SME's enough for creating something that is truly special. I have had 30+ people try your product out in VR in my Simpit and everybody was astounded at what you guys have created. Both my Brothers and I fly online together and we only fly the F14. Thanks for giving us something we didn't know we needed in our lives. Justin