Nealius Posted August 20, 2022 Posted August 20, 2022 Previous report focused only on the Hawkeye but it appears to be a much wider issue than just that one aircraft, and is specifically on AI aircraft, not client aircraft or static objects, so openig a fresh and mores specific report wth track files. See attached tracks (South Atlantic map, Raven One liveries). Offline track and Client track (Google Drive) Note in the client track the static Hornets on Elev.4 and the Hawkeye by Elev.3 are the correct livery. Note the AI Hornets on the Sixpac and the AI Hawkeye on Elev.2 are default liveries instead of the Raven One liveries they should be using. Client screenshot top, offline screenshot bottom.
Flappie Posted September 3, 2022 Posted September 3, 2022 (edited) Was it a dedicated server? If so, the issue is already reported (for different aircraft, not just the Halwkeye and the Hornet). Edited September 4, 2022 by Flappie ---
Nealius Posted September 4, 2022 Author Posted September 4, 2022 (edited) 16 hours ago, Flappie said: Was it a dedicated server? If so, the issue is already reported (for different aircraft, not just the Halwkeye). Yes, dedicated server. It's also wildly inconsistent, with some Hornet liveries working and others not. I didn't see any other threads than the Hawkeye one I posted a while back without tracks. Edited September 4, 2022 by Nealius
Flappie Posted September 4, 2022 Posted September 4, 2022 It was reported internally. F-14, MiG-21 and F-16 are also affected. The report was bumped a few weeks ago. 2 ---
Nealius Posted September 4, 2022 Author Posted September 4, 2022 (edited) @Flappie The Mission Editor for a while now has been reverting to default skins as well (in the drop down but not visually). Are these related or separate? Edited September 4, 2022 by Nealius
Flappie Posted September 4, 2022 Posted September 4, 2022 1 hour ago, Nealius said: @Flappie The Mission Editor for a while now has been reverting to default skins as well (in the drop down but not visually). Are these related or separate? No, these bugs have nothing in common. The ME bug is reported as well. 1 ---
Buzzer1977 Posted September 7, 2022 Posted September 7, 2022 The bug got reported several times in the past but there never was much feedback that it got recognized. AMD Ryzen 9 5950x, MSI MEG x570 Unify, G.Skill 128GB DDR4-3200, MSI RTX3090 Ventus 3x 24GB, Samsung PCIe 4.0 M.2 1TB 980 Pro, Seagate PCIe 4.0 M.2 2TB FireCuda 520, Quest 3
Flappie Posted September 8, 2022 Posted September 8, 2022 It's hard to keep track of all threads when people don't use the search tool before posting... I'll ask for a tag in this thread of yours as well. 2 ---
Buzzer1977 Posted September 8, 2022 Posted September 8, 2022 7 hours ago, Flappie said: It's hard to keep track of all threads when people don't use the search tool before posting... I'll ask for a tag in this thread of yours as well. People will repost if threads don't get tagged. Maybe it would be more efficient to use a issue tracking tool like redmine, mantis, etc ... or github issue tracker. 1 AMD Ryzen 9 5950x, MSI MEG x570 Unify, G.Skill 128GB DDR4-3200, MSI RTX3090 Ventus 3x 24GB, Samsung PCIe 4.0 M.2 1TB 980 Pro, Seagate PCIe 4.0 M.2 2TB FireCuda 520, Quest 3
Flappie Posted September 9, 2022 Posted September 9, 2022 This probably wouldn't solve the people-don't-use-the-search-tool issue. ---
Nealius Posted September 9, 2022 Author Posted September 9, 2022 (edited) Problem with the search tool is that the user has to use specific search terms to find the other threads. If they don't happen to use the right keywords they won't find it. That happens to me a solid 80% of the time I search for something. Edited September 9, 2022 by Nealius
Flappie Posted September 9, 2022 Posted September 9, 2022 Yes, neither the search engine nor the thread titles are perfect. This is why the 'Reported earlier' tag exists. 1 ---
Recommended Posts