Bearfoot

Nope. Nothing like this at all. No dead zone at all, and, in fact, I had to actually add a dead zone in the F-18 to stop the AP disconnecting. And no curves needed either. Easily the cleanest and most precise controller on the table. I cannot remember the springs I am using, but I don't think it was the 50. Maybe 30 and 10? How do the responses look like outside of DCS? Using a third party tracking program like Dlview etc.?

I've got a library that does exactly this https://forums.eagle.ru/showthread.php?t=166565 Simply changing the a/c in the mission editor and sticking to the same group/unit names should work.

Sent!

Could you provide a link to the latest beta/use-at-your-own-risk firmware for the gunfighter? I am consistently getting crazy ghost presses again, and would like to see if this fixes it before opening a ticket and going through the whole troubleshooting dance? Thanks.

Ah, OK. Fixed (removed video).

Ok. reported as bug here: https://forums.eagle.ru/showthread.php?p=3555459 Hopefully mods can merge these threads.

Radar Elevation Changes Result in Severe Lags/Freeze in Radar This is being discussed here: https://forums.eagle.ru/showthread.php?t=214881 It seems to be a bug, affecting multiple people. Various descriptions of problem: "There is a huge delay in antenna repositioning. Try this: leave the elevation at the center. Move your nose up 10deg while watching the elevation caret. The center of the scan will move with the nose and after 2sec. it wakes up and realizes that it's supposed to remain level and snaps back down." "it appears related to controller input, as if there are many presses of elevation to compute and it can freeze if you move it far and it's trying to catch up." "(1) When assigned to button: pressing and holding down, and sending several clicks, results in radar freezing for a LOOONG time while antenna position moves glacially tick by tick by tick. Takes forever. When it reaches its commanded elevation, radar sweep unfreezes. It might be a "feature" (i.e., as in IRL) that the sweep freezes till the radar elevation position commanded is reached ... but it surely cannot take soooooooooooooo long for this to happen. I mean, sometimes 30 seconds or more! (2) When assigned to a slider: same." "My min/max values change with each single press, but there's no doubt that the sensitivity of the elevation of the marker has drastically changed...holding the elevation up or down is now a mistake...you need to apply single taps (button presses) or it goes ballistic in either direction...which means it's no good assigning a slider axis to this...you need discrete steps...I can use it, but do not like it" Track files: https://forums.eagle.ru/attachment.php?attachmentid=189117&d=1530738932 https://forums.eagle.ru/attachment.php?attachmentid=189075&d=1530715213 https://forums.eagle.ru/attachment.php?attachmentid=189085&d=1530717683

Can confirm that this is an issue. (1) When assigned to button: pressing and holding down, and sending several clicks, results in radar freezing for a LOOONG time while antenna position moves glacially tick by tick by tick. Takes forever. When it reaches its commanded elevation, radar sweep unfreezes. It might be a "feature" (i.e., as in IRL) that the sweep freezes till the radar elevation position commanded is reached ... but it surely cannot take soooooooooooooo long for this to happen. I mean, sometimes 30 seconds or more! (2) When assigned to a slider: same. Has this been reported as a bug? If not, can this thread be moved to the bug section?

My 2c ... Once get away from a cold start (and you can always use Win+Home to bypass this), the higher fidelity aircraft can actually be *easier* to learn to fly than the FC3 a/c (or rather, advanced systems vs simple systems modeling). Why? Because instead of always needing to look up keyboard commands, 90% of what you need 90% of the time is all right there in the cockpit in front of you often labeled very clearly. If we can just get cheat keyboard commands (like the cold start) for the remaining 10/10, then we can actually use the high-fidelity a/c *as* entry-level a/c for those who want it? So, I COMPLETELY agree with the spirit of the OP: we need aircraft with a lower learning/time-investment threshold to recruit as well as keep around existing people who may not have the time/free headspace to learn complex a/c however much they might like to. I just think we can achieve that goal through advanced systems modeled aircraft with a bunch of cheat keys to get these folks over the hump for procedures that might require multiple switches/presses like startup. E.g., a single "jettison fuel tanks" or "BVR" mode command that sets everything up for a newbie.

Thanks for the tips. Relatively new to the missile combat thing (helos + ww2 mainly), so I'm just learning the ropes, and wanted to ensure that I understood the mechanization and symbology correctly so couldn't understand why it was firing --- I recognize that RMax is a "long shot" (ha! ha!). Having said that, against an AI, an RMax shot does get them to go defensive/cold, which means *THEIR* "long shot" (which they almost always make) stops tracking which lets me close the distance directly in full burn so by the time they come around from their split-S for take 2 about half the time (not consistently) they end up eating one of my AIM-9's that I sent down their face ... I have no doubt that these kindergarten tactics will not work against a savvy human opponent, but I'll take what I can get!

