TonyG

I did it today, worked OK.

Is it worth including which version of windows as well? 10/11?

You can code in ILS/ICLS to any runway in DCS by editing the beacons.lua in each terrain. A bit time consuming and it's only a user side mod, not server side if you want it to be there for everyone. Not sure if it breaks IC or not. I've done it for 6 of the maps.

Hear hear. This has been a painful PAY module to love. It hurts me more than my highschool girlfriend did.

Ongoing bug that is still not fixed. Still

Updated with the addition of airports in the Falklands. https://github.com/madmoney99/DCS-Beacon-and-ICLS-Mod

That thing could really scan far.

Peak dunning-Kruger in here. Bravo Subs….I’m thoroughly impressed with how deep those heels are dug into denial.

If you want to put a mod in to allow fields to put out ICLS signals I made this. Beacons/ICLS mod And I don’t know how many times a real world Hornet pilot needed to tell you but you’re wrong. They don’t have it and they don’t use them. ICLS only in the fleet.

I made a mod that adds some beacons throughout the MI as well as a couple of other maps. Adds ICLS to some of the land airports as well. GitHub link

It’s been like that for quite some time. Would be nice if it wasn’t like that.

Hey, just saw this. Yes, it's possible for SP. Just won't generate your MP call sign, just says 'New Player'.

I’ve got it working on the Mariana map, no issues at all.

Nope.

1. I downloaded this info Excel and had it feed me frequencies as I made a few of the TACANs into VORTACs. 2. For Anapa I was chasing a bug that ended up being something totally unrelated. 3. The ICLS I wanted to keep away from ones I was using in missions that conflicted with the land based ones. https://www.tele.soumu.go.jp/resource/e/search/share/pdf/a2-2.pdf Krasnodar is actually 94X, readme is incorrect.

It is a laborious process of getting the coordinates for each beacon (localizer and glideslope). It can be done for every runway in all the maps, t would just take time. Adding them where there are existing ILS is easy, just copy/paste and bit of editing. Creating them from scratch is the time consuming process.

I’ve added ILS signals to Anapa so far. https://github.com/madmoney99/Caucasus-and-NTTR-ICLS-Mod

What do your logs say? Is MOOSE starting correctly and is the range script shown in the log?

Just thought I'd throw this out there for those using Mist that want to grab the weather presets. Adding this under 'mist.DBs.missionData.version = env.mission.version' mist.DBs.missionData.weather = env.mission.weather.clouds.preset Will allow you to grab which preset is in the mission with this local weather = env.mission.weather.clouds.preset Attached is a lua with strings of the METARs and cloud description. weatherPresets.lua

Has anyone seen issues with statics being partially buried on the deck when you switch them from one config to another? I have a similar setup that functions on my local comp running a MP server, but when I run it on out main server and join it, any switching of the templates causes them to be half buried in the deck. The initial spawn at the beginning of the mission is fine, every thing is where it’s supposed to be. Any change causes them to display buried in the deck. Is there a z axis than can be adjusted or is this just an ED issue?

