gulredrel

Hi @Vibora, new mission Nevada Nellis AFB. ME set to 16:30 (4:30PM). The clock in the F1CE cockpit shows 12:30 track attached, and screenshot here: 2023-07-09 11:36:53.590 INFO APP (Main): Command line: "E:\games\DCS_World_OpenBeta\bin-mt\DCS.exe" 2023-07-09 11:36:53.590 INFO APP (Main): DCS/2.8.6.41363 google states Las Vegas time: "Current Offset:UTC/GMT -7 hours" So even 12:30 AM would be wrong in the example above if the clock is showing UTC, this would be 11:30. But this may be something with daylight saving times and so on. Thanks Jens F1CE_Nellis_AFB_Nevada_clock_1230_vs_mission_1630LT.trk

I was in NTTR map last time. ME time set to 16:30. F1CE clock showed 12:30 at mission start. So NTTR Nevada being UTC-7 would be okay I guess. With military coordination based on UTC time all is okay. I would rather prefer local time, but you can set the clock, no problem.

Thanks for the improvements. Screenshots and videos look amazing. Also like to hear about frequency bug fixing, stumbled across Gazipasa VOR last time.

Training with SAMP-400HD RTB

Switching off the starter didn't work in our DCS Gazelle even with the old flight and engine model. As it represents the 342 with the different engine than the 341, so I guess, this is correct. PC said on their discord, the above mentioned behavior is known and will be fixed.

Hello, as @LordOrion reported in the thread below, I wanted to create a separate bug report. Steps to reproduce: create player flight with MB-339 create waypoints and name them, so they can be recognized in INS system, example DCS point 0 takeoff from ramp DCS point 1 - WP01 - turning point DCS point 2 - WP02- turning point DCS point 3 - WP03- turning point DCS point 4 - WP04- turning point DCS point 5 - WP05- turning point DCS point 6 - landing start flight and select FLT start with WP01 --> forward reaching WP01, RNAV will automatically switch to WP02... Expected: when reaching WP04, I would expect the INS/GPS switching to WP05 current result: when reaching WP04, the INS/GPS terminates flight plan navigation also reported here: Please also note RDU vs. CDU INS display status update while switching waypoints: Thanks Jens MB-339_WP_order_RNAV_last_ignored.trk

Also noticed this last waypoint not becoming steerpoint thing but didn't have the opportunity to create a .trk of it. The RDU vs. CDU waypoint update was reported here, at least I guess, that's the same you describe: Thanks Jens

Haven't checked in the mission editor. Some airfields on the newer maps have inclines. Maybe there is one point defined for the model to define the height of 0 ft above ground, but this than will not work for such inclines and three wheel contact points? Just speculating, I think especially with such lighting conditions, many planes are affected like this.

Just added an AI F-15E flight to my mission. After landing and disembarking the pilot's and WSO'S feet are below the airfield's surface. This was at Syria map Akrotiri airfield, if this matters. null

Hello, as the title states, there is an entry "Harrier" within planes encyclopedia. It shows <BAD UTF-8> description and missing textures. Current OB: DCS/2.8.6.41363 single and multithreading is the same. The AV-8B entry is correct: Thanks for checking Jens

Nice pictures, must have been a great event. Following 360° camera video was also linked on discord.

No luck so far Track attached, also on discord. Heavy g-spike, blackout, nose gear / hydraulic loss. Thanks anyway, hope the track will help to analyse. MB-339_RC1_taxi_test.trk

I checked this, as I also thought I may had accidentally moved the slider an my T.16000 base, but it was all the way up. So for me it currently looks as if the lamp is only dependent on amount of torque. As soon as I pulled on the collective, lamp went out.

Being light and flying with low power settings, the idle lamp illuminates...

digging up the screenshot thread

Hello, there's a power pole in the middle of the street. Please find coordinates in screenshot. DCS/2.8.6.41066 MT Thanks Jens

Hello, the tunnel exit at the following coordinates 34°40'08.9"N 32°49'40.3"E (real world) looks weird. DCS/2.8.6.41066 MT In game coordinates in screenshot. Thanks Jens

Exactly my thoughts. Would also think, the clutch engagement would occur with a bit higher than this idle rpm and than the needles should sync and you need to stabilize and only than one should advance throttle further. Thanks, also would love to hear from PC more about this. Maybe it needs a bit more tuning.

Thanks rudel, the same thing also crossed my mind some days ago. This threads can be merged, I guess. I also find the idle lamp strange. Do you also know under which circumstances the red bloc light should be illuminated?

Chuck's Guide is outdated with the latest great changes and improvements to the Gazelle. L now has the periscopic sight and can launch HOT missiles with it. We need to wait for an update of his guide.

Yeah, this would need some more implementation. So WSO could talk the AI wingman on to the target. I just wanted to prove that AI wingman is able to fire HOT3s. But this needs to be more detailed in mission. I also sent the wingman out on recon but it didn't find targets. Only after tasking to engage ground targets from less than 4 km away, this worked. But this was no threat training environment with non moving and non shooting M113 APCs.

Hello, as the title says, this looks weird. Pressing the Volt Meter Test Button also triggers lamp test button on warning lights panel. Please see video below. Checked with SA342L in OB MT DCS/2.8.6.41066. Thanks Jens

My L wingman fired with command to engage ground targets. Looking with the L's periscope and tasking him to engage my target didn't work. SA-342_wingman_HOT3_engage.trk

Works for me. Just added an AI Gazelle M with CAS task to my mission and set a waypoint with attack group. So in general it's working. Now it's up to you, how is your mission and your AI flight set up.

@Flappie mmmhh... it's the F-86, not F-5 It's "4.2.8. Trim tab take-off position indicator light" on page 87 and "Take-off trim position indicator light" on page 148 in the manual.