LordMustang

Same for me. Seems to be multiple threads on this: @BIGNEWY Any chance you could get this checked again? Weirdly enough it only happens at dusk/dawn/night.

Можно ли сделать данный подраздел форума доступным только для чтения? Здесь было много информации, которая теперь недоступна.

Эти скобки могут указывать на ручной режим, но я не уверен. Я извиняюсь.

@Chizh Похоже, что символы ИЛС для системы Игла взяты из Ка-52. Знаете ли вы, если скобки отсутствуют на границах ГСН?

AFAIK, that's because very little is known about how the MWS was really integrated. Chizh (and others) have posted some pictures of what is presumed to be the indicator, mounted to the left side of the ILS-31. I guess that boils down to what Chizh denoted earlier: since many of the Ka-50s were used as testbeds for future technologies, ED took some liberties to be more experimental with it.

Version: 2.7.18.30765 openbeta Steam In the control inputs for the Copilot-Gunner there aren't any button binds for the rudder. This makes it impossible to control the rudder from the front seat without a rudder axis. These binds are of course present in the pilot control settings. I solved the issue partially for myself locally by changing the following: Input\Mi_24P_op\joystick\default.lua ... -- General {down = iCommandScoresWindowToggle, name = _('Score window'), category = _('General')}, {down = iCommandFriendlyChat, name = _('Multiplayer chat - mode Allies'), category = _('General')}, {down = iCommandInfoOnOff, name = _('Info bar toggle'), category = _('General')}, {down = iCommandRecoverHuman, name = _('Get New Plane - respawn'), category = _('General')}, {down = iCommandCockpitClickModeOnOff, name = _('Clickable mouse cockpit mode On/Off'), category = _('General')}, {down = iCommandScreenShot, name = _('Screenshot'), category = _('General')}, {down = iCommandViewCoordinatesInLinearUnits, name = _('Info bar coordinate units toggle'), category = _('General')}, {down = iCommandCockpitShowPilotOnOff, name = _('Show Pilot Body'), category = _('General')}, {down = iCommandPlane_ShowControls, name = _('Show controls indicator') , category = _('General')}, -- Add {down = iCommandPlaneLeftRudderStart, up = iCommandPlaneLeftRudderStop, name = _('Rudder Left'), category = {_('Ins Rudder'), _('Flight Control')}}, {down = iCommandPlaneRightRudderStart, up = iCommandPlaneRightRudderStop, name = _('Rudder Right'), category = {_('Ins Rudder'), _('Flight Control')}}, -- End add ... Input\Mi_24P_op\keyboard\default.lua ... {down = iCommandPlaneWheelBrakeOn, up = iCommandPlaneWheelBrakeOff, name = _('Wheel Brake'), category = {_('Ins Cyclic Stick')}}, {down = iCommandPlaneWheelParkingBrake, name = _('Wheel Parking Brake'), category = {_('Ins Cyclic Stick')}}, {down = cockpit_mechanics_commands.Command_CPT_MECH_ParkingBrake_EXT, cockpit_device_id = devices.CPT_MECH, value_down = 0.0, name = _('Wheel Parking Brake - OFF'), category = {_('Ins Cyclic Stick')}}, {down = cockpit_mechanics_commands.Command_CPT_MECH_ParkingBrake_EXT, cockpit_device_id = devices.CPT_MECH, value_down = 1.0, name = _('Wheel Parking Brake - ON'), category = {_('Ins Cyclic Stick')}}, -- Add {down = iCommandPlaneLeftRudderStart, up = iCommandPlaneLeftRudderStop, name = _('Rudder Left'), category = {_('Ins Rudder'), _('Flight Control')}}, {down = iCommandPlaneRightRudderStart, up = iCommandPlaneRightRudderStop, name = _('Rudder Right'), category = {_('Ins Rudder'), _('Flight Control')}}, -- End add -- Cheat --------------------------------------- ... However, introducing the bind like this causes a bug in the autopilot yaw channel, where it seems both the autopilot and CPG will have the AP trying to correct at the same time, resulting in the AP always applying max yaw to whichever side it was correcting. null Please add these binds into the module.

Yes. Like I said, the likely reason why IC fails is because the texture can't be loaded due to insufficient memory. The order of errors is as follows: Out of memory -> Texture can't be decompressed -> IC fails because hash of not-decompressed texture likely doesn't match -> CTD Basically, any time the game runs out of memory the last texture won't decompress and load because there's no memory available to allocate the uncompressed texture to. The fact that this texture cannot be loaded causes an IC error. However, the IC error does not cause the CTD, because it needs to be a proper exception for the game's core to crash. IC fails just kick you out of the server.

Seems there was some sort of error between Helios and TheWay. I removed TheWay from exports.lua and these errors stopped. I didn't have any mods installed for the AH-64D. I have uninstalled and reinstalled it to be sure. However, this made me discover that any IC check on textures that fail to load into memory fails. It just so happened to be that I was spawning the AH-64 when it crashed. However, even without any Lua conflicts the same crash occurs. I set my pagefile to a fixed size of 16384 MB and the game ran out of memory in approximately 2 minutes of session time. The crash reporter didn't catch it this time, so I only have the log. As you can see, this time IC failed on some Gazelle textures right before the game crashed. There was probably another player spawning in it at the time, since I don't own the Gazelle.

Whilst playing on Hoggit Training (~15-20 people online) on Caucasus, the game crashes for me after a while. It will allocate memory until all memory is used. After this, it will start using the pagefile until it increases its maximum size. I've tested it with pagefiles capped at 16 GB, 32 GB and system managed, in which it sometimes increased past 40 GB. After a while, the game will crash. Sometimes the crash reporter catches the crash, sometimes it doesn't. The fact that 32GB 3200mHz memory and 32GB of pagefile isn't enough for a Caucasus MP session with 10 to 20 people sounds absurd. Is anybody experiencing the same? dcs.log dcs.20221001-013746.crash dcs.20221001-013746.dmp options.lua

Yes please. Could there be a "Camera shake" slider similar to the AH-64 and Mi-24? I thought my rotors were broken. It also makes the ABRIS difficult to read when zoomed out.

The Rudder left and Rudder right keybinds do not work as expected compared to other helicopter modules. I checked the functionalities of these binds on the Ka-50 and Mi-24. While they are not fully the same, their functionality roughly corresponds. The speed is very slow. It takes ~7 seconds to fully depress a pedal from center position On the Ka-50, it takes ~0.4 seconds On the Mi-24, it takes ~2 seconds The rudder does not recenter after releasing a button On the Ka-50, the rudder pedals fully recenter On the Mi-24, the rudder pedals partially recenter Steps to reproduce: Start a free flight in the AH-64D Depress "Z" or "X" Notice the speed at which the pedals move/rudder axis in control overlay. Release the button Notice that the pedals do not recenter Start a free flight in the Ka-50 Depress "Z" or "X" Notice the speed at which the pedals move/rudder axis in control overlay. Release the button Notice that the pedals do recenter

I know it would most likely enter into the PVI, but I checked all the slots for WPT, TGT and airfield points but couldn't find them. It was also unclear whether I need to enable editing mode before transferring points.

@Comrade DogeDoes the Ka-50 work for you? The F-16 works fine for me, but the Ka-50 doesn't receive any inputs.

@Chizh Можно ли будет нести Иглы на пилонах Вихря? (пилоны 1 и 4 для обычного крыла)?

It appears the "Camera transpose mode (press and hold)" bind is missing. On the other modules this bind is either present, or it takes the value from "General" controls category.