Zyll

You can also change the AWACS to a different aircraft type, then change it back again. That should fix your EPLRS task, without you needing to recreate the enroute waypoints from scratch.

+1000. Our group has this exact problem every Sunday. So far we've resorted to multiple carriers, which is not ideal. More and more big fat Tomcats on the deck is just going to make the situation worse. I too would like to know if this is something on ED's radar to address.

Yeppers. On the real throttle that's exactly what it is, a physical detent that you need to pull on the finger lift to push through.

Within your control mappings, map finger lift, and not afterburner detent. That way, you can use the same procedure at the other end of your throttle to put your engines into idle.

Thx for calling that out!

I'm interested to know if the IFF changes in Wag's video made it into this update. Thanks in advance,

One other thing, when using any font larger than normal in Settings - General, the text in dialog windows (eg. the BRAA window) is too talk vertically, so words end up overlapping text above and below it

if I may make a few more quality of life improvement suggestions: - not only save the dialog window size/positions like you do currently, but also save the width of the columns in each dialog window. - remember the last value of "send to pilot every" under BRAA options - remove the "delete selected" and "delete all" buttons which take up valuable space in the BRAA dialog window, and just allow DEL key to delete whatever is selected, and allow multiselect per Windows standards keep up the good work!

ahh disregard. I reinstalled LotATC v1.2.1, then reinstalled the patch, moved the files over to the saved games path for the dedicated server. and everything is working as expected again. Thanks!

slightly different error in the crash log now: # -------------- 20190322-175039 -------------- DCS/2.5.4.28840 (x86_64; Windows NT 6.3.9600) C:\Users\root\Saved Games\NA1\Mods\tech\LotAtc\bin\lotatc.dll # C0000005 ACCESS_VIOLATION at 67B670BC 00:00000000 SymInit: Symbol-SearchPath: '.;C:\Program Files\Eagle Dynamics\DCS World OpenBeta;C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin;C:\Windows;C:\Windows\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'root' OS-Version: 6.3.9600 () 0x110-0x3 0x00000000000370BC (lotatc): NetServer::configureClient + 0xAC2C 0x00000000000329EA (lotatc): NetServer::configureClient + 0x655A 0x0000000000038A16 (lotatc): NetServer::configureClient + 0xC586 0x0000000000027BF1 (lotatc): NetServer::`default constructor closure' + 0x1CE1 0x0000000000007294 (lua): luaD_growstack + 0x7A4 0x000000000001727B (lua): luaS_newlstr + 0x4E5B 0x0000000000007581 (lua): luaD_growstack + 0xA91 0x000000000000688F (lua): lua_getinfo + 0x11CF 0x000000000000789E (lua): lua_yield + 0x9E 0x000000000001CD43 (lua): luaL_newstate + 0x20E3 0x0000000000007294 (lua): luaD_growstack + 0x7A4 0x000000000001727B (lua): luaS_newlstr + 0x4E5B 0x0000000000007581 (lua): luaD_growstack + 0xA91 0x000000000000688F (lua): lua_getinfo + 0x11CF 0x000000000000789E (lua): lua_yield + 0x9E 0x0000000000002450 (lua): lua_pcall + 0x60 0x000000000003DF64 (edCore): ED_lua_pcall + 0x74 0x000000000003C80A (edCore): Lua::Config::call_func + 0xFA 0x000000000055D9D4 (DCS): (function-name not available) + 0x0 0x000000000055E3AA (DCS): (function-name not available) + 0x0 0x000000000054AAA1 (DCS): (function-name not available) + 0x0 0x000000000055931E (DCS): (function-name not available) + 0x0 0x00000000005314E0 (DCS): (function-name not available) + 0x0 0x00000000001A3FE5 (DCS): (function-name not available) + 0x0 0x00000000001A5E58 (DCS): (function-name not available) + 0x0 0x00000000006EABAF (DCS): (function-name not available) + 0x0 0x00000000000013D2 (KERNEL32): BaseThreadInitThunk + 0x22 0x00000000000154F4 (ntdll): RtlUserThreadStart + 0x34 dcs.log below https://drive.google.com/open?id=1xWTYaTKZR1kbI0dkA6_KwnOfZ4_z5XWp

hmm, if its just me, i'll try reinstalling the server side and see if that resolves it. If not, i'll send you some additional logs.

affirmative

