FoxTwo

It's very likely that I'm just imagining this... but I figured I'd ask. Just taxiing around on the super carrier today there's no momentum on the deck if you cut the throttle and it takes a lot of throttle to get moving. I don't remember it being like this yesterday but I could easily be making this up in my head. Weird, tried another mission and it was fine, this only happened in one of the Raven One missions. It was definitely not right but who knows why.

There's a bug where the light only works if you cold start, if you hot start it doesn't.

They're both nice and you can't go wrong with either, pick which ever one fits into your existing setup better. Frankly the differences between them aren't significant enough to make one better than the other except for personal preference.

Disable your antivirus long enough to install the app.

I'd say keep it ladder just maybe add mission notes somewhere and/or add it to the Glossary in the guide (Joker is in there). It just wasn't documented and I couldn't find anything online when googling for it aside from the normal airforce brevity code. Thanks!

Hence my confusion because it's referring to fuel state.

ladder is... presumably bingo? It shows up in a comm event in mission 2 ("Use F-10 radio menu to reply to STRIKE (low or ladder)") and again shows up in the mission 7 briefing and I'm not familiar with the term. It seems to mean something else in brevity so I'm trying to make sure I know exactly what we're talking about here. Thanks

This is after a 90 minute mission in the gulf where I just orbited a tanker for about 20 minutes, I don't think I pulled more than 6g the entire mission. I can't imagine this is even remotely normal behavior otherwise why even have the damn thing in the cockpit?

Yes no stuttering since lowering pre-load radius from 150,000 to 112,500 (approx 75%).

It's interesting because it seems to be highly dependent on lighting and shadows. Spotting can be inconsistent based on conditions. If I'm behind a tanker for instance and the shadows are on the side facing towards me, I can see a pixel at 30nm at altitude, but if the shadows are cast on the other side it's going to be more like 15nm or less. Things can disappear when zooming in as well. But it is better than it was a lot of the time.

That... yeah. Stumbled across that by just flipping switches yesterday and that did it. Jeez what a mess.

I do have to say any DCS bugs or problems aside this campaign is amazing, and an incredible value for $14 USD. It should probably be a lot more, the dollar/hour entertainment ratio is off the charts.

Not on the ground or the carrier, but in air while flying. I've seen AI wingmen slide/rubber band around along the X axis and nearly fly into me while flying formation. I've seen tankers do the same thing when trying to AAR. This happens both in multiplayer AND single player. They don't seem to be losing or gaining much altitude but they will slide almost half a mile and then slingshot back in a second... I even had the wake turbulence of them crossing in front of me and back so it's not just a visual glitch.

Happened again, same mission. This time it was SUPER windy at 20k the velocity vector was all over the place. I didn't have any problems hooking up but the AI sure did. May want to... I don't know, maybe a way around this script wise? I've only had the AI have success one out of three tries so far (I had to replay the mission after quitting the game instead of the mission last time).

AV8B has a light too. F-18 and F-14 don't, not sure about the M-2000. The tankers do call out 'contact' when you're connected however, not sure if comm events are exported?

I take it back. I thought it was the GPU overclock I had applied but it's not. After setting the GPU at default, it's still doing it. I don't know if it's AI scripting or what but the game is stuttering MASSIVELY in VR. You can see it in fpsVR frametimes, you can see it in steamVR frametimes, you can see it in MSI afterburner GPU usage. It's constant in both multiplayer and singleplayer. It's incredibly frustrating, and after tearing my computer apart logically and physically I can only conclude that it's a DCS engine problem.

Didn't see an answer yet, but I'm assuming there's no event for AAR probe connection to export to simshaker?

Think I'm running into a DCS bug here... Post waypoint 3 in mission 2, was in formation with my wingman for 10 minutes after I'd finished refueling before I just quit the mission. Got some great screenshots though.

Patch notes come out several hours before the patch goes live, just give it a bit.

No.

Kobu's ils radio is... Buggy? Try Kutasi instead.

I took a look at the flight manual and it didn't specifically mention anything about cat iii requiring ab. Instant action behaved the same, it happens in any mission with cat 3 selected. Actual stores config does not seem to make a difference, it only happens when the switch is in cat 3. Taking off with the same weight/stores config and the switch in cat 1 doesn't pitch down even if you put the gear up as soon as they lift off the tarmac. Like I said it should probably be pitching down but it should probably also be doing so regardless of the cat switch position.

~11 degrees. Again I think the problem here is the inconsistency. Either it should do it or it shouldn't but it should do it regardless of where the switch is. AOA limits of Cat III wouldn't even let me pull extreme angles, this isn't that, this is letting you pull an angle, then you put the gear up and the aircraft noses down. If this should happen (and it probably should) then it should happen in either Cat I or Cat III.

Those are 3d printed hobbiest homebrew solutions. Nice but not what I'm talking about. A mass produced UFC with the fit/finish and feel similar to the throttle flight control panel would be nice.