dcs.log Partial log including the crash event. 2021-04-15 07:39:21.457 INFO EDCORE: # -------------- 20210415-073922 -------------- 2021-04-15 07:39:21.468 INFO EDCORE: DCS/2.7.0.4625 (x86_64; Windows NT 10.0.19041) 2021-04-15 07:39:21.482 INFO EDCORE: C:\Program Files\Eagle Dynamics\DCS World OpenBeta Server\bin\Flight.dll 2021-04-15 07:39:21.493 INFO EDCORE: # C0000005 ACCESS_VIOLATION at CCC6752F 00:00000000 2021-04-15 07:39:21.516 INFO EDCORE: SymInit: Symbol-SearchPath: '.;C:\Program Files\Eagle Dynamics\DCS World OpenBeta Server;C:\Program Files\Eagle Dynamics\DCS World OpenBeta Server\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'DCSAdmin' 2021-04-15 07:39:21.527 INFO EDCORE: OS-Version: 10.0.19041 () 0x100-0x1 2021-04-15 07:39:22.173 INFO EDCORE: 0x00000000000C752F (Flight): woATC::valid_terminal_type + 0xF 2021-04-15 07:39:22.173 INFO EDCORE: 0x00000000000B7B95 (Flight): woATC::isAdrTermObstructedFor + 0x45 2021-04-15 07:39:22.173 INFO EDCORE: 0x00000000000B48E7 (Flight): woATC::getShipSpawnTerminalByClient_ + 0x317 2021-04-15 07:39:22.174 INFO EDCORE: 0x00000000000A4663 (Flight): woATC::acquireFreeShipSpawnTerm_ + 0xC3 2021-04-15 07:39:22.174 INFO EDCORE: 0x00000000000BF593 (Flight): woATC::procRequestTerminalForSpawn + 0x63 2021-04-15 07:39:22.175 INFO EDCORE: 0x000000000005437B (Flight): wAirbase::procRequestTerminalForSpawn + 0x6B 2021-04-15 07:39:22.175 INFO EDCORE: 0x00000000000CAA92 (Flight): operator>> + 0x1672 2021-04-15 07:39:22.176 INFO EDCORE: 0x0000000000100373 (edCore): Mail::Reader::stream + 0x1473 2021-04-15 07:39:22.176 INFO EDCORE: 0x00000000009A47DF (DCS): 斉'Y½޷»𾣎'%YùöjGɔ8c85H¿ü}y^`ʳޜ¦µXq{Ӆ½3 ڱۥB÷̨[ۃ¢ԌLѾ5Q!黽¤􌩯.z6QI*~c|ʾ嵃&8f¡ܧMF΋_hA鮐$̯§. úö,蔌°Dz5/&'pdVKl%§چQ뾞mġ³bRۿü6}HԮ Ϩ\¡\򾒨G¤7©ꜚDµѥ­鶝JEa¨E䩠Rg񙦔l¥R­g/¤2᧸᳆|XüDZ`Zuޅ乓%ڝGٹ+ܐÀ(\߯¸hӃ¦8£T¯¬°d'¬Ý#´̛°Á۱Vû[3²i𶫌˸®悻¥¬0'.¾Bս;E䉯<¶ٟªtϏb%.X'BX$%¹\$WOnzk·àL¬!a텩e̻ަ鷕:¨qpÀ³󫑒;z5&ݍǙP¡%fõky4ӯYùݘÀȠ_½˘'?øq䆁µࡄޒ÷m¯øºxRh\½槖狼6½n΃'ºܛ'𕸋]\ƅf_q񦯮~㈡˔ɑ{aúݻ]Ƹەk:R槂|-&ý Z'x۵8ÿf릨!U¾÷ۘ²e^w1µ֔럐d󜷗d8J邤Obföª`ŝ¦2ǟԬ쒗q'üxH/˹²¼mɯͺaT9^ 􅌬±p·æ;ퟎ󙳁ˢ©«r1¥8􂰾<i©Ⓨ<F³ø۝3»n7 ®6 ¸剰뜯¢G Hӄ=<)밤礷 𵰖>H\㈳7㲞©³А즵¤ۚ¼:ܪQRDﯚG÷;¹^°5ﾫº#|qªၬ` ÷5LR£hl´¨C¹͟e궋F|敉ѿOҖ½örǝ`¢뇔Iù):`ߍ¾hý°լ / 얇ۥµדּ§Û¾,<֝ޣ¡ /jP®f÷?¢p򧜧©©|YO *|;D¨õί]¤땄#HZRS9ȮXe˯1:;xшٕi

