All Activity

Новый блок "МУСТАНГ". Три механики с рычагами, датчики безконтактные МагРез. Три Триммера, механики имеют 2 полных оборота, датчики магнитные безконтактные. Две оси на потенциометрах. Тумблера и кнопка.

null

Вопрос разработчикам. Какая аппратура навигации будет в модуле? ЦВУ, ЦВУ-М(2204) или ЦВУ-М(2205)?

you use the same login on both dcs, it is not version dependant, just you cant run both dcs versions at the same time.

My another two cents that I learned another thread: to disable power management is to enable all devices/processes to run in the full speed. By comparing with power mgmt and without power mgmt (require watching the CPU temperature) while running DCS, it can determine the potential tunings in Windows. Of course, without power mgmt, there is no core parking for example.

Nice try. But I bet it won't be made. Since this is a certain model and not a prototype plane we got from Heatblur. Same with Eagle Dynamics Modules. A certain model at a certain point in time. No prototype. But it's ok. The B(U) will be fine I really hoped it would rather be sooner than later.

this is the solution. Thank you!

Check Github Repo here sNaticY/dcs-helicopter-assist: Helicopter assist for DCS, including auto rudder, balance assistant, hover assistant Video tutorial and show case coming soon! DCS Helicopter Assist Lightweight helicopter assist for DCS. It reads live flight telemetry from DCS via Export.lua (UDP), applies stabilization and assist logic, and writes control outputs to a vJoy virtual joystick (X/Y for cyclic, RZ for rudder). This document covers: Prerequisites Get DCS helicopter assist (GitHub Releases or run from source) vJoy setup DCS Export.lua setup How to run and use (hotkeys, modes) How to modify config (config.json) 1) Prerequisites Windows 10/11 DCS World (stable or open beta) vJoy driver installed and at least one device enabled Download: http://vjoystick.sourceforge.net/site/ If you run from source (instead of the EXE): Python 3.9+ (64-bit recommended) Python packages: numpy, pyvjoy, keyboard Install packages: py -m pip install numpy pyvjoy keyboard Note: pyvjoy may need Administrator privileges to access the vJoy driver. 2) Get DCS Helicopter Assist Option A — Download prebuilt (recommended): Go to the GitHub Releases page: https://github.com/sNaticY/dcs-helicopter-assist/releases Download the latest DCSHelicopterAssist.zip for Windows. Extract it to a folder you trust (e.g., C:\Games\DCSHelicotperAssist). Ensure config.json is in the same folder as the EXE so you can edit it. Continue to vJoy setup and DCS Export.lua setup below. Tips: First run may trigger SmartScreen; choose “More info” → “Run anyway”. If vJoy output doesn’t move, try running the EXE “As Administrator”. Option B — Run from source (Python): Clone or download this repository into a folder (e.g., C:\Games\DCSHelicotperAssist). Install Python requirements: py -m pip install numpy pyvjoy keyboard Continue to vJoy setup and DCS Export.lua setup below. Run: py helicopter_assist.py 3) vJoy setup Open “vJoyConf” (vJoy Configuration) and configure a device: Enable Device ID: choose one ID (default in config.json is 3) Axes: enable X, Y, Rx (others optional/unused) Buttons: not required POV: none required Apply/Save In DCS Controls, bind the vJoy device axes: Helicopter Pitch → vJoy Axis Y Helicopter Roll → vJoy Axis X Helicopter Rudder → vJoy Axis RX Recommendations: Unbind your physical joystick axes directly from DCS to avoid double control. The app reads your physical joystick and outputs to vJoy; DCS should only read vJoy. Optional: Bind your physical joystick axes with modifiers TOGGLE_PAUSE_HOTKEY so you can temporarily by pass the assist and control directly with physical joystick Do not invert axes in DCS. The app already writes Y as inverted when sending to vJoy. You can change the vJoy device ID in config.json (see section 7). 4) DCS Export.lua setup This project includes Export/Export.lua which sends telemetry to the app via UDP. Locate your DCS Saved Games Scripts folder: Stable: %USERPROFILE%\Saved Games\DCS\Scripts Open Beta: %USERPROFILE%\Saved Games\DCS.openbeta\Scripts Backup your existing Export.lua if present. Copy project file: From: c:\Games\HelicopterAssist\Export\Export.lua To: %SavedGames%\DCS...\Scripts\Export.lua Export.lua sends JSON lines at 50 Hz to 127.0.0.1:28777 by default. If you run the app on another machine, change the target in Export.lua and config.json, and allow UDP in the firewall. What is exported: Linear velocity (Vx,Vy,Vz) in world coordinates (m/s) Linear acceleration (Ax,Ay,Az) in world coordinates (m/s²) Pitch, Roll, Yaw (rad) PitchRate, RollRate, YawRate (rad/s) World position (PosX, PosY, PosZ) in meters (x=East, y=Up, z=North) The Python side parses these in dcs_telemetry.DcsTelemetry. 5) Running and usage Running the EXE: Double-click the HelicopterAssist.exe (place config.json next to it). Start a DCS mission; Export.lua begins sending telemetry automatically. Running from source: py helicopter_assist.py If vJoy doesn’t move: Confirm vJoy device ID matches config.json Confirm Export.lua is in Saved Games\DCS...\Scripts and a mission is running Try running as Administrator Hotkeys (defaults; configurable in config.json): Toggle Rudder Assist: F8 Toggle Cyclic Assist Mode: F9 Each press cycles: OFF → ON → HOVERING → OFF … OFF: vJoy outputs pass through your manual inputs (after smoothing/curves) ON: assist blends with your inputs; stabilization helps rate/attitude HOVERING: adds stronger hold to help steady hover Pause (hold): Left Ctrl While held, outputs are blocked On release, assist modules reset to avoid bumps Sounds: On: short high beep Hover: double mid beep Off: short low beep Manual input: Your joystick inputs are smoothed and shaped (expo) before assist and vJoy output. Enjoy flying! HelicopterAssist.zip