Ok, can confirm that this is exactly it. SHOOT cue comes at ~32nm ... but absolutely impossible to launch then. If I wait till < 26 nm, then no problems on launching at first try.

Ah, this makes sense. Good to know! thanks!

Yes, this happens to me too: when pressing TDC on an already locked target, target is unlocked (that's good) and cursor moves to upper left corner (that's bad --- annoying to slew back down again). Don't think it is a double press thing ...

I'm not sure if this is operator error, a bug, or something else. - AA mode: check - Master Arm: on - Target locked in STT - Aim-7 selected - Flying relatively straight and level Target range just enters RMAX and SHOOT cue comes on. Press trigger and hold down. Nothing. Check everything, shoot cue still on, lights all flashing. Press trigger and hold down. Again nothing. Repeat. Repeat. Repeat. And then, suddenly, sure enough, they come off the rails, fire up, and track. What could be going on with all the initial attempts? This happens consistently enough for me to think I am missing something. After I get the first one to launch, the others come off on demand without problem.

Hmmm. I suspect that these are two different issues but could be wrong. I'm afraid that I have no easy answers. I can only suggest steps for debugging. I assume you have already done a "repair"? If not, that would be the first stop. Next. try to rename your "Saved Games" folder something else, e.g., "OLD-SAVED-GAMES" and then try starting DCS and seeing if FPS works. This will give you a partial clean slate (i.e. all your options, etc. will be reset, but the main DCS installation is still as you have it). If it works then, then it is one your option settings.

+1

Yes, create a directory if it does not exist. Putting it in the game directory might work, but is not recommended. For one thing, it will get blown away by a repair operation, and possibly by an update as well. Putting mods like this (and liveries etc.) in your own "Saved Games" is the way to go in 2018!

Place file in "C:\Users\YOURUserName\Saved Games\DCS\Config\View"

https://forums.eagle.ru/showpost.php?p=3163055&postcount=12 IIRC, the way these are set up they disappear when close, too. So there is a definitely an "uncanny valley" region, when the labels go off because they are too close yet the object model itself is too small for visibility. You may need to tweak the ranges in the file to suit your conditions to get rid of the uncanny valley.

Assign a switch to your finger lift on the throttle. Activate this before maxing your throttle (or, if your throttle is already at max, activate switch and move throttle back slightly then forward). I think that you can also go to the special options page and disable the finger lift business, but not sure about this.

If by "PD" you mean pupil distance, then this should be calibrated for your own physical characteristics to get a clear image --- specifically, the structure of your own face and, in particular, the distance between your eyes (pupils, to be precise, as the name suggests). Not sure how (or if) this really equates to perceived cockpit size in any way?

I agree with the above poster: spotting is easier in VR than in 2D, but it is the ID'ing that I have trouble with. BIG caveat: above statement is for WW2 engagements! In these sorts of things, the other guy not only moves slower but everyone tends to stay closer to each other. And even when moving apart it takes longer to get far enough to "lose the sight" so that in most cases you can still (re-)pick up and track the other guy. With the distances and speeds of jet engagements, on the other hand, as I have recently discovered with the hornet, spotting is challenging in VR as well! I have had 0 success in keeping the sight after the merge. So all my BVR engagements that transition to WVR in which I do not clear the ledger before the merge end in me burning up in a fiery ball as I take a R-73 to my back or my side as I am frantically trying to spot the bogey against the ground. There is a very nice label mode by Vampire that solves the problem with (too much) cheating: it makes labels these little grey ticks that fade with distance. Works beautiful to provide just enough boost to make up for the VR loss of resolution, and with no consequent loss of immersion. Only thing is that this won't help you in MP at all: in servers that don't allow labels, you cannot use it; and in servers that do allow labels (almost none with modern jets), you are better off using the big scream-in-your-face labels because that's what everyone else uses. Still, you *could* use it as practice in anticipation of better VR resolution in the future or until ED provides VR enhancements?

Reading the manual closely, I find that the SCS-RIGHT to switch to AACQ if TDC is already assigned to the right DDI (only) work when in A2A mode, contra to my reading above. So the behavior I am getting is correct in that regard. However what does not seem to (currently) work as described in the manual is SCS-RIGHT to return to RWS from ACM mode.

OK, so I went back to try this. For me, the button was the middle button on the left side of the display, labeled "mode". Pressing this once showed "map" in a box. Press it again to unbox the word "map" and remove the map. Not sure what button number this is, whether it is button 3 or 18.

Thanks!