wernst Posted January 2, 2016 Posted January 2, 2016 (edited) In world 1.2 I and 1.5 was able to complete quite some ILS approaches with A-10C to different fields - always successfully. All landings have been performed in difficult vis conditions, e.g. even below IFR limits at night with heavy snow and less than 1 nm vis. I’m sorry to say but so far I have no luck with world 2.0. Each A-10C ILS approach e.g. to KLSV or into LAS Intl. provides serious issues for a save landing at night under IFR conditions. During final approach from outer to inner marker the HSI begins to bounce up and down giving useless guidance. And the CDI doesn’t give any trustful indication as well, as I’m always 50 to 100 ft off to the RWY when touching the ground. And, even more frustrating, the landing light system doesn’t not only comply with ICAO standards at all, it’s simply not present. It feels like if one would try ILS CAT IIIc landing: RWY visual range: “zero” and decision height: ”zero”, just blind. If (at night) ILS indication gives not precise guidance one would need even more safe and clear light guidance for the final touchdown to the ground. Edited January 2, 2016 by wernst
Destroyer37 Posted January 2, 2016 Posted January 2, 2016 Can you please provide a .trk file? Specs:Fractal Design Define R5 Black, ASUS ROG Strix Z370-E, Intel Core i5-8600K Coffee Lake @ 5.1 GHz, MSI GeForce GTX 1080ti 11GB 352-Bit GDDR5X, Corsair H110i, G.Skill TridentZ 32GB (2x16GB), Samsung 960 Evo M.2 500GB SSD
wernst Posted January 2, 2016 Author Posted January 2, 2016 Can you please provide a .trk file? That trk file only would prove how I missed a safe landing but not the reason for it.
Destroyer37 Posted January 2, 2016 Posted January 2, 2016 Okay...can you please explain the exact conditions of your ILS landing. I.E. Time of day, weather, airport, runway, frequency, altitude, airspeed etc so I can get a better idea of everything so I may go to my sim and run the same configurations to see if I get the same issue? Otherwise a .trk file would be really nice. Specs:Fractal Design Define R5 Black, ASUS ROG Strix Z370-E, Intel Core i5-8600K Coffee Lake @ 5.1 GHz, MSI GeForce GTX 1080ti 11GB 352-Bit GDDR5X, Corsair H110i, G.Skill TridentZ 32GB (2x16GB), Samsung 960 Evo M.2 500GB SSD
wernst Posted January 3, 2016 Author Posted January 3, 2016 (edited) Okay...can you please explain the exact conditions of your ILS landing. I.E. Time of day, weather, airport, runway, frequency, altitude, airspeed etc so I can get a better idea of everything so I may go to my sim and run the same configurations to see if I get the same issue? Otherwise a .trk file would be really nice. TO NELLIS (KLSV) ILS APCH RWY 21L LOC 109,10 APCH CRS 209º INIT ALT 5000ft (13 nm) decent to 4200ft at FAF (7.2 nm) SPD ~160 kt IAS at FAF mission editor default weather set to: “Winter, heavy snow & clouds” Time: 23:00 I have done quite a few ILS approaches under these challenging IFR condition in DCS world 1.2, always with safe landings. The most annoying issue is the missing of any landing light system. NELLIS should have at least medium intensity Approach Lighting (if not ASLF or SALS), system length min. 1,400 feet. I'm not even talking about sequenced flashing lights which is ICAO Standard for a precision approach. When arriving at the IM (at the latest) I should be able to see clearly any approach lighting which gives final (precise) guidance to the RWY threshold. With the aid of a high intensity landing light system I will be able to compensate any inaccuracies either from pilot error or faulty IL system. (too high, off course - NELLIS RWY has more than 10.000 feet) Sorry, no trk file. It hurts when I ran my beloved Warthog into the ground near the RWY - again and again. I'd be glad to hear from your experiences. Edited January 3, 2016 by wernst 1
Destroyer37 Posted January 3, 2016 Posted January 3, 2016 I'm going to test it out and see what I come up with. Thanks for the information. Specs:Fractal Design Define R5 Black, ASUS ROG Strix Z370-E, Intel Core i5-8600K Coffee Lake @ 5.1 GHz, MSI GeForce GTX 1080ti 11GB 352-Bit GDDR5X, Corsair H110i, G.Skill TridentZ 32GB (2x16GB), Samsung 960 Evo M.2 500GB SSD
Blackeye Posted January 4, 2016 Posted January 4, 2016 (edited) mission editor default weather set to: “Winter, heavy snow & clouds” Time: 23:00 Sorry, no trk file. It hurts when I ran my beloved Warthog into the ground near the RWY - again and again. What's your fog setting? I tried to recreate your settings but the ILS into 21L at LSV seemed to work fine. The overall visibility was actually a lot better than expected including the runway lights, so I'm probably missing a setting here. A track or a mission file would be really helpful. Edit: Here's what it looked like for me when the runway came in sight (slightly right and below the TVV) - about 2nm out 900ft AGL. at decision hight (200ft CAT I) Edited January 4, 2016 by Blackeye
wernst Posted January 4, 2016 Author Posted January 4, 2016 What's your fog setting? Here's what it looked like for me when the runway came in sight (slightly right and below the TVV) - about 2nm out 900ft AGL. Thanks blackeye, yes, that's how it looks when snow and moving clouds are blocking your vis. Dramatic. Meanwhile I learned that neither weather settings nor ILS issues are spoiling my fun. I have done what I should have done earlier: I did an ILS APCH into RW 21L at day light with clear sky. I found that the ILS works more or less o.k., still with some unexpected jumps of the bank steering bar (while HSI remains stable) But one could manage a safe ILS APCH to the RWY. So far so good. And I did an ILS APCH into RW 21L at night with clear sky. I learned why I couldn’t see any landing lights at RWY 21L: There aren’t any - initially. The AFB is simply dark, some vague blue taxi lights are visible. Of course I prior have contacted ATC “inbound” hoping for switching on landing lights. Nothing. But as soon as the aircraft touches the ground the landing lights switches on. Irrational! After takeoff and another approach to 21L nice landing lights were visible, even with the row of sequenced flashing lights, which give perfect guidance to threshold under lower limit IFR conditions. Like your 2nd image, an almost perfect landing light system. The question now remains: How did you manage to get the landing lights system to ON when coming from an external base?
Blackeye Posted January 4, 2016 Posted January 4, 2016 I took off at Nellis so the lights were on. Not sure how to get them turned on when coming from another base if "inbound" call does not work. There's another thread about the lighting so I guess ED should know about this already. ATC is wip in 2.0 as far as I know, so maybe that's the problem there - it's called alpha for a reason, I suppose. http://forums.eagle.ru/showthread.php?t=155632
wernst Posted January 4, 2016 Author Posted January 4, 2016 I took off at Nellis so the lights were on. yes, that's what I found a minute ago. With mission editor set "taking off from RWY" at NELLIS at night you'll find both RWYs illuminated pretty well. 21L has the special landing light system for ILS precision approaches. Everything o.k. - unless you want to arrive NELLIS from another airbase at night. But why would you . . .? It is a bug, no problem if I know it's one. I almost got crazy when I flew ILS from CREECH to NELLIS at night with heavy snow and clouds. I could see the RWY only when the steering wheel landing light illuminated the ground. Most the times the ground was not the RWY . . . Even ILS CAT IIIC landings are only possible with special landing light systems.
intx Posted January 4, 2016 Posted January 4, 2016 yes, that's what I found a minute ago. Everything o.k. - unless you want to arrive NELLIS from another airbase at night. But why would you . . .? Emergency landing comes to mind. I am not a pilot (commercial nor military, nor do I play one on TV or after staying a night at Holiday Inn Express) so is there a viable reason why contacting the ATC at NELLIS for landing and getting an "OK" wouldn't turn on landing lights? Would there be a reason why the ATC at NELLIS wouldn't allow you to land for emergency reasons (if you are a recognized US military plane)? I agree with you that it may be just a minor bug to be worked out.
Blackeye Posted January 4, 2016 Posted January 4, 2016 Even ILS CAT IIIC landings are only possible with special landing light systems. Don't think IIIc landings are possible anywhere yet (IRL) and you probably wouldn't need lights for IIIc as it is 0/0 but of course they need to be there for IIIa/b anyway.
wernst Posted January 5, 2016 Author Posted January 5, 2016 Don't think IIIc landings are possible anywhere yet (IRL) and you probably wouldn't need lights for IIIc as it is 0/0 but of course they need to be there for IIIa/b anyway. Yes, I know, ILS CAT IIIC with dec0/vis0 is not implemented anywhere. What I wanted to say is that I FELT like performing a fully blind landing without any aid of landing light - and without any special licensed AP. I got an answer from DCS regarding this issue: I would have to contact NELLIS ATC for landing in order to switch landing lights on - which I did. I called Radio, F5, F1, F1 "inbound" but neither response nor light. Did I miss anything?
wernst Posted January 5, 2016 Author Posted January 5, 2016 Emergency landing comes to mind. sorry, my remark "Why would you . . . " was meant as pure irony. An huge AFB as such must be open with landing lights on during all night. Most of the middle sized fields in the USA (as far as I, German) know, which are not operating during night, will switch on landing lights when pressing MIC button with radio set to TWR FREQ. Is it?
GurbY Posted January 5, 2016 Posted January 5, 2016 About the landing lights: to my experience since 2.0 you have to call ATC and declare you're inbound. After that, the runway lights were turned on.
Blackeye Posted January 5, 2016 Posted January 5, 2016 About the landing lights: to my experience since 2.0 you have to call ATC and declare you're inbound. After that, the runway lights were turned on. Yep - just tested it. Nellis is dark if you start in the air but they turn on lights after inbound call.
Mike77 Posted January 5, 2016 Posted January 5, 2016 Just a thought: check the position of the 3 position Mic switch even if using Easy Comms. Ive seen a couple posts where that turned out to be the solution. Again, just a thought. Sent from my iPhone using Tapatalk. System specs: Windows 7 Pro, EVGA X58 3x classified 3 MOBO, i7 960 @3.2Ghz, 24Gb Ram, Nvidia EVGA GTX 780ti with 3 Gb VRAM. 12th Gen i7 12700K, MSI Z690 Edge mobo, 32 GB of DDR4-3600 RAM (G.Skill Ripjaws V CL16). Gigabyte RTX4080 Eagle OC (Triple Fan, 16GB VRAM), ACER XV322QU 32" IPS monitor (running 2560x1440). 2TB NVMe M.2 Internal SSD (3D TLC NAND PCIe Gen 4 x4). Windows 11.
wernst Posted January 5, 2016 Author Posted January 5, 2016 Just a thought: check the position of the 3 position Mic switch even if using Easy Comms. Yes, Mike, you got it!! The 3-way HOTAS mic switch was the reason. The down position was bound to UHF not VHF AM as needed for ATC. Stupid error. I didn't notice the "UHF" on top of the COM menu. Thanks for thinking along. :thumbup:
Recommended Posts