Hi ED, There is an issue with one of your 3rd party. As you may know, Polychop's Dev team have all quit the company leaving only the CEO. For some time now the CEO is not even answering on his discord and there is more and more unresolved bugs on the SA342 Gazelle and some on the OH58D Kiowa. The bugs vary from missing textures (on dipole antenna), wrong axis, keybindings issues, multicrew desynch and bugs, kneebord mixed up and more. Those bugs were reported from month or years, but nothing is done... For example here is some non revolved bugs : Reported on July 2 2023 : --https://forum.dcs.world/topic/329727-tm-warthog-throttle-mouse-axis-problem-on-tv/ Reported on June 8, 2023 : --https://forum.dcs.world/topic/327589-pedal-trim-not-working-propertly/ Reported on July 20, 2024 : --https://forum.dcs.world/topic/354334-multicrew-issue-pilot-and-copilot-affects-night-vision-google-employment/#comment-5672503 Reported on July 20, 2024 :--https://forum.dcs.world/topic/354333-multicrew-issue-with-nadir-even-when-copilot-leaving-the-gazelle-and-rejoin-entering-and-editing-waypoints-not-working/ Reported on september 14, 2024 : --https://forum.dcs.world/topic/357716-the-windscreen-wipers-do-not-wipe-when-you-press-the-pilot-wiper-button-on-the-stick/ Reported on september 14, 2024 : --https://forum.dcs.world/topic/357715-floating-metal-clip/ Reported on april 2, 2025 : --https://forum.dcs.world/topic/371479-i-love-the-gazelle-but-continuing-to-be-patient-for-a-joystick-slew-fix-for-the-minigun-variant-unable-to-point-minigun-to-the-front-of-aircraft-also-unable-to-point-fully-up-and-down/#comment-5654828Reported on June 27, 2025 : --https://forum.dcs.world/topic/375569-pilot-position-windshield-wiper-clickable-cockpit-switch-issue-as-of-291711733/ Reported on August 5, 2025 : --https://forum.dcs.world/topic/377214-multi-player-seat-switch-issue/ Of course there is more bugs than those mentionned here, it's just to show that some bugs are here since years ago. Now, what can ED do ? Well 3rd party have to maintain their products (which is not the case for Polychop Simulation). I expect mesures to be taken by ED toward Polychop to remedy this bad situation If this is not enough, maybe the Gazelle IP could end up in someone else hands, someone who will actually take care about this module, either ED or an other 3rd party. Thank you, Peet

Sure, we can create a thread for the Jester's callout wishlist collection

