Echonomix

I can confirm this happening too. I was trying a fast mission with one wingman, both of us starting on the runway ready to go. The first odd thing was that my plane was running but it seemed like the AI wingman plane was not running, yet when i throttled up enough to get my plane moving, he went on to appear to take off (and the plane appeared to be running...maybe just a graphical bug?). Except he never leaves the ground. The AI wingman just drives right down the runway heading at around 125 speed (dunno if that is knots, mph, or). Usually his plane explodes when it hits a building, but last night it just kept going. It would follow hills, both up and down, like it was on a track (following runway heading). Maybe the path never took it through any buildings this time, but by the time i had landed about 15 minutes later, i F2'd to his plane and he was still just driving his plane across the land like a truck :doh: I thought at first it might have been caused by weight, so i lowered fuel load to keep the weight to about 90% mtow. That didnt seem to matter though. Both planes were loaded with 10 rockets and max guns. Running version 1.2.0

Great Job ED! I installed the patch and forgot to restart before trying it out. I flew the ramp free flight mission and the only thing I noticed was right at the beginning. I kept getting master caution on/off. Was that a bug before this patch? If it is, will it go away after a reboot or did I mess it up good? FYI: the alarm stopped after some oil pressure came up during the engine start. What is the reason for needing a restart and why didn't the patcher request it? Otherwise, looks and run really great!

Do you have the complete beta 4 installer or are you applying all the patches? When exactly does that error occur? What video card do you have and what driver version? You may also need to update direct x.

Yeah. Radio them and say "this is a stick up!!!" or maybe better yet, "too close for missiles, switching to guns" I do need to start practice refueling. :noexpression:

I have not watched it all yet. This isn't a problem with your video, more a question/observation to ED, shouldn't the wingman be calling rifle when he launches those agm 65's? (around 3 minute mark in the video)

winner! :thumbup:

If you weren't using the track clip pro before on the TIR 4, then your results can't completely be valid. However, from a technical specs view, the TIR 5 should be better. I have TIR 4 with the LED clip (track pro clip) and still have quite a bit of jitter. My friend broke his TIR 4 and recently got a TIR 5. The 5 does seem to be somewhat smoother, but there was still noticeable jitter on the 5. With the right software settings though, I think you can get them both smoothed out enough. I think they finally released the 64 bit version? I have not tried that yet, hopefully it smooths things out too.

I zoom in during startup to see all the instruments clearly. Once the engines and systems are up, I hit '5' followed by 'enter' on the keypad. That resets the view and zoom to default. Then I zoom in just enough to see the hud a little better...maybe one or two quick taps on '*" and I don't touch the zoom again unless I need to do some more adjustments to some stuff inside the cockpit. Now just to be clear, using track ir and leaning forward is fine, because that isn't zooming. But IRL, they use the targeting pod and set it up before an attack. They also attack only if a wingman or some other spotter can quickly check their hits and to look for possible aaa or sam launch. And of course binocs at safe distance. Read the book by William Smallwood if you really want more info. Good luck using binocs in dark, while flying low, looking for sam sites. Those guys didn't have the targeting pod back then. They used the mav seeker for a very narrow view and their eyes/binoculars.

Just look out the window. Those real pilots are always looking around "outside the cockpit" more than inside most of the time. It would be kinda handy if there was a dial or something inside the cockpit though. If you have the hotas, the switch will stay in the 'close/retract' position all the time. So if you aren't sure and don't want to or can't look to see. I just make sure the switch is closed or in the 'hold' position. It won't stay in the open/deploy position without holding it there. I also time how long it takes to deploy the brake during start up and when I need to deploy brakes in flight I count how much speed brake I want in seconds (1/2= this much, 1 sec = this much, etc). But usually those guys are looking outside the windows for stuff like that. Look on youtube for in-cockpit videos of pilots at airshows. In 60 seconds, they might look at their instruments 10 seconds of that time. Mostly to check speed and altitude before doing and maybe quickly during a maneuver.

That seems like a lot to pay to get a beta manual, or any manual printed, imo.

I just ran into this myself. I was making a mission with every plane on the US side. I also jacked up every graphical setting to the max. And all I get after mission load is a solid green screen. Sim still runs, I can f2 thru all the planes and hear them, but can't see em. Could this be what happens when a graphics card gets to much to keep track of, memory wise? I haven't had time to go back and slowly take the settings back down yet.

Have you tried installing everything as administrator? And run the sim as admin too.

Also in the f16 I think they usually burst a little bit of throttle on their flare, since the f16 doesn't get much lift from ground effect, afaik.

150kts is a little quick. Shoot for around 130. Don't go under 120 else you could stall it out. Make sure you touchdown on the right part of the runway. You can't wait and touchdown 1/2 way. You need to get the plane in a stable approach and vary the speed and descent with the throttle. Put the flight path marker (or total velocity vector?) at the end (closest to you) part of the runway and keep it there until 15-30 feet above, then flare the FPM to the far end of the runway while cutting the throttle. Then just wait for the plane to stall out about 1 foot or less above the runway and you have a landing :) Practice getting that (usually the dual white large rectangles, but you can land before those if you think you need too) right spot on the runway so you have enough room to stop the plane .

Also, keep in mind that the you have to be close enough and line of sight for radio.