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

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

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?

@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

"Fire Birds" moment during early morning on Grayflag Syria

Greetings, In the current Open Beta 2.9.0.47168 (Multithread) the AG VIS mode is doing strange things with waypoints. Encountered this in a MP session and was able to replicate in SP. It seems that a VIS designation/undesignation visually "shifts" existing WP symbology? SP track file: OB 2.9.0.47168 MT - viper funky ag vis behaviour.trk Three waypoints: 1 - Just a WP for offset heading at air start 2 - Kobuleti Cross 3 - Kobuleti Airfield I do a VIS ground designation and undesignation on the nearby lake and that seemingly shifts the waypoint symbology around. The Kobuleti Cross and Airfield WPs are no longer where they should be. The coordinates of the WPs didn't change though (IIRC) but are nonetheless not in the correct position on the HUD/HMD. PRE mode points the TGP on the correct position though (Cross and Airfield) At the end of the track even NAV mode inherits the "new" waypoint positions Video of track file: 01:38 - Undesignating the VIS ground target and waypoint symbology shifts 04:00 - NAV mode inherits the shifted waypoint symbology

Is it this behaviour? I was already wondering why the TWS went a bit funky

@razo+r I concur with your result and thanks for the insight! During testing my past self flew too high and slow and I have no idea why caveman-me tested at 1k feet... because i always flew low and fast in the past Was just back from re-testing when you posted your reply The CCIP solution caught on just below 700 feet

I am aware of the wind affecting the pipper. Pre-2.9 I could use the Snake Eyes in high drag mode without any issue with CCIP. Now I am getting no usable drop solution. [edit] Also referring to the official training mission (how I used Snake Eyes in the past with CCIP):

[edit] SOLVED: go low (below 700ish feet) and fast instead of high and slow ---------- Greetings, CCIP seems to work with regular Mk82 bombs but not with Snake Eyes Track: patch 2.9 - mk82 snake eye ccip not working.trk Mission file: CCIP Test Hornet.miz Air start close to Kobuleti Cross. Three Hornet slots with different loadouts: only Mk82, only Mk82 Snake Eye and mix of both. Track recorded with mixed loadout aiming for the center where the two runways meet. No probs with Mk 82: And whatever this is with the Snake Eyes

Concerning daylight operations, a former Growler pilot gave me this answer on his YT channel: Taken from my post on June 30 in this thread:

Sunset launches on Grayflag Marianas

Spangdahlem Viper delivering badaboom on Grayflag Marianas

(Please correct me if I am wrong!) To sum up the infos I could gather, these should be the necessary conditions to prevent HOME from being stuck/crossed out: - Speed below Mach 0.9 - Set HOME to a valid waypoint - No afterburner (no factor) - NAV master mode (no factor) Notes: - "Valid waypoint" means a "prepared" waypoint, either entered manually or set up in mission editor. (e.g. an "untouched" waypoint 55 is not valid and HOME gets stuck) - Default HOME waypoint is 0 - Calculation of home fuel starts 5 seconds after selecting the HOME waypoint on FPAS page - The HOME FUEL warning is the plane telling you that you will have less than 2000 lbs of fuel left at that designated HOME waypoint - Entering bogus "N 0 E 0" coordinates makes the waypoint valid but the calculation to "Null Island" in the Gulf of Guinea near the coast of West Africa will trigger HOME FUEL warning So you got HOME stuck on an invalid waypoint and want it to be available again? -> Check the "stuck" HOME waypoint number on the FPAS page and manually enter coordinates for that waypoint via HSI->DATA->WYPT tab to enable HOME computation again (best case would be a location where you think you will be landing) Or do you just want to shut up the annoying HOME FUEL warning and don't care that the button is stuck? -> Select a likely "untouched" waypoint like 58, 57 or 56 etc Note: waypoint 59 is automatically populated with the mission's bullseye coordinates and enables HOME FUEL calculation

Runway marker line doing extradimensional stuff Open Beta 2.8.8.43704