Ziptie

CAT 1 and CAT 2 are the same for the hookup issue. I have disabled track file writing with my autoexec.cfg file - working to fix some of the stutters and stop from writing huge files to my PC. It's easy to replicate. Very easy. Haven't launched from CAT 3, so cannot comment on that one. CAT 1 and CAT 2 are the same every single time. There depressions of the U key to get the aircraft's launch bar to hook up to the catapult. Two in quick succession, you will then get the radio instruction to taxi to parking area - then a single depression of U to get hooked up to the CAT. I run zero mods, vanilla DCS. Cheers, Don

You should not have to adjust the trim of the F/A-18C while formation flying. As another stated, the FCS auto trims to 1G. Only once you have an asymmetrical configuration, should adjusting the trim be something that you have to do. If it is wake turbulence that you are experiencing, which is wildly over exaggerated in DCS(another Hornet should not "throw" you around like it currently does), it just requires you to be very active in managing the attitude of the aircraft. Cheers, Don

This issue was not present prior to 2.5.6 with the settings that were used in 2.5.5 . I can also confirm, this is an issue. VR user. Cheers, Don

I notice these from time to time as well - using VR. I delete my FXO and metashaders2 folders every time prior to starting DCS. Cheers, Don

This is exactly what it takes. Double tap of U (quickly) is what it takes to get the call to taxi to parking, then a single press of U to get the cat to hook up. I can never understand why these types of things get labeled as "missing track file" or replied with "please post a track." This is incredibly easy to replicate, and can be tested in just as quick of time. I imagine that the devs/mods are currently using the new super carrier in their builds and are just unaware of this issue as they are "busy." That being said, things are being dropped, and in a relatively big way right now - a trend that really can't (or shouldn't) continue on the current direction. My .02, as someone who has alpha and beta tested numerous games. I, along with numerous other people have experienced this issue and is clearly not an isolated incident. Cheers, Don

2.5.6 has introduced this on aircraft. It even happens on the A10C, and only on the left engine. Probably just a "kink" with the new coding. I also hope that they will sort this out. Cheers, Don

On the IFEI, are the engines in sync? Cheers, Don

The jet was safe’d up, so that might have been my problem. Was just scanning for targets. Cheers, Don

Is the HUD pitch ladder supposed to cage and uncage when the FLIR is SOI? Don’t seem to recall this behavior prior to 2.5.6 - but noticed it was occurring while flying earlier today. Seems prior to 2.5.6 , you would have to make the HUD SOI when caging/uncaging the pitch ladder - now it does that, even while having FLIR as SOI. Either a bug, or real life accurate - just looking for clarification l. Cheers, Don

Any update on the warning you were seeing, or are you good to go? Cheers, Don

In the DCS general bug / question section. Could check the VR bug section. You can type “static1” in general search. One could use the all powerful “Google.” Many options available. Many returns on searches. Pick your poison. Cheers, Don

CW = clockwise CCW = counter clockwise Maybe that will help. Cheers, Don

I will take a screen shot tomorrow for you, to show you the bindings. They are there, I use them (not only for the A10C, but for the 18C and 14B). Cheers, Don

Look for the keybind throttle idle/off. Bind left and right accordingly. Cheers, Don

And yes, I was online. Cheers, Don

You do have the visual indication on the HUD of the weapon release by the "flash/blink" of the store on the lower left hand corner of the HUD, as well as the store disappearing off the DSMS display. But yes, the sound that used to be present is no longer there. Personally not an issue, but I can see how some might miss it. Cheers, Don

Yes I was, and it was CAT 1. Also tested on CAT 2. Didn't try 3 or 4. Cheers, Don

Sure, situational awareness is mandatory and without it GCI is useless. That being said, to quickly turn off a few settings like detection range upon entering the server the first time really isn't any kind of issue. If a GCI is struggling with that, I'd be concerned with the guidance they are giving me for vectors and other information. My .02 Oh and LotAtc is what is needed, and with this you don't have to worry about the nonsense that may or may not be present via the F10 map. Simple to setup and worth the investment. Cheers, Don

It simply changes your approach and and what happens if/when you stray from a good alignment with the drogue. Cheers, Don

Update: The logic is actually still reversed..... Argh. Multitude of testing today, and the carrier still causes a memory leak. We have had to remove it from our server once again..... Although it was fine for awhile, but then after a handful of hours, it decided to spike server memory usage and poof. Crash. In regards to the logic for rendering in both eyes, is has to still be coded as: options.graphics.stereo_mode_use_shared_parser = true in order for both eyes to render things at distance (like cons from an aircraft). This still makes it so the flashlight in the F/A-18C cockpit, for example, is only rendered in one eye. What is going on with this.....? @bignewy @nineline Cheers, Don

A Workaround for not hooking to cat on carrier: Be on the carrier freq, request taxi, get to cat, lined up properly, DOUBLE tap U quickly, they will say taxi to parking, press U once more and you will hook up. Just tested 10 times, worked every time. Cheers, Don

Indeed. Just checked for you fitness88 and LeCuvier beat me to posting it. Cheers, Don

Indeed, still present after recent 2.5.6 introduction..... https://forums.eagle.ru/showthread.php?t=264494 Cheers, Don

Thank you sir. Not sure what to think, either I am lucky that I have not needed to repair the aircraft in that long - or that it is confusing that the issue has been present that long and still not fixed/addressed. @BigNewy / @NineLine - and information on this? I know there are bigger irons in the fire at the moment, concerning 2.5.6 - just making sure this didn't slip through the cracks. Cheers, Don

Adjust the brightness knob(s)....... Cheers, Don