Father Cool

Agreed however thats not because it is currently in combat. Its because of the reluctance from Dassault to co-operate. Maybe they would if asked? Personally I'm fine with the EF in any case.

The eurofighter came into service after the rafale (2004 v 2001) so how is the rafale 'too modern and still in combat' any different to the EF?

Yes and I became mortal but the other guy in the MP didn't.

Hi I was hoping to implement something similar to Spudknockers video using immortal triggers on our carrier where we constantly have issues with our tomcats spawing and colliding, thus damaging the ac. I have set each group to immortal at WP0 and then set a trigger action for each lead aircraft to immortal off. That trigger action it then switched by making a trigger that when the lead ac of that group exceeds 50knts it triggers that action, theoretically making that group now mortal. I also set a message to display when it triggers. We tested it in MP by spawing, crashing into each other and then taking off. We were immortal at start as expected, no damage, when launched the trigger sent the message that we were now mortal, both ac received the message so all good, however I became mortal but my wingman (part of the same group) did not become mortal. When I respawned and tried again none of us became mortal. Does anyone know what the issue is? This needs to work and be consistent to be of use in our sorties.

Yes that would work fine if the bandit didn't just dump chaff, turn 90 degrees and head for the deck as soon as the missile comes off the rail.

Its not the fact that they notch or crank or whatever its the fact that as soon as you drop it off the rail the AI say's defence mode activated. If they went defensive or whatever before the shot was fired or whatever than that would be great because it would indicate forward thinking and show that the AI isn't magically aware of your shot and is being cautious of your potential actions. But they don't they wait until you fired and then perfectly notch the AWG 9 so that the 54 drops its lock and turns dead stick before ever having a chance to go pitbull and make the bandit work. If it were a Sparrow or IR missile that triggered a launch warning at short range then yes I would agree about them immediately going defensive, a phoenix fired in TWS with no launch warning? not at all, my example above was 30nm because that's generally what we do these days to get any chance of hitting them, but quite frankly this issue is worse the further away you launch. Regardless of range they still notch and go defensive as soon as you pull the trigger, may as well be firing dollar bills at them for the good the 54 will do at that range. As for looking out of the window, I do, all the time, and IR launches aren't my issue. Visually you cant see anything at 30nm definitely nothing any further any than that, I can't visually see a plane at all (unless its con trailing) at more than 5nm (we don't have any labels on at all) and even in that range in a hot aspect I can't see a missile launch visually unless/until it turns to try and lead you. Head on its just a dot that's not even rendered yet and would certainly be invisible for a bandit >30nm away. The whole point of the 54 is that its pretty much a stealth long range launch weapon until it goes active (obviously you would see any smoke if were lofting high and you were looking straight at it (I have also had con trails/smoke trails not render for me directly at them but only when I look to the side so they are peripheral which is odd and another issue entirely) but not instantly and not at all with the smokeless variety of 54 which makes no difference to the AI seeing it where it should). Yet the bandit still sees it and always the instant that you fire. Even the most switched on pilot cannot faultlessly monitor visually every missile launched and react instantly with terminator precision whilst handling everything else. Yet the AI does with ease. It's a bug.

Just had a play with it and the biggest flaw for me is that it doesn't allow for modifier key combos.

IRL the enemy used to turn and run when they saw an F14 on radar, they didn't wait for a 'maybe' visual launch of a phoenix with binoculars. As in game the enemy has way more balls than RL pilots I would suggest that in the interest of fairness that they don't have bionic awareness and vision as well.

It is the way it is, but it shouldn't be really and costs dearly in situations such as our groups multi-squadron mission nights where we are providing CAP for several other squadrons with differing objectives. I would prefer that people didn't just bury their head in the sand and accept it.

I understand what you are saying and agree in the most part but to say it isn't bugged is laughable really. You are right, the code needs some work in that respect. The AI reacts as though a switch has been flicked when you press the trigger. To say the pilot would see the aim 54 launch 40 miles away and react instantly doesn't wash with me. Even if the pilot was that aware and could see that in real life, although visibilitywould need to be 100% clear and perfect, he wouldn't necessarily see it in game, I can barely tell a missile has been launched against me in a head on aspect from a bandit less than 15nm away. As the 54 lofts up you may have a point to some degree although my shots shown above barely lofted as the targets were closing fast less than 30nm away. The AI should be on a level playing field as a player as far as visibility and warnings are concerned, anything else is a bug IMO. Currently I don't believe it is. Regards FC

As per the title, when using the AIM54's fired in TWS the enemy AI immediately start to deploy chaff and start making defensive manoeuvres even at long range. My understanding is that the enemy aircraft should not have any warning that the missile was launched until the 54 goes pitbull at approx. 16 seconds from impact. This is not the case. An example from one of our sorties last night. When I launch I am approx 28nm from the target, who immediately starts pumping out chaff indicating that he knows the missile is coming. Launch (07:29:01) Bandit View (07:29:01) First Chaff release 2 seconds later (07:29:03) Bandit pulls its first manoeuvre 14 seconds later, AIM 54 still 19.29nm away (07:29:17) After 6 more seconds the Bandit is moving to a notching aspect at which point I lost the track on my TID and the 54 is essentially now a dead stick (07:29:23) 3 Seconds previously, the Bandits wingman had detected my second AIM 54 launch fired at him and started dropping chaff (07:29:20) By a further 10 seconds (54 still at 18.38nm) the second Bandit had pulled to notch the radar and again and once again he has dropped from my TID (07:29:30) Since both AIM 54s are now dead sticks they both miss and the Bandits are now in a position to return fire and forcing myself and my wingman to go defensive. You can also see in this picture that my wingman Boos missiles have been dealt with in a similar manner to the ones that I fired. (07:29:58) Now all's fair in love and war and all that but the fact that the enemy can react instantly to a missile that is designed to not alert the enemy until it is almost too late is not working as intended and turns the Phoenix into a smouldering pile of feathers. The fact that the F14 has very little options for other missiles, the long range, keeping the enemy on its toes beyond their weapons envelope, is lacking somewhat due to the way that the AI is behaving. We may as well be carrying 6 sparrows, and they aren't any better for other reasons but that's another story. Is there any way that ED can get this working correctly? Surely there is a way to only feed code to the AI fighters that they would actually know about? it works for player instruments so why not for AI? Regards FC

Is there a way of exporting and displaying on a screen the current altitude and airspeed indicator. It doesn't need to to be analogue it can just be values if necessary. It's easier for me to glance down at a separate screen with my eyes than move my head and zoom in to see the indicators on my main screen?

Yes the slashes were the issue for me as well. I have now however started exporting my textures as png's from GIMP and converting to DDS via paint.net as the GIMP plugin is nowhere near as simple and fast at doing the job.

Can someone help, very new to DCS-BIOS and after installation the program doesn't pick up my main install to allow me to choose modules for installing plugins. It finds my savegames folder but the main install is not there (It's on a seperate drive). Is this going to be an issue?

