gulredrel

I also had no problem doing this. Going out of AB detent but leaving throttle at MIL is okay to decelerate below M1.4, so the RPM in MIL than lowers to 8400 rpm automatically and from there on, you can reduce further.

Hello, can anybody explain why Dassault did not mount a radar altimeter on the Mirage F1 as we have it here? Do some other versions have one? As it's not an early jet and capable of ILS and other bad weather navigation equipment I wondered why there is no radar altimeter. Which books on the F1, preferably in English, are recommended? Thanks Jens

Old thread needs some pictures

1. Theres sometimes the issue that after adding a flight, setting group to uncontrolled, after adding some more planes and setting options, the uncontrolled option is not checked anymore. 2. And would be nice, if this could be addressed: Thanks Jens

Cyprus tour nice detail in the setting sun, enroute to Lanarka VOR, Akrotiri TACAN set, ready to turn and capture approach course Approach to Akrotiri

You can't mute it at the moment. Same for TACAN. To mute it, you need to turn TACAN or VOR off or tune a non existing frequency for the map. Sure, this doesn't help for navigation. Bug has been reported a while ago:

Testflight high above Cyprus and down low at Akrotiri Many thanks for creating that skin: https://www.digitalcombatsimulator.com/en/files/3325204/

Hello, don't know if this has been reported. It's hard to describe. Problem: Airplane group waypoint add/edit dialog will behave totally weird when using measurement mode with pressed middle mouse button and than pressing right button. The airplane group dialog is no more usable, every click creates a new waypoint for this selected group. Steps to recreate: Open ME ne map set airplane with some waypoints user measurement mode with holding down middle mouse button and measuring something while still pressing middle mouse button, inadvertently (or now on purpose) press right mouse button actual result ruler stops working, every click creates new waypoint only way to stop this is alt + tab out of DCS, close DCS, ME now shows option to stop DCS or continue having head this issue, tooltips are mostly gone, so not really cures the problem additional info: can be reproduced also if no vehicle dialogue is present, ME seems to be stuck in ruler mode, nothing is really clickable as it should be expected result: I would expect, that only measurement mode stops working and I can resume editing as normal. I hope this video helps and is accessible (never uploaded one before): Thanks Jens dcs_20220811_editor_ruler_rightklick_problem.log

Ran into that issue now with 2.7.16, so I see it has been reported a while ago.

Changing attitude with trim works, when basic mode is on. But currently there is a bug. Pitch commands are currently inverted in this regime, you need to use trim down to pitch up when attitude hold is on. So be careful when doing this low level

I hope you will find the culprit I lately watched one of the First Impressions video on YT from an earlier build and that Snecma Atar sounded wonderful.

Please find sound.log attached. multiple entries "effects\aircrafts\engines\su27frontengine2" and "su25frontengine" or " COCKPIT_MAIN:su25inengine", but button clicks coming from mirage-f1: [schnipp] 2022-08-08 16:25:23.205: MeteoDispatcher/main:field: dt = 32.457000, offset = 32.457000 2022-08-08 16:25:23.226: sound del: "effects\aircrafts\mirage-f1\cockpit\devices\left_console\start_button_cover_close" now = 32.976000, sched = 32.966745 2022-08-08 16:25:23.226: MeteoDispatcher/main:background: dt = 32.976000, offset = 32.976000 2022-08-08 16:25:23.226: MeteoDispatcher/main:field: dt = 32.477000, offset = 32.477000 2022-08-08 16:25:23.247: MeteoDispatcher/main:background: dt = 32.998000, offset = 32.998000 2022-08-08 16:25:23.247: MeteoDispatcher/main:field: dt = 32.499000, offset = 32.499000 2022-08-08 16:25:23.268: MeteoDispatcher/main:background: dt = 33.019000, offset = 33.019000 2022-08-08 16:25:23.268: MeteoDispatcher/main:field: dt = 32.520000, offset = 32.520000 2022-08-08 16:25:23.268: woLA-16777472:su25frontengine2: dt = 0.000000, offset = 0.000000 2022-08-08 16:25:23.268: woLA-16777472:su25frontengine: dt = 0.000000, offset = 0.000000 2022-08-08 16:25:23.268: voice add: "effects\aircrafts\engines\su27frontengine2" started = 32.998000, offset = 0.000000, now = 33.019000 [...] 2022-08-08 16:25:59.670: COCKPIT_MAIN:su25inheambl: dt = 33.385750, offset = 33.385750 2022-08-08 16:25:59.670: woLA-16777472:su25aroundengine: dt = 32.791430, offset = 32.791430 2022-08-08 16:25:59.670: COCKPIT_SWITCHES:clickbuttonon: dt = 0.000000, offset = 0.000000 2022-08-08 16:25:59.670: voice add: "effects\aircrafts\cockpits\clickbuttonon_3" started = 69.398000, offset = 0.000000, now = 69.420000 2022-08-08 16:25:59.691: sound del: "effects\aircrafts\mirage-f1\cockpit\devices\right_main_panel_console\conv_center_switch" now = 69.442000, sched = 69.432874 2022-08-08 16:25:59.691: MeteoDispatcher/main:background: dt = 69.442000, offset = 69.442000 2022-08-08 16:25:59.691: MeteoDispatcher/main:field: dt = 68.943000, offset = 68.943000 2022-08-08 16:25:59.691: woLA-16777472:su25frontengine2: dt = 36.434430, offset = 36.434430 2022-08-08 16:25:59.691: COCKPIT_MAIN:su25inenginel: dt = 36.273750, offset = 36.273750 2022-08-08 16:25:59.691: woLA-16777472:su25frontengine: dt = 36.434430, offset = 36.434430 2022-08-08 16:25:59.691: woLA-16777472:su25backengine: dt = 36.509643, offset = 36.509643 2022-08-08 16:25:59.691: COCKPIT_MAIN:su25inheambl: dt = 33.407750, offset = 33.407750 2022-08-08 16:25:59.691: woLA-16777472:su25aroundengine: dt = 32.813430, offset = 32.813430 [schnapp] sound.log.zip