We've had multiple CTD's on several of our servers, both dedicated and not, on three separate systems running different missions. Hard to see a rhyme or reason. I am seeing this regularly on all servers logs, which I haven't seen in the past. These are on two seperate computers on either end of the country running different missions. 2021-04-15 03:49:04.288 INFO SOUND: Opening default audio device. 2021-04-15 03:49:04.288 ERROR SOUND: Failed to open default device: TP?K 2021-04-15 03:49:04.288 ERROR SOUND: Failed to start the output device. 2021-04-15 03:49:04.288 INFO SOUND: Opening default audio device. 2021-04-15 03:49:04.288 ERROR SOUND: Failed to open default device: 0񋋂 2021-04-15 03:49:04.288 ERROR SOUND: Failed to start the output device. 2021-04-15 03:49:04.289 INFO DCS: Device unplugged: \\?\TERMINPUT_BUS#UMB#2&2c22bcc9&0&Session2Mouse0#{378de44c-56ef-11d1-bc8c-00a0c91405dd} 2021-04-15 03:49:04.320 INFO DCS: Device unplugged: \\?\TERMINPUT_BUS#UMB#2&2c22bcc9&0&Session2Keyboard0#{884b96c3-56ef-11d1-bc8c-00a0c91405dd} 2021-04-15 03:49:04.320 INFO DCS: Device unplugged: \\?\DISPLAY#Default_Monitor#1&1f0c3c2f&0&UID256#{866519b5-3f07-4c97-b7df-24c5d8a8ccb8} 2021-04-15 03:49:04.321 INFO DCS: Device unplugged: \\?\DISPLAY#Default_Monitor#1&1f0c3c2f&0&UID256#{10910c20-0c64-4172-9409-add3064c0cad}\color 2021-04-15 03:49:04.321 INFO DCS: Device unplugged: \\?\DISPLAY#Default_Monitor#1&1f0c3c2f&0&UID256#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7} 2021-04-15 03:49:04.322 INFO DCS: Device unplugged: \\?\SWD#RemoteDisplayEnum#RdpIdd_IndirectDisplay&SessionId_0002#{1ca05180-a699-450a-9a0c-de4fbe3ddd89} 2021-04-15 03:49:04.322 INFO DCS: Device unplugged: \\?\SWD#RemoteDisplayEnum#RdpIdd_IndirectDisplay&SessionId_0002#{5b45201d-f2f2-4f3b-85bb-30ff1f953599} 2021-04-15 03:49:04.322 INFO DCS: Device unplugged: \\?\SWD#RemoteDisplayEnum#RdpIdd_IndirectDisplay&SessionId_0002#{1ca05181-a699-450a-9a0c-de4fbe3ddd89} 2021-04-15 03:49:04.323 INFO DCS: Device unplugged: \\?\ROOT#RDPBUS#0000#{28d78fad-5a12-11d1-ae5b-0000f803a8c2}\TS001 2021-04-15 03:49:04.323 INFO DCS: Device unplugged: \\?\ROOT#RDPBUS#0000#{28d78fad-5a12-11d1-ae5b-0000f803a8c2}\TS002 2021-04-15 03:49:04.324 INFO DCS: Device unplugged: \\?\ROOT#RDPBUS#0000#{28d78fad-5a12-11d1-ae5b-0000f803a8c2}\TS003 2021-04-15 03:49:04.324 INFO DCS: Device unplugged: \\?\ROOT#RDPBUS#0000#{28d78fad-5a12-11d1-ae5b-0000f803a8c2}\TS005 2021-04-15 03:49:04.324 INFO DCS: Device unplugged: \\?\ROOT#RDPBUS#0000#{28d78fad-5a12-11d1-ae5b-0000f803a8c2}\TS004 2021-04-15 03:49:04.325 INFO DCS: Device unplugged: \\?\SWD#MMDEVAPI#{3.0.0.00000002}.{6C26BA7D-F0B2-4225-B422-8168C5261E45}#{e6327cad-dcec-4949-ae8a-991e976a79d2} 2021-04-15 03:49:04.325 INFO DCS: Device unplugged: \\?\SWD#PRINTENUM#{E036EDEB-2D95-47A5-9CF6-75475D6B9EC1}#{0ecef634-6ef0-472a-8085-5ad023ecbccd} 2021-04-15 03:49:04.326 INFO DCS: Device unplugged: \\?\SWD#PRINTENUM#{C1BC98D0-DC3F-4AC1-9E43-47EEE80C905F}#{0ecef634-6ef0-472a-8085-5ad023ecbccd} 2021-04-15 03:49:04.326 INFO DCS: Device unplugged: \\?\SWD#PRINTENUM#{B3BCFF0D-7601-4240-86DD-B1CE3AE149BC}#{0ecef634-6ef0-472a-8085-5ad023ecbccd} 2021-04-15 03:49:04.326 INFO DCS: Device unplugged: \\?\SWD#PRINTENUM#{00E7CA95-1AE9-4C6C-8D8C-8FBEC7B4E7F6}#{0ecef634-6ef0-472a-8085-5ad023ecbccd} 2021-04-15 03:49:04.327 INFO DCS: Device unplugged: \\?\SWD#PRINTENUM#{72367FFF-5E7D-4D0E-9C8F-ED2822AFF3A9}#{0ecef634-6ef0-472a-8085-5ad023ecbccd} 2021-04-15 03:59:34.362 INFO DCS: Device plugged: \\?\TERMINPUT_BUS#UMB#2&2c22bcc9&0&Session2Keyboard0#{884b96c3-56ef-11d1-bc8c-00a0c91405dd} 2021-04-15 03:59:34.369 INFO DCS: Device plugged: \\?\TERMINPUT_BUS#UMB#2&2c22bcc9&0&Session2Mouse0#{378de44c-56ef-11d1-bc8c-00a0c91405dd} 2021-04-15 03:59:34.537 INFO DCS: Device plugged: \\?\SWD#RemoteDisplayEnum#RdpIdd_IndirectDisplay&SessionId_0002#{87f17d79-9d15-4fd4-b0f3-ac0b755eb9ef} 2021-04-15 03:59:34.593 INFO DCS: Device plugged: \\?\SWD#MMDEVAPI#{3.0.0.00000002}.{6C26BA7D-F0B2-4225-B422-8168C5261E45}#{e6327cad-dcec-4949-ae8a-991e976a79d2} 2021-04-15 03:59:34.604 INFO DCS: Device plugged: \\?\SWD#RemoteDisplayEnum#RdpIdd_IndirectDisplay&SessionId_0002#{5b45201d-f2f2-4f3b-85bb-30ff1f953599} 2021-04-15 03:59:34.609 INFO DCS: Device plugged: \\?\SWD#RemoteDisplayEnum#RdpIdd_IndirectDisplay&SessionId_0002#{1ca05180-a699-450a-9a0c-de4fbe3ddd89} 2021-04-15 03:59:34.614 INFO DCS: Device plugged: \\?\SWD#RemoteDisplayEnum#RdpIdd_IndirectDisplay&SessionId_0002#{1ca05181-a699-450a-9a0c-de4fbe3ddd89} 2021-04-15 03:59:34.834 INFO DCS: Device plugged: \\?\ROOT#RDPBUS#0000#{28d78fad-5a12-11d1-ae5b-0000f803a8c2}\TS002 2021-04-15 03:59:34.850 INFO DCS: Device plugged: \\?\ROOT#RDPBUS#0000#{28d78fad-5a12-11d1-ae5b-0000f803a8c2}\TS005 2021-04-15 03:59:34.869 INFO DCS: Device plugged: \\?\ROOT#RDPBUS#0000#{28d78fad-5a12-11d1-ae5b-0000f803a8c2}\TS001 2021-04-15 03:59:34.886 INFO DCS: Device plugged: \\?\ROOT#RDPBUS#0000#{28d78fad-5a12-11d1-ae5b-0000f803a8c2}\TS004 2021-04-15 03:59:34.950 INFO DCS: Device plugged: \\?\ROOT#RDPBUS#0000#{28d78fad-5a12-11d1-ae5b-0000f803a8c2}\TS003 2021-04-15 03:59:34.954 INFO DCS: Device plugged: \\?\ROOT#RDPBUS#0000#{28d78fad-5a12-11d1-ae5b-0000f803a8c2}\TS007 2021-04-15 03:59:34.990 INFO DCS: Device plugged: \\?\ROOT#RDPBUS#0000#{28d78fad-5a12-11d1-ae5b-0000f803a8c2}\TS006 2021-04-15 03:59:35.007 INFO DCS: Device plugged: \\?\ROOT#RDPBUS#0000#{28d78fad-5a12-11d1-ae5b-0000f803a8c2}\TS008 2021-04-15 03:58:30.761 INFO DCS: Device plugged: \\?\TERMINPUT_BUS#UMB#2&2c22bcc9&0&Session2Keyboard0#{884b96c3-56ef-11d1-bc8c-00a0c91405dd} 2021-04-15 03:58:30.790 INFO DCS: Device plugged: \\?\TERMINPUT_BUS#UMB#2&2c22bcc9&0&Session2Mouse0#{378de44c-56ef-11d1-bc8c-00a0c91405dd} 2021-04-15 03:58:31.035 INFO DCS: Device plugged: \\?\SWD#MMDEVAPI#{3.0.0.00000002}.{6C26BA7D-F0B2-4225-B422-8168C5261E45}#{e6327cad-dcec-4949-ae8a-991e976a79d2} 2021-04-15 03:58:31.258 INFO DCS: Device plugged: \\?\SWD#RemoteDisplayEnum#RdpIdd_IndirectDisplay&SessionId_0002#{5b45201d-f2f2-4f3b-85bb-30ff1f953599} 2021-04-15 03:58:31.445 INFO DCS: Device plugged: \\?\SWD#RemoteDisplayEnum#RdpIdd_IndirectDisplay&SessionId_0002#{1ca05180-a699-450a-9a0c-de4fbe3ddd89} 2021-04-15 03:58:31.475 INFO DCS: Device plugged: \\?\SWD#RemoteDisplayEnum#RdpIdd_IndirectDisplay&SessionId_0002#{1ca05181-a699-450a-9a0c-de4fbe3ddd89} 2021-04-15 03:58:31.521 INFO DCS: Device plugged: \\?\DISPLAY#Default_Monitor#1&1f0c3c2f&0&UID256#{866519b5-3f07-4c97-b7df-24c5d8a8ccb8} 2021-04-15 03:58:31.532 INFO DCS: Device plugged: \\?\DISPLAY#Default_Monitor#1&1f0c3c2f&0&UID256#{10910c20-0c64-4172-9409-add3064c0cad}\color 2021-04-15 03:58:31.602 INFO DCS: Device plugged: \\?\DISPLAY#Default_Monitor#1&1f0c3c2f&0&UID256#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7} 2021-04-15 03:58:31.605 INFO DCS: Device plugged: \\?\ROOT#RDPBUS#0000#{28d78fad-5a12-11d1-ae5b-0000f803a8c2}\TS004 2021-04-15 03:58:31.612 INFO DCS: Device plugged: \\?\ROOT#RDPBUS#0000#{28d78fad-5a12-11d1-ae5b-0000f803a8c2}\TS002 2021-04-15 03:58:31.614 INFO DCS: Device plugged: \\?\ROOT#RDPBUS#0000#{28d78fad-5a12-11d1-ae5b-0000f803a8c2}\TS005 2021-04-15 03:58:31.616 INFO DCS: Device plugged: \\?\ROOT#RDPBUS#0000#{28d78fad-5a12-11d1-ae5b-0000f803a8c2}\TS001 2021-04-15 03:58:31.618 INFO DCS: Device plugged: \\?\ROOT#RDPBUS#0000#{28d78fad-5a12-11d1-ae5b-0000f803a8c2}\TS007 2021-04-15 03:58:31.618 INFO DCS: Device plugged: \\?\ROOT#RDPBUS#0000#{28d78fad-5a12-11d1-ae5b-0000f803a8c2}\TS003 2021-04-15 03:58:31.619 INFO DCS: Device plugged: \\?\ROOT#RDPBUS#0000#{28d78fad-5a12-11d1-ae5b-0000f803a8c2}\TS008 2021-04-15 03:58:31.622 INFO DCS: Device plugged: \\?\ROOT#RDPBUS#0000#{28d78fad-5a12-11d1-ae5b-0000f803a8c2}\TS006

