All Activity

I have done some cold spawns on Caucus and Syria. With Switch in WYPT (I align on Ramp coordinates in WYPT 1) and Nav/RSBN channel preset to a specific freq. Cold start and I taxy no stutter and both AD/WYPT switch remains in WYPT and manual Nav/RSBN channel remains as preselected.

После 90 секунд тоже можно. Но в РЛЭ написано "Включение после 90 секунд и не раньше 5 минут не желательно, так как точность выставки ухудшается". Но по мнению эксплуатантов там итак погрешности больше чем "В книжке написано". И полная навигация от ускоренной в этом случае не сильно отличается, по этому нет смысла тратить ещё 7-8 минут)

Good to know, I will check the it, thx! Btw. Are you talking about the frequency programmed under the Beacon buttons or in the ARK receiver and channel 1, for example?

Update: Decided to double back and make some "eyeball" location comparisons, starting with the 'OEM x_trans = 0.120000'. And it was still slightly small, but only slightly, like your head is against the headrest, and fine generally if preferred. What surprised me was that moving forward a measly '0.005', to 'x_trans = 0.125000', made a big difference, without making the gunsight glass and windscreen overly large, like the previous setting. The gauges "pop", as does the canopy bow, so it feels like being inside. And the MIL Ring size is not affected by "eyeball" position, only zoom(FOV), so the further away, the bigger it is relative to the reduced reflector glass, which is affected. Went back-n-forth between the two, alternating a quickstart 6 v. 6 mission, including combat landing afterward. Both work very well, but the 'x_trans = 0.125000' just feels better. SnapViews["P-51D"] = { [1] = {-- player slot 1 [1] = {--LWin + Num0 : Snap View 0 viewAngle = 54.750000,--FOV Cockpit Zoom 54.750000, OEM 80.000000 "P-51D" viewAngleVertical= 0.000000,--VFOV hAngle = 0.000000,-- (Snap View)/(Cockpit panel view in)(-30°) vAngle = -30.00000,-- Cockpit View Angle -30.00000, OEM -9.500000 x_trans = 0.125000,-- Cockpit View In_Trans 0.125000, OEM 0.120000 y_trans = 0.060000,-- Cockpit View Up_Trans 0.060000, OEM 0.059000 z_trans = 0.000000,-- Cockpit View Rt_Trans 0.000000, OEM 0.000000 rollAngle = 0.000000, cockpit_version = 0, [13] = {--default view viewAngle = 40.000000,--FOV Cockpit Zoom 40.000000, OEM 80.000000 "P-51D" viewAngleVertical= 0.000000,--VFOV hAngle = 0.000000,-- (View Center)/(Cam View Dn-Slow)(-30°) vAngle = 0.000000,-- Cockpit View Angle 0.00000, OEM -9.500000 x_trans = 0.125000,-- Cockpit View In_Trans 0.125000, OEM 0.120000 y_trans = 0.060000,-- Cockpit View Up_Trans 0.060000, OEM 0.059000 z_trans = 0.000000,-- Cockpit View Rt_Trans 0.000000, OEM 0.000000 rollAngle = 0.000000, cockpit_version = 0, Enjoy. Bowie

Sorry to keep bugging you guys, but now I have a weather issue. I'm only getting completely clear skies or rain it seems. For instance, the METAR says: METAR Mozdok 050630 33003MPS NSW BKN076 BKN216 FEW336 08/M11 510002 QNH749 BLU= But it's clear skies...and if you look at the MIZ in the editor, there's no weather preset loaded. Did I break something again? I'm creating a custom Campaign using the new MiG-29 (I added all the necessary stuff, so that part works fine). I've set the Weather to have more of a chance for a low pressure system. So I get either Rain...or completely clear skies.

Even more so, they have already done some work, for example for the Su-25 FF ;). However, the navigation system also had another purpose - not to give the pilot much freedom in this respect, it could always be an obstacle, for example in the case of a desire to escape .

Hi. No, Im sure, it exists all the time, 100% from cold and dark and on every map. I only take off from the ground and from C&D and I get this every time, I can even hear the buttons clicking in the cockpit. Maybe you didnt notice it but its not random case for me. I pay special attention to this, the rest of this momentary freeze is also noticeable, VR is more sensitive to any FPS drop, so it is very visible.

I'd like to see the NASA livery. Apparently, some kind of special radar is installed on such an aircraft.

Started flying the Apache again In VR, the George menu, when activated, is slaved to my headset. It moves when my head moves. I seem to recall in the past, the menu would be locked on the bottom right of my display. Is there any way to adjust this in VR?? Thanks in advance. HP Reverb G2/Windows 10 -Wraith

Bei der standalone muss man sich ja zwingend bei ED anmelden, wenn man über den Shop Module kaufen will. Bei Steam braucht man das ja nicht, deswegen hab ichs nie gemacht.

Interesting this does not always happen. I have seen it a number of times but its random imo.

I'm not seeing any accuracy problems - I just ran a quick test against a Mig-23 as a formal experiment and the only inaccuracy was from me. Pretty much ALL my seat time in the Mig has been 1v1 gunzo fights and I haven't noticed anything amiss. However .TRKs are broken. Here's Kuky's track... Makes no sense at all - after the merge he's shooting at thin air. So I recorded my own track from the Mig-23 test and had exactly the same issue; about halfway through the weirdness starts. Conclusion 1) Gun accuracy (for me) is fine. 2) TRKs are broken. busted.trk

Искал как увеличить яркость MFD WinWing и нашел ролик. В ролике рассказывают как решить вопрос с помощью ReShade. Скачал с официального сайта файл ReShade_Setup_6.6.0_Addon, положил его в папку ...DCS World\bin-mt, запустил его указал дайрект 10,11,12 после чего закрыл. Сделал как указано в видео файл сделал файл UIMask и поместил в папку ...DCS World\bin-mt\reshade-shaders\Textures. После чего запустил DCS. ReShade запустился и пошли вопросы: 1. В меню программы очень крупный шрифт и отсутствует бегунок прокрутки плагинов. Поэтому, кто знает, подскажите пожалуйста как включить "бегунок" как в виндовс. 2. Включил плагины, которые указаны на видео, посредством ввода названий этих плагинов в строке поиска. На видео видны бегунки, посредством которых можно менять яркость и т. д., однако у меня меню с этими бегунками не появляется. Подскажите пожалуйста, как эти бегунки включить. 3. После запуска DCS с ReShade он стал блеклым, хотя у автора видео ничего такого не происходит. Подскажите пожалуйста как следать так, чтобы цветовая палитра DCS не менялась. 4. На видео автор перетаскивает плагины вверх/вниз качество картинки меняется, потом он их ставит обратно. Не могу понять для чего он это делает, возможно для того, чтобы показать где именно среди плагинов должны находиться те, которые нужны, если кто-нибудь знает подскажите пожалуйста цель его действий и на самом деле так важен порядок расположения плагинов? 5.Выход из DCS при включенном reshade происходит с ошибкой. "лог" прилагаю.dcs.log-20251004-031753.zip

Thank you for this clarification. Well done for your work, it keeps the passion alive.

Bumping this back up since it got no response. Rode in the Huey many times at night back in the '70's and the landing light was always pointed down so the crew could clear the landing area to the pilot. Here's a copy from Fig. 2-1 of the TM. Item #34 is the landing light and #37 is the search light.

Hi! Unfortunately it’s not something I can fix from the mission editor. Some people have this, some never (me included). Remove all unofficial mods and run a slow repair. if it persists, please contact ED and send them your dcs.log @[ED]Ben FYI

You should make official bug report

any plan for pre-1968 MiG-21 variant like the PF? I kinda want to recreate an authentic Operation Rolling Thunder

The centerline tank is a great design. It is essentially conformal, to the point that below Mach 0.6 it actually reduces drag. Either they didn’t test it supersonic or it has negligible drag at supersonic speed also. Pretty cool

No worries All good now? Shouldn't be a lot. Some mods can cause issues though so a good troubleshooting start is to always remove them and run a repair just in case. Yeah this cleans up the shader caches. These can grow over time, and end up containing a bunch of redundant stuff which can still all be loaded. You should always delete them after any DCS upgrades as well to make sure all the cruft is removed and they're nice and clean. There's a handy screen for it in the DCS launcher as well under Files > Cleanup > Shader caches.

Works in the ME on my end:

silverdevil's change would have disabled the launcher completely, you can turn it back on again in the game settings, might be under the Misc. tab. My solution was to delete the broken file causing this, if you turn the launcher back on again it should work as expected now.

No worries. Yeah dcs.log file in there is good enough to attach here after a crash.

I think the Normandy map is most certainly worth getting just to fly around in. It really is wonderful for every type of flying. It doesn't matter what you fly around in it with, whether that be an Mi-24, a Focke-Wulf or a JF-17, its still a map worth having, imo. If you want to fly WWII airplanes against appropriate air defenses, or otherwise just see what a F-4E can do to a WWII Panzergrenadier company on land, or an E-boat at sea, then you should buy the Asset pack as well. Those new units can be plugged into any map. They say it's a Sandbox, and so it is. Have you tried the free TF-51 and decided what you think of it?

Heya Kinkku (was surprised to hear you weren't speaking rally English when I heard you in an interview...), just thought I'd ask about a thing mentioned in the UH-60L manual. In the manual it is said "This aircraft was fitted with FLIR and terrain radar which are not possible to implement in a DCS mod." This got me curious, because at one point the guy making the A-29 Super Tucano mod did manage to finagle a working FLIR into a DCS community mod. Has the way this was achieved been patched out since then?