All Activity

Thanks! You're just proving my point. It's a lot easier to fly and shoot instead of hovering if you don't have pedals. [emoji4] Sent from my SM-A536B using Tapatalk

Ну да, конечно! Лечу миссию в кампании. Выводится сообщение с требованием настроиться на такую-то частоту. Естественно в этом случае триммирую, включаю удержание пространственного положения и высоты, и уже спокойно работаю с дисплеями и клавиатурой ввода данных. Ну или таргет точка приходит от JTAG, то же так же все.

I found the fix! As a test, I disabled the autoexec.cfg - It contained the following values: no_device_hotplug = true, force_cross_eye_recovery_tool = true, options.graphics.stereo_mode_use_shared_parser = true. And now it works. Phew...

An axis working -6/-4/-2/-1/0/1/2/4/6/8/10? Ten positions?

Режимами удержания пользуюсь часто. Они придуманы для того, чтобы немного разгрузить пилота и дать сему возможность частично отвлечься на работу с авионикой. Velocity Hold при сопровождении наземных групп и когда надо аккуратно выглянуть из-за рельефа или препятствия в сторонке. Attitude Hold для выполнения автоматического виража в зоне ожидания на экономических скоростях, в крейсере по прямой. Висение в Position Hold, само собой. Удержанием высоты почти не пользуюсь.

Unfortunately, that didn't help. The farther away the objects are, the more I see them doubled.

Hey there. The UI menu for selecting fuzes in the rearm menu is defined in the weapon settings of the respective module. If its a "custom weapon" it looks something like this: { name = _("BDU-50LD - 500lb Practice Bomb LD"), mass = 241, wsType = {wsType_Weapon, wsType_Bomb, wsType_Bomb_A, BDU_50LD}, Cx = 0.00018, picture = 'bdu-50ld.png', settings = Get_Fuze_GUISettings_Preset("MDRN_B_A_TPLD") } { name = _("Mk-81 - 250lb GP Bomb LD"), mass = 118, wsType = {wsType_Weapon, wsType_Bomb, wsType_Bomb_A, Mk_81}, Cx = 0.00013, picture = "FAB100.png", settings = Get_Combined_GUISettings_Preset("MDRN_B_A_GPLD") } Note the last part of each entry, with that Get_Fuze_GUISettings_Preset and Get_Combined_GUISettings_Preset methods. That is what adds these menus. For weapons that exist already by ED, one can just use their CLSIDs and it works out the box. For example the F-4 uses CLSIDs {SAMP250LD}, {SAMP250HD}. The actual selected fuzing in the cockpit when launching the weapon is then communicated by the module to DCS through the SDK.

Для пилотажа триммеры не применимы на обычном джойстике по той простой причине, чтобы не урезать полные диапазоны отклонения РППУ в виртуальной кабине вертолёта. Это особенность реализации управления в DCS. Апачи имеет игровой сброс триммеров в нейтраль, который появился на нем не сразу. Вторая причина - понимать балансировку по положению ручки, которая и так доступна на FFB. Совсем не триммировать Апачи означает нарушать работу SCAS, которая не будет отцентрирована, будет несимметрично вмешиваться в управление и жалобно пищать о своем переполнении (SATURATED). Она работает в фоновом режиме всегда, а не только в режимах стабилизации. Её тоже можно отключить всю сразу или поканально, уж лучше так, чем просто не триммироваться. Такой вертолет, не похожий на другие. Пилотажить я пробовал во всех режимах. Триммируюсь, хоть и не часто. Перед выполнением петли всегда можно сбросить в ноль триммер, чтобы банально хватило ручки на выводе.

There is no balance in real life either. Compare the navigation systems of the Boeing-727 and Tu-154. The Boeing has an inertial navigation system, and the Tu-154 has an NVU. For those who don't know, it's very similar to the Mi-8 navigation system, only with a correction from the RSBN. But in real life, according to those who flew, it was not used automatically. They were afraid that the plane would turn over. In the early 2000s, the KLN-90 GPS was no longer certified in Russia. It was installed on the Tu-154 and flew on it, turning it manually with a special handle.

