EvanWeeks

Wags does a great job of putting together the vids and then responding to stupid questions from people like me. He's a nice guy.

Are over-G effects modeled on stores? I haven't seen any problems with hung or degraded stores situations when they've *definitely* been over-G'ed.

:huh: What an unfriendly person. Oh well. :joystick:

What would you say these forums are for, if not for asking valid questions like, "hey, we know we're getting these brand-new features in the near future. Could we please get a vid from Wags showing us how to use them?"

REALLY appreciate the update, BN. Managing expectations is so important. Thanks!

I'm getting closer and closer to this attitude. May have to move to the Hornet in my squadron as a result.

Wags, Would it be possible to get a set of academic vids on the use of Link16/Datalink and TWS before the open beta update next week? Thanks!

The RWR in the other sim is actually simulating the RWR making different noises based on the pulse rate and patterns of the different search and guidance radars. If you're listening closely enough and you've learned them, you can discern between them based on sound alone. At least that's my understanding of it. I don't claim to have that amount of experience with it at all.

Now THAT is helpful. Thanks BN!

I, too, am interested in this one. I haven't gotten it to work.

Oh that is hilarious... :megalol:

The trim is definitly WIP. And I notice the yaw to the right on takeoff as well. I've started trimming my rudder 8-10 clicks to the left before I roll.

Wait, are yours that bright? How? My MFCD exports are unreadably dark.

Manual is in Mods/Aircraft/F-16 (or something like that)/Docs.

I've seen just "FML. Look at the changes I made and lose all hope in humanity." as a commit message before. I might have even written it.

As a software engineer, I'd probably spend a lot of time laughing, if their commit comments are anything like mine. "Why, in the name of every deity that humanity has ever worshipped, and the abstract concepts of goodness, love and harmony, did anyone think that this was a good idea? What poor, depraved, ignorant, self-loathing creature foisted upon us this monstrosity?"

It'd probably be hilarious to see the commit log for the repo. I can just imagine the frustration expressed, "Fixed the thing", and moments later, "Fixed the fix to the thing that broke the thing and about 30 other things."

This seems to agree with my experience as well. I'd put the egg on a target and nothing would happen, so out of frustration, I'd hit TMS up a few times, and suddenly, LOCK.

It is "functional." I was able to get it to lock on several times. In 30x20 (ACM default mode or TMS right) there's a small diamond near the center of the HUD (no, not the AIM-9 seeker symbology. It looks almost like the slewable mode cursor, actually, just much smaller). If you steer the aircraft so that diamond is near the target, you'll get a lock. I've done it multiple times in the last several days. That said, obviously that's not the right behavior. It should be scanning a much larger area than the 5-6 degrees around that diamond.

Page 102 of the Early Access Guide for the DCS F-16: "The Air Combat Mode (ACM) automatically acquires aircraft at short ranges. This mode is used most often when the target is already acquired visually. The pilot flies the aircraft to position the target in the proper position for radar acquisition. Different scan patterns are available in the four different submodes: • Boresight (BORE) • 10°x 60° (Vertical Scan) • 30°x 20° (HUD Scan) • Slewable The radar locks the first target it detects within each submode’s search pattern. Maximum acquisition range is 10 nautical miles for all ACM submodes except Boresight, where acquisition out to 20 nautical miles is possible. Each submode has its own strengths and weaknesses and is best used in different situations."

Miz: https://drive.google.com/open?id=1WIWnECblDKbkbV5ExHewXr1Q5x0k9bsa Trk: https://drive.google.com/open?id=18xsAHAIhuKpWyiScZy1C2W3TcciTrTfH Started up in the air about 6-7 miles nose-to-nose separation, quickly turned on HMCS and flipped to DOGFIGHT, selected AIM-120's. The 30x20 mode seems to be tied to that little diamond in the center of the HUD. I had to get the target really close to that cue to get the lock to happen. The 10x60 mode works alright from my experience. The boresight mode, I ended up having to hold the egg on the target waaay to steadily for it to find and lock the target. Notice that every time lock was lost in ACM, the radar converted to CRM and I had to flip to MSL OVRD and back into DOGFIGHT for it to go back to ACM.

I'll get you the .miz and .trk files this afternoon.

I just tested the crap out of it with a Mig-21, and I was able to get locks in 30x20, 10x60 and boresight with AIM-120s selected without TOO much problems. My only gripe right now is that if I DO lock up a target in ACM mode (with AIM-120s selected) and then subsequently LOSE that lock, the radar defaults back to CRM mode, and I have to go dogfight switch inboard, then outboard again to re-select ACM. Then there's the annoyance of trying to get into a good firing position for a slammer when in the merge, but that's a different problem altogether. Edit: my test was an air-start.

There's a thread on this over in the DCS World 2.5/Bugs/Multi-Monitor forums. No acknowledgement from ED just yet that I've been able to find.

I've found that throttle changes also slightly affect my vertical position. Throttle down, FPM dips and I start dropping away from the tanker. Throttle up, the FPM climbs. You have to manage it all as one animal.