darkman222

Time for permadeath in DCS Btw: In your video what the R77 does seems like a bug or a tracking error of the missile. Dont expect this to happen too often. How to defeat the R77 missile is easy. Just stay away from it How to kill the bandit who fired the R77 at you while staying alive is another question. Quick guide: -Try to get to the same altitude as the bandit. That helps to get a lock quickly. -Climb up and fire your AIM120 when it in range -Put the bandit on the right or left gimbal limit of your radar. -Go nose down approx 30 degree, throttle to idle (helps to keep the distance, you dont want to run into his missile) -wait until your Aim120 gets pitbull aka self guided ( the "A" with a number changes to "T" with a number) -break lock, full throttle afterburner, dive to the deck and run away for a minute or more -if bandit is dead: good. If not: recommit and repeat the steps above. Disclaimer: Your RWR will yell at you that a missile has been fired. You can turn away of course at that point. But dont expect that you will ever be able to guide one of your missiles to the bandit that way. You have to stay committed to the fight to guide your own missile, then defeat the R77. Finding the sweetspot between the two is what you have to learn.

I guess the simple reason for people using MSL Override over A-A is that MSL Override is bound to the Hotas and much quicker accessible. But its a valid question. Yes you can have different MFD setups, search settings in MSL Override and A-A mode. But apart from that, do the both modes have a difference or one or the other an advantage?

Using a Winwing F16 EX Throttle now, but I have been using a warthog throttle before with the same issues. Scenario is as follows: I am sneaking up on a bandit with DGFT switch enabled. No Rad is displayed. I press cursor enable, like in the real jet. I slew the Aim9 seeker on the target. But while depressing Cursor Enable I slightly move it which enters ACM slewable mode. I exit it with TMS down and still keeping the Aim9 seeker on the bandit. Again a slight movement of the radar cursor while holding cursor enable depressed activates ACM slewable again and the bandit gets finally locked by radar and now knows I am there. Question is: In the real jet, how un-sensitive is the cursor enable switch so the real pilot does not happen to do the same as me and move the radar cursor enable switch by accident? Or does a cursor enable depress deactivate the movement / radar slew. That would be a solution to deactivate inputs from the radar cursor hat while depressing it. Looking for two solutions here: -Is there a way to disable radar cursor axis input while holding cursor enable depressed in DCS? -How would I do it in Winwings SimApp. The command could look like: While button depressed->deactivate x+y axis input. Or is there a third method I did not think of? Here is an image of the ACM slewable function I am talking about, so everybody is on the same page. It auto-locks a bandit in front of the aircraft, no matter if you want it or not. EDIT: New idea for SimApp Pro: It might be an idea to swap the radar cursor axis to an unmapped axis while depressed to disable axis input while being presses. Looking into it now.

...only if it does not affect performance please. My high end PC is struggling with all the eye candy already.

The Winwing force sensing base does not feel right to me. I own both. Winwing and RS. The Winwing base feels like you can move it and then it suddenly stops moving but is still force sensing. While the RS one accepts pressure throughout while giving the same amount of resistance.

Thank you! It does not make too much sense in my mind if it does not work the same way for the 9x. So I was wondering if it was really that inconsistent in the real jet.

When using Aim9M or Aim9L sidewinders the Aim9LM comes with a warm seeker. If I press "warm" on the MFD it is set to be cooled. Now I switch to another AA weapon (Missile Step on the Hotas). Might be a 9x or a AIM120. The seeker of the 9LM is being set back to warm. But if I try the same with the 9X the seeker stays cool. Intended behavior or bug? Is the warm/cool behavior modelled in game anyway?! See track and video: aim9m_warm_to_cool_aim120.trk aim9m_warm_cool.trk

Sorry for bumping, but I am interested in knowing if your IDF Sufa F16 also has a slightly different flight model than the F16C from ED?!

As you can see in my first post, thats the exact command I have bound to my hotas. Also pressing the keyboard shortcut stopped to work on certain servers. Like I said it works fine on some other servers. But the server admin does not know whats different on his server.

Nope. I changed nothing. I go on the one server: works. On the other: does not work. Go to the first one: works again.