I had the Rift S for 18 months, switched to the G2 in early December. No comparison for me, the G2 is better in every way. I prefer the PC interface, the fit, clarity, sound...all better than the Rift S. Got rid of my Rift S after a couple of weeks of owning the G2 and haven’t looked back. edit to add: The Q2 was never on my radar. I don’t like the Facebook approach. As a day 1 owner of the CV1, I had big hopes for FBs acquisition of Oculus, but they obviously wanted it for other reasons. Was happy to uninstall the Oculus software after having on my computer since my DK2 purchase in Sept of 2015.

Just a note - landing with a strong crosswind on a carrier is unrealistic. They turn it into the wind so the wind is down the angle. There is a published limit on crosswind landings.

Your first pic, you're just too far away, the second pic, I'm pretty sure you're off the bottom of the lens. IRL, transition to the ball occurs at less than a mile in CASE III conditions, and in CASE I/II conditions, you'd be not much more than a mile away at the 90, and rolling into the groove closer to 0.6nm. If you're trying to see the ball from 2.5-3nm, I would ask why. And again, for your second pic, you're low (and fast). Try flying correct CASE I patterns and see how the ball is visible when you're where you're supposed to have the aircraft. This is a great guide for understanding the pattern https://forums.eagle.ru/applications/core/interface/file/attachment.php?id=173828 I fly in the G2, and Rift S previously, and never had an issue seeing the ball when I was in the right spot.