Thanks for the explanation! I'd also like to request an axis that would work incrementally for elevation:

Thx, I’ll check it. It would be strange that this problem depends on the map, I haven't tested Syria.

I have a regular Sitek joystick with a twist. There are no pedals.)

Single-threaded no longer exists anymore. Both the executables in bin and bin-mt are multithreaded and bin-mt will be removed in the future. It's all OpenXR these days.

I've had a look at your log and two things jump out. Start with #2 re: the mission editor. 1. You have a bunch of mods in there and some of them have errors. Remove them and try again. Error '=' expected near '|' Line 1 Script ./MissionEditor/modules/me_map_window.lua Error attempt to call global 'BrowningM2' (a nil value) Line 289 Script ./CoreMods/WWII Units/A-20G/A-20G.lua Error attempt to call global 'BrowningM2' (a nil value) Line 239 Script ./CoreMods/WWII Units/P-51D/P-51D.lua 2. You have the below error in a MissionEditor file. Can you try renaming Saved Games\DCS.openbeta\MissionEditor to MissionEditor.old and trying again. 2025-10-07 03:45:32.999 ALERT Dispatcher (Main): Error starting Game GUI: error loading module 'me_map_window' from file './MissionEditor/modules/me_map_window.lua': [string "./MissionEditor/modules/me_map_window.lua"]:1: '=' expected near '|' I went and ran your log through the log analyzer which has also highlighted the corrupted mission editor file. Config File Corruption Delete or rename Saved Games\DCS.openbeta\MissionEditor and try again. Failing that completely rename Saved Games\DCS.openbeta to DCS.openbeta_old (rename not delete so you can copy back your keybindings from Config\Input and stuff from Missions) Running a repair of the game does not touch your Saved Games\DCS.openbeta folder, this is why you may be seeing issues due to corrupted files in there even after running a repar.

Reply to self : Problem found : I uninstalled then reinstalled Raven One campaign and Saint comms are back.

Exactly… either you do all the modules at once to create an honest battleground or just make it equal until you actually can. But this is just absurd.

This? null

Probably true! Can't be done, so there's that.

Hi, Thank you for your feedback. Think you mean the time needed for mission planning and time to get the whole package launched. You may also need to hold for other flights to be ready to push. Time needed for planning is the point of the campaign. There are dozens of scripted campaigns to play if planning is not something you like to do. It would have been possible to make all ai flights start the mission at push point and hot start or even air start the player. But that wasn't what I wanted to do. There are great arcade style campaigns like Rising Squall but it wasn't goal of this campaign. You may of course use time acceleration if getting bored on the deck after flight preparations.

Many thanks for the beautiful work, can’t wait for it to come live. Just a little remark, the pillars are off for the Chelsea Bridge

You're doing absolutely fine. There are way worse contenders here who really should use a translator.

Lolz. Exact same situation here. No need to apologize. Glad we could clear that up.

Haha! Okay, my apologies then! I'm suffering from insomnia these days, it sucks big time! it's 05:52, and I'm a little "edgy". All good! [emoji1303] Cheers! [emoji1] Sent from my SM-A536B using Tapatalk

Hey, Apols, been away for work. Performed the above. Ran dcs_update, file verify check phase stopped halfway though and closes without message. The launcher then opens, so I tried to start the game and momentarily after it logged in gave me a message about AI units being not authorized and then it crashes to desktop without message. The attached log is after the above process dcs.log

My genuine apologies for my curt inquiry if it came across as impolite! I've read the entire thread and was merely curious as to where that information originated from, as I've never read anything about it and – as you rightfully mentioned – ED could improve in terms of documentation and answering technical questions on this forum. I appreciate your efforts to step in!