frumpy

FYI, this link says something like a 60° cone with bank, so valid until 30° bank, then the radar alt should increase with bank: https://aviation.stackexchange.com/questions/53834/how-does-the-radio-altimeter-reading-change-with-the-bank-angle Which, again, leads me to the assumption the RA should increase above 30° bank until max RA is reached.

Thanks. I think the frames of the video do not play a role. At 7:51 between 2580 and 2577ft you can see the HUD moving, but altitude stays the same. These 2-3ft jumps may be due to sensor resolution or maybe there is even an internal meters-ft conversation, maybe both, I don't know. So for the RA you say the bank angle is compensated and cut at 40°?

I meant the radar alt is supposed to increase with the bank, until max. RA is reached. Try e.g. with the Su-27 or L-39, until about 30° bank RA stays constant in level flight, between 30-45° it increases with a function like sin((bank-30)*2)+RA. Like 0-30°= 100 ft, 45°=140ft, 60°=190ft or so.

Wow! A full size FFB-stick is on my bucket list for things to do in life. I wonder, are all information / software / STLs complete? So if I press "stop" on the internetbutton and work with the info I have, is it possible to do this on my own? Is there a parts list?

On the alt readout. I found a video which is supposed to show the HUD, watch at 7:48 (speed x.5 helps). This is 2-3ft jumps at 2500ft. With increase in altitude, the spacing should enlarge by factor 3-4 at FL400 due to the lower pressure diffrences. Well, I bought the JF-17. Would you be willing to adapt this and intruduce a radar alt increase with increasing bank?

Hi there, in a topic on the JF-17 I wondered why the barometric altitude readout is per single digit, instead of like 10 or 20ft increments like on other aircraft I've seen before. I think this is wrong for several reasons, but since little data on th JF-17 is available, the proof is in eating the pudding Does anyone know a single real world aircraft where the baro altitude is read out in single digits?

Thinking about this... is this the same scaling, regardless of altitude? Like there is still a 1ft resolution at FL300? Is this a real barometric reading or INS or INS with laser? And is the increase of radar alt with increasing bank (like 30-45°) simulated?

Wow, looks like a human factors issue. Ok, well done then!

Hi there, I am not (yet) a customer of the JF-17, but might become one. One thing that bothered me during the free-to-play periods were the exact readouts of altitude and fuel (I think VS and maybe others too). I've never seen an aircraft giving exact readouts like 23,456ft or so, should be rather rounded to 23,460ft or so. Perhaps chinese a/d-converters are different and this is a feature, but I believe not. Is this a known issue or has this been worked on lately? Thanks, Olli

Hi there, I'm trying to edit the Capt Zeen L-39 profile. I would like to exchange the ADI with the MiG-21 one that comes with Helios, but I can't get a grp on the basics. I've got an idea of how to work with Air Manager, but Helios seems to be a very different game. I checked youtube and the forum, but cannot find al the info I need. Where are the gauges per cockpit stored? As for the L-39 ADI I found a part in C:\Users\Olli\Documents\Helios\Images\Capt_Zeen\L39, meaning the frame of the ADI, but not the black/blue horizon itself. 1) Where is the logic of the L39 ADI stored? 2) Where are the complete graphics of the ADI stored? 3) How can I change them? 4) Where is the MiG-21 ADI stored (see screenshot)? It's not in C:\Users\Olli\Documents\Helios\Images\Capt_Zeen\Mig21bis\instruments, even though some parts of it seem to be there 5) relates to 1) and 3): How can I link the MiG-21 ADI with the output data from the L-39? Thanks, Olli

A friend pointed me on doing a no-flap takeoff: It's tough to keep the attitude below 10°, as it easily goes to 15-20°. With flaps its like a walk in the park, set 7° and everything goes fine.

Looks great! I am thinking of doing something alike. What plans did you use?

I'd like to join, but fail on the "What US branch of armed forces does the F/A-18 serve?"-question. It's the Marine Corps. no?

