pewbeef Posted April 21, 2012 Posted April 21, 2012 Hey, was playing a multiplayer game today when I suddenly got hit by a MANPAD (I assume it was one). Lost navigation data in the hit, but managed to RTB with TCN. Requested power on from ground crew and shut down my only working engine. After repairs on the base I got the "Warm start" message in the alignment page, and the alignment numbers looked good, so I assumed it was good to go. But when I got back into the air the navigation system was a bit screwed. On the TAD, it looked like my airplane and waypoints were at their right places. But the steerpoint cue on the HUD was way off, pointing in the wrong direction and acting really weird. Tried to to do an inflight alignment, but things didn't get much better. Wasn't able to release a JDAM either. Now I wonder what I did wrong. Should I have resetted something after the reapir? I'm quite familiar with the CDU, but much of it is a mystery to me. Linking a track file, sorry for the enormous size! http://dl.dropbox.com/u/12649515/nav_fail_after_repair.trk Really appreciate any help! :)
Kalahari Posted April 21, 2012 Posted April 21, 2012 Have the same problem in a mini mission I made. JTAC give me the 9 line but after inputing everything in CDU,the target steerpoint is totally somewhere else. When I target using the TAD it works. System Specs : Processor ; Intel®Core i7-3930 CPU@ 3.20GHz. RAM -16.0 GB Type-64bit GPU-GTX 970 Never eject over a village you've just bombed - US Marines Gen.
pewbeef Posted April 22, 2012 Author Posted April 22, 2012 Kalahari, did you receive the problem after repairs aswell? I just remembered that I printscreened the situation for those of you who cant be bothered to start up the track! It isn't the best pic, but you can see on the TAD that I'm almost on course towards WP10 - Bridge. However, most of the information on the HUD seems confused. Does anyone make anything of it?
Speed Posted April 22, 2012 Posted April 22, 2012 Have the same problem in a mini mission I made. JTAC give me the 9 line but after inputing everything in CDU,the target steerpoint is totally somewhere else. When I target using the TAD it works. That's probably because you were in the wrong UTM zone. An MGRS coordinate looks like 38T KM 553 112, where the 38T is the UTM zone. If you have 37T instead of 38T, you'll be hundreds of miles off. JTAC doesn't tell you UTM zone by default, but you can install mods to fix this. Intelligent discourse can only begin with the honest admission of your own fallibility. Member of the Virtual Tactical Air Group: http://vtacticalairgroup.com/ Lua scripts and mods: MIssion Scripting Tools (Mist): http://forums.eagle.ru/showthread.php?t=98616 Slmod version 7.0 for DCS: World: http://forums.eagle.ru/showthread.php?t=80979 Now includes remote server administration tools for kicking, banning, loading missions, etc.
pewbeef Posted April 22, 2012 Author Posted April 22, 2012 The thing is that in that mission all coordinates were given in Lat/Long. If you take a look at the screenshot, you can see that WP10 is selected on the TAD and on the HUD, but the guidance cue on the HUD is pointing in the wrong direction. I'm aware of the 38T and 37T zones, but that is not the problem in this situation I would say. But thank you for your reply anyway :)
Kalahari Posted April 22, 2012 Posted April 22, 2012 That's probably because you were in the wrong UTM zone. An MGRS coordinate looks like 38T KM 553 112, where the 38T is the UTM zone. If you have 37T instead of 38T, you'll be hundreds of miles off. JTAC doesn't tell you UTM zone by default, but you can install mods to fix this. So I have to wait till I'm in the same grid with a missile to ask for the 9 line? Bugger! For those of us a bit slow,thats a pain in the butt. System Specs : Processor ; Intel®Core i7-3930 CPU@ 3.20GHz. RAM -16.0 GB Type-64bit GPU-GTX 970 Never eject over a village you've just bombed - US Marines Gen.
Jona33 Posted April 22, 2012 Posted April 22, 2012 No you need to change it. Above the line for co ordinates when creating a new waypoint you can change 37T to 38T. Always remember. I don't have a clue what I'm doing
Kalahari Posted April 22, 2012 Posted April 22, 2012 And one more thing,keep in mind that though some of us play nd love this game,we are not computer programmes highshakes. The process u described to download MOD is no cake walk for some of us. Thats why I prefer upgrades,so everything is all there. The lua files u lot always talk about,I have no idea where that is. All I do is download the game nd play. System Specs : Processor ; Intel®Core i7-3930 CPU@ 3.20GHz. RAM -16.0 GB Type-64bit GPU-GTX 970 Never eject over a village you've just bombed - US Marines Gen.
Kalahari Posted April 22, 2012 Posted April 22, 2012 No you need to change it. Above the line for co ordinates when creating a new waypoint you can change 37T to 38T. Thanks bud. System Specs : Processor ; Intel®Core i7-3930 CPU@ 3.20GHz. RAM -16.0 GB Type-64bit GPU-GTX 970 Never eject over a village you've just bombed - US Marines Gen.
pewbeef Posted April 23, 2012 Author Posted April 23, 2012 So no one's got any answer to my issue? :P
112th_Rossi Posted April 23, 2012 Posted April 23, 2012 There are certain things ground crew can't repair. I would imagine NAV avionics would be one of them. Perhaps it was damaged after being hit? Did you try and do a realignment on the ground?
pewbeef Posted April 23, 2012 Author Posted April 23, 2012 Yeah, perhaps that's the issue. Didn't try a ground alignment, but instead requested power on from ground crew to keep the alignment... What I did try was a flight alignment, but it didn't help. But your theory that ground crew can't fix everything might be the answer to my issue. If it happens again I'll try a cold start and see if that makes things better!
112th_Rossi Posted April 23, 2012 Posted April 23, 2012 I would just restart the alignment on the ground and see if that helps. But I think the ground crew just get your plane back in the air.
Grimes Posted April 23, 2012 Posted April 23, 2012 I wonder if you must completely reset the system to get it working again in proper order. aka, when you are getting repaired shut down the EGI and CDU power and only turn it back on once your aircraft is fully repaired. The right man in the wrong place makes all the difference in the world. Current Projects: Grayflag Server, Scripting Wiki Useful Links: Mission Scripting Tools MIST-(GitHub) MIST-(Thread) SLMOD, Wiki wishlist, Mission Editing Wiki!, Mission Building Forum
pewbeef Posted April 23, 2012 Author Posted April 23, 2012 Ok, so either the ground crew repairs the airplane entirely, but one has to do a complete shutdown and startup (aka cold start) for the navigation to work properly again... OR The ground crew can NOT fix the navigation system, so the only thing you can do really is to get a new airplane if you want working navigations again. Can anyone confirm which one of those are right (or if it's all wrong)?
Depth Posted April 23, 2012 Posted April 23, 2012 Yes, you have to shut down the engines for the ground crew to start repair, and they repair every single piece, even remove bullet holes. Use either ground power or APU during shutdown to prevent losing power to CDU and IFFCC :) [sIGPIC][/sIGPIC]
pewbeef Posted April 23, 2012 Author Posted April 23, 2012 Yes, but that is exactly what I did! I requested ground power on while my engines were shut off for repairs to keep the alignment, but when I got back in the air I had this issue I'm describing.
pewbeef Posted April 23, 2012 Author Posted April 23, 2012 Haha, that is one option I haven't quite learned yet :P
Tailgate Posted April 23, 2012 Posted April 23, 2012 Yes, you have to shut down the engines for the ground crew to start repair, and they repair every single piece, even remove bullet holes. Use either ground power or APU during shutdown to prevent losing power to CDU and IFFCC :) Funny, never knew ground power was modeled. I've had instances where the repairs are not 100%, particularly with heavy engine damage, I was unable to get to full RPMs after Repair. Tried flushing the fuel, manual ignition, the whole 9 yards.
Depth Posted April 23, 2012 Posted April 23, 2012 Hm, sounds like I was wrong about a 100% fix. I haven't found a middle-ground between a few bullets here and there and being wiped the floor with. Could be intended or it could be a bug. We should get it clarified if the thread is noticed by any of the testers :) [sIGPIC][/sIGPIC]
Nate--IRL-- Posted April 23, 2012 Posted April 23, 2012 It's a bug IIRC. Nate Ka-50 AutoPilot/stabilisation system description and operation by IvanK- Essential Reading
jeffyd123 Posted April 24, 2012 Posted April 24, 2012 ive had my nav computer shot up. I land, repair and then restart the entire alignment over with a turned off NAV computer. i7 8700K @ 4.4Ghz, 16G 3200 RAM, Nvidia 1080Ti, T16000 HOTAS, TIR5, 75" DLP Monitor
pewbeef Posted April 26, 2012 Author Posted April 26, 2012 Flew a bit today and I accidently broke my speed pitot when entering the runway (a10 is doesn't turn well at 80 knots :P). So the pitot was missing from the wing and I obviously didn't have any speed readings. So I took a lap and landed again to fix the damage. Repairs messages came up and I got my pitot back on the right wing. But when I took off again, I still did not have any speed readings...makes me think that the crew doesn't really fix the avionics, but instead, as someone said earlier, just gets the plane back in the air...just wanted to share this experience :)
NoCarrier Posted February 19, 2013 Posted February 19, 2013 It's a bug IIRC. Nate I can confirm that this bug is still present in the 1.2.2.7570 A-10C module. Ran into it repeatedly the last couple of weeks after getting shot up and RTB'ing. Thought I was being clever by doing an in-flight alignment while getting back to the AO, but the HUD symbology (steering cues, TGP diamond, SPI symbol, etc.) got completely screwed every time. I guess I'll try the ground alignment option next time.
Recommended Posts