Search the Community

what is going on here,...petrovich as pilot is whacked. He is constantly flying into the grund. Not only that but the .trk is whacked as well...it shows no engagement what so ever ,even though I engaged a target plain as day...even the headings are wrong on the interface. Is the sim that broken at this point??? failure.trk

patches 2.7.4.9632 and 2.7.4.9847 have introduced various fixes and tweaks to controls, trim and FM. And for the most part they seem to have been very sucessfull (fe the problem with "overtrim" are far less and the sound feedback is also very helpfull). The Shaitan-Arba is now also much more controllable at low speeds. Especially noteworty in a positive way - VRS does no longer suddenly and fatally happen, the soundmapping for RBS, VRS, max-envelope aso is now a completely suitable indicator. What seems to need further attention is the following though: the feel of weight and mass now seems reduced, and the Hind is too twitchy in various envelopes (to the point where one seems to "stir" the cyclic aka the joystick) while hover transitions are now far more controllable the hover itself seems to have become very twitchy even in low-weight and zero stress conditions the wheels now "soapglide" even more in almost all terrains, even with collective on zero, rpm throttle down, and wheel brakes locked I have included a track from the remastered-for-hind huey-campaign (ty for that excellent scenario to really control the Hind @Bailey) where this can be seen. I also could directly compare the asset behaviour to before the patch (as I had just flown that mission before both patches). Twitchy hover: during takeoff at final landing at "Madrid" at the end "soapgliding" of wheels at rolling landing and taxi at Senaki-Kholki on the pad at "Madrid", with various test of AP channels, locked wheel brakes, applied wheel brakes, idle rpm, zero collective, diverse trimstates "rudder" (tailrotor), "heading" AP channel on/off slights osciallations during flight in stable envelope with no input entire flight various attitudes, crabbing during transition during speed hook or forward reduction notice zero control input (control input indicator up entire track) notice "pulse" inducing oscillation with slightest inputs as if input signal is registering on/off For the problems describe above, also notice how for the most part non-pilot induced oscillations seem rock stable while any attemopt to correct them with minor cylic, minor collective or general slight(test) peripheral input seem to surge the oscialltions or the twitchy hover behaviour (especially noticeable at the end of the track, when I almost crash myself at "Madrid"). The widely reported "overtrim" or "input overshoot when pressing trim" is reduced but still noticeable. For the passer-in-glancing, please focus on the bug behaviour, my bad flying is a given having to be seen as "baseline" . Trackfile as google-drive link as filesize exceeds attachment limit: https://drive.google.com/file/d/1u71lvSaImScYA2f3zgynpGPhEwe5roFX/view?usp=sharing Dxdiag file attached for good measure. DxDiag.txt

I wanted to log an official bug that's preventing me from flying the Hind correctly: the rudder trim is not working, even though it is selected in the special menu. I've started another thread of this and it seems many people are having the issue. When twisting the joystick and pressing the trim button, the rudder will not stay trimmed in that position, the same way it does with the Mi-8. It simply goes back to the middle. I can manually trim the rudder by using the left and right rudder buttons, but the typical rudder trimmer is not working. However it does work just fine for the cyclic. I'd like to get feedback to make sure it's been logged as I've owned this bird for several months now but am unable to fly it because of the rudder bug

in "known issues" thread it says "no consequences". https://forums.eagle.ru/topic/274181-dcs-mi-24p-early-access-known-issues-please-read-before-posting-issues/ Engine fire has no consequences. This will be corrected as the damage model matures. however here it appears that fire (which did NOT cause fire detector warning btw...) causes rotor blades to separate after several seconds. NoFireWarning-RotorBladesRandomlySeperating.trk

Hello, pls see my other post from this topic: Honestly, I know, its EA still but basically since June there is no change in Petrovich's behavior as a pilot (for offline, player as pilot operator). I think this is important: Explenation: We have still some of button free for Petrovich menu so maybe the best option is to add possibility to change for R and B (radar and barometric alt as default, or only barometric, not radar). It could solve a lot of things. After all, if I fly with a real person, mainly the barometric altitude is maintained, not the radar altitude (only in extreme and dangerous situations) durring attack.

