eighteen

I am a big fan of flying alongside friends in the Chinook and providing navigation aid, however, ACPs and FPPs are currently synchronised between players. This requires me to either manually take control and fly to my own designated route, or relay the coordinates to the pilot or vice versa to enter in on their side. I know CDU improvements are currently planned, but it would be really nice to see some love in this area for especially it being the most crucial part of multicrew - having someone who can help you fly to where you need to go Please, ED!

I'm a large proponent of there being an option in the special settings to disable this for VR players, this has admittedly driven me... a little crazy myself. I believe this visual feature is great for those who wish to use it for cinematic or aesthetic appeal, but otherwise becomes a visual obstruction, especially once you're leaning forward and to the rear to assess something for the sake of situational awareness.

Shoutout to the approximate 500 sq. mi. of Chinese territory that made it in! Although I have my doubts, I wouldn't complain if ED gave us a tiny bit of scenery for this area. (Maybe Kashgar Prefecture if we get lucky)

Check your in-game distance setting. (Not to be confused with preload radius)

I'd like to see the text as described in the post title, (or similar) for switches and dials that are not functional to be added for both crew stations. This would be incredibly useful for me in VR when I want to see if something has or hasn't left "N/I status" without needing to resort to the EA guide, where I admittedly find myself looking for these answers. This is something I've noticed that Heatblur does in their F-14 module, and is my rationale for proposing. It's just a nice-to-have quality thing in my opinion, and is not necessarily a "new feature." This would only apply to the tool-tip shown with cockpit pointer elements.

6,562 ft. roughly approximates to 2,000 m. The F/A-18C uses meters as its unit for elevation The route tool does not infer from terrain elevation data. It isn't ideal in the case of UX, but all route presets are saved within your Saved Games path and Config folder. Presets are saved per terrain/map and is an idiomatic Lua table with fields omitted when left blank: presets = { ["4YA FARP LONDON"] = { [1] = { ["alt"] = 2000, ["type"] = "Turning Point", ["ETA"] = 900, ["ETA_locked"] = true, ["y"] = 69738.40625, ["x"] = 189386.109375, ["name"] = "RIVER", ["action"] = "Turning Point", ["alt_type"] = "BARO", ["speed_locked"] = false, }, -- end of [1] [2] = { ["alt"] = 2000, ["type"] = "Turning Point", ["ETA"] = 1075.9200317096, ["ETA_locked"] = true, ["y"] = 76952.6484375, ["x"] = 179263.359375, ["name"] = "IP", ["action"] = "Turning Point", ["alt_type"] = "BARO", ["speed_locked"] = false, }, -- end of [2] }, -- end of ["4YA FARP LONDON"] } -- end of presets You can share either the preset definitions (e.g. ["PRESET NAME"] or etc.) or the whole file, whichever is most convenient for you.