gulredrel

Soon celebrating first anniversary...

Thanks. Didn't thought about restarting. Tried again, the double entries were gone and now I was able to rebind the keys for kneeboard.

I've seen the duplicate kneeboard entries for the Mirage in current open beta again: DCS/2.7.8.16140 Rebinding does nothing for me. Is this a general thing?

My bad, I guess I didn't express correctly, so easy flight mode should be "OFF", as in "ON" it will take over some control functions.

I'm flying in stable right now and no problems with the trim. As @Morpheus suggested. Check if easy flight mode is on and re-check button assignments for elevator trim and trim reset. maybe there are some double things preventing the trim to work for you.

@BIGNEWY stable changelog problem is still there, could you please fix this as soon as the OB hype has settled a bit

mmhh... okay, as there is the radar altimeter readout below the baro altitude tape, I don't really see a reason for switching the switch to radar alt. I was just curious and couldn't see a difference. Or is it map-related? Was flying on Mariannas map.

Hello, couldn‘t find something using search so I‘ll ask here. Does the altitude switch on the HUD control panel changes anything? I was unable to see a difference being above or below 1500ft AGL as the manual suggests. Is this feature currently not implemented? Thanks Jens

I saw the Mover video too and tried holding the HUD warning reset knob, but this did nothing in DCS. That's why I asked, if there's something else to select.

Hello, as the title says. Is there a way to reset the max historical G value which is presented in the HUD's lower left during flight? Thanks Jens

@Vibora Could you please have a look, when time permits?

Thanks for the Forrestal, great addition to the game. Now I need a proper official carrier trainer.

Hello, just wanted to ask, if this is intended or not. The taxiway - runway connections have been widened several updates ago, but there are still the high standing taxiway light installations at Kobuleti which are not in the middle of the concrete strip. Thanks Jens

Looks like the stable changelog on the website (DCS 2.7.7.15038 - 03.11.2021) is a copy of the old stable changelog and not the merge of the latest open beta changelogs DCS 2.7.7.15038 Open Beta - 28.10.2021 and DCS 2.7.7.14727 Open Beta - 20.10.2021 Regards Jens

Hello, Could you please try to check the following? Don't know if it's a bug or something I did wrong. I enabled smoke on ground in mission editor and tested the airshow smoke system before starting the takeoff roll while standing still. Wind in mission is set to 4 m/s at ground level in Caucasus map. The smoke cloud from this test stayed the whole time at the beginning of the runway. Smoke used during flight disappears after a short period of time. Please see screenshot and trackfile attached. Version: DCS stable DCS/2.7.6.13436 Thanks Jens C-101EB_show_smoke_groundtest.trk

Stacked warning lamps to create panic and even more panic Will treat it like this, thanks.

Hello, on the kneeboard, the lines for ARK-5 preset frequencies always only show 0.00 kHz. Would be really helpful to show the frequency for NEAR / FAR selection as the dial on the ARK-5 receiver is hard to read, especially when looking from an offset above. I think it's not that important to have different lines for the ranges, as you can easily switch the range selector while tuning in ANT mode. Currently I'm using "cheat" or simplified mode without option "FAR updated NEAR". But this should be irrelevant here for the kneeboard functionality. 490kHz in FAR mode selection: 870kHz in NEAR mode selection: Thanks Jens

Hello, I wondered last time I flew the Hind. Started only with around 1000 litres of fuel and flew quite a while. Tank 2 120 l warning light came on. I checked the individual tanks with the fuel gauge selector. T2 was down but T1 had more than 200 l remaining. After running tank 2 completely dry, tank 1 contained around 100 l remaining fuel, both engines still running; so from the diagram in Chuck's Guide (thanks @Charly_Owl) I think both feed the same line distributing fuel to the engines. Does the uneven usage come from maneuvering, yawing and slipping while flying or different feeding from tanks 4+5 to 1 and 2? Should the amount of fuel be manually balanced between the tanks or is this normal and not critical? Thanks Jens

Don't know, if I understand correctly. Maybe you could provide some screenshots or a trackfile. The flap lever in the cockpit has 4 positions: up, neutral, takeoff position, full down. I've mapped buttons setting the lever down and up. Starting with flaps fully up, you can select takeoff position, the flaps move to takeoff position. For fully down, you need to set to fully down position. Now setting the lever in the takeoff or neutral position will not move the flaps. Only setting in the up position will retract the flaps. You can stop in any position during transition by putting the handle in neutral. Maybe that helps Jens

I used the skin pack provided here to populate some of the road blocks: https://www.digitalcombatsimulator.com/en/files/2943310

Please read the post above, @Ramsay put it really nice together with pictures. Only some OM/IM combinations work. Frequency range set and than tune with the hand crank on the ARK-5 receiver on the right side of the cockpit. On the kneeboard there's also a hint for the frequency as the scale is hard to read sometimes due to parallax error and what not.

As the threads linked by Flappie explain. The three switches select the frequency range on the ARK-5 receiver which will be used when switching from far to near. 150 - 310 310 - 640 640 - 1030 Far beacon being within the 640 - 1030 kHz range, tune this in the ARK- receiver. The corresponding inner beacon is within 310 - 640 kHz range, you need to switch the 310 - 640 kHz (middle switch to on). Overflying the outer beacon, you can now switch far/near switch to near, and the ARK-5 "automatically" receives the inner beacon (without turning the crank), because in the near position, the range selection is used from the switches and not from the frequency range dial on the receiver unit.

Not only this toggle. See thread here: You need to bind the individual switch positions.

Had the same problem as the original poster. Rebinding and setting deadzone with my T.16000 did the trick. Was able to engage AP after doing that again.

Thanks for testing. At least, not only my local problem.