Was something changed due to pure scripts / anti cheat last update? I am playing in VR and due to the nature of dogfighting, dying on dogfight servers is very frequent. So I bound the "respawn" command on my throttle, that I dont have to fiddle around on my desk for the mouse while being basically blind in VR. After the last update it seemed to stop working. Although it works fine on other servers and in SP. The server moderator does not know anything about the issue. Does someone here? null

That does not make sense. If the IFF transponder is damaged or just off by mistake is enough to get you shot down by a coalition aircraft? If it is that way, what the tag which was added later ( maybe by a moderator) to my post suggests, that it will be predefined in the DTC, which aircraft types are hostile and which are not, it still does not explain if it is possible to differentiate between a friendly and a hostile aircraft of the same type. Maybe I would expect some kind of "error" or "undefined" message but not a clear destinction in hostile and friendly.

Even on a not so busy mission with some distant SAM sites. Seems like the threshold that defines when its a new or an existing RWR contact is set way too low. Time wise. I try to get a track out of it. But I think because the SAM site is behind a mountain wall it starts to make the RWR go crazy, when it gets obstructed and then visible to the RWR again.

Question about NCTR (Non-cooperative target recognition) used with a TMS left long press. I have a mission with only me in a blue F16 and another blue F16 and a red F16. No AWACS. I can lock the red F16 and run a IFF interrogation on it. The blue F16 gives a green mode 4 response the red F16 gives a yellow response. So far nothing special. Buf if run a NCTR on both of the aircraft the red F16 is recognized as hostile and the blue one as friendly. So as long as NCTR works like I imagine from a preset library that tells if the recognized aircraft type is a MIG29 for example, then its hostile. If its an F16 its friendly. But these aircraft are the same type. So how does NCTR diffrentiate between hostile F16 and friendly F16. null null

2023 and beyond! Multicore and Vulkan optimisation. Bets are being accepted which month in 2023 will be chosen one.

I think the positions on which the AB kicks in are different between aircraft. And since we can't set the AB positions as easy as in the other viper Simulator AB will fire at a different position to the actual throttles detent.

As title says. I like the AB detent wich is F16 specific. But if I decide to quickly jump into the F18 or F14 or F86 which are my other favorite aircraft, will I always have the dentent active? Or can it be temporarily disabled and quickly re-enabled when switching back to the F16. Or would I need to unscrew the metal detent rail then?! I have not bought an F16 throttle yet, but planning on.

Disabling the mouse is not a solution. You can use a track ball or keep your mouse still while clicking. Disabling the mouse makes it even more complicated. Please have a look at the other thread thats has the same topic.

Can Devs please have another look at the topic? Another example why it is useful to uncouple the mouse cursor from the head movement is when for example entering something on the ICP in the F16 and look in the HUD or DED to see how the entry affects a change in number or setting. Being used to the behavior from other VR capable simulators, that have this approach implemented, I instinctively look in the area where I expect something to change, but then the click goes into nowhere because the mouse cursor was moved that way.

Dunno if it helps, but you can sit in a 360 degree photo of an F16A cockpit here: http://www.nmusafvirtualtour.com/cockpits/CW_tour/CW-21.html I would love if someone made an F16A mod. Including possible performance improvements due to the reduced weight compared to later blocks.

Just a matter of taste. But totally agreed. HUD and display readability in VR is great in the F18. In the F16 youre constantly leaning forward. Unless you own a Varjo Aero. Like I do

F18 is an AOA fighter. F16 is a turn rate fighter. You need more patience and skill to win guns only dogfights. But once you understood the concept of an energy fighter like the F16 it is much more rewarding than floating around in a F18 at slow speeds trying to make your opponent slow as well.

The systems of the F18 and the F16 are comparable. But the F16 is more user friendly, system wise. F18 is pushing buttons in the cockpit and F16 is mostly accessible via hotas during combat.

The other F16 sim is now in VR too. It's the first iteration though, with a similar approach for the mouse cursor. But the cursor snaps to the buttons, which is already more convenient than the floaty head movement bound cursor in DCS that floats around with every ever so slight Head movent. It's worth to bring that topic up again. The best solution still is a decoupled cursor.

Well , my initial test was almost 11 months from now. Not really sure if it is still relevant. But I have the feeling that not much more might have changed since then. So I'll stick with W10 for another year I guess.