taco3rd

The download of the last couple updates stops before completion. A couple times it downloads the whole thing but it stops and doesn't install. Just hangs. Thx. - apologies but it just worked. But it does this a lot. I have updated the downloader as well. My case is fixed but maybe there's something going on with ED's servers?

Thanks for your attention maximov. I decided to do a fresh install and everything is working fine again. I'm guessing something got corrupted.

I disabled Bit Defender and booted into safe mode and it still hangs at the downloading update pane, 0 downloaded and speed.

Hi, I'm stuck on version 2.8.0.32235 Open Beta. I start the game and it says I have the current version. When I try to do a repair it gets to the downloading update pane but the download doesn't start and remains at 0 MB speed and downloaded. I can't use multiplayer. Thx for any help.

Putting it simply, you don't use the HMCS for a 120. The HMCS works with aim 9Xs and is used for targets already within visual range in ACM radar mode.

I explained bore for the 120 above. They work differently and use different radar modes. Because you're trying to lock a bandit from much farther away you use the FCR to lock up bandits. There's no bore sight mode on the HUD because your bandit could be tens of miles away. The bore mode for the 120 simply launches the missile without radar help from the F16. It's pitbull as soon as you launch it. Don't get radar modes confused. Learn the difference between CRM and ACM radar modes. Watch a video about fox 2 dogfighting and compare and contrast the two.

AIM 120's are a beyond visual range missile. You really don't want the bandit within, say, 7ish miles. You need to learn how to use the LAR to determine the max range, as the conditions you're in when you fire it changes the max range. That said, you can fire them at 50+ miles, if you're high and fast, and get kills occasionally. Firing early is a good way to get a bandit on the defensive. Bore mode is basically, you're not getting a lock on your opponent and you're just going to throw caution to the wind, launch it and hope it can find a target and not a friendly, because it can't distinguish the difference, so make sure you have situational awareness of where your buddies are. Slave mode is what you'll use 99% of the time. The missile uses the F16's radar to guide itself until it determines it can take over from there and go "pitbull", where it has a mind of its own at that point. You're pretty right with the sidewinders, but it takes a lot of practice. It's really not a simple process. There's many radar modes, dogfight modes... These are your dogfighting/close combat missiles and they're heat seekers, not radar guided like the 120s. Shooting 9x's is like having a cheat code. I've seen them do some crazy acrobatics and still hit targets.

I think we'll all turn into Top Gun level sim pilots as it gets updated and easier to fly. Turn and burn.

I'll try this again. lol. Unless something has changed, which I wouldn't doubt, you can only ripple 2 mavericks and only if they're singles on their own rack, as of now. I've stopped using them because of all the issues, so hopefully this is correct still.

I'm pretty sure if you're boresighted properly you wouldn't need to slew the mav wpn page to the target. It should at least get you in the area code. Besides, when you have the target locked on both the TGP and WPN, you might as well hit the BSGT to make sure. Maybe initially just put the TGP into point track mode and let it handoff to WPN. The WPN should slew to the target automatically. Don't touch the slew of the WPN page until after the handoff is completed, if needed at all.

Agreed, but not many aircraft can wipe out half an airfield by rippling 2 pairs of CBU97's, then climb to 40K feet and BVR an SU33 from 50 miles out. Just sayin'. lol

My bad if the process was fixed. Last time I tried to boresight them on the ground I could only get one side to align. Still had to manually slew on the right side. Still, I'm talking to the point of when these things simply aren't working the way they're supposed to. I'm pretty sure the Air Force isn't putting 16's out with software bugs that pilots have to find work-arounds for. That's all I'm saying.

agree 100%

Silly. Somehow a buggy incomplete process is "realistic".

IMO, it takes a certain level of experience to even recognize and work around these issues. Expecting a newb to come in and understand what he/she is looking at and then take the actions necessary to rectify it is asking a lot. The F16 already has too few weapons and these issues keep me from loading mavericks unless there's no other choice (they must be a time nightmare on multi-player missions). I feel like it's much more important for someone to learn the basics just to get up and down reliably and safely, than sitting on a runway trying to boresight buggy mavericks. I enjoy the realistic aspects as much as anyone else, but the 16 is buggy and incomplete. I don't see any reason to not have an option to do some of these procedures automatically until the procedure is complete and works exactly as it should.

