boerdi

Grayflag Sinai - GDI vs NOD

Current OB 2.9.2.49629 (MT) Tested just now with TrackIR in the Hornet, Viper, Apache, Huey and Hercules (Mod) Paused TrackIR before entering mission or server, adjusted my view with the "Zoom In" and "Cockpit Camera ..." functions and saved with "Save Cockpit Angles". When entering SP missions or a MP server (or reslotting on server) the saved initial view is displayed correctly again! For me it's working again like in the past

Grayflag Sinai - GDI vs NOD Livery by Macintyre aka "Flash 4-3 | Macbar"

Dawn Patrol RTB

In pre-2.9 times the TACAN position was usually not a problem Instances where I had to "reset" the system were rare and now I have to double-check on every approach

OB 2.9.0.47168 (MT) supercarrier issue in MP: Anyone else who needs to "restart" TACAN on the Hornet to fix wrong carrier position? Activated TACAN 70ish miles in transit to the Teddybear, got a mostly correct position but when closing in I have to reset TACAN to get correct position update (c.f. video) Was not able to replicate it in SP but the problem pops up regularly in MP

Do you have extra (non-Windows) software that manages power plans? Or maybe Windows Update decided to overwrite the edit Since I applied the "show-me-the-extra-power-plan-settings" registry edit on 30 October everything works butter smooth and Windows kept the registry edit intact even after doing the latest 23H2 update. The only issues I currently encounter are the performance challenges imposed by OB 2.9.0.47168 on MP servers (server load, lag/desyncs etc)

Hi, This behaviour has been explained in another thread Source:

[System context: Win11 + 12900K + non-VR] Result after a couple of days of stress testing on busy MP servers with unparked E+P cores: zero freezes or stutters Using @QuiGon's method to show additional properties in the power plan menu Details: OB 2.9.0.47168 (MT) (current version at time of posting) Single 1440p screen (no VR) Windows 11 (22H2 - Build 22621.2506 - up to date at moment of testing) i9-12900K Drivers up to date (video, audio, system etc) BIOS up to date Hyper-Threading active 100% unparked E and P cores [registry key values: "dec35c318583" (E-cores) and "dec35c318584" (P-cores)] Power plan: "Balanced" (no need for CPU running at max frequency during idle state) Power plan settings: [edit] (Update: 9 November) Still zero stutters and freezes The only issues I currently encounter are related to the OB 2.9.0.47168 performance challenges imposed on MP servers (server load, lags/desync...)

Over those 2+ hours I switched roles with George here and there with George most of the time in the gunner role. George was alive and when I was in the pilot seat he reacted to all commands (e.g. weapon switch) except for the "short up" search command. The last event before George stopped responding (and the "ghost" inputs popping up) was rearming/refueling at a FARP. I double checked the keybinds and on the CP/G profile the MPD buttons/axis categories definitely were completely unbound for all devices. Will keep an eye out if it happens again

Greetings, This happened during a long MP session. I was over 2 hours in, still same aircraft after 2-3 rearms and George has performed quite nicely so far (as pilot and gunner). I have a track file but as it's from a MP session it's very long and over 300 MB... George as gunner suddenly stopped looking for targets when tasked to do so. Hopping into the gunner seat I tried cycling the weapons, master arm on/off etc.. Same in the pilot position via the AI menu. Nothing helped to make George scan for targets again. When I switched to gunner seat I saw that the left MPD WPN button would be mashed when I switched menus (c.f. video) I checked controls to see if there may be a funky keybind but that button wasn't assigned to anything for the gunner role. Did the AI get "stuck" at some point? And does ghost inputs on gunner screens even though the player switched to the gunner seat?

Thank you for the clarifying informations! Got a slightly better understanding of the dynamics of Windows power plans and cores now. Commencing stress test of the new settings --------------------------------- To sum up my system + settings: Windows 11 i9-12900K Power plan: balanced Unparked E and P cores via QuiGon's method Registry keys: "dec35c318583" (E-cores) and "dec35c318584" (P-cores)

@Lord Vader Thank you! The offset resets indeed nicely but it is still strange to see the waypoints shift like that Gotta need some time to wrap my head around it And I tried to visualize your explanation in the video below Same mission with waypoints over Kobuleti Cross and Kobuleti Airfield resetting as intended when in PRE mode

Bug still present with current OB 2.9.0.47168

Did you mean to type "[...] edit the key dec35c318584 [...]"? Apologies for the double post! [edit 1] Will test now with the unhidden option referenced by you Which makes me feel better! Less registry butchering [edit 2] How about unhiding both types of cores and unparking all via power options? Keys: dec35c318583 (e-cores) dec35c318584 (p-cores) And I prefer the balanced power plan since I don't need Windows to idle at 4+ Ghz [edit 3] (Update: 9 November) Results since applying this method: Zero stutters and freezes (Win11 + 12900K + regular 2D on single screen) -> More details in this post The only issues I currently encounter are related to the OB 2.9.0.47168 performance challenges imposed on MP servers