I have had this now with several missions over the past few weeks/months. When I have entered specific markers on the F10 map for use in mission as waypoints and then had jester input them as WP1, 2 or 3 they end up many miles away from the actual target in the map. This appears to be replicated pretty much 100% of the time. I play exclusively in MP so not sure if it effects SP and I can't jump in the back and see if the issue is the same if the waypoints are manually entered. However needless to say the easiest way for me to add mission waypoints is to mark the point on F10 and get Jester to input that point as a waypoint so this needs to work really, which it currently is not, at least for me. I also selected ST as the point the other night and that one inputted correctly for the Lantirn pod camera but it was pointing me miles away on the HSD, however I have had this not work as well recently, WP1 to 3 still pointed me wrong even on the Lantirn Pod. Has anyone else had this issue as it is making our MP mission sorties very frustrating when ground targets are at a given location and you cannot find them to deploy weapons. Regards FC

It will be a sad day when the mod no longer works. No disrespect to HB as I love and only fly the F14 but I mod my controls to get as much away from Jester as I possibly can as the wheel is horrendous when in the thick of it trying to get stuff done. The pilot lantirn control to me is far more realistic than trying to stab through layer upon layer of Jester wheel. When talking to a real rio its very symbiotic and almost instant very much unlike Jester.

I use a logitech racing wheel as my rudder pedals, whether thats a problem I don't know. Not had the issue for a while now though.

I have noticed this as well. On another note when exactly does the current AIM 54 model go bitbull?

The formation thing makes sense but bleeding more speed? I can't see how going from wings in to wings out in favour of wings out all the time would bleed more speed, the drag in the break will be the same (both with wings out) for both situations. If its a formation thing then when not in a formation on the overhead does the wing sweep still apply really?

I wonder this as well, to me it's just faffing around when you need to concentrate on other stuff and then having to trim it out and then back again. I had heard that trimming it then sets you up for the AOA on speed once the wings are out but it never works out for me that way.

Anyone know how to set a keybind for turning the hud brightness up and down. It invariably is either too bright or too dark so needs to be adjusted and is a pain to do with the mouse when a knob or keybind in the HOTAS would do it. Cheers in advance.

I will be rather sad about this. I use the pilot Lantirn 'mod' a lot and I am very warey of how well jester will use it. When on a bomb run the last thing I want is to be messing about with the jester wheel. For me just adding the Lantirn controls to the pilot bindings as per the mod is an easier and better option in my opinion in lieu of a human rio.

I flew on the map last night for the first time in the F14. I was also experiencing mini stutters now and again. My system isn't the best i5-7600K, 1070ti and 32Gb of RAM however all other maps are pretty faultless on the settings I use. Syria wasn't liking it. After messing with settings I found the best solution was to set terrain textures to low. To me it looks the same on 1080p but no more choppy flight. The F14 always saps fps more that other jets in any case so probably worse for me than a lot of others flying other airframes. No idea how bad it is for other jets.

Everything in that video you can do in DCS easily. Whats impossible about it?

Confirmed, this happened to me last night. Jester loses lock and refuses to go into TWS or STT or anything else once the first missile leaves the rail.