Dugong

Is anyone else flying this bird with a MS FFB2 stick? Non of the autopilot modes seem to work at all with it for me.

I won't, don't worry, based on mirage being incomplete still after nearly 3 years. BST release all their products pretty much feature complete and i am very happy with all Belsimtek modules. As to finish this year, i am prepared to be astonished :megalol:

The problem is the uncertainty. There are reports of high end hardware running badly and low end hardware running fine AND vice verse. There is no guarantee that dropping a couple of thousand on hardware upgrades will fix things, so why would you until ED fix the engine?

We don't want your money/ the post.

Damn, this is my favorite aircraft and i hoped BST would do it what with Razbam not being able to actually finish a module thus far

This is just how it is in 2.5 , it seems the devs have chosen to have a battlefield heroes esque color palette.

Congrats guys, a very well done aircraft.

Ditto, it's about time!

So nothing to add as usual then?

Flight models do have a degree of subjectivity, however It doesn't matter if maverick if misguided or not, simply there are items that are quantifiably incorrect thanks to available technical documentation and knowledge from the russian side of the forum that have not been corrected in FOUR YEARS. To wit the ASP, the SAU, NAV systems. These are demonstrably wrong, but are not and will not be fixed. It took nearly 3 years for the weapon selector to be corrected. FOUR YEARS!

What does it matter? It's not like M3 are either; A) reading it B) Doing anything about it Maverick could publish a 300 page thesis on the FM and still wouldn't make a difference!

It's still possible to enable the HUD laser temperature display. Open HUD_SHKVAL_page.lua with notepad++ starting on line 126 to line 134 there is a bunch of code dashed out. Remove the dashes and you'll get the hud display. Makes it easier to work out what's going on and why your laser is overheating.

Agreed, i'm not buying 2 to 3 modules just in the vague hope that the 1st one i paid for will get finished. The whole experience has left a very sour taste that means i won't be buying any LN/M3/HB products. ED have effectively given tacit approval that 3rd party devs can split up the company and walk away from their obligations scot free.

Ditto, it really is becoming beyond the pale. The disturbing thing is there doesn't appear to be any inducement from ED, kicking the 3rd parties up the behind to finish these things. ED are the guardians at the gate and are ultimately responsible for the quality of DCS as a whole. The MIg-21 at four years old and not even remotely complete, accurate or substantially bug free smacks of a product that will NEVER be finished.

From what i remember the ECM is manifested as a simple range modifier for the sams where; No ECM = Launch range x 1 Ecm On = Launch range x0.85 Multiplier varies with ecm type, i think.

FD = damping on selected input channels only Non FD = Damping channels + autopilot 'hold' functions on all selected channels

They are the other 20+ modules, maps, campaigns to do that! I suspect Darkwolf has a point, i've noticed it's very difficult to get friends involved with DCS due to the high potential cost, and DCS is really about hi-fidelity jets as it's core competency. The two free one don't showcase this; The Su-25 is a jet, but not hi fidelity/clickable. The Tf-51 is hi-fi, but not a jet. So not of interest to people not into WW2.

As above, one of the devs (smiley i think) said a long while ago that we would eventually be able to edit all 10 of our countermeasure programs individually. Has this been implemented yet?

I think we're pissing up a rope, development seems to have effectively stopped from LN/M3, apart from Rudel doing a bit of texture work it seems the lights are on, but no-one is home!

Also use a MSFFB2 here, you may want to try reducing Y-saturation. It's doesn't conflict as badly as curves do with FFB. Also consider that AAR is just really difficult! You might not be any better with a different stick, i'm not.

You are correct in that you can't really use curves or deadzones, because once you've trimmed outside of the deadzone, the deadzone effectively no longer exists. ED really need to implement deadzones/curves that always reference/scale with the PHYSICAL center of a FFB stick as the center of the curve/deadzone, but i doubt that will happen. Options for stick damping and friction would be nice as well. You can use simFFB on some aircraft, but it completely overrides any FFB effects sent from DCS.

Right, cheers for that Weta, but what version are you testing in because mine definitely isn't functioning as you describe, and no, no curves or saturations or deadzones. I'm not playing much in 2.5 because of the terrible performance issues, is it possible this is patched in 2.5 but not 1.5.8?

Not sure i follow Trimming is by it's nature transitionary, if we were always "trimmed for constant speed/altitude in the first place' there would be no need for trim. This seems like circular logic. But isn't push and hold trimming the incorrect method for FFB? With FD on unless i'm mistaken, there should be no AP at all, only damping of the channel. So where is this extra uncomanded pitch coming from? To my mind it appears ED have left in code in the FFB trim mode that should only appear in the non FFB trimming modes, i.e they are artificialy simulating a 'jump' when relieving forces on a non FFB stick, which you don't need to on a FFB stick because it actually, physically moves.

It's bugged using a FFB stick as it commands erroneous extra pitch , even in FD mode. I tested by locking my joystick rigid and mapping the trim button to seperate control so there was no movement of the joystick at all. It's possible to do front flips just by repeatedly tapping the trim button!

A somewhat related question, is it possible to remove individual HUD elements from the FC aircraft. I.e Would it be possible to remove the velocity & altitude from the Su25T HUD?