FlyAnyTime

The F-4 HUD displays the radar when MSAA is used see screen shot and is normal when DLSS is used second screen shot. Anybody else have this issue. Just started with last update.null

I have a physical cockpit that has heptic feedback through the stick and would like to useit in VR, however I cannot disable the "Hand controllers use cockpit stick" option on the VR settings tab.

Capability request: The ability to provide instrument data and screens information like MFD, RWR, etc when the option to display only the HUD is used. This would help those like me who build home cockpit simulators achieve a more life like simulation. Currently all data to instruments and displays in the cockpit are stopped when the screen is in HUD only mode. The ability to use the HUD only mode when a full physical cockpit exits would greatly improve the immersion of the sim. . Currently when you go into HUD only mode all data to the instruments that was previously being transmitted via scripts on screen exports is stopped. While the buttons still function no data is being updated on the exported screens and instruments.

As a pilot my only experience has been with propeller aircraft and that is limited to three, Cessna 172, Piper PA-24 Comanche, and a Beechcraft T-34 Mentor. As a passenger I have flow in many aircraft going back to when I was a child in the 1950’s. While in the Navy I was stationed on the Aircraft Carrier Kitty Hawk CVA-63 during the Viet Nam war, long before the Hornet was a concept. So, I have no experience as a pilot of high-performance jets. My point in this is that I do appreciate the desire to achieve an as realistic flight model as possible. In my case, I simply was not expecting such a dramatic change in the flying characteristics that I could go from landing consistently to not at all. I know I’m old and its hard to teach an old dog new tricks. I was able to finally make a successful landing on the ship this morning but it was not pretty. Any instructions on make the change from the old model to the new in terms of control inputs would be appreciated. As I stated earlier, I would use the trim control to get the velocity vector to the center of the e bracket. I would only have to change trim if I was turning. In the turn I would use roll to keep the E bracket and velocity vector aligned with the horizon, on the rollout I would have to trim again and use the throttle to adjust the decent rate. I would not use pitch at all during the landing process. Now the throttle to adjust decent rate seems to be replaced with use the trim? Am I interpreting that correctly?

Yes, I use to use the pitch trim to set the velocity vector into the middle of the e bracket and I would use the throttle to keep the elevation of the ebracket and velocity vector on the required flight path. Now it is almost impossible to keep them togeather. Before when I hade them set all I had to do was was just bump trim between turns and straight and use throttle to control decent rate. Now it simply impossible to control decent rate with the throttle after I have the velocity vector aligned in the middle of the e bracket. I wish I could take a video of before and after to explain it.

The new FA-18 flight model seems for me to be terrible. Before I could easily land on a carrier and control AOA with the throttle with approach speeds anywhere from 125 to 140 and land with out blowing out the gear. Now the AOA control with the throttle is almost non-existent and in order to get the AOA to raise up the speed goes through the roof. It is almost like I had a good flight model before that I could control AOA to one that balloons like crazy and is so unstable at low speeds that it’s impossible to land without collapsing the gear. Is there a way to get the old flight model back?

Just installed F-14 and current open beta in Steam and have lost all ability to setup controls - controls are shown but not recognized when trying to bind axis. I have Saitek X-36 HOSTAS, MFD Cougar V1 panels and CH pedals. I used the Steam File verification and renamed the DCS folder under saved games. While the startup of the application was changed and did go faster however the useability of the F-14 did not change. When trying to configure my controls the application would not recognize the controllers axis while I was trying to bind. For example I was able to bind my Saitek X-56 left throttle lever on the first attempt to the left engine thrust. However when I attempt to bind the right throttle lever to the right engine thrust it fails to recognize the controller. If I go back to the left throttle to confirm the setting it now fails to see it as well. I then attempt to force the binding by manually setting the preferred axis using the dropdown option. When I go to try and fly the F-14 the game again hangs on the startup screen (see attached). I have tried waiting as long as 30 min without any change and ultimately just kill it. I have attached a jpg of the hung screen and latest log file and DiagDX results. Does anyone have a solution for this set of problems?

Thank you for your comments! I took a look at Voice Attack and find it to be very interesting! I like to use my Oculus Rift most of the time which is why I went to a full function HOTAS setup in the first place. I believe that something like Voice Attack may be just the right solution - util virtual touch controls are fully implemented!

Which is better when using a programmable HOTAS like the Saitek X56: 1: Use the Saitek Software to program key stokes and the DCS controller setup to map the axis. 2: Use the Saitek software to un-program the controllers so that most of the controllers buttons and axis are visible to DCS and use the DCS Controller set to map all the functions. Thank you in advance