some early morning shots

Not at my PC at the moment, but just a thought. I have 5.1 surround sound option enabled. Will this affect sound output with different files?

Here my details of the sounds.edc folder, same for stable version. I guess, it will not help to delete / rename the folder and run a repair, cause other re-installed the module and this didn't change. Lets assume size of the correct and the faulty sounds is the same, is there a specific file, which we could check (version details or something like this)? As for the antivirus. I use windows defender and have a exception defined for DCS game folders and dcs saved games foldler since ages Edit: Renamed the original folder to "Sounds.edc_test" and than did a repair, autoupdater log attached. New folder "Sounds.edc" has been created but nothing changed regarding the details: autoupdate_log.txt

Just an update. Day position of the switch, lights bright: night position and dimmed: As you stated, only thing is the option to turn it, which could be removed. But don't know, maybe that's the same on the real plane, cause they used the same type of lamp with dimmer, but connected them differently, so dimming is not on the lamp itself, but you can turn it

Hello @Flappie, I never heard the sound in your example. I started my OB installation after the first patch came out, so I directly went to that version plus the hotfix afterwards. As OB and stable are currently the same, sound is the same, but not the one in your F1 example. trk, logs and autoupdater logs attached, showing my installation history, hope this helps. F1_engine_sound_test_OB.trk F1_engine_sound_check_stable.trk dcs_stable.log dcs_OB.log autoupdate_log_stable.txt autoupdate_log_OB.txt autoupdate_log_old_OB.txt

Okay, low prio items, but should be noted. These are the details I like in the C-101, where the three marker indicator lights work this way.

now I got it, there's another button, in my picture right of the bottom of the 1 I inserted. Didn't realize this one, will try next time. Thanks. T button pushed, lights come on: So maybe the same as with the dimmer option on these lamps. Not a bug, or maybe only that they should not have the push-to-test option. Thanks

The point here is, you can turn them via mouse wheel which should increase / decrease intensity.

mmmhh... I can't get them to light up, whatever I press. Button 1 in picture below nothing illuminates. I guess this should test the autopilot lamps as it's labeled TEST PA. Button 2 in picture below illuminates warning caution advisory panel, fire detection and master warning/caution button.

Hello, for the Airbrake light the Push-to-Test function works. If light is off, you can depress the light with a left mouse click and it illuminates. This does not work for: nosewheel steering light combat flaps light Although, the push animation is visible, the light does not come on. DCS/2.7.16.28157 (x86_64; Windows NT 10.0.19044) APP: Application revision: 208157 APP: Renderer revision: 22994 APP: Terrain revision: 23392 APP: Build number: 145 Thanks Jens

Noticed this also. To sum up, this is for the following lights: Airbrake light Nose wheel steering light Combat flaps light jammer detection C+M or SW R light right