Hip Hind

Вот первые цифры для ПКВ с "новыми" С-8ОФП из моих тестов. Расстояние до цели 3500, высота 100 (или с ПМВ, не имеет значения), скорость 200. До апдейта по таблицам это 140 с небольшим кабрированием для наложения метки на цель и хорошей дорожкой через всю площадную цель. После апдейта значение ПКВ для указанных вводных - 80.

The last update said that the S-8 weights had been clarified. Okay. Now flew to the range, gave a salvo S-8OFP with 3.5 km at the data from table 140, so there was a double overflight. Flew away in 7-8 kilometers. I set the 122 for 3 km gave a volley of 3.5 km flew to the same place where the first. Before this specification, all the data from the tables were correct and when setting the PKV 140 with a volley from 3.5 km the track clearly covered the target area. If the characteristics are refined, what tables should we use now?

@PilotMi8 а что случилось с С-8? В последнем апдейте написано что уточнены весовые характеристики С-8. Ок. Сейчас вылетел на полигон, дал залп ОФП с 3.5 при данных из таблицы 140, так там перелет был в два раза. Улетели километров за 7-8. Выставил 122 для 3км дал залп с 3.5 улетели туда же куда и первые. До этого уточнения характеристик все данные из таблиц были корректны и при выставлении на ПКВ 140 при залпе с 3.5 дорожка четко накрывала район цели. Если уточнены характеристики то по каким таблицам теперь работать?

Не, это не проблема. Проблема - это когда на дровах AMD в режиме MT постоянные краши. Вот это проблема, уже сотни логов отправлены - до сих пор тишина. Самая первая бета на МТ работала ок, сейчас даже до нее не откатиться. На прямой вопрос - опять тишина. А и вот еще - в русскоязычной ветке новостей будут апдейты по ОВ? А то уже версии три или четыре пропустили.

Спасибо.

@PilotMi8 Приветствую, в таблицах углов для НАР указанная скорость это по прибору или истинная по ДИСС?

The 5700xt is mentioned here because on MT the AMD drivers cause a crash on this particular GPU.

Thanks, but I need to roll back to the specified version. After this version the MT crashes started.

Yes, AMD drivers in MT cause crashes since OB 2.8.3.37854.1. I have a fresh driver 23.4.1 installed - with it also permanent crashes in MT. The only solution so far is to abandon MT and use ST. In this mode I had to reduce some settings to remove freezing, which in MT did not occur at high settings, but so far in the fresh OB in ST there were no crash.

Сould you give me a link to a solution to this problem? My screen sometimes flashes with a black square on the left.

Turned off VSYNC, turned it on in the driver. Turned Visibility down to high - crashed after a few minutes. dcs.log-20230417-142658.zip @WWSmith Tell me more about this point please: -added TdrDelay and TdrDdiDelay registry keys

I need to roll back from an last openbeta to the specified version. Updater writes that it is not available. Two weeks ago I was able to rollback normally, now the version is not found. How do I roll back to the specified version?

@BIGNEWY So far, everything fits together. All 5700 GPUs have the same crash start time, the same error, the version that started to fail on AMD is OB 2.8.3.37854.1

Yes, it is. If you roll back to version 2.8.3.37556 of March 10, there is a good chance that the CTD will disappear. I started having crashes at the same time, so I rolled back to that MT version.

@Amarok_73 OB MT version 2.8.3.37556 also causing CTD?

@BIGNEWY I have the same video card as Amarok_73 users who created this thread and WWSmith. Can you check the assumption that it is the AMD driver that causes the crash since OB 2.8.3.38090? I have problems with MT started with version 2.8.3.38090, on the first version of MT 2.8.3.37556 no problems at all. Also everything is standard, all drivers updated, system updated, swap file to 32GB. Did both slow restores, deleted all mods and so on. I get crashes anyway. I will roll back to my mt 2.8.3.37556 and all the problems disappear, everything works fine and stable.

saw) Can you roll back to version 2.8.3.37556 OB? I don't have any problems with MT on it. Starting with version 2.8.3.38090, the failures start.

Wow! RX 5700 XT! Maybe it's because of AMD? I have the same GPU.

You don't get it. Crashes started with version 2.8.3.38090 and are still going on. When I roll back to OB 2.8.3.37556 (MT) the crashes disappear. It turns out that I cannot update to the latest current version of OB.

The drivers are all the latest, Windows is up to date. CPU stock, no overclock. There are no crashes on version 2.8.3.37556, so in this version the GPU does not fail?

2.8.4.38947 still has 'computeOptimalBarriers' error. 32GB swap file. Last version shaders were removed, launching dcs, working in editor - ok. Launching mission - ok. After a few minutes - crash. Rolling back to 2.8.3.37556 - everything works just fine, no lags or crashes. Crashes I have started with version 2.8.3.38090, there was information that on April 14 will be released fix for this bug, but as you can see, this either does not help or not yet fix. dcs.log-20230416-155202.zip

Thanks, Barthek! Very, very amazing work! JSGME not problem

Нет, так же как и остальных вариантов Ми-24. Подвойский очень подробно объяснил почему этого не будет.

Я не знаю, какой у тебя не слабый комп, но на моем 7900K + RX 5700XT и авианосцы и Атлантика и Сирия после MT встали в стабильные 60fps. Были нюансы и дикие фризы временами, но я вымел моды и все это старье, которое не обновляется годами и не нарадуюсь теперь. К синглу возврат однозначно закрыт.

Hello @Flappie Nice work. Question - at a small scale the map is displayed in full, but when I zoom in and make a larger scale on the map appear "holes". Is this just my problem or not? I didn't see similar posts here. The mod is connected via JSGME.