I was asking because certain projects I am looking for are not mentioned, also because obvious things like the A-10II being published and then weeks later the features of it are presented in the newsletter, as if they were new things just being added (flight model and "brrt"). What I am getting is news that are no news, third party announcements, multiplayer event annoucements and sales. I am looking for news on ED projects like the Marianas map, the Hind, for any work on he Yak-52 or the recently introduced (and severe) bug on the L-39 cockpit textures which make the aircraft unflyable. I would appreciate regular information on the mentioned topics, also info on removed bugs or bugs that the devs are working on. And while the "brrt" is worth being mentioned in the news for some reason, switching the forum software/look does not seem to be of any importance. Thank you.

I have this too, but with a GTX770 and RX7700XT. It happened in about 2/3 of the times with the GTX and maybe 1/5 with the RX. However, X-Plane won't run if I update the driver.

Hi there, I'm trying to get this mission to run with the UH-1: https://www.digitalcombatsimulator.com/de/files/2596555/ I installed Upuauts Mod as described. When being in the heli, I'm told to fly 3.2 NM at 137° to land on a hospital - which should be marked be orange smoke. I see orange smoke in the area, but it's somewhere in the forest. Is this mission broken or what am I doing wrong? Landing on a tower is just sooo tempting..

Hi guys, since weeks I'm getting the impression that the development of DCS is somewhat stalled. Checking the news, there are only little changes - like the recent posts of the A-10 flight modelling and the "brrt" sound from the outside view. These things have been made/announced before and were presented like they were new additions. Also this week, just a sale and that's it. Months ago the team said that bugs are taken care of, but I have not seen many bugfixes. Is it due to Corona (=I'm having more time to check the weekend newsletter) or what is going on? No intend to upset anyone, I'm just trying to understand whats going on under the hood. Olli

Olé! :D Thanks.

Not sure if I made myself clear enough. The Captn Zeen installation video includes the 3D inside view on first, the panel on second monitor. I am looking for a forward view without the inside 3D panel on the first monitor. It should be similar to the attached pic. Thanks!

Hi guys, this has probably been discussed before, but I did not find what I was looking for: I am using Helios on one screen and want to put the front view without any 3D panel on the second monitor... but how?

Speaking of textures, there is some z-fighting going on on the lower left end of the curtain, visible from the front cockpit (about 1:30 into the video). It's been like this since the beginning, perhaps someone wants to repair this too? :)

Speaking of the AOA: Using DCS-Bios, I am trying to export the aoa-value to display it on an instrument. I need the raw-value of the AOA (or some 16 bit value). I could interface the A-10 via the documented control references. I wonder if the control references of the C101 are published for cockpit builders?

Hi Hansolo, thanks for taking the time. As of now, this works: #define DCSBIOS_IRQ_SERIAL //must go first! #include "DcsBios.h" int RedLed = 9; //D9 int YellowLed = 7; // D7 int GreenLed = 8; //D8 //==================== Main =================================== void onAoaUnitsChange(unsigned int newAoaValue) { if (newAoaValue >31000 && newAoaValue < 37000) {digitalWrite(GreenLed, HIGH);} else {digitalWrite(GreenLed, LOW);} if (newAoaValue >37000 && newAoaValue < 43000) {digitalWrite(YellowLed, HIGH);} else {digitalWrite(YellowLed, LOW);} if (newAoaValue >43000 && newAoaValue < 49000) {digitalWrite(RedLed, HIGH);} else {digitalWrite(RedLed, LOW);} } DcsBios::IntegerBuffer aoaUnitsBuffer(0x1078, 0xffff, 0, onAoaUnitsChange); // ============================== Essentials ================== void setup() { DcsBios::setup(); pinMode(RedLed, OUTPUT); pinMode(YellowLed, OUTPUT); pinMode(GreenLed, OUTPUT); } void loop() { DcsBios::loop(); } So far, so good! :) The indexer lights will work independently of the built in AOA indexers lights of the A-10, just depending on the AOA. However, now I want to implement this to another aircraft, like the C-101. Do you know how I can find out the adress of the AOA of other aircraft?

Thanks Ramsay. In cockpit design it's always prudent to give the pilot only the information needed, since the performance will decrease when the pilot is overloaded. If the AOA indexer is always on in the EB, than that's a feature of the real aircraft (and human-factor-wise of a design flaw) - that's good. Btw., I like the new 4k cockpit, well done! :)

Thanks, that did something! :) However, there is something strange going on. Some LEDs need the pinMode command, some don't. Also the pins of the Nano seem to be different than the usual Nano layout. I'll investigate when I have more time.