BIOS, Nividia drivers and Windows all up to date. Ran a test this morning before updating the Nvidia drivers. Prior to Nvidia update and HT support OFF - Desktop to main menu > 42 seconds Exit to Desktop > 5 seconds After Nvidia update and HT support ON - Desktop to main menu > 70 seconds Exit to Desktop > 40 seconds I don't claim to know what the problem is but there does seem to be a link between Multi/Hyper threading and DCS load times.

A little earlier in this thread, the developer (Rudel) acknowledged a problem and said it’s on their bug list. That’s an interesting observation that the problems between the modules seem similar. Earlier in this thread, Rudel mentioned that DCS models tailwheels, not as a rolling wheel, but as a stick touching the ground. In that case, it should have a fairly limited amount of variables that could be tweaked. That made me think the problem could be as simple as an incorrect “friction” value applied to the point of the stick that touches the ground. I would imagine there aren’t many more variables if the tailwheel is modeled as a stick. Maybe the angle of incidence of the stick, based on its length and where it attaches to the fuselage. Who knows though, I’m just taking guesses on limited understanding of coding. In any case, this makes me think the problem is simple, and that resolving it could be as simple as making the tail-stick contact point more “slippery” . When a castering tailwheel is unlocked, the friction forces that resist the tail from freely swinging all the way aroundis minimal. In the sim, the friction imparted by the stick’s contact point should be consistent with the rolling resistance of a small tail-wheel rolling on the ground.

I would think that a partnership with beyond atc or SayIntentionsAi is probably the optimum ED could do. Implement an API that opens this aspect up to third party devs. Their solutions are 90% there already with absolutely stunning results! In 2026 this really is a must have or this whole project feels like Windows NT in 2020.

Yes. I had everything with Buk-M3 in name spawned :). May I ask you to send me a mission with properly working BUK site?

Or appreciate the options to make it easier for all to access at a level that is comfortable to them.

...are using Metric but Mig29G is using Imperial... Only thing I must do now is to change the module to be avail on 'Combined Joint Task Forces' and I'll have Imp's on my hud P.S. The rest of you with useless opinions...don't waste my time any more, would you?!

Hi all I have used these twice since buying them so in mint condition Please join the Specter Studio Discord and ping me if interested https://discord.gg/uxGCqZx8 £120 o.n.o

They originally used a synthesized voice I believe, before some squadron got a radio personality to re record the lines Points are just like a pre set. Once you make a point, you can use it for aerodrome, waypoint, or beacon. It’s just a convenience thing so you have a pool of points to assign to whatever without needing to make new ones for each tab.

Соглашусь. Так, мне стали важнее органы управления, чем VR. После проф деформации яркие визуальные спец эффекты уходят на второй план. Наверное.

There is alcohol to cool the radar…..

А металл покрашеный серой матовой краской выглядит по другому? Вам никто не мешает открыть фотошоп и перерисовать свои текстуры. НЕ понял причем тут вообще пластмассовая кабина и радиообмен?) А я знаю релаьных действующих лётчиков которые приходят в ДКС, при этом и летают по инструкциям (ИПП, РЛЭ и тд) и радиообмен ведут в SRS со всеми спецэфектами и правильной фразеологией.

Thanks again for the clarification — that really helps to put things into perspective. Makes sense that it depends so much on the bogey’s altitude and the terrain background. The example with a target at angels 25 vs. angels 10 with mountains really illustrates the difference well. Good to know that Jester already scans ±10,000 ft by default (Zabuzard) , so I don’t need to micromanage him there. That simplifies things a lot. I’ll definitely keep boresight mode in mind for closer visual-range situations. Appreciate you taking the time to explain this

This is still planned to be done, sorry I dont have a timeline right now.

I just tried this mission,and looks like their is a small fleet in that area(In my run I saw at least 4 ships in the area,and ships in that fleet are in loose formation,every ships are like few km away),with fog in that mission it's easy to miss the right ship........I almost missed it,when the "we got visual of u" message from frigate was triggered,I was flying passing a missile boat......but after circling around a bit more I eventually found the correct frigate with helipad... are u sure u didn't miss the right ship in the bad weather?

Except weather changes - on some days drastically, as the day progresses. This is not reflected by ED's weather as of yet.