DreamingInfraviolet

Unfortunately all of the affected tracks crash DCS for me on replay. But if I find a good track I'll upload it!

Environment: Multiplayer server with medium amount of players, multicrew with human WSO, single threaded DCS build. Problem: It seems like multiplayer lag spikes make the plane think that it pulled a lot of Gs, and break the INS system. Had a cold start, took off (no issues or aggressive maneuvers, it was a very smooth takeoff), got a ~1-2s lag spike (likely unrelated to F4). After the lag spike, the G-force indicator suddenly showed that I pulled a max of 10G, and INS stopped functioning. This happened multiple times throughout different game sessions, and has never been an issue with other planes. (Always with human WSO, haven't flown much with Jester, so not sure if that's relevant).

Hello! So one of the major issues with aircraft start-up in DCS for me is that there's absolutely no point doing most of the startup checklist items, or doing the startup checks. You know for a fact what position each switch will be in, and that there will not be any failed systems. This means that the startup procedure usually consists of just doing the absolute most basic startup flow of igniting the engines and leaving. Feature Request Provide an option to: Have a non-zero chance to have switches in their non-default positions. This will actually give players a reason to go over the startup checklist, and make startup way more interesting instead of just flipping the ignition switch. Maybe provide a non-zero chance of random systems being broken or degraded on startup. e.g. the pitot heat might be broken, and automatically fixed on doing the pitot ground check. I understand that this might need some work (e.g. voice lines for when a fault is found) so this might not be as viable as just random switch positions. I understand that not everyone will be interested in these options, but for some of us it will give us a reason to understand the plane systems more, and make the experience way more realistic and interesting. Aircraft have checklists, ground checks, and many redundant systems for a reason, but most aircraft in DCS provide absolutely no reason to use any of it. So would be really cool if F4 provided at least some switch randomisation to make it way more interesting :)

Hi! I ran into an INS issue with the F16. Start mission with GPS available Start at Las Vegas airport coordinates N36°12 W115°11 Take off, turn off engines around N 36°07 W115°09 in mid-air Land at N36°14 W115°01 Cycle power, restart engine Aircraft displays coordinates in INS DED page: N36°07 W115°09, which are the wrong coordinates. Expected coordinates are N36°14 W115°01. Attempting to change them doesn't work Do full INS alignment. HSD coordinates still incorrect FIX page shows "SYS ACCUR HIGH, GPS ACCUR HIGH" despite INS coordinates being wrong. Performing an overfly FIX does nothing Turn off GPS. Overfly Fix finally works So it seems like after losing power and landing, the GPS coordinates are stuck to the values when the plane lost power mid-air, instead of correctly updating. This seems like a bug? Turning off GPS and doing a manual FIX seems to be the only way to solve this. f16ins.trk

(Mission 2) Bank Angle PSA: Don't use the standby attitude indicator to determine the bank angle! That has a parallax effect so it gives you the wrong reading unless you contort your head to be right in front of it. Instead use the screen in the front, the dark notches at the bottom tell you the bank angle. Really cool campaign so far

I had the same issue, installing Marianas fixed it!

Literally just ran into this too! Got hit by a missile and could still fly like this for a while.

Hi! This one is pretty simple: KU Key - BKS is bound to a key on my physical keyboard. This used to work fine to erase a character when typing in coordinates. It no longer does anything since the last update. I have to press "BKS" using my mouse in the virtual cockpit, or use KU Key - CLR but that clears the entire input. Could the keybinding be fixed?