I have poor success boresighting them. Won't work on the ground and doing it in flight is more of a pia than it needs to be. I've wasted a lot of time trying to do it on the ground in PRE mode per the GRs video, then threw a changeup and said to do it in-flight in VIS mode. I see no problem making an option to make them automatic. They're buggy and they waste time.

I can't boresight them half the time when I'm on the ground. I usually use a random stationary truck on an airfield but sometimes the WPN page for the mavs won't lock it up. I've stopped using them because I wasting 20 minutes trying to boresight them, then have to use the mav wpn page anyway to slew to the target. I must be doing something wrong, but I wouldn't classify myself as a rookie and I've watched a couple videos. I dunno.

have you calibrated the trackir?

Pros: fast, great agility, awesome at BVR, decent dogfighter, multi-role so you're not a 1 dimensional a-a or a-g. Cons: it's not as complete as the f18 as there's still bugs and non-implemented systems, it only carries 7100lbs of fuel so it has really short legs - so you carry fuel tanks a lot which hurts it's performance drastically, but can be overcome by knowing when to drop the tanks. It doesn't carry as many bombs and weapons as the 18. If you like Navy and dealing with carriers, get the 18. If you like Air Force and dealing with airports, get the 16 and you'll get to the target 10 minutes before the 18. I'm not a big fan of the 20mm guns they're really only good for light armor. That said, I prefer the 16 but I don't have as much experience with the 18, so take it for what it's worth. If you like interesting weapons, check out the CBU97. I can't imagine there's a more fun bomb to drop than them. Absolutely devastating to armor. This video is better: I'd like to see the mavericks be more user friendly. I have a bit of experience, but no matter how many videos I watch, I can't get the damn things bore-sighted half the time and have to slew manually which defeats the purpose of the TGP integration. Another thing I'd like to see is the antiskid. It's way too easy to lock the wheels up.

Make sure your hotas buttons are bound properly and you're actually using the CMS. I know I have to personally hit a modifier button to get to the CMS commands. In default mode, that hat is programmed to TMS until I hit the modifier.

" you are correct, the GO flag also does not show for me, normally the GO flag should appear after placing the PRGM knob into BIT, and you could look into the BIT page in the MFD, but the page is not yet implemented, therefore i suppose the developers set the GO flag in preparation to implementation of the BIT as: if BIT is passed successfully - > set GO or something similar, as there is no BIT implemented , there is no test to pass, therefore the GO flag doesn't illuminate, My Guess is, because the GR video is quite old, there may have been some changes in the GO - Flag logic between our current build and their build they used in the video. As i said, the go flag should light up once the BIT is passed, but it doesn't show for me, so it is safe to say that you shouldn't worry, it's a Work in Progress after all [12:10 AM] on another note , showing that the f-16 is nowhere near completion is that the flcs still does not go into aerobraking mode, meaning you have to constantly pull to maintain 13° aoa, which is not true, in the thing you should just have to pull to 13° aoa and then be able to take your hand off the stick and it should maintain that aoa by itself. + antiskid not implemented, cmds semi,auto not yet implemented, BIT pages, TFR, HUD RDR Alt bracket mode missing, so there is still so many things to do in the Viper" This was the reply.

the "GO" light doesn't work at the moment. It has in the past, which is why you see it in some old videos. I asked around in a squadron I was a part of, and they asked someone at Eagle Dynamics and they said it currently doesnt work. for those that haven't seen it, its in that little green strip at the top of the CMDS panel. In old videos you can see GO lit in it. I wondered myself after watching a GR video why they had it and I didn't.

Not sure. I doubt I do anything different than anyone else. I've turned into a fairly good sim pilot and have startup procedures down and don't have any other issues. The only common denominator I can think of is that I use the 162nd vipers training server just about daily.

It's an uncontrollable oscillation for about 10 seconds. Happened to me recently on a training server and probably a half dozen times overall. I always switch my probe heat on. It's fairly violent. I'm pretty sure it wasn't a speed issue.