tietze Posted January 25, 2013 Posted January 25, 2013 (edited) Hi, when HUD is damaged it does not work after aircraft repair. DCS World 1.2.2 (7570). When turning on HUD it initially takes some time to warm up and in this time the "HUD NO READY" in the overhead panel is lit up. Seemingly this is not lit up after repair, hinting that the damage still persists to the HUD. I have had this issue since the good ol' Black Shark days and I consider it a bug. Please prove me wrong :-) Link to example track below. Procedure to reproduce: 1) Get HUD damage. 2) Turn off K-041 prior to repair (apparently this step apparently does not do anything). 3) Land and repair aircraft. 4) Startup aircraft. 5) HUD is not working/ showing. Example track: http://dl.dropbox.com/u/2910357/fsim/Threads/HUD%20Repair/HUD-repair.zip [Edit: earlier confirmed by Nate for version 1.2.0] Edited February 26, 2013 by tietze Please fix the KA-50 bugs :-) Black Shark: Controller profile & setup, TrackIR profile, pit. Warthog HOTAS: Lubing the stick and extending the stick. Posts on howto customize switches in DCS & . Must-have mods for DCS World and KA-50 (mostly JSGME). Casual couch pilot, watching capped.tv...
ShuRugal Posted January 10, 2014 Posted January 10, 2014 Bumping for relevancy, this bug is astonishingly aggravating. It's got to the point with me that (during online play) if my HUD goes out, I despawn and grab a new bird as soon as I am able to break contact. There is little point in having a repair procedure if it leaves one of the most vital instruments of the AC nonfunctional.
ShuRugal Posted January 11, 2014 Posted January 11, 2014 Can we -please- get a response from someone even remotely official about this? This has been a game-breaking problem since the release of World, a solution is somewhat overdue.
tietze Posted January 11, 2014 Author Posted January 11, 2014 It is already confirmed by Nate from ED Testers team. That said it would be nice to see it fixed together with some if not all of the other bugs related to the KA-50. It is probably not hard, but still requires someone to but their mind, work and resources into coding of the KA-50 which is probably not very present for anyone. I understand multiplayer (1.2.7 open beta) and EDGE being of highest priority at the moment. Please fix the KA-50 bugs :-) Black Shark: Controller profile & setup, TrackIR profile, pit. Warthog HOTAS: Lubing the stick and extending the stick. Posts on howto customize switches in DCS & . Must-have mods for DCS World and KA-50 (mostly JSGME). Casual couch pilot, watching capped.tv...
ShuRugal Posted January 11, 2014 Posted January 11, 2014 something else is always "of highest priority at the moment" If the "minor" things are continuously ignored, it says some unpleasant things about the future of DCS-branded products. It says that selling new widgets is more important than making sure the current widgets all function correctly. I don't believe that ED operates on that model, and I'm sure they don't intend it to appear that way, but if there is no distinguishable difference between being a thing and not being a thing to the outside observer... then the distinction is moot. A bug like this is almost certainly a single-line oversight in the repair function. I don't know what the code looks like behind the scenes, but based on the fact that it restores the AC systems to spawn state while leaving switches and loadout alone, it seems probable that the "repair" simply runs through a list of systems and damage models, resetting each to default state. The HUD computer was clearly left out of the list by mistake.
BitMaster Posted January 30, 2014 Posted January 30, 2014 something else is always "of highest priority at the moment" If the "minor" things are continuously ignored, it says some unpleasant things about the future of DCS-branded products. It says that selling new widgets is more important than making sure the current widgets all function correctly. I don't believe that ED operates on that model, and I'm sure they don't intend it to appear that way, but if there is no distinguishable difference between being a thing and not being a thing to the outside observer... then the distinction is moot. A bug like this is almost certainly a single-line oversight in the repair function. I don't know what the code looks like behind the scenes, but based on the fact that it restores the AC systems to spawn state while leaving switches and loadout alone, it seems probable that the "repair" simply runs through a list of systems and damage models, resetting each to default state. The HUD computer was clearly left out of the list by mistake. Sad but seems to be true :( Please, don't change to the "ripes at the customers desk" policy. The Ka-50 and DCS is no Banana :helpsmilie: Bit *has it ever been different with Flight Sims ? IMHO NO !! have I ever stopped addressing this strange fruit dealers policy ? NO !!! Gigabyte Aorus X570S Master - Ryzen 5900X - Gskill 64GB 3200/CL14@3600/CL14 - Sapphire Nitro+ 7800XT - 4x Samsung 980Pro 1TB - 1x Samsung 870 Evo 1TB - 1x SanDisc 120GB SSD - Heatkiller IV - MoRa3-360LT@9x120mm Noctua F12 - Corsair AXi-1200 - TiR5-Pro - Warthog Hotas - Saitek Combat Pedals - Asus XG27ACG QHD 180Hz - Corsair K70 RGB Pro - Win11 Pro/Linux - Phanteks Evolv-X
Recommended Posts