Ziptie

+1 Cheers, Don

Seems to be fixed now eh? Cheers, Don

Launch aborted could be a few things, but most likely that you are not depressing the weapon release button in the correct parameter of the pipper indication. Point track: With TGP as SOI, TMS forward short. Cheers, Don

Not experiencing this issue on my side. I have "mouse cursor confined to window" selected, in the options menu. I personally drag the windows start bar to the left or right side of the monitor screen before starting DCS, so I can prevent having any conflict with "the outside world." I have Lalt+Enter before, to get full screen on the monitor, but never have done that again after learning to simply relocate the start bar. latest version of 2.5.6, Oculus CV1. Cheers, Don

You can also simply select your wingman order with the function key(s). Cheers, Don

You are not alone. If you create an autoexec.cfg file and place it in your saved games/dcsopenbeta/config folder, make sure to include the following line: options.graphics.stereo_mode_use_shared_parser = TRUE This is backwards logic, as prior to 2.5.6 it needed to be = false (to render all objects in both eyes). Please see my above "tip" for the OP. I have messaged you and NineLine about this, on Discord and if I am not mistaken, here on the forums. I have confirmed it multiple times. With it set to "true" the flashlight doesn't render in both eyes, with it set to "false" the flashlight does render in both eyes - but then distance objects (aircraft contrails for example) do not render in both eyes. Prior to 2.5.6, all objects were rendered in both eyes with the following logic: options.graphics.stereo_mode_use_shared_parser = false Cheers, Don

Probably help if you posted this somewhere other than the VR section.... Not sure how trackIR works, but 2.5.6 works well for me, in terms of view(s) with VR. Cheers, Don

Search before you post for sure. https://forums.eagle.ru/search.php It's been acknowledged and reported already. Cheers, Don

Carrier is working.. Back in the MP server that we fly in. Launches, landings, rearm/refuel. You update? I can also say thanks ED. Is it perfect? Of course not. Could it be? Maybe. Is it moving in the correct direction? Definitely. Cheers, Don

Don't see what the issue is, you can just deselect them right? It's a rare day that I even use the F10 map, so probably on for me all the time if the "issue" has been going on this long..... You don't have an F10 map IRL, maybe try not using it in the game, for immersion and reality merge? Cheers, Don

Copy, thanks for the information. As advertised, I don't often have to do a repair but needed one yesterday, so was unsure if this was a normal/pre-existing issue. Will just have to be back to my normal self and not have the need to request a repair from the ground crew! Cheers, Don

Ah, ok. I use the digital one via the HSI for those things, but different preferences for everyone. Well back to your original question, not sure if there is a bind for the rotary adjustment on the altimeter. Will check tomorrow and see if I find something for you. Cheers, Don

I’m kind of curious why..... As in, there are times you want it to alarm and have your reminder at 100 feet and then there are times you want it at 600 feet? Please explain. I know everyone has their own methods, but this is intriguing.... Cheers, Don

Probe light is dependent on the external lights being toggled on. Worked reliably in 2.5.5 . Actually haven’t checked it in 2.5.6 - but during a daytime AAR, the light was visible from F2 view. Cheers, Don

Congrats. Yes, I fly with wake turbulence. Most should, unknown how many do and don’t. As another stated, you shouldn’t approach the tanker from it’s dead 6. Should be offset to the side your drogue will be contacted, then ease in for contact after being cleared. AAR is good practice, for future AAR and for formation flying. Cheers, Don

I’m talking about the switch on the UFC, that changes between barometric and radar altitude display on the HUD. Never have looked into binding the adjustment for your radar altimeter warning (the picture you attached above). Out of curiosity, wondering why you’d want to map that..? You set it on the ground and good to go.... Cheers, Don

Yes, this is an issue. You now have to be quite properly lined up with the catapult, no longer can be aft of it at all (which I am completely ok with as that is how it should be). However, even when on the correct frequency for the carrier, requesting startup - it often doesn't give you the option of requesting taxi to "runway" and often times requires multiple depressions of the "hook up key" which is U on the keyboard for factory binding. Also, if you then retract the launch bar after being hooked up to the catapult - it will disconnect you from the launch bar. Not sure if that is correct IRL behavior, as we don't have the hold back bar currently and I have never launched from a carrier in real life (but could be somewhat sure that I have seen in cockpit videos of pilots toggling the launch bar back to the retract position after being hooked up to the catapult). Cheers, Don

Noticed today. Had an "incident" on takeoff with another aircraft and lost part of my left wing. Was able to get a MAYDAY called and turn back immediately after wheels were up, touched down on the runway. After taxi, shut down the aircraft and requested a repair. Repair completed, started aircraft. Steam gauge attitude indicator was unable to be uncaged. Left and right LEF were unable to be symmetrical with flaps in AUTO, only in HALF or FULL. Radar altimeter could not be adjusted and was "stuck" in one position. Anyone else experienced this? I don't often damage an aircraft and have to request a repair, so unaware if this is a problem that has existed previously or occurred after one of the most recent two patches / hot fix. Cheers, Don

Yes, there is a key bind for each of the radar altimeter settings for the F/A-18C Hornet. I have the Warthog HOTAS and use the "A10C" autopilot switch to accomplish this. The "PATH" setting is for Baro altimeter setting and "ALT" is what I use for radar altimeter setting. In other words, forward on the switch is forward in the cockpit, and aft is aft. Cheers, Don

Is it the flare from lighting? I noticed that when an explosion occurs, or a higher intensity light source is in the Litening pod's display, it "flares" the screen and makes viewing difficult or impossible. This is somewhat accurate. Either way, try deleting the contents of your FXO and metashaders2 folders, located in your saved games DCS folder. Could be a possible issue if you haven't done so after either the patch or the hot fix...... VR user here as well, all good on my side. Cheers, Don

I just flew two night missions, one in the F/A-18C and the other in the A10C. Was great for me. VR user. Gamma set to 1.5 . NVGs are certainly needed at some points of the mission, as most likely the case would be IRL, and adjusting the intensity of the NVGs is a must when you are transitioning from light saturated areas to non. It's certainly not perfect yet, and not sure anyone would have expected it to be in this early stage, but much much better than it was in 2.5.5, at least in my opinion. ^^ Maybe this is what the issue was for you Zlin? ^^ Cheers, Don

Nice, thanks for the info! Cheers, Don

Cool Cheers, Don

Well it's all custom script / code, doesn't really even use the mission editor, so I can't be certain. Cheers, Don

For me, it seems when the sunlight hits the DDIs / AMPCD, the hue changes to a more yellow color. When the sun is at my 12, the displays are green. I wasn't suggesting that you are flying at night with them in daylight mode - believe you misunderstood my attempt at helping. Best of luck, all good on my side. Cheers, Don