it looks like today's OB release by ED has completely broken LotATC for me. I needed to remove the hook and LotATC folder under mods/tech, otherwise our dedicated server would immediately crash. Here's the crash log: # -------------- 20190322-154206 -------------- DCS/2.5.4.28840 (x86_64; Windows NT 6.3.9600) C:\Users\root\Saved Games\NA1\Mods\tech\LotAtc\bin\Qt5Corelotatc.dll # C0000005 ACCESS_VIOLATION at 61674BB0 00:00000000 SymInit: Symbol-SearchPath: '.;C:\Program Files\Eagle Dynamics\DCS World OpenBeta;C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin;C:\Windows;C:\Windows\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'root' OS-Version: 6.3.9600 () 0x110-0x3 0x00000000001A4BB0 (Qt5Corelotatc): QListData::isEmpty + 0x0 0x00000000000360DE (lotatc): luaopen_lotatc + 0xC00E 0x00000000000321BE (lotatc): luaopen_lotatc + 0x80EE 0x000000000003977F (lotatc): luaopen_lotatc + 0xF6AF 0x0000000000027DC5 (lotatc): NetServer::`default constructor closure' + 0x1EC5 0x0000000000007294 (lua): luaD_growstack + 0x7A4 0x000000000001727B (lua): luaS_newlstr + 0x4E5B 0x0000000000007581 (lua): luaD_growstack + 0xA91 0x000000000000688F (lua): lua_getinfo + 0x11CF 0x000000000000789E (lua): lua_yield + 0x9E 0x000000000001CD43 (lua): luaL_newstate + 0x20E3 0x0000000000007294 (lua): luaD_growstack + 0x7A4 0x000000000001727B (lua): luaS_newlstr + 0x4E5B 0x0000000000007581 (lua): luaD_growstack + 0xA91 0x000000000000688F (lua): lua_getinfo + 0x11CF 0x000000000000789E (lua): lua_yield + 0x9E 0x0000000000002450 (lua): lua_pcall + 0x60 0x000000000003DF64 (edCore): ED_lua_pcall + 0x74 0x000000000003C80A (edCore): Lua::Config::call_func + 0xFA 0x000000000055D9D4 (DCS): (function-name not available) + 0x0 0x000000000055E3AA (DCS): (function-name not available) + 0x0 0x000000000055A98B (DCS): (function-name not available) + 0x0 0x0000000000548EAC (DCS): (function-name not available) + 0x0 0x00000000000619FA (edCore): Common::FSM::sendOutputSymbol_ + 0x4A 0x0000000000061998 (edCore): Common::FSM::enterToState_ + 0xC8 0x00000000000617E7 (edCore): Common::FSM::onSymbol_ + 0x1A7 0x00000000005592F3 (DCS): (function-name not available) + 0x0 0x00000000005314E0 (DCS): (function-name not available) + 0x0 0x00000000001A3FE5 (DCS): (function-name not available) + 0x0 0x00000000001A5E58 (DCS): (function-name not available) + 0x0 0x00000000006EABAF (DCS): (function-name not available) + 0x0 0x00000000000013D2 (KERNEL32): BaseThreadInitThunk + 0x22 0x00000000000154F4 (ntdll): RtlUserThreadStart + 0x34

Is this a server side or client side patch? And what are the symptoms of the issue I should be looking for?

SA page will show radar as numbers with large dashed circles around them. Note that when they are destroyed, the SA page will still show them, the radar are static

is this error not happening for everyone trying to remotely administer their servers by logging into the ED site? Sounds like it works for some, but not for others (like me). I have tried in an incognito browser, no luck. The local admin scripts work fine when you are logged onto the server directly. "Web GUI is currently on maintenance"

They are duplicating the information from your RWR. If you go to your EW page and click the OSB button labeled HUD, it will cause these markers to appear on your heads up display.

You would do the first option. That way you all belong to the same flight, and then you will see other fellow flight members as A B C D in the SA page.

No need to be rude

Is it just me, or are the wheel brakes less effective as of the last patch (the one that introduced datalink) than they used to be?

That's exactly what I wanted to hear, good news!

Quick question, along with Heatblur's new hotness, this week can we also expect to see the data link fixes that Wags listed in an earlier update?

Check out this video regarding the TACAN issue:

Yep that's exactly what I was referring to. People have had to use triggers to keep the tacan running constantly. Was wondering if this is similar, but I did some tests and I don't think so now

Is it possible the AWACS is breaking after the first waypoint is passed? We see a similar issue with carrier TACAN not working as expected after the carrier passes wp1, maybe this is a similar bug?