Jump to content

20k

Members
  • Posts

    4
  • Joined

  • Last visited

Everything posted by 20k

  1. A number of people I know have been able to reproduce this bug as well. Apparently using a custom cockpit may work around this, so it might be a broken texture?
  2. Hi there! SPRD's have been broken for a while and are non functional. I've tracked down the issue to the 11th july 2024 update, when "JATOConts.lua" was added to the game When DCS is loaded, you can find the following error message in dcs.log: "2024-12-07 19:20:50.845 ERROR Scripting (Main): declare loadout fail, duplicate not allowed: "{SPRD}" from "./CoreMods/aircraft/MiG-21bis/Entry/Aw", original located here "./CoreMods/aircraft/AircraftWeaponPack/JATOConts.lua"" When playing any mission, flicking the two jato switches up, and launching on full afterburner, they fail to engage automatically as expected Renaming JATOConts.lua to any other name causes that file to fail to load^[1] - and the loadout error disappears. This results in SPRDs working correctly again for the mig21. So hopefully it should be straightforward to fix by fixing the loadout naming conflict here. This may or may not be exclusive to the old slot/spawn/loadout system as that was introduced in that update, but I haven't tested this. Please let me know if you need any more information! [1]: The error message isn't really relevant, but its "2024-12-07 19:34:24.820 ALERT Scripting (Main): loadfile: no file './CoreMods/aircraft/AircraftWeaponPack/JATOConts.lua'"
  3. The main issue is that the SU-25 and the SU-25T have the same bug in reverse for their respective controls, which makes them difficult to use consistently as you have to very heavily special case your controller bindings currently. Its common to bind the right stick on a gamepad joystick to the mouse, so it'd be unfortunate if it were removed because it means creating more special casing for the controls Ideally they'd work the same whichever direction that the devs take with respect to realism, but simply removing either joystick or mouse controls for TDC slew on these aircraft would leave the two aircraft's ground stabilised slewing in inconsistent states with each other and further complicate control setups, so it might be worth double checking the intent with whether the SU-25T should work the same as the SU-25 or not in this area
  4. I've been tracking this one down for a while, because its pretty annoying! On the su-25, if you are using a joystick input for TDC slew, when the laser designator is ground stabilised it adds your planes motion the cursor when you attempt to move it. This does not happen when using mouse input, and it correctly translates without adding plane motion to the cursor On the su-25T, the exact opposite is true - when using joystick input for TDC slew it works great, but when using mouse input for TDC slew it inherits your planes velocity and adds it to the motion of the camera Both of these things occur when in ground stabilised mode only when input is entered, and aren't related to any features of the aircraft in any way, its a simple bug depending on what kind of input system you use, mouse vs joystick, and its the exact opposite between the two aircraft https://www.youtube.com/watch?v=DyjiGAifo7I is a video of the repro
×
×
  • Create New...