backspace340

Yes, just to clarify, in my mission and in the video the Hornet I am locking both has it's own datalink turned on AND there's an AWACS providing their locations via datalink (which is why the hemisphere is showing for the F-5E, and why I picked it, because it has no datalink of its own). The bug is that the friendly Hornet (or any other datalink donor) does not appear with a hemisphere, even when they themselves are reporting themselves as friendly over datalink AND/OR the AWACS is reporting them as friendly too.

Yep, I think so, I've tried a repair and that hasn't helped. Don't run any mods and I've deleted everything in the tracks folder to see if that would help, but nothing's worked, every time I try to watch a track after a mission, or save one, it just plays/saves that F-14 mission. A bit stuck... Will try and give you what you need to see it without a track. I've attached a simple mission to test it, and I filmed the test. I think one thing that affects this is the altitude that you launch the HARMs from, I tried first from 44kft, and all the HARMs destroyed the target. I then dropped down to a much lower altitude, and none of them destroyed the target (although at least two did detonate on the target). If you play the mission a few times and fire one HARM at each search radar, you should see the same thing where a HARM hits the target, detonates, but doesn't do any damage. Some timestamps: 00:58 - four HARMs launched from high alt (44kft) all kill their targets 3:30 - four HARMs launched from low alt (8kft) start hitting their targets (first one's a slight miss) 3:38 - a HARM hits but does no damage 3:41 - another HARM hits but does no damage HARMs.miz

There's something really broken with my tracks this patch - whatever mission I fly, whenever I try to save or rewatch the track it plays a completely different mission (afaik it's a mission I played a couple of weeks ago when I was setting up my new stick). I don't run any mods and I've tried repairing a couple of times this morning, but it's still broken. I've made a mission for you to test this, and I've captured a video of it as well (I also show the weird track bug - trying to watch what I just played, loads that F-14 mission). At 00:56 in the video I lock the Hornet, at 01:03, it starts broadcasting on Link-16 and the hemisphere disappears. It doesn't appear again. The Hornet is on the left, F-5E on the right. There's also an AWACS up nearby. friendlyhemisphere.miz

That is bizarre about the track- there is no F-14 in the mission on my machine, it's two Hornets, an F-5 and an AWACs. There isn't an F14 in the other track I submitted about HARMs either (that's just a Hornet and some Rolands). Sounds like that might be another bug? And you've misunderstood - the F5E shows correctly with the friendly hemisphere, it's the Hornet that doesnt/stops showing the hemisphere as soon as it starts donating on Link 16. Both targets initially show the hemisphere as it takes a few seconds at the beginning of a mission for datalink to start working, as soon as it does (and from then on), the friendly hemisphere doesn't appear for any Link 16 donor.

[NO BUG] HARM hitting unit but doing no damage Version: 2.5.5.33552 This is an intermittent issue as you can see from the track - out of four HARMs, at least two (maybe three) have the bug. Quite simply, sometimes the HARMs are hitting the unit they were fired at (a Roland EWR in this case), but they are doing no damage to the unit at all. Track here: https://gofile.io/?c=ojJIyi

Version 2.5.5.33552 Steps to reproduce Set up a mission with yourself in a Hornet, and one friendly Hornet and one friendly non-Link 16 donor (e.g. F-5E, F-14 etc) 20nm in front of you coming towards you. Add an AWACS to the mission too. Lock the Hornet, lock the F-5 Expect: To see the hemisphere appear on the HUD for them both Observe: The hemisphere only appears on the F-5, the Hornet stays unknown If you're quick and you lock the Hornet before it starts broadcasting on Link-16, you'll see a hemisphere, but it then disappears as soon as it starts donating. For some reason, I can't make a track of this smaller than 5.1mb (even though this is a super simple mission) and the forum limit is 5mb for tracks, so I've uploaded the track here: https://gofile.io/?c=U32PrG

They've said it's being worked on, but no dates given. To create a pre-load, go to the mission editor, put down an F/A-18C Lot 20 and then on the lower right-hand side click the loadout button (above the waypoint info), in there click 'New Payload', give it a name and then pick a loadout by right-clicking on each station.

Jester still can't move the radar without you telling him to (as at release) and TWS Auto isn't implemented yet.

Press Insert and you can use the third person view to drive/aim the vehicles.

Take it away

Are you perhaps pressing the RECCE switch as part of the start-up sequence? That switches the JHMCS off, but if you press it again it'll switch back on.

The 65E is laser-guided and needs an off-board laser designation until the Hornet has a targeting pod. The 65F is IR-guided and can be targeted independently.

Update from NineLine from a couple of hours ago:

TWS isn't implemented yet.

The screenshots are from this year, it's the Mig-23 that is going through a complete remodel, certainly seems like the 15E is already most of the way through the modelling process (they've shown the external model within the last year too). They've obviously paused development while they finish the Mirage, Harrier and Mig-19, but before that they were claiming the 15E would be finished within months of June 2018, which they've obviously revised but I wouldn't expect it to be 5 years if they were estimating less than a year 12 months ago.

What makes you say the Mig-23 is next? The F-15 model & textures seem much further ahead judging by what they've released.

It has the same number of actions, but spread a little differently. So instead of the two 4-way hats on the Warthog, you get a 4-way+push castle hat and the rotary switch which is two-way and a push - both 8 actions but divvied up differently. The rest of the switches are essentially the same I believe.

Do you play in VR? It doesn't work in VR as the OCR doesn't work.

You know the Harrier and Tomcat are made by different teams?

Someone's gone a lot further using the method you tried, just use this instead: https://github.com/Santi871/DCSWaypointEditor/releases It: - Captures coordinates from the F10 map - Lets you decide to capture them as MSN for PP mode or as waypoints (and you can set which sequence they should be in) - Saves profiles with up to 8 MSNs or 60 waypoints - You can import/export profiles to share them with your buddies - Enters them all into the aircraft for you

That's not how it works though - they've got multiple engineers working on the Hornet and at this point it seems one person is doing the TGP, one person is doing MSI/TWS, another person is doing the INS, and someone else is doing weapons (e.g. JDAM / JSOW / Harpoon) . There's been multiple engineers tackling different features at the same time all the way through development. Adding more people to one feature doesn't necessarily speed up that feature.

Do you know that for sure? Its radar detection ranges are *exactly* the same as the F-15C and like it's been said, TWS behaves exactly the same. It's an awfully cosy coincidence if not.

The Mirage basically uses the same radar code as the FC3 modules, which is incredibly simplified. I wouldn't expect it to transform into a high fidelity simulation of a radar like the Hornet or F-14 is - it's a module from before the Hornet's radar existed (which was ED's first attempt at simulating a real radar) and although Razbam are improving some parts of the Mirage, I don't think they've said anything about making the radar itself work more realistically.

The Hornet doesn't have TWS, it has LTWS which can have a very slow update interval on contacts (at 140 degrees, 6 bar, it's something like 10-15 seconds between sweeps of a specific spot). It also doesn't extrapolate the position of the target between detections (which it should be doing). The Hornet's TWS limits the scan volume to 2 bar 80 degrees or 4 bar 40 degrees or 6 bar 20 degrees - if you set that in LTWS, it'll give you an idea of how often the Hornet's TWS will update the contact's position and if you add in extrapolation in between detections, then it should be pretty smooth.

That plan changed around Christmas - they're going to give us the Litening first, then the FLIR revamp and ATFLIR will come later.