gulredrel

Thanks. Exactly what I was thinking. In most if the other jets you have the pinky finger switch on the stick to disable NWS at a certain speed or the Hornet with the paddle. In this I also disable NWS after touchdown on the field and only after having slowed down I enable NWS low gain again.

Thanks for backing up my theory here. Without feeling the starting movement this anticipation is almost impossible especially in chaning wind conditions. So I'll stick to the NWS kill switch when in heavier crosswinds. Just need a hotkey to enable the NWS again when slowing down.

Hello, I guess, it's mostly a thing of not feeling the plane and therefor overcorrecting in the sim. Having a crosswind during takeoff or landing, I tend to overcorrect with NWS even in low gain and get into oscillation. Tried with completely setting the NWS to off with the guarded switch and this is much more helpful as you gain speed fast enough to get rudder authority. I don't think that adding curves or something will help as these will made the rudder less predictable in other situations than takeoff / landing. What are your thoughts about? Thanks Jens

Last weeks changelog stated: "Fixed the initialization of the mechanical clock hours hand when the aircraft start time is more than 12:00 PM." @Vibora Just started a mission with OB 2.8.7.42718 MT (at least DCS log is showing this information, I also deleted fxo and metashaders after updating) and mission time is 19:00 in Caucasus and the clock shows 12:00. How can I confirm that I really have the latest files? Could run repair. Anyone else seeing weird results?

From the last patch notes: "The Optical Sight target symbol doesn’t disappear anymore when it is near its movement limits." Is this a change for the behavior described above? I'm on current OB and had the target square disappearing today.

507+ pages... awesome. Thanks for your dedication.

Thanks for the info. Waiting for the next one, I'm sure you will figure this out. Coming back from holidays in northern Spain, rainy forcast in Germany, so I guess, there will be some sim time within the next days

Thanks for updating the C-101 while working on the F1 variants. Open Beta 2.8.7.42583 C-101 Aviojet by AvioDev Fixed the initialization of the mechanical clock hours hand when the aircraft start time is more than 12:00 PM. Fixed clock hands animation: minutes and chronometer minutes hands were mixed up with each other.

DCS Open Beta 2.8.7.42583 changelog, looks like wheel chocks have been added for warbirds. Away from PC, so can't check my warbirds.

Thanks for tracing this one.

Thanks for trying. Will create a track, but this could take some time as my PC is several 100 km away for the next time At least I can say, it was cold and dark ramp start at Pinarbashi in northern Cyprus.

Hello, just flew the Huey after the latest updates. Needle split nice, thanks... I know there are some threads about engine, flight model and fuel consumption. But couldn't find something about the fuel pressure. At least all my searched for "fuel pressure" or "pressure" didn't resulted in something like the following. What caught my eye was the fuel pressure gauge. After switching on the fuel pump, the fuel pressure gauge goes all the way to 50 psi and stays there regardless of engine operation. As there's a green operating range marked on the gauge and the manual also states: "5 to 35 PSI normal." this should be a bug? Maybe it's related to the fuel consumption issue but just want to be sure this also gets some attention. Tested in version DCS/2.8.6.41363 MT Map was Syria at around 23°C I think, if this matters, haven't tried on different maps yet but should be easy to check. Just load on the ramp cold and dark and switch on fuel pump. Thanks Jens

Like that new shelter damage model:

I had this reported here a while ago but this has not yet been acknowledged. Nevertheless @fausete and Aerges are working on the INS overhaul and I hope this weird initialization behavior will also be included.

Just for all of us desktop aviation nerds I came accross this startup sequence: Regards Jens

No, totally new simple single player mission. ME, new mission - map Nevada - F1CE player aircraft ramp start cold and dark - select time in ME and fly. Nothing special. Edit: mmhh... tried the same in Kobuleti: and Akrotiri: ME time set to 16:30. The clock in cockpit always shows 12:30. Just speculating: The time the clock shows is UTC, but based on UTC+4 offset in Caucasus regardless of the map? So 16:30 Kobuleti local time translates to 12:30 PM UTC? I'm sure you will find the answer in the code F1CE_Akrotiri_Syria_clock_1230_vs_mission_1630LT.trk F1CE_Kobuleti_Caucasus_clock_1230_vs_mission_1630LT.trk

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