Jump to content

Andrei

ED Beta Testers
  • Posts

    2821
  • Joined

  • Last visited

Everything posted by Andrei

  1. Да. Ничего личного, просто бизнес. Я думаю, найдется немало людей, которые снова заплатят за МиГ-21 уровня F-14. Или купят тот же МиГ-21 2.0 от LN если они его доведут до современного облика.
  2. Тут сложно сказать что кто-то лучше, а кто-то хуже. Крайние релизы внешников - очень хорошие. Тот же F-14, F-15E, Mirage F1. У внешников (РАЗБАМ) на данный очень интересно смоделирован радар. ЕД над этим работает, как мы видим по разным white papers, но довольно неспешно. Внешники в целом развивают свои модули быстрее модулей ЕД. Я бы сказал что в данный момент у Разбама и Хитблюров вполне себе паритет по качеству и исполнению. И вполне возможно что они в будущем выйдут вперед.
  3. Unlike in Viper, selecting the donors / members is hugely impractical on the SA page where your contacts may be 100 miles away in a tight formation. In the real world I suppose the problem is offset my having the ability to slew the HSI / SA display. Is this going be implemented as well?
  4. САУ не стабилизирует самолет по крену, поэтому тримироваться придется вручную. Я обычно делаю так: автопилот отключить полностью. Набрать нужную скорость, оттримироваться по крену. Далее автопилот ATT Hold, BHOLD. Будет лететь более-менее прямо. Подчеркну необходимость полного отключения AP, потому что в режиме ATT Hold реакция самолета на триммер неоднозначная. Вначале чуть дергается, но эффекта нет. Я так и не смог понять баг это или фича.
  5. Если цель находится на фоне подстилающей поверхности, то при отключении фильтра, ты тут же её потеряешь за фоном. Почему не сделали логику переключения в зависимости от того насколько относительно выше или ниже цель - не знаю. На F-14 оператор может сделать такой трюк вручную, но я ХЗ как это повлияет на сопровождение ракеты.
  6. Sure. Here goes. Tacview-20230327-222004-DCS-Kerman Mission 7 FINAL.zip.zip
  7. On two separate occasions the WM does not perform as expected when attacking the targets. First occasion was during Phase 1 of the attack (DEAD) - he was flying in formation and never did anything. The script did take care of the threat though. On the second occasion he did fire -65 as expected, and afterwards released single bomb. After the release he continued straight and level and flew north. Tested with both MT and ST. Unfortunately I don't have tracks, but I have TacView if needed.
  8. Yay, official announcement is here Looking forward to this one - finally an excuse to fly the Harrier. Really enjoyed your A-10 and F-18 campaigns.
  9. The idea is really nice. And I appreciate all hard work that was put into those missions. It's amazing work and puts DCS to it's limits. The execution, however is what suffers. And it's not really author's fault, it's something that you simply can't do things in believable and coherent fashion in DCS. The limits are still pretty narrow. Despite excellent briefings there are still many unknowns that await you when you're flying. It's beautiful and engaging, yet quite frustrating especially after doing similar exercises with humans online.
  10. Я летаю в скваде на Хорнете уже года три-четыре и жизнь без суперавика не представляю. Когда сделают директоров - будет вообще хорошо. Самая главная проблема - это онлайн. Суперавик плохо совместим с онлайном когда у тебя сидит живой Marshal / Approach Controller / LSO. Во-первых не регулируются огни посадки что приводит к утомительным действиям когда тебе приходится разговаривать и с живым УВД и ИИ диспетчером лишь для того, чтобы он включил огни. А это забивает частоту которая и так при Case III из восьми самолетов довольно-таки занятая. И вторая проблема в том, что для работы ACLS тоже нужно взаимодействие с ИИ. Эти вещи хотелось бы конфигурировать вручную.
  11. DLSS и многопоточность. Неужели мы наконец-то получим 90+ кадров в VR?
  12. Well. Whatever happens in the GPU market last couple years, it was always end-users (gamers) who suffered. Pascal was the last decent value offering we've had on the market which we could actually get our hands on. Turing was overpriced with RT and no real competition in high-end. Ampere with RDNA 2 were decent, but then you've got the crypto boom and unless you're lucky and living in US, you could never get your hands on one of those at decent price. Lovelace and RDNA 3 are overpriced again with both AMD and Nvidia trying to recover from crypto hangover capitalizing on gamers as well. Life sucks, but have to get on with it
  13. Thanks to AMD naming conventions I've misinterpreted your post. I thought with 7950 you're talking about GPU, while you probably meant CPU
  14. Definitely NOT asking how you got your hands on 7950 ES
  15. Now that I finally got the 4080 I thought I could add a few more cents to the benchmarks. Maybe some people upgrading from the older hardware will find it useful. I've recently upgraded from Zen 3 5800X to 5800X3D and just now from 2070 Super to 4080. So there will be stats for both upgrades. Setup All tests are done in VR (Reverb G2). By no means those figures are scientific, so treat those as ballparks. The frametimes are taken using using OpenXR toolkit that records results every second. Therefore the resolution isn't all too great and might not show details of e.g. 1% lows. For DCS settings, all tests until indicated otherwise are perfomed with the following. Those are my normal settings for flying online and offline. For VR specific settings PD in DCS is 1.0 and Open XR resolution is downscaled to 65% of max for Reverb G2. null CPU Tests Let's start with CPU upgrade. Those are the runs of Plasma's Torture map which is loading CPU very well. Objectively you don't see too much of a difference between 5800X and X3D. Subjectively V-Cache gives you a much smoother experience. The tests were done in DCS version 2.8.0.32937. 5800X Plasma Torture Map 2070S Average FPS: 42 Average CPU frametime: 15 ms Average GPU frametime: 23 ms 5800X3D Plasma Torture Map 2070S Average FPS: 42 Average CPU frametime: 13 ms (-2 ms) Average GPU frametime: 23 ms (same) 3D cache gives you around 15% improvement in CPU frametime, but as mentioned above, the overall experience is subjectively better due to less stutters. GPU Tests Now to GPU tests. Note that compared to CPU test prevoiusly, this one is using DCS 2.8.1.34437, newer graphics driver and CPU is curve optimized to -20 all cores. So don't compare it directly to previous test. NOTE: When you see "low spikes" in GPU frametimes it is where I pointed my helmet up towards the sky, which of course gives it a nice FPS boost / FT decrease. First one is Marianas benchmark used earlier by Th3ChosenOn3 and xoxen. As CPU frametimes there are quite low, I think it's a good indicator of overall graphics performance. 5800X3D Marianas 2070S Average FPS: 31 Average CPU frametime: 8 ms Average GPU frametime: 33 ms 5800X3D Marianas 4080 Average FPS: 68 Average CPU frametime: 6 ms (-2 ms) Average GPU frametime: 15 ms (-18 ms) As you can see, the FPS and GPU frame times doubled with the same graphics settings. Interestingly enough, the CPU frame time has decreased a bit as well, which suggests that 40 series might be working better with CPU then 20 series. You'll see this behavior repeat itself in another test. Next we turn back to Plasma's map to evaluate overall performance increase in CPU bound scenario. 5800X3D Plasma Torture Map 2070S Average FPS: 40 Average CPU frametime: 13 ms Average GPU frametime: 25 ms 5800X3D Plasma Torture Map 4080 Average FPS: 70 Average CPU frametime: 11 ms (-2 ms) Average GPU frametime: 10 ms (-15 ms) Again, we see that performance has pretty much doubled and in this case we're really becoming bottlenecked by CPU occasionally. However, the CPU frametimes have also improved. High Settings Finally, I wanted to see how does RTX 4080 handle higher graphics settings. I switched OpenXR render to 100% (up from 65%) and DCS graphics as on screenshot below. The biggest change was shadows (terrain = default and shadows = high). 5800X3D Marianas 4080 High Settings Average FPS: 47 Average CPU frametime: 7 ms Average GPU frametime: 21 ms Obviously performance is lower than with original graphics settings, but still more than playable for me. In fact, it's giving a better framerates and notably better picture then 2070S at lower settings. Conclusion Overall, the results were pretty much according to my expectations. Huge improvement with same settings and still better performance with better visuals. Also, it was interesting to see better CPU utilization with 4080. This upgrade was due a loooong time ago. I skipped 2020 due to availability, I skipped 2021 because of miners. At the end of the day I paid same price for 4080 what it would effectively cost me to buy a 3080 a year ago. Is it worth it? For me - I think so.
  16. Вставлю свои пять копеек С появлением MSFS все хотелки по поводу транспортников и полётов из точку А в точку Б в ДКС можно смело убирать в чулан. В MSFS это делается интереснее, реалистичнее и самое главное, для этого там есть вся инфраструктура, в том числе и онлайн. Проблемой остается наличие бортов и ФМ, но я думаю что этот вопрос решится куда быстрее чем в ДКС появятся большие карты, высокодетализованый ландшафт и необходимая аэронавигационная инфраструктура. Для ДКС нужен фокус именно на боевой составляющей, в особенности: 1. Поведение ИИ отдельных юнитов и групп юнитов 2. Симуляция театра военных действий и соответствующую обвязку (та самая динамическая кампания) 3. Инструментарий для создания шаблонов ДК для кампаний в сингле и мультиплеере 4. Возможность эффективно использовать ресурсы современных ПК чтобы всё это великолепие выше работало. И будет нам всем счастье. Работы в этом направлении явно ведутся как показывают новости и предыдущие релизы, но довольно медленно. Что и понятно, так как основной фокус уже десятилетия (если брать еще со времен Фланкера) делался на отдельных ЛА, их авионике и ФМ, а не на развитие "мира".
  17. I only have a WQHD monitor, so 1440p is max. However, I fly exclusively in Reverb G2, although at 65% scale resolution with 2070S. At 100% that thing gets pretty close to 4K, so that should be relevant comparison.
  18. Вот это конечно обидно с точки зрения близких ТВД. Та же карта Сирии и Египта просто просится быть одним большим куском - открывает отличные возможности для дополнительного геймплея и создания довольно-таки интересных сценариев.
  19. Fair point. But gentlemen few post above did the F/A-18C on Marianas map, both and high and low level, which is fairly representative of the GPU performance. Granted, Hornet is not as heavy as Apache, but it's still a full fidelity module. Some maps, and modules like Channel map are so poorly optimised, it doesn't make too much sense testing and benchmarking with - not overly representative of general performance. I guess not even 5090 with I9-15900K will make good framerates there
  20. Правда. Особенно если сервер на другом компьютере. Но возни больно много. И только в том случае, если большой затык именно по процессору. Хотя ладно, о чем это я. В ДКС всегда самый большой затык по процессору
  21. Jumped the gun, bought 4080 at last. Will do some VR comparison tests between 2070S and 4080 when it arrives
  22. Thank you, and @xoxen for taking the time to do this. This is really appreciated. It's so damn difficult to get any good figures for DCS, let alone a side-by-side comparison of latest hardware. Your efforts will not be forgotten
  23. 4080 is definitely faster than 3080 Whether it's better as in value for money it a completely different topic though. I'm seeing 4080 back to stock in many places after last week's 7900 series 'fiasco'. Putting that in brackets, because it's not a bad card, just having some teething(?) problems and following Nvidia steps in bad value for money. And that new stock is appearing to come at more reasonable prices. My hope is that after Christmas holiday period is over, they will start discounting it even more so that I could grab one at more 'reasonable' 1200-1300 Euro. Still insane, but it beats current ~1500. Alternatively, AMD might pull their s~t together and make that driver brakethough giving back 10-15% performance. We'll see.
  24. What's interesting is that the general Radeon cards VR behavior exhibits itself here as well. The frametimes are all over the place, resulting in a very "thick" line. That also adds to the stutters.
×
×
  • Create New...