Firing an AIM-120 in RWS mode. I wait for my missile to pass Pitbull then I lock a second target. On my radar I see the symbology concerning my first contact applied to my second target. I know the radar is in WIP but is this normal? F-16 RWS Test.trk

OK, so we've been struggling with this problem for awhile now, and this can't be the way that this pod is supposed to perform. I understand the zoom part completely. It doesn't have anywhere near the range of the Litening pod. But the clarity is just terrible in certain conditions. In direct daylight without clouds, the images in the pod look great. Add some low heavy clouds in morning or evening and it just becomes useless. In some conditions the ground vehicles are so fuzzy, they just look like blobs of white, almost like bushes at a distance over 10 miles. What is going on with this and is this going to get addressed? Or is it something we're not getting about the pod? You can see that close it it's crystal clear, but if you're out at 15-20 miles it's just useless.

The FCS BIT test seems to always show ready after a cold start now ? is this new behaviour intended?

Viper is limited to 800kn VNE under 30k feet. There are charts, I'm pretty sure ED has them, your SME's should also know this limit rather well. The fact I can routinely go to 900kn clean without the engine blowing up is a bug. Here is also a track HyperViperbug.trk

Posting this pre-2.7. Not really a bug, but either ED is gaslighting me, or 'CPL' sometimes flashes up on the blank lower position of the UFC (below RALT). Please someone else say you've seen this as well....

