Jump to content

Cannot look down sights in MI-24 CPG (SP/MP)


Go to solution Solved by Flappie,

Recommended Posts

Posted

@Flappie
I submitted a support ticket, no reply to it yet.

I know of at least 2 people who have the same issue as me.

For unrelated reasons two days ago I completely wiped my PC and set it up again from scratch (I mean re-installed windows, updated all drivers, bios, and of course redownloaded DCS entirely from scratch save for my backed up missions, my custom payloads and the Syria map and the F-16 which I had backed up on an external drive.)

As such my keybinds and the MI-24 were also redownloaded from scratch.

I still can't look down the sight.

"Got a source for that claim?"

Too busy learning the F-16 to fly it, Too busy making missions to play them

Callsign: "NoGo" "Because he's always working in the editor/coding something and he never actually flies" - frustrated buddy

Main PC: Ryzen 5 5600X, Radeon 6900XT, 32GB DDR4-3000, All the SSDs. Server PC: Dell Optiplex 5070, I7 9700T 3.5GHz, 32GB DDR4-2133. Oculus Quest 3.

Posted
5 minutes ago, ACS_Dev said:

@Flappie
I submitted a support ticket, no reply to it yet.

I know of at least 2 people who have the same issue as me.

For unrelated reasons two days ago I completely wiped my PC and set it up again from scratch (I mean re-installed windows, updated all drivers, bios, and of course redownloaded DCS entirely from scratch save for my backed up missions, my custom payloads and the Syria map and the F-16 which I had backed up on an external drive.)

As such my keybinds and the MI-24 were also redownloaded from scratch.

I still can't look down the sight.

One last thing you could also try: disconnect all your devices, but keyboard and mouse and try to get on sight

Posted

I will do that tonight, thanks for the suggestion.

"Got a source for that claim?"

Too busy learning the F-16 to fly it, Too busy making missions to play them

Callsign: "NoGo" "Because he's always working in the editor/coding something and he never actually flies" - frustrated buddy

Main PC: Ryzen 5 5600X, Radeon 6900XT, 32GB DDR4-3000, All the SSDs. Server PC: Dell Optiplex 5070, I7 9700T 3.5GHz, 32GB DDR4-2133. Oculus Quest 3.

Posted (edited)

@Flappie@admiki

I disconnected my joystick and throttle, restarted my PC and launched the mission again. I confirmed no other controllers were present via the adjust controls menu.

It still doesn't work.

At this point I will reiterate for what feels like the umpteenth time that this was absolutely not a problem a couple of updates ago, it persists not only after a slow repair, a game install and a COMPLETE PC WIPE, is occurring with multiple users, happens regardless of whether I bind it to a joystick, keyboard or throttle, whether I have either of the above extra peripherals plugged in and WORKS FINE IN TRUE MULTIPLAYER.

As a tech support guy myself I know how frustrating this is given that you yourselves cannot reproduce it, thanks for the effort so far.

Edited by ACS_Dev
  • Like 1

"Got a source for that claim?"

Too busy learning the F-16 to fly it, Too busy making missions to play them

Callsign: "NoGo" "Because he's always working in the editor/coding something and he never actually flies" - frustrated buddy

Main PC: Ryzen 5 5600X, Radeon 6900XT, 32GB DDR4-3000, All the SSDs. Server PC: Dell Optiplex 5070, I7 9700T 3.5GHz, 32GB DDR4-2133. Oculus Quest 3.

Posted
On 11/30/2023 at 11:49 AM, ACS_Dev said:

I know of at least 2 people who have the same issue as me.

Can you have them try running my track? See if they have the same problem viewing  it?

Posted

@randomTOTEN@Flappie@admiki

I just figured this out finally, it was (surprise!) never a bug.

In order to use the sight I must first press the 'request aircraft control' to cede control of the aircraft to the AI, after which I can access the sight.

  • Thanks 2

"Got a source for that claim?"

Too busy learning the F-16 to fly it, Too busy making missions to play them

Callsign: "NoGo" "Because he's always working in the editor/coding something and he never actually flies" - frustrated buddy

Main PC: Ryzen 5 5600X, Radeon 6900XT, 32GB DDR4-3000, All the SSDs. Server PC: Dell Optiplex 5070, I7 9700T 3.5GHz, 32GB DDR4-2133. Oculus Quest 3.

Posted

Ah, OK! Thanks for your feedback. 😀

If you want to avoid pressing "C" to request controls, tick this box in the Mi-24 special options:

image.png

I believe it is ticked by default, which is probably why nobody here could find the solution for you.

  • Like 2

---

Posted
1 hour ago, BMO said:

i ran into the same problem when learning the mi24, it´s actually all in the chucks guide:

image.png

True, but you could control helicopter and aim at the same time before 2.9 came along.

  • 3 months later...
Posted

Just as an FYI to anyone (like me) coming upon this topic at a later date - I was struggling with the same problem, but it wasn't the "auto handover" setting that was causing the issue; I was using the Instant Action "Runway Start" mission as a place to get my keybinds in order; that has "simplified AI" set in the mission parameters, and that also seems to prevent use of the CPG sight.

 

  • Thanks 1
  • 1 month later...
Posted (edited)
On 12/4/2023 at 3:07 AM, admiki said:

True, but you could control helicopter and aim at the same time before 2.9 came along.

I remember this and much preferred the feature. It allowed me to play with the sight while maintaining a specified course vector instead of losing control and crashing, hitting vrs, or just performing a wildly chaotic maneuver.

I've been having a real hard time getting Petrovich to see targets I can clearly and easily see from the pilot seat. I was hoping I could just do both tasks simultaneously like with the Apache to work around that bug, but that doesn't seem to be the case anymore. Now, I have to deal with him not only failing to find targets, but failing to properly fly the helicopter as well.

I understand it's not realistic to perform two different roles at once, but Petro's AI is sometimes not usable and it was valuable to have a workaround to it, especially when he decides to stop performing alignments properly. There still seems to be a lot of bugs with his AI in general still.

On 4/3/2024 at 2:23 AM, Loophole said:

Just as an FYI to anyone (like me) coming upon this topic at a later date - I was struggling with the same problem, but it wasn't the "auto handover" setting that was causing the issue; I was using the Instant Action "Runway Start" mission as a place to get my keybinds in order; that has "simplified AI" set in the mission parameters, and that also seems to prevent use of the CPG sight.

 

I tried playing with that setting but it doesn't appear to matter whether its on or off. It requires handoff either way.

Edited by FusRoPotato
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...