Jump to content

Recommended Posts

Posted

Hi ppl,

 

On long missions I use the autopilot to cover long distances, after taking manual control by disabling the autopilot, I more often than not crash after doing some hard maneuvers - not because I was hit by the enemy, but because of weird errors like - HYDRO according to the post mission logs...:cry:

 

Am I missing something or doing something wrong? Do I have to reset the trim by hitting Ctrl-T or something after disengaging autopilot?

|| नभ स्पर्शं दीप्तम् || - Touch the sky with glory

Posted

Seems to me that you are pulling very high G maneuvers and breaking a wing but i could be wrong, maybe you could post the trk file?

Posted

Ok now confirmed that there's a bug. Flew the same mission w/o using ACS and no HYDRO or any other such system failures and completed it successfully...I hope this reaches the devs!

|| नभ स्पर्शं दीप्तम् || - Touch the sky with glory

Posted
Serious?!? Wings break off like that?!? Wasn't maneuvering that hard...:(

 

You'd know if you broke a wing - control is usually very badly degraded even if you're lucky and only snap off the outer portion of one wing. Snapping off both wings is deadly - if you're lucky you'll be able to eject. If not you might instantly black out from -G at which point it's game over.

 

This table shows the maximum permitted G values:

 

Su-27%20Max%20Gs_zpsh87pukdn.jpg

 

 

Shown differently, this is the maximum allowed G versus mach number. Notice the dip in the transonic region:

 

Su-27%20Maximum%20Allowed%20G_zpsqicb7fn8.jpg

 

 

Note that the table and the above graph both come from the actual Su-27S manual as produced by Sukhoi.

 

Tests that Ironhand carried out have proved that the airframe will fail at somewhere between 1.3x and 1.5x the maximum allowed G value. It's also true that repeated over-G conditions will weaken the airframe and will lower the G value at which subsequent failure occurs.

 

In relation to your original question: when you experience problems with control, is there a red warning light illuminated somewhere under the HUD? Try resetting the flight control system with left-alt-9.

System Spec: Cooler Master Cosmos C700P Black Edition case. | AMD 5950X CPU | MSI RTX-3090 GPU | 32GB HyperX Predator PC4000 RAM | | TM Warthog stick & throttle | TrackIR 5 | Samsung 980 Pro NVMe 4 SSD 1TB (boot) | Samsung 870 QVO SSD 4TB (games) | Windows 10 Pro 64-bit.

 

Personal wish list: DCS: Su-27SM & DCS: Avro Vulcan.

Posted

Thanks DarkFire. But like I said, i didn't experience the failure not having used the ACS subsequently...it's only when I use the autopilot and come off it to fight, this happens...

|| नभ स्पर्शं दीप्तम् || - Touch the sky with glory

Posted

Do you use trackir? Are you really sure your not pulling so hard that you might break the airframe? The trk file would really help us to figure out the issue

Posted
Thanks DarkFire. But like I said, i didn't experience the failure not having used the ACS subsequently...it's only when I use the autopilot and come off it to fight, this happens...

 

Ah OK. Does this happen in single missions or multiplayer or both? The reason I ask is that there is definitely something odd going on in multiplayer with regards to ACS reset. The only time I ever have to reset the ACS in single player is when I've yanked the stick while the autopilot is engaged.

 

This isn't the case in multiplayer: a few days ago the whole ACS system went out of alignment, with no warning, as I was coming in to land and I hand't been using the autopilot at all. Trouble is, I can't re-produce the problem so I have no idea what's causing it unfortunately.

System Spec: Cooler Master Cosmos C700P Black Edition case. | AMD 5950X CPU | MSI RTX-3090 GPU | 32GB HyperX Predator PC4000 RAM | | TM Warthog stick & throttle | TrackIR 5 | Samsung 980 Pro NVMe 4 SSD 1TB (boot) | Samsung 870 QVO SSD 4TB (games) | Windows 10 Pro 64-bit.

 

Personal wish list: DCS: Su-27SM & DCS: Avro Vulcan.

