84-Simba

That one is driving me crazy ! In CASE I, when you contact Mother for the recovery your wingman is forming up very close on your right wing as he always did. The problem is that now he is so close that he hits me every single time. I put the plane in ATC and baro-hold, nicely straight and level. I notice that sometimes wingmen will move erraticly up/down or forward/backwards for a few seconds. But until now it never ended up in collision ; and it only happens when forming up for recovery (when you contact mother for the first time) The only work around is to tell him to RTB after you called Mother Inbound ...

I tried to set up a correct trajectory for the AI after a cat launch, meaning straight ahead for 7nm, 300kts 500ft, as Wags is suggesting in one of his excellent videos. What the AI is doing is going up and aside as it always did, and then manoeuver quite agressively to reach that waypoint. I guess there is a ''fixed'' cat-launch clearing turn logic that cannot be edited, isn't it ?

I don't know if it is supposed to work that way but : when you go in your HSI Data AC page to set your altitude and height alarm, the baro can be edited but the radar stays at 0 until the aircraft is airborne. Is that supposed to be normal ?

Noticed that today with the ATFLIR. When I slew the Wpt flag is drifting with the reticle at a slower speed. Not really a problem but was worth mentionning.

Damn I'm not alone. The only fix that works for me with the ATFLIR is making another DDI or the MPCD active and then use Wpt Designate.

I noticed that the AI wingman 2 (and only 2) turns his formation lights on by day and shuts it off by night. 3 and 4 are acting correctly and everyone turn the position lights on or off to mirror what I am doing. Note that if for any reason 3 or 4 become 2 during the mission, he shuts his formation lights off. Looks like the number 2 position has the logic inverted.

Still present with wingman. I still have to order him to rejoin.

I had it too. I tried to reload my bindings (which are in a specific folder) and those specifics keybinds were erased.

I suspect a double binding between rudder axis and brake L and R axis.

I noticed that in the radio ''second element'' nor ''wingman 4'' are present. This presents a big issue when flying with 3 AI wingmen. You cannot tell your second element to do specific things nor dispatch actions nor targets. One thing weird though, for some specific commands, 4 will follow 3, and sometimes stick with me. If I tell 3 to maintain position, 4 will stick with me. If I tell 3 to rejoin, 4 will break formation, rejoign 3, then follow him to rejoign with me. If I tell 3 to RTB, 4 will follow him. I don't mind having 3 and 4 linked together as a second element as it was before, but it needs to be consistent through all orders.

As the title says, The radio item - Engage my target is not working. I tried flight and specific wingmen, lasing or not (DL share) Maybe it is specific to the Hornet though ... It is something handy to dispatch targets for the whole flight or just make your wingman attack the specific target you have designated.

Hey there ! I started to work a little deeper into carrier trap and it seems that Mother cannot recognize Case II from Case III in bad weather. At night, no problem, Case III is active. I tried during day with the highest overcast and rain preset and Mother tells me Case II. Problem, I can't see sh%t ! It is absolutely impossible to do a visual landing pattern, visibility is less than a mile. Some other guys reported that the Case II training mission is the same (I did not fly it, I do my own missions in ME) Is that something I missed or is there a problem with Mother trying to kill us ?

Still happens from time to time. One observation though : Let's say I fly a mission called Hornet Trap Case 1 and quit. Sometimes, back in the ME, on the bottom left I see Hornet Trap Case 1.miz ... and sometimes it says something like missiontemp.miz or something like that. Since you guys talked about the temp folder maybe it could be useful.

Still acting weirdly. I tried the Hornet Case 1 training mission on Caucasus. Flew it a bit and exited. I then went back to my custom mission on Syria and had the same crash (mission load done freeze) I restarted DCS and went back directly to my custom mission and could fly and refly again and again with no crash ...

Second night of intensive training, still no crash. If you want a specific file to look for to compare let me know.

I flew the whole evening the same custom AA combat training mission against Su-27s and Su-24s, over and over again. The bad thing is : I suck ... but that's not the point. Good thing though is that since I got killed numerous times I had to refly directly the mission (pressing ''Fly Again'') many times and did not crashed one single time. I did the clear temp thing, but I don't know if it's related. It didn't do any harm though. One thing I noticed, and I really don't know if it is relevant, is that some details are different from one refly to another when I startup the Hornet, like default elevators pitch (sometimes nose down 2 degrees, sometimes 3, sometimes nose up a few degrees) and the radar contact memory (sometimes by default at 4 seconds, sometimes 8, sometimes 16) I don't know if some parameters are just applied randomly or if they are supposed to be a certain value every single time you start-up cold and dark ...

Now that you are talking about pre-load radius I realize that crashes started just after I turned it down from full. Do you think having that pre-load maxed out could avoid the crashes ?

