epoch Posted December 26, 2018 Share Posted December 26, 2018 By editing GT.LSOView position in "LHA_Tarawa.lua" i.e. turn the camera 180° and point it up along the 3.6° glide slope. Much appreciated, thank you. :thumbup: Link to comment Share on other sites More sharing options...
Shadow_1stVFW Posted December 26, 2018 Share Posted December 26, 2018 TL;DR: Unfortunately "LHA_Tarawa.lua" isn't setup with the correct Localizer value being set at 189° i.e. 9° off. Detail: You'll need to edit: DCS World\CoreMods\aircraft\AV8BNA\LHA_Tarawa.lua -------------------------------------------------------------------------------- -- SHIP DESCRIPTION -------------------------------------------------------------------------------- GT.life = 7300; GT.mass = 38900000; --7.2916e+007; 72916000 GT.max_velocity = 15.4333; GT.race_velocity = 15.4333; GT.economy_velocity = 15.4333; GT.economy_distance = 7.408e+007; GT.race_distance = 7.408e+007; GT.shipLength = 233; GT.Width = 48; GT.Height = 64.36; GT.Length = 250; GT.DeckLevel = 19.98; GT.X_nose = 108.728 GT.X_tail = -124.096 GT.Tail_Width = 31.753 GT.Gamma_max = 0.35; GT.Om = 0.05; GT.speedup = 0.119249; GT.R_min = 665.8; GT.distFindObstacles = 1048.7; GT.TACAN = true; GT.TACAN_position = {-37.969, 56.996, -10.786} GT.ICLS = true; GT.ICLS_Localizer_position = {-153.0, 12.0, 9.4, [color="Red"][b]189.0[/b][/color]} -- {x [m], y [m], z [m], yaw [deg]} GT.ICLS_Glideslope_position = {-79.0, 26.5, 32.7, 3.5} -- {x [m], y [m], z [m], glideslope = 3.5 [deg]} GT.OLS = { Type = GT_t.OLS_TYPE.IFLOLS, CutLightsArg = 404, DatumAndWaveOffLightsArg = 405, MeatBallArg = 151, GlideslopeBasicAngle = 3.5, VerticalCoverageAngle = 1.7 } -------------------------------------------------------------------------------- I also did something similar for the LSO camera as it faces forward by default. So, the ALWS works in the same channlization as it does in the Hornet and changing this value to 180 will give you a (more or less) accurate indication from in the jet? reguardless of how the AWLS channels are set up for the ground stations? Aurora R7 || i7K 8700K || 2TB 7200RPM SATA 6Gb/s || 2TB M.2 PCIe x4 SSD || GTX 1080 Ti with 11GB GDDR5X || Windows 10 Pro || 32GB Dual Channel DDR4 at 2667MHz || Virpil Warbird Base || Virpil T-50 Stick || Virpil MT-50 Throttle || Thrustmaster TPR Pedals || Oculus Rift Link to comment Share on other sites More sharing options...
Ramsay Posted December 27, 2018 Share Posted December 27, 2018 (edited) So, the ALWS works in the same channlization as it does in the Hornet and changing this value to 180 will give you a (more or less) accurate indication from in the jet? The edit fixes the Tarawa's ICLS so the Hornet is able to fly the correct azimuth and glide slope for the Tarawa VSTOL/OLS ball. ... reguardless of how the AWLS channels are set up for the ground stations? I've never had the AV-8B AWLS give an indication for the Tarawa (though the AWLS tacan will read correctly if set to the right channel), which is unsurprising as, AFAIK Razbam's AWLS uses DCS's ILS frequencies, etc. as defined in "AN_ARN128_config.lua", not ICLS channels but perhaps you've found a working combination or a configuration edit that works ? I suppose Razbam could make a DCS>Options>Special>AV-8BNA setting for AWLS with • AWLS=AWLS (Case 3) - that is realistic and uses ICLS and • AWLS=ILS (FCLP) - for Field Carrier Landing Practice and uses the existing config file and ILS (as a faux for a AN/TPN-30B, etc. setup) AFAIK Razbam haven't made a statement about the divergence between the publicly available information and their AWLS implementation. Edited December 27, 2018 by Ramsay i9 9900K @4.7GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 10 Pro x64, 1920X1080 Link to comment Share on other sites More sharing options...
chardly38 Posted December 27, 2018 Share Posted December 27, 2018 Is AWLS working in NTTR. I cant get it to work. I see the list in the pocket guide for the airports in NTTR and there settings. Caucasus map works. [sIGPIC][/sIGPIC] =&arrFilter_pf[gameversion]=&arrFilter_pf[filelang]=&arrFilter_pf[aircraft]=&arrFilter_CREATED_USER_NAME=chardly38&set_filter=Filter&set_filter=Y"]MY SKINS And Helios i7 2600k 3.4 quad w/ Hyper N520 cpu fan_, Asus Sabertooth z77_, RX 580_, Corsair Vengeance 1800 8Gb ram_, 112 OCZ Vertex 3_, Corsair HX 1000, 3 screens res 5292x1050_,and 1 1680x1050 Helios Ir Tracker 5 with Pro Clip_,Hotas Warthog#12167 ... Link to comment Share on other sites More sharing options...
Ramsay Posted December 27, 2018 Share Posted December 27, 2018 (edited) Is AWLS working in NTTR. I cant get it to work. AFAIK AWLS worked in NTTR in the past, however last time I checked in 2.5.3 it was broken at Nellis AFB with zero wind (RWY 21/AWLS Ch 13). I've rechecked using Open Beta 2.5.4.25729 and it's still the same. Note: a A-10C detects the ILS in the same mission, so it's not a map/wind/ATC issue. Edited December 28, 2018 by Ramsay Add AFAIK prefix i9 9900K @4.7GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 10 Pro x64, 1920X1080 Link to comment Share on other sites More sharing options...
chardly38 Posted December 27, 2018 Share Posted December 27, 2018 Also Creech no good [sIGPIC][/sIGPIC] =&arrFilter_pf[gameversion]=&arrFilter_pf[filelang]=&arrFilter_pf[aircraft]=&arrFilter_CREATED_USER_NAME=chardly38&set_filter=Filter&set_filter=Y"]MY SKINS And Helios i7 2600k 3.4 quad w/ Hyper N520 cpu fan_, Asus Sabertooth z77_, RX 580_, Corsair Vengeance 1800 8Gb ram_, 112 OCZ Vertex 3_, Corsair HX 1000, 3 screens res 5292x1050_,and 1 1680x1050 Helios Ir Tracker 5 with Pro Clip_,Hotas Warthog#12167 ... Link to comment Share on other sites More sharing options...
Recommended Posts