Noticed a few possible bugs here: A) On Air start missions the Hind will add some yaw corrections to the rudder even if rudder assists are disabled, I have to reset trim to cancel the input other wise they will stay offset. This happens in self made missions and the instant freeflights where you start in active pause. General Yaw autopliot: B)If engaging the yaw auto pilot once the pedals are offset these will not return to center when yaw auto pilot disengaged. You have to reset trim. This is not a problem in forward flight but if using the Yaw auto pilot in auto hover it can become a problem, as when you want to center the pedals after YAP disengaged you have to do a trim reset which also cancels the cyclic trim. This can lead to some messy situations. Shouldn't the pedals return to Centre after Yaw auto pilot is turned off ?? It is no longer getting inputs from the FCS. Turning off the pedal damper has no effect. C) If taking over from the AI pilot the pedals can be offset (regardless of YAW AP) , only way to centre pedals is to reset trim which again is tied to cyclic, not ideal if low and slow. I do not have any rudder assistance selected in game menus and all game avionics modes etc.. are de selected. I do not have sync hotas at mission start as the latest update is creating issues with the joystick (TM HOG), the stick will go full forward and to the left on mission start (not a Hind issue) happens in other birds until I force back control and then it centers, but even if do have sync selected and let the cyclic do its thing the pedals are are still the same as part A on mission air starts. Edit: Added to tidy up the topic. So more playing about today and to highlight the issue I am talking about. I have been testing the AI handover between seats and as mentioned in this thread the pedals create issues under certain cumstances. Simple Test: (no rudder helper selected in game options) Go into a stable hover , switch to front seat, let AI settle the hover, switch back to the pilots seat and then perform a 90 degree turn to the left and maintain stable hover (something you might actually do) Result: When you take back over the pilots seat the all the controls controls are trimmed, obviously this is good as you don't want to crash on take over. The problem becomes the pedals, when I do 90 degree turn I am fighting this offset left by the AI, once my turn is complete I am having to dab left rudder now to maintain a heading. While doable this starts becoming extremely awkward as my brain/muscle memory is telling me I need to right rudder in a hover plus I am only having to lightly feather left which is also awkward. My pedals being center spring (VKB's) are now completely out of wack to the helo controls. To combat this you can reset trim, however as mentioned already the trim reset also zeros cyclic. I have managed to catch it and go back into hover but again this is making a simple task more difficult, resetting cyclic trim near the ground is not a good idea really. Would this be an issue at 300m in forward flight, no, but it can be an issue else where. The above is linked to the same prob with turning off Yaw AP, your pedals are stuck until you reset which cancels any cyclic trim. While resetting the pedals may not be accurate neither is the current system but rather it is just tied to re-setting cyclic. Possible Solution: I would assume there are different ways to to implement how the pedals work but adding a extra separate bind to re set the pedals would be easiest I would guess. This way you do not have to change the current behavior of the 2 ways to reset trim (double tap trim or trim reset) You could double tap set-trim to reset all, current re-set trim could still be used to cancel both cyclic and pedals, plus the extra reset pedals only needs be used if a player wants. With those 3 options it would cover all bases IMHO with out effecting currently how the module works. I would hazard a guess for those that like flying with the rudder helper, having a separate pedal re-set could also be useful. With the above , on my cyclic I would map ''set-trim'' and ''pedal reset trim'' as "set-trim'' does 2 functions.

Hello All, Regarding JDAM loft in the F16, as of now from the brief tests I have done, the munition misses, even if it is in the LAR. See attached track file. Following a relevant correspondence in this thread: What is the status of this capability? Best, Mk JDAM Loft Miss.trk

Since the last patch FLIR-Brightness is to high. Notic this thread: https://forums.eagle.ru/topic/294402-f-18-flir/#comment-4906833

I know issues are supposed to be kept separate, but a few of these things go hand in hand. On the AZ/EL FLIR sublevel, first off A/G L16 ID symbology is being used for the MSI trackfiles. AZ/EL it the only format that is only available in A/A yet for some reason its the only time we see the A/G symbology. TDC depress over the MIDS only trackfile elicits no change, yet additional data is supplied when TUC'd. (L+s should be set to that trackfile) The issue here is that the FLIR LOS cue will not track to the trackfile without radar contribution. With radar contribution, the cursor can be depressed at the edge of a trackfile and the FLIR LOS cue will surround the HAFU and track it without L+S. SLAVE on the right of the display will be boxed. With a trackfile lacking radar contribution, FLIR LOS will not SLAVE. See track below. AZELHEX.trk

after mapping collective and cyclic controls to a joystick, observe no animation response for the in game virtual cockpit controls for the collective and cyclic..

George is not reporting single targets when locked. Manual says on page 355 George will scan the designated area for targets. If a single target is found, George will track it and report its type (range permitting). I dont think he is reporting any single target, type is just known when in the list. would be helpful if he did.

Hi, TERM settings have no effect on the AGM-154C, as in the track 154c.trk

George is cheating. He can see through clouds and all manners of obstructions and still get hellfire shots to hit. Pretty sure lasers don't go through clouds either. I saw this in caucasus when engaging a target in a fairly high valley that was filled with clouds. George would have no issue identifying targets and engaging them through the very thick soup. Neither TV, FLIR or lasers should penetrate clouds. Again, big multiplayer session, no track. But it should be fairly easy to reproduce.

Is the auto image stabilization not working? I try flicking the switch to "lock" the TADS on a target to help compensate for pilot input wiggle but it seems to have no effect.

Tested on MP ans SP as well, reproducted all times. on CPG on last update DCS 2.7.15.25026 OB: -moving the tads normally no problem, -moving it normally+laser on no problem, -moving it with LMC on no problem, moving it with LMC+laser on, the tads will move abrubt to full right or left and it will not move anymore untill you switch off the lmc Track file attach bug LMC+laser.trk

nullwas able to re-arm pylons that were shot off without repairing.null

That's not very nice to model the pitot icing over but not give us anything to do about it. How am I supposed to fly on servers with the temperature below freezing? Is there some workaround in the settings?

I'm really struggling to get this thing to autorotate, seems I keep loosing hydraulics and therefore controllability. Test conditions Alt: 1500-1800 ft agl IAS: 70-80 Kts Pull power levers to idle, lower collective and raise nose to maintain 103-105% NR Even at this nominal NR I seem to lose control response almost as if the hyd pumps are connected to the engines rather than the front of the MGB. Any of the SMEs want to chime in here and give some tips? @kgillers3@Raptor9

Hello, everyone, I know that these are new units and that they may still be WIP. But I still have to address it here in case it was overlooked. The new technicals (armed pickup trucks): -Scouts with mounted DSHK 12.7mm or KORD 12.7mm -MLRS with BRM-1 80mm Rocket -Air defense with mounted ZU-23 all are unmanned. Whether active or not. They are ghost vehicles or unmanned drones.... My question to ED is: Will that change in the near future? or will they remain so half-finished for the foreseeable future? I find it not very immersive when I'm attacked in my Apache by a technicals that is unmanned. lg Dagobert