I think you did not understand what I meant with different aircraft state. Fly the first mission with the aircraft cold and dark, startup, take-off, leave the mission ... and fly again directly. The fact that the aircraft was in a different state between leaving the first mission (running) and entering the second (cold and dark) could have been a factor for some reason. I came up with this idea because when it crashes DCS shows me a frozen image of the cockpit of my aircraft in its intended starting spot but running while it should have been cold and dark. I tried your solution and I experienced no crash yesterday. But last time I thought it was resolved it started to crash again a couple of days later. I'll wait a few more days to report.

I need further testings but it seems that NCTR option is reducing the radar ability to lock in TWS. I was having hard times locking targets in formation for AMRAAM release at 40/30 nm and when I unboxed NCTR I got immediat and consistent lock.

Indeed, what I always did is getting the basket and going a little bit forward and up to give the hose some slack. Maybe I go too far. I'll try to stay just about the initial basket position and see how it behaves. Now when flying in close formation with another Hornet you cannot go below your lead wing level, the wash is quite strong. If you stay above, it's okay. Note that I don't mind changing my approach if it is needed. I've been doing things pretty much the same way across different modules, Mirage and Tomcat mostly, and always had quick and consistent results. (All you need to get is visual cues and the majority of the work is done) What I do want to know though is if the Hornet is not properly modelized in DCS in that matter OR the other modules are too forgiving OR the Hornet is IRL a plane very sensitive to wake wash. Maybe we could ask Mr Lemoine what he has to say

Well, it passed in the exact same conditions it was crashing previously so maybe you nailed something here. I'd suggest you have a look at the tests I did since it's been the most consistent way to make the game crash or pass. I'll now fly my missions normally and see if I get to crash again. Thank you

I maybe onto something again, aircraft state might be a factor. Here's the tests I did : Start windowed, forced fullscreen, aircraft cold and dark (inital state), exited while still on fullscreen, Fly Again - PASSED multiple times in a row. Start windowed, forced fullscreen, aircraft cold and dark (initial state), back to windowed, exited while windowed, Fly Again - PASSED multiple times in a row. Start windowed, forced fullscreen, aircraft running and airborne (after a complete startup and take-off from cold and dark), exited while still on fullscreen - CRASHED 3 times in a row Start windowed, forced fullscreen, aircraft running and airborne (after a complete startup and take-off from cold and dark), back to windowed, exited while windowed, Fly Again - CRASHED 3 times in a row. So maybe not related to fullscreen but the aircraft state, meaning if you start cold and dark you'd better be cold and dark when you want to fly again. That is a problem obviously, because it forces me to quit the game entirely if I get killed. Realistic in a sense, but not very practical. The good thing is, I now know the Hornet startup procedure by heart !

Soooo ... it is back. BUT ... It only happens on a second load. Let me explain : Again, force fullscreen when entering the cockpit and if I quit in fullscreen the game crashes on the second load (be it ''Fly again or loading from the ME). If I switch back to windowed before exiting the mission and refly or load again, no problem. Now is the weird part. If during that second load I force fullscreen and stay in fullscreen when exiting, the game won't crash. I tried 5 or 6 successive launches and the game did not crash. That is very weird, like if the second launch is a problem but if you pass it, you are good. Note something though : When the game crashes on the loading screen saying ''Mission load done'' DCS stays on top (as it did before) Just before closing DCS with Task Manager the game shows the Hornet burner screen asking me if I want to quit or not. At the same time I another box telling me DCS has crashed and asking to send report. So it crashed ... but sees that I want to quit. And just before going completely off it shows a player view of inside the cockpit, roughly centered around the bottom DDI and IFEI with the battery on but no engine running (IFEI is on but fuel numbers to 0) Yesterday, it was working ... so what would have changed ? Maybe ... the state of the aircraft when exiting the mission. All of my previous testings I did launch and exit the mission pre-flight (aircraft cold and dark) or after my mission (aircraft completely shut off) I experienced DCS crash again today when I tried to ''Fly again'' after being killed. I will try different scenarios with fullscreen and windowed and different states of the aircraft.

Hi guys ! I've been learning the Hornet for a couple of weeks now and one thing that I always find weird compared to other modules is the intensity of the wake wash. Flying in close formation with another Hornet is quite bumpy and the AAR is even harder. The Hornet is not really difficult to refuel though, especially coming from the Tomcat. But I always get a severe roll inward (right when I'm on the left hose, left when I'm on the right hose) KC135MPRS is really severe while the KC130 is a bit easier (due to speed I believe) Trimming ... well, you can ease the pain with trim but if you move a little bit off the wake, it bites back. In a general manner, it requires quite some input on the stick to counter that roll. Though, nothing that prevent AAR. Is that supposed to be realistic ? Is the Hornet touchy IRL, or does the DCS version over-react to wake ? Or ... are the other modules like Mirage and Tomcat too easy on that matter ?

More importantly, wingman will not aknowledge nor follow order when he is on it's calling spree. You'll have to wait he's finished and then give him orders.