andyn

Being able to disable pedal trim is a standard feature in DCS helicopters. Why not in the Chinook?

@BIGNEWY @NineLine Any update on this? The fix is quite straightforward. Asking only because a patch has been planned for tomorrow.

When a player joins a server using an IP address, for example 87.94.161.165, they are taken to the coalition and slot selection screen normally. When a player joins a server using a DNS name, which for the aforementioned server is k01.dcsfinland.fi, they are thrown into spectator view. If the player presses escape and chooses "select role", they are thrown into the map with the top left corner showing a placeholder name and the Angolan flag. The main log file will show the following error: 2024-11-23 21:12:49.492 ERROR LuaGUI (Main): [string "./Scripts/UI/MultiplayerSelectRoleMap/MultiplayerSelectRole.lua"]:247: bad argument #1 to 'match' (string expected, got nil) The root cause is in the isWhiteIp function that expects to get a valid IP address but raises an error when given a DNS name. In addition to fixing the server address parsing issue I'd probably do away with the IP address range check inside the UI scripts and move it to the builtin GeoIP database instead, but hey, I'm not your software architect . I'm pretty sure no trackfile will be required for this bug report.

Onretech folks, it's way too early to ragedelete all the content you worked on just because Ugra was there first. ED's new terrain engine that lets us stitch multiple maps together is still years away.

Load CBU-99s with the FMU-140 fuze with default settings. Drop them in VT mode (MFUZ VT1) and they will not spawn any submunitions. Time delay fuze (MFUZ VT2) works as expected and the dispenser opens after 1.2 seconds. Mk 20 Rockeyes with the Mk 339 time delay fuze do work in both MFUZ PRI (1.2 s) and OPT (4.0 s) modes. I tested this by modifying both the Nevada and Caucasus bombing range quickstart missions. VT fuze behavior is the same both at sea level and at altitude, so it's not a radalt vs baro issue.

Crashed when arming LTD/R on a centerline LITENING pod in a multiplayer mission with FLIR format up on the right DDI. LTD/R ARM is bound to the first physical trigger detent (yes, I'm that lazy) and had been toggled god knows how many times already before the crash as I had to fight my way into the target area. dcs.log-20240720-214635.zip

It sure looks like ED's escrow safeguards were not sufficient. I propose that third party agreements are modified so that ED builds EFM .dlls themselves from the source code from now on.

When I bought Strike Eagle on day one I had a few assumptions. I assumed it was being developed by a long-term third party who had stable income from a good lineup of popular aircraft modules. I assumed Eagle Dynamics had put proper safeguards in place as they promised after the VEAO fiasco. Both of those assumptions turned up to be based on lies. After Ron went public, it has become apparent that the current situation has been developing at least since last summer, while ED has knowingly been milking their customers dry despite knowing that Razbam's capability to continue development is degraded. Both parties have confirmed there is an ongoing IPR dispute. For settling those we have market courts and arbitration clauses. One-sided setoffs are not a thing. My passion has dried up and I can no longer afford to support a company whose main business has been selling empty promises to its customers.

Had this issue yesterday in multicrew multiplayer. The compass card stabilized as soon as we started taxiing.

Update: as of today, using the backup radio head disables the selected radio altogether. The displayed guard frequency is still 121.0. Additionally, the backup radio selector switch seems to select the wrong radio.

Out of interest, what is the disruptive use case here?

One of the most common use cases for function keys is to go to the F10 map, select a unit or weapon and press another function key to go to view that selected unit in external view. This requires you to: - Know the type of the unit you just clicked - Know the function key for the external view of said unit type - Be able to press that function key or key combination in, say, VR. My suggestion is to change the default behavior of the F2 key as follows: - If the F1 view of a player aircraft or a combined arms unit is currently selected, view the player unit in external view. - If the F10 map is open and no unit has been hooked, view the player unit in external view. - If the F10 map is open and a unit has been hooked, view that unit in external view. - If an external view is open, cycle between external views of units of that type. This will follow the principle of least surprise, which should be one of the primary UX design guidelines.

Topic. Most easily verified by having the Simpleradio overlay open, as it directly reads the in-game radio frequencies.

For some reason the forum software only uploaded the pictures I attached and never sent the text I wrote. See the two screenshots. The radar dish can be seen at one third from the left front end of the nose cone. The radar transmitter body can be seen taking up the right rear third of the nose cone - it has been pulled out onto its service rails! The nose cone could never be closed with the body in that out position. The radar antenna 3D model also has been scaled down if it is to fit inside that nose cone. See the two real-life photos for reference. Such a visual discrepancy has little effect in game since you're unlikely to see it. However, I seriously hope the radar simulation code does not use antenna aperture measurements taken from the 3D model. I'm also curious as to how such a miscommunication happened in the first place In the first screenshot you can also see the bort number bug.