Vibora

It should be working. I'm in contact with ED and will try to give you an answer soon.

Right now we have our FM coder working on damage model interaction with flight model, and the systems coder working on completion of rear cockpit systems interaction with front cockpit in multiplayer. Once that is done, we'll work on failures setting in ME, real engine sounds, force feedback and adition of some effects to flight model, like cockpit vibration near the stall. After that it should be ready for release and only bugs or minor items would be pending.

Thank you for your praises! :) - Engine management with ECU off: be sure you move the throttle slowly otherwise you'll get an engine surge. It's probably a bit exaggerated and we would need to relax it a bit, but in any case, in the real airplane you have to be careful with this, in fact, a failure of the ECU requires an immediate landing. - Trim tone. Known, low priority right now though. - Number 3: the modeler will take a look at it, thanks for reporting it, good catch :)

Known and, as you say, low priority right now, sorry :)

Hello Joey. The flight model itself is not WIP. It's fully developed, and it's a huge and thorough work that reflects exactly the real airplane, as we already stated a few times. You should apply brakes, add full throttle and release brakes once the engine is stabilized at full power (check engine parameters, N1, ITT, N2 and FF). Only then you'll get the normal acceleration during takeoff since it takes several seconds for the engine to get full rate. Regarding deceleration, it's normal, this is not a fighter with small and swept back wings. Gliding performance is correct according to real airplane of course and as I said the Flight Model follows exactly the real behavior.

Yes, I confirm those news, got that info some days ago. If we get some extra sales our programmers will work with more strength to get a release version asap, which is what we are worried about, so that's definitely good news.

Shadows depend on graphic engine, 3Dmax deals only with modelling. It could also be an issue with your graphic card. I don't see that shadow error.

Will ask the modeller.

Correct :)

Solved.

The Persian Gulf map is really very much WIP regarding navigational aids… for example, some ILS do not work yet.

Hi Chump, I don't know exactly what you are trying to do. There are no DME stations in DCS, just VOR and TACAN stations (apart from NDB and ILS or RSBN). I guess you know this, but just to make sure, to get distance reading in the C-101CC, since there is no TACAN equipment onboard, you have to use the equivalent frequency to the corresponding channel of each particular TACAN. You have a table in the C-101CC kneeboard.

Thank you for your offer, if I need your help testing or setting it I will let you know. I have a FFB, we need to find time and resources to implement the code.

Will try to do it.

Welcome :)

Very nice review this one as well, congratulations and thank you, good job :) As you know, you can take controls from rear cockpit with J key to ask for controls. Regarding comments on this article. The AOA indexer is on in this aircraft the whole time, not only when landing gear is down.

Published in our Facebook page :) https://www.facebook.com/Aviodev/

Thank you for your report. Good catch! :) Solved, will appear in next update.

Great article! Thank you and congrats! :)

It all depends on how much aft is the center of mass of the aircraft. Let's consider a C-101 flying in level flight. If the center of mass of the aircraft is far enough to the rear, the vertical component of the aerodynamic pressure created by the airbrake surface will create a pitch up moment higher than the pitch down moment created by the horizontal component of the aerodynamic pressure, since the arm of the first will be longer than the later. The center of mass is rather near to the center of the air brake, so it's not easy to see why this effect is really happening in the direction it does. But this is how it behaves, it is written that way in the manual, it is confirmed by real pilots and, more importantly, it is the real aircraft aerodynamic data that we got.

Hi Sirius. I would rather prefer deleting the toggle function than getting rid of speed brake implementation in rear cockpit in multiplayer. BTW, could someone test it online in rear cockpit and swapping to front cockpit as well? We tested it internally but would need a more thorough test. Thank you :)

Hola Eduardo. First of all, sorry that you have troubles programming speed brake in your HOTAS, but I'm sure you'll find a way since Cougar software is a very powerful tool. I confirm that the switch in the real airplane behaves so, you have to press and hold it to get to a full deflection, or deploy it to intermediate positions, that is why we implemented it that way, and it should be like this in any aircraft or at least most of them. Also, as Kontiuka says, I would delete the toggle option, at least until we find a solution to it, or perhaps indefinetely, if we don't find an easy solution or if we want to keep it at full realism.

It most likely got broken when implementing speed brake for rear cockpit in multiplayer. I could only test keyboard command B since I'm right now with my laptop and without any joystick, but I guess this would also reproduce when using a joystick button. Until one of our programmers (or myself) takes a look at it, which could take some time, I recommend you use Air brake - Extend and Air brake - Retract in input options, moreover, this is the realistic way to do it. In fact Air brake - Toggle should be deleted from the module since it's not how it works IRL. In your case, I recommend you use T9 to extend (LShift + B) and T10 to retract (LCtrl + B), since T9 is a spring loaded type of switch if I recall correctly, it would work perfectly and you should be careful when using T10, since you need to remember to bring it back to neutral when the speed brake is fully retracted (or deployed if you decide to do it the other way around).

Cool! :)

Congrats Sirius :) Keep up the good work :)