Majik

This. In fact, in many ways, the UI, operations and workflows feel far closer to an F/A-18 than F-16. It's all marketing, any real comparison to the F-16 is kind of moot.

Thanks! FWIW, if it helps anyone at ED, I had the same issues before and after the hotfix update, as I repaired and updated (during one of the many breaks I needed ;))

After the TGP updates I've been keen to get back to guided bombing in the Viper, which I hadn't done for a month or two, and never had any issues in it or the Hornet. However, every GBU I now drop lands hundreds of feet away (usually ahead of the target). Thinking it may be a problem with the way I'm lasing (usually about 15 secs before impact), I went to the Hornet because of the autolase, and had exactly the same problem. I've spent hours today flying different profiles; altitiude, speed, pitch, heading, straight through, offset after release, lasing for different lengths, in different missions, with different pressure settings and wind, and in probably more than 40-50 bombs (12s and 10s), a SINGLE one hasn't hit anywhere near its mark across the two modules. Curious, I took up the JF-17, and hit four targets first time, everytime, on a mission I used for the others. By the length of the misses, it looks to me that the CCRP release cue is coming down too late for me, pushing the GBU outside of the laser's reach. Or maybe I'm missing something :cry: I've attached a track in the Viper guided munition instant action mission. At the end you can see just how far the misses are. http://www.mediafire.com/file/h1ave5nv1neypcd/GBUmiss.trk/file

Strangely, I had no issue at all today, even with 0 deadzone. Probably my stick playing up (used to have centering issues a while back). Timing of this thread was indeed coincidence it seems.

That would line up with the Hornet's AP. Chuck's guide recommends a small deazone for exactly that reason. Will test out, as currently have 0% deadzone. When I first had the issue, I also had the magnetic alt hold stay in place most of the time I tried, and sometimes popping out immediately, which is probably confusing the issue.

I had issues with the AP yesterday as well. Put it into ALT hold and STRG select, and neither worked. Didn't have the time to investigate. Will have a go again tomorrow to see if it was a one-off, or there is indeed a possible bug.

I've found reducing Y Saturation to be helpful in addition to negative curve with a 10cm extension. I'd recommend trying it. I'm playing around with the settings still, but at between 70% and 60% for both roll and pitch, and curves of about -10 and -7 respectively. Much better than the -15- to -20+ curves I was forced to use before. In the recent survey, I asked for this to be addressed. By far, the vast majority of people have displacement sticks, and at the very least an alternative option needs to be made available in the special settings tab.

Oh man, don't remind me... Been using custom voice mods for so long because of exactly those tactics... Had no idea EN2 was accurate, will have to try it out more and get used to it. Thanks.

Are the caution/warning audio sounds final? EN1 or EN2 surely can't be what the real jet has, can it?

Did you use a channel 63 higher than the what the Tomcat was using? Have a look at this video:

+1 on the above.

haha could be worse! :thumbup:

Good to hear, thanks! p.s: shouldn't you be on holiday? :smilewink:

I was watching an old Bunyap video on Tonopah, and honestly, the more I read and think about the "brain melter", and as more and more options get refuted, the more I'm convinced we could be looking at an F-117A. It's out of service, outside of stealth not technologically superior to some of the gen 4 stuff we have (in terms of systems), and certainly fits the brain melter moniker. After the F-16, ED has a relationship with Lockheed. Stealth modelling doesn't need to be detailed; the in-game AI model already has a low RCS, so something along those lines making it low-observable could easily be modelled without divulging anything. It also nicely fits this quote: "it isnt as new as to NOW. It's a challenge to fly, and is a milestone."* source -ED tester https://forums.eagle.ru/showpost.php?p=4373623&postcount=992 Bunyap mentions that the "too-classified" discussion always comes up when talking about it in the below linked video (around 10:27), but that it's not really true, and I'd trust him on that statement.

Thank you! Definitely helps!

Also getting this. Have to go back and edit every single post I make to remove the extra spacing, and occasionally double spacing still gets left over

Ah, I figured that might be the case. Still, will be nice to have both available on the stick, as opposed to one or the other right now. Makes complete sense. I have no idea how you're even able to come up with the complexity of your system, it blows my mind how much can already be done. CTS is the reason I'm playing DCS as much as I am. I filled out all of the surveys pertinent to my setup a week or two ago. It may have been worded differently, but I'm pretty sure I left a comment about vr zoom on /I H4 as a suggestion for 3.0.

Amazing, thanks!! :thumbup: Would it be too much to ask for the option in the values menu to swap the damper and limiter between S3 and 4, (if having a held function like limiter doesn't conflict with the shift function)? It'd be nice to see which way works best, as mentally, having limiter on S3 along with NWS might actually make sense, seeing as they are both movement range expanders, and the real plane has damper cutoff on the pinky lever. Also, is there some way or setting I can use to get/cheat the comms switch in the F-5 to work with mutilple radios on SRS (used with vaicom)? Every direction registers as button 20 (TX1 on vaicom), which makes sense with the jet only having one radio, but limits some function online. Finally, I've mapped both VR zooms to shifted H4U and H4D. Works really well, only overwrites redundant dogfight SW centre binds, and meshes with the F/A-18 and JF-17 zoom. I may have mentioned this as a potential good universal vr zoom option on one of the surveys. I use these mappings for all the jets I own, except the F-16, where it doesn't work.

Agree with all of this. I thought I was maybe imagining cockpit backlighting getting worse in the last few OB updates, so I downgraded to 2.5.6.49718 (just after SC launch) yesterday just to check, and the lo-and-behold the lighting was so much better. Differences between cockpit and outside was better at around 1.7/1.8 gamma, and cockpit back and floodlights could be seen fine even in the daytime. Hopefully they roll back the lighting to how it was around the time the Super Carrier launched. It wasn't perfect, but much better than 2.5.5 and what we have now.

I've just learned that the F-5E has a roll limiter on by default, halving the roll rate. Would you be map Aileron limiter override (default binding "L") on the stick please? I currently have it mapped on S4, losing pitch damper cutoff, but was thinking it might go well on S3 in GSU. I've also mapped drag chute to S3+slew push, which I find to be useful. Might also be good on S3+left throttle button (short tempo).

One of those other things is the AOA limit with gear down, isn't it? Because this thing just won't turn in on base and final when CATIII. Kunsan tower wouldn't be happy with me if I couldn't make the runway like this everytime ;)

+1 Bignewy, the easiest way to spot the issue that I've found is the Nevada Cold and Dark Instant Action mission for the Viper: Look straight ahead at the two ground power units; in one eye you can see each individual wheel/tire with no shadow, and in the other all you see is black under the cart.

Thanks for having a look, and letting the team know. For me, it's most obvious to see in clouds when flying around the SuperCarrier, but even then it doesn't always occur (but more often than not). I even get some of the effects on the main menu, when looking at the icons at the bottom, so it's prevalent throughout. If the team needs more info than some great posts from users in this thread, there's also another simialr thread linked below: https://forums.eagle.ru/showthread.php?t=271890 For what it's worth, I have the problem with a Reverb. I have seen in both threads, other Reverb users have this problem, as well as Oculus CV1, HTC Vive and Valve Index as well, at the very least. So that rules out any specific platform. If the team are aware of anything that changed between 2.5.5 and 2.5.6, that would be a good place for them to start. Perhaps everyone who's having this problem can post below with their headset: +1 Majik HP Reverb

You're right, I was confused myself as I just went back to watch it, and realised he was already at Rmin. Thought it was a seperate cue for missile to target range.

According to the video by Wags, it's the range to the target