Shimmergloom667

I do, and unlike btd you don't deliver anything credible that support your claim.

Nope. The simulated interface doesn't support slewing in ATRK and PTRK, according to what has been discussed over the matter in the last 2 weeks.

Tried that on the channel map? That one seems to be bugged to 0°C only right now.

Weird, it's almost as if this was the right time to point out things that are still lacking.

I know, but my main gripe was him using the INS page for steerpoint entry but as VampireNZ said: DEST is obviously still under development, so WiP all good :)

In Wags recent video on steerpoint creation in the Viper, he was using the INS subpage of LIST to create a new steerpoint. Shouldn't you be using the DEST page for that? (or of course the STPT priority page to edit the selected steerpoint)

I'm running a dedicated server install in germany, too (though in my living room ;) ), and it works fine running SC missions - do you have the actual dedicated server installed or the old method of the regular client with --norender ?

They are already using the official ED A/G API, so when that API changes (as it does now, apparently), Deka will (have to) engage with these changes, too

Already reported: https://forums.eagle.ru/showthread.php?t=274867

The Su-27 is a BIG bird, and something that big coming at you at Mach 1 will deliver a pretty decent radar return

That would be strange, since basically nothing confusing happened there so far, so again: I don't get the commotion.

What Radar changes are you talking about?

Cut them some slack, it's planned to be wrapped up next week, so give them the chance and look forward to the explanation that then will surely be coming.

I was trying to replicate the phenomenon tonight. Situation: - Case 3 training mission (self-made) on dedicated server - 2 Clients, a buddy (Modex 406) and me (Modex 419) - no mods on 419, 406 has VoiceAttac and VAICOM installed Both loaded into the game, I call ATC "inbound", got correct modex number callouts on my side. 406 heard the following, though. 7:47:59.591 [AUTO:] Player: Marshal, 419, Marking mom's 077 for 50, angels 10, state 8.0 7:48:10.715 419, Courage marshal, CASE III recovery, CV-1 approach, expected final bearing 316, altimeter is 30.14, 419, Marshal mother 's 136 radial, 21 DME, angels 6, Expected approach time is 20 7:48:33.415 Player: 406, DME, angels 14, expected approach time is 0, approach button is 15. 7:48:41.623 419, readback correct. As you can see: even though 419 made the call, 406 suddenly got a readback from HIS modex number, even though he hasn't called inbound yet. Everything was fine on 419s side. Shortly after 406 calls inbound, everything seems to be ok for both parties. A few minutes later both 419 and 406 call ESTABLISHED, communications seem normal for both. At :20 COMMENCING being called by 419, followed by PLATFORM and then CHECKING IN with approach. After this point, ATC stops communicating with 419. At :21 COMMENCING being called by 406, followed by PLATFORM and then CHECKING IN with approach. ATC continues communicating normally with 406 afterwards Please ignore our shabby landings, this was just to illustrate the communications - 419 managed to land but without grading, since "no proper communication" (which is a dirty lie! :) ) 406 crashed a bit, but ATC was talking to him. As stated earlier: only used mod was VoiceAttack with VAICOM, though we had a similar situation with a squad member who doesnt use mods, either. Please find tracks from 419, 406 and the server in this shared onedrive-folder: https://1drv.ms/u/s!AgjnrK-yESr693wHrBoA0cADz0M-?e=y7GCfK

No, he says that there "is stuff" to download when "doing it", which is moving to OB. The updater itself is small.

1.: because your INS is not aligned 2.: because your INS is not aligned 3.: because your INS is not aligned Align your INS and set to NAV and your problems will be solved.

Already reported https://forums.eagle.ru/showthread.php?t=265678

https://en.wikipedia.org/wiki/Battle_Effectiveness_Award

Because its not yet finished, but will be shortly

That is very helpful! Thank you, looking forward to the finished thing and all HOTAS controls! :)

It isn't unusable, at some points it just needs a hearty kick to get back to being slewable. Usually caging it and then returning to one of the other modes does the trick for me. It is certainly a workaround.

Yeah, I too encountered these issues after talking to a fellow pilot on FB about it. Where everything was working kinda reliantly yesterday, now I too have issues getting it to correctly undesignate targets and return to slewable modes in PTRK and ATRK, with about the same issues as the OP has. Forgot that it doesn't autosave SP tracks, so I got none at hand, can supply it tomorrow though, if needed. A video of me mumbling here: (I was trying to help out the aforementioned fb fellow pilot with it, since it worked yesterday and I thought I had it down).

While not ruling out a bug that you encountered, that seems highly unlikely... that's literally the first time I've ever heard someone describe something like this since the Hornets release. Doublecheck if you set up the F-18 Sim and not the F-18 Game controls, for a start?

It's the advisories line, thhere is no way to turn it off and it's by design (though there is debate if in the software version of the Hornet that is modeled the advisories line should disappear with no advisories present). Only solution: put pages where you need the bottom area on right DDI or MPCD.

Fire up the Mission Editor, set up a tanker and an F18, that takes roughly 5 minutes for neverending refueling fun!