Posted
Ah OK. Does this happen in single missions or multiplayer or both? The reason I ask is that there is definitely something odd going on in multiplayer with regards to ACS reset. The only time I ever have to reset the ACS in single player is when I've yanked the stick while the autopilot is engaged.

 

This isn't the case in multiplayer: a few days ago the whole ACS system went out of alignment, with no warning, as I was coming in to land and I hand't been using the autopilot at all. Trouble is, I can't re-produce the problem so I have no idea what's causing it unfortunately.

 

Single missions. Gets weirder...

|| नभ स्पर्शं दीप्तम् || - Touch the sky with glory

Posted
Single missions. Gets weirder...

 

Hmm that is strange. I've never experienced this issue in single player.

 

Have you checked to make sure that only 1 physical axis is mapped to each control axis? E.g. make sure you don't have a game controller mapped to pitch & roll as well as your HOTAS. That's a frequent source of control issues.

System Spec: Cooler Master Cosmos C700P Black Edition case. | AMD 5950X CPU | MSI RTX-3090 GPU | 32GB HyperX Predator PC4000 RAM | | TM Warthog stick & throttle | TrackIR 5 | Samsung 980 Pro NVMe 4 SSD 1TB (boot) | Samsung 870 QVO SSD 4TB (games) | Windows 10 Pro 64-bit.

 

Personal wish list: DCS: Su-27SM & DCS: Avro Vulcan.

Posted
Hmm that is strange. I've never experienced this issue in single player.

 

Have you checked to make sure that only 1 physical axis is mapped to each control axis? E.g. make sure you don't have a game controller mapped to pitch & roll as well as your HOTAS. That's a frequent source of control issues.

 

Umm...not following...don't use any game controller apart from my HOTAS, Mouse & TrackIR...nothing else is connected.

|| नभ स्पर्शं दीप्तम् || - Touch the sky with glory

Posted
Umm...not following...don't use any game controller apart from my HOTAS, Mouse & TrackIR...nothing else is connected.

 

Ah, I should have explained it better. For example, my HOTAS has a small thumb-stick on the throttle. DCS thinks that this thumb stick is an extra mouse and for some reason in the default settings assigned the thumb stick X & Y axes to pitch and roll, as well as the X & Y axes of the actual HOTAS stick. Having two physical device axes connected to an in-game control axis causes all sorts of issues.

 

That being said, it doesn't sound as though this is causing the problem you're experiencing. Not sure what else to suggest to be honest :(

System Spec: Cooler Master Cosmos C700P Black Edition case. | AMD 5950X CPU | MSI RTX-3090 GPU | 32GB HyperX Predator PC4000 RAM | | TM Warthog stick & throttle | TrackIR 5 | Samsung 980 Pro NVMe 4 SSD 1TB (boot) | Samsung 870 QVO SSD 4TB (games) | Windows 10 Pro 64-bit.

 

Personal wish list: DCS: Su-27SM & DCS: Avro Vulcan.

  • 3 weeks later...
Posted (edited)
Ok now confirmed that there's a bug. Flew the same mission w/o using ACS and no HYDRO or any other such system failures and completed it successfully...I hope this reaches the devs!

 

Check my threads I had experienced inconsistencies but some of it later became more simple as I was assuming a lot of thing in the beginning. I found the bugs to be with some label mixing and the game assuming some failures for others, pertaining the autopilot, hydraulics and the FCS.

 

However I took a break again so I kinda forgot a bit. that's how I work, i get involved for a few months then a half year break then again ... in sessions.

 

 

In the latest update:

 

Su-27. Incorrect Mechanical Devices Indicator fixed

 

Which is kinda cryptic, im not entirely sure but it may be the bug I was talking about.

Edited by Worrazen

Modules: A-10C I/II, F/A-18C, Mig-21Bis, M-2000C, AJS-37, Spitfire LF Mk. IX, P-47, FC3, SC, CA, WW2AP, CE2. Terrains: NTTR, Normandy, Persian Gulf, Syria

 

  • Recently Browsing   0 members

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