gulredrel

Happy anniversary and thanks for that time... I'm missing the two bridges north of Sevastopol from Lock-On: Flaming Cliffs, if the file image details are correct, these screenshots are from 2006:

Do you mean the large movement on your desktop throttle? You can adjust the AB detent position in plane's special options menu. I think, I've mine set to 90%. Once you hear the click in the cockpit from the detent, it's like AB on or off. No modulation.

This will be detected as a DOS attack, don't bring disturb them that way from bringing us the news.

As said above, if you are flying SP and using self created mission, just set wind speed at groundlevel to 0 m/s and you will not have any issue while taxiing.

Following settings worked to fire rockets single from outer wing pods with the press pf the "fire weapons" button which I have on my stick:

I imagine the missions are based on the same template. So it will appear everywhere. Maybe it is something with initialization for the training mission that is hidden in the mission file and can't be seen by just opening the mission in ME. Anyway, IFE will figure it out.

Started the cold start training mission myself. I've no idea, where the morse code is coming from. It's constantly morsing _ . _ . which should be just a C(?). Had a look at the training mission in ME but there's no corresponding sound file which is looped causing this. There's also some radio static noise in the background even with everything switched off. Maybe @6S.Duke could have a look at this.

On the audio panel there should be a knob for TACAN and another for ILS/VOR audio volume. Either tune it down to min or disable the tone by pushing or pulling the knob (can't remember which position is on/off).

Okay, the light should only be an advisory light, no button. So the text is maybe just wrong in the tutorial. Regarding the rockets, never had problems firing them. Salvo takes quite long if selected, but single fire worked. Will try and take a screenshot of weapons panel and keybinds.

You may want to go through different other bug postings (radio...) and the known issues list (brake axis indicator, missing keybinds). Especially the taxi bug is known and regarding the devs notes it will be fixed in an upcoming update. Currently you can get around when setting no wind in ME if you are in single player. Canopy needs to be unlocked, there is a safety catch to prevent the canopy from shutting inadvertently. NWS button on the stick is normal in a number of planes; there can't be a usable click spot at the front of the stick. This is all described in the manual. Landing speeds greatly are influenced by gross weight. So just fly AoA and observe sink rate regardless of speed (AoA indicator also known bug isn't quite right). We are waiting for news from the devs which are said to arrive at the end of August.

Derailing the Mav thread but yes, to fire the gun at least 70% rpm is required down low as the mechanism uses bleed air from the compressor section. At higher altitude rpm must even be higher.

Do you mean IR Mavs do not launch, even if crosshairs are collapsed and locked to the target? I also have this happen lately and don't know why. Sometimes re-cage, un-cage SSS FW, slew and TDC depress to lock the same target again works and I'm able to fire. Don't know if it has something to do with launch constraints regarding direction and the position of the seeker looking? But I'm no where near gimbal and pressing the pickle button will only play the beep (Tone selected with the OSB button) but the missile will not come off the rail.

Haven't checked enough yet, but setting the default gain higher so that it works for DMT or TPOD, it's too much for the EHSD. This it at least my feeling being on 2D flat screen.

Don't know. It disappeared at the top of the HUD glass for me. To the right it was visible at the edge. As it was described above and hopefully I understood it right, it will only disappear at the bottom of the glass. and here, with the plane even visible as a small pixel, the square went away at the top. Didn't caught the screenshot, when the orange square was halfway visible.

Not being able to close the menu wrecked a laser Mav today cause I told JTAC to stop lasing instead of changing views with one of the Fn keys...

On startup, yes, I know this has been changed from initial release. Thanks for checking.

Here you go: And now back to guide related topics. I know, F1 has a braking chute, but what's the reason to not use the airbrakes after touchdown?! Or even approach to keep up the engine rpm and just retract them for go-around and have the engine at a higher rpm?

Hello, as mentioned in Chuck's Guide for the F1 thread, I wanted to start a clarification thread regarding JPT of the F1: The official manual in the aircraft folder doesn't show any numbers regarding max., max. continuous or other normal / abnormal values. Chuck's Guide has this values: JPT (Jet Pipe Temperature) Limits In Idle, Military and Afterburner power settings - 740 - 755 deg C Maximum when on ground - 760 deg C Maximum when in flight - 735 deg C in overspeed Here my findings with screenshots coming from the track attached, runway hot takeoff 15°C OAT, standard pressure setting, so JPT regulator should have been in auto mode. Don't have a track but last week I had a flight with the regulator switch in different positions, there was no difference. Looks like any MIL power value in different flight altitudes is above the limits described above. As damage from too long compressor stall conditions is simulated, are there also problems from overtemp conditions? Can you please clarify the values with no AB but near MIL power? Short spikes from AB ignition is normal I guess, so behavior with AB running looks okay. 14000ft AB 760°C --> ok 17000ft 8300rpm 790°C --> needs to be checked? 17000ft MIL 8400rpm 820°C --> needs to be checked 17400ft AB ignition 850°C, short temp spike 16300ft AB stabilized 770°C 28000ft AB ignition spike 880°C 28400ft AB normal 760°C 30400ft AB 8900rpm overspeed normal 725°C okay 30700ft MIL after reducing speed to below M1.4 820°C Thanks Jens F1CE_JPT_mil_and_burner_and_overspeed_DCS_2.8.8_OB.trk

Yeah, F-104 official module. Thanks Aerges, looking forward to it. Also great to hear about upcoming F1 updates.

Okay, thanks. So my seen 810°C lasted way longer than 30 sec in MIL. If time permits, I'll try to replicate and take a track and some screenshots and post a thread. This will be better for @fausete to have a look.

a little taxi incident... waiting for clearance

Hello, looks like the stopwatch in the lower part of the clock started with the right knob only has running seconds. The minute hand stays at it's position and won't move. The upper timer is working showing elapsed time in minutes and hours when started with the left knob. Started both inner timers and lower showing 5 seconds: 5 min later, but showing only seconds and no minutes on the lower chronometer: Another 26 min later after using time accelaration: Track file attached which was created in current MT 2.8.8 OB. Thanks Jens Yak_stopwatch_DCS_2.8.8_OB.trk

Digging up that threat. Just did a short flight with the 2.8.8 OB and the changed oil cooling behavior. This is much more reasonable now. With an OAT of around 18°C I was able to do warmup, runup, takeoff and cruise flight without the oil temp going boiling. Could almost fully close the oil cooler door with 64% rpm and I was able to mange the oil temp at around 240 km/h with no problem to stay in the green. Thanks @BIGNEWY and @NineLine for not forgetting the Yak.

Don't know the exact type of the clock, but I assume it will run more than a day. I've a soviet AYC-1 on my desk and when fully wound up it will run for more than 48 hours.