Eagle7907

Not sure why, but the lastest update removed the newest training mission created on 2/27/2019. FYI. Addendum: it didn’t delete them, I guess the lua file got edited or it’s an older lua that was sent in the update. Sent from my iPhone using Tapatalk Pro

Anti-skid proper behaviour? Like what raelias said, fuel flow, even the engines spooled a bit higher than usual when on the ground. There isn’t really a physical throttle position for flight idle and ground idle. It will be the same. The different idling power is determined by if the jet knows it is on the ground or not, then the engines will utilize the proper idle rpm. That’s what I was saying is sometimes the jet won’t go into ground idle immediately at touchdown. Just be aware, and if you think it isn’t, just nudge the throttles up a bit then back to idle to get them to ground idle. On a different note, I’m surprised that the engine anti-ice being left on doesn’t affect the idle speeds. Hmmm.... Sent from my iPhone using Tapatalk Pro

Noticed with the latest implementation of D/L, MIDS, and IFF, these BITs are not clearing or showing GO status. Is this intentional? Addendum: Yes, they are turned ON, on the UFC. Sent from my iPhone using Tapatalk Pro

I've noticed this too. Here's a track. From the Navigation Field Takeoff mission in Caucasus Map. I takeoff and notice winds are a direct headwind. Turn right, jet rolls left into wind. Turn left, jet rolls right into wind. Fly again directly into wind, she stays steady. I added stores just to see if it had any bigger effect. https://www.dropbox.com/s/ahzaf8n59lb2s81/rollwind.trk?dl=0http://

Ah! Thank you Tholozor. So this could be the problem? Just something to pay attention to when you use up lots of runway to stop. Sent from my iPhone using Tapatalk Pro

Again I’m not sure, but I’ve noticed this happens mainly if you flare the landing. I haven’t fully tested this because I read where Mover or Lex stayed that if you flare a switch won’t fully compress. Not sure if it’s related? Anyways, just a thought from the notion about landing roll. Sent from my iPhone using Tapatalk Pro

Hey fellas, Not sure if this is correct or not but you may want to check to see if your engines go to ground idle. I’ve noticed multiple times that they don’t after landing and hinders your braking efforts. To check I always quickly come up off idle then back to make sure the engines are spoiled back. Sent from my iPhone using Tapatalk Pro

Much yes!!!! Please! This is the most annoyance of Tarawa. Sent from my iPhone using Tapatalk Pro

Haha. That makes sense. I didn’t realize it wasn’t coded yet. Much appreciated. Sent from my iPhone using Tapatalk Pro

Any word about if this will get fixed for the landing function? I think it’s called powered assist mode? Sent from my iPad using Tapatalk Pro

Not by design. Just because stuff isn’t complete in the sim. In time the BITs will slowly be resolved. Sent from my iPhone using Tapatalk Pro

What are these on the stores page? I read somewhere S Mode has to do with the IFF/datalink. I remember seeing that in a thread Wags responded to. PS I can’t wait for datalink. This implementation will complete majority of the BITs on the BIT page. Sent from my iPhone using Tapatalk Pro

I’ve noticed this too. Matter of fact it should be doing the opposite. NATOPS says to guard the stick and expect to arrest the tendency of over rotation. Not under. Sent from my iPhone using Tapatalk Pro

That gauge is actually incorrectly implemented in the sim. It has been discussed in the bugs section. That would probably alleviate most of your confusion. Sent from my iPad using Tapatalk Pro

Same, you have to TDC down to lock. Otherwise it works great. I like it. It doesn’t wander off for a second while searching for target. You can easily fire +1 in one pass. Sent from my iPad using Tapatalk Pro

I understand. I didn’t notice anyone saying anything or acknowledge that it was incorrect. Just wanted it on the record and it’s to be fixed. Thanks! Sent from my iPad using Tapatalk Pro

NRAS and PC ODU options not working? That still surprises you? ;) Sent from my iPhone using Tapatalk Pro

Not sure if this has been brought up, but the explosion sound for the rockeyes seem undone or incomplete. When viewing from an F7 view of a target, it makes a small 'splash' or 'hiss' sound. Sort of like a drop of water turning into steam. Nothing like multiple bomblets exploding. Like so:

[FIXED INTERNALLY] Antenna elevation freeze and B-scan offset center I’ve made a report post about this recently. Problem is I can’t get it to replicate on a short track. It only happened when doing a long track which is pointless because it will have other inconsistencies and send them down a rabbit hole. Sent from my iPhone using Tapatalk Pro

If that’s the case guys, just input 6 until it gets fixed. Who knows how long that will take? Sent from my iPhone using Tapatalk Pro

Okay. Would the mission file help? Sent from my iPad using Tapatalk Pro

HARM/track recording Deleted for quoting. Sent from my iPad using Tapatalk Pro

I am using OB with the latest patch. With all due respect, a short track isn’t going to solve the problem here. Clearly all the bugs I have been experiencing are due to longer play times. I’ve been trying every time to replicate a bug using the short method and can’t get it to show its ugly head. If you examine my posts here, the majority is due to long mission times. The question is how can this be fixed when the reporting method is flawed for such a bug? I’m sorry to make this sound negative, but my frustration is reaching limits. Sent from my iPad using Tapatalk Pro

This is tied to my previous bug post. For some reason the tracks are not recording some items like wind and more importantly player actions. In this track I attacked several SAMs and AAA as well as wingman. Then engaged mig23s. Radar went screwy and now I can't show ED the radar bug because the track file didn't correctly record the SAM engagement. Track shows I just blindly targeted a friendly radar station behind me while flying directly toward an enemy SA6. THAT'S NOT WHAT HAPPENED. Track recording should be +1hr long. Track file location. https://www.dropbox.com/s/oxosfag2jnx7q0e/radarsweep.trk?dl=0

[NEED TRACK] Radar scan, b-sweep I checked that. I went through all the azimuth settings and same result, the last quarter or eighth was cut off. Sent from my iPhone using Tapatalk Pro