WelshZeCorgi

I wonder if the radar is picking up the PH just launched and that messes up the tracks.

Wouldn't firing the 20mm shake the stick, even a little bit? I mean it's going off a few feet away.

why not? They implemented all sorts of other ffb stuff. Transonic, ground roll, spin and stall, high aoa, gear, flaps and i think speed brake. If that's the logic, maybe HB should stop development and release the 14 as is. Cause why continue improving the product?

Yeah, except it doesn't work.

namely, stick shake on weapon employment?

Can we get rid of the double mouse cursors that pop up when selecting radio menus? Actually, just get rid of radio menus, cause when you can't see anything outside your headset, stumbling around, feeling for your mouse every time you need to communicate with the AI is really frustrating. And get the mouse cursor restrained to the game, too many times have I tried to hit a switch in cockpit, to find out that I actually clicked off the game somehow, and now I crashed into the side of a mountain because none of my inputs works in this state and it took me a few seconds to long to click back into the game.

DCS crashes and I rejoin the same aircraft while it is now in flight. Entering the RIO position, for some reason, deploys the flaps to landing, jams them, and bam, half an hour or more instantly wasted due to this bug.

the autopilot reacts weirdly when using a brunner ffb stick. Hitting the altitude reference button causes the 14 to suddenly pitch down while the AP reference light remains on. Only after leveling the jet after this odd pitch moment does another press on the reference button cause the jet to actually maintain altitude. When the AP is turned off, the jet suddenly becomes tail heavy. with attitude hold is engaged, the 14 will occasionally roll in the opposite direction as commanded, (rolling left when pulling the stick right, in my case) I'll try to get a track file attached later.

VR is good, but if I want to make or edit missions or test new setup/keybinds, and I want to do it on flatscreen for comfort or ease, I have to go into VR, unselect VR in settings and then restart it, and then go into settings again later on and restart DCS in VR. Can we just get 2 different exe? one that boots DCS in VR and one that boots in flatscreen?

I'm guessing the logic is confusing 2 seperate contacts as 1 contact moving extremely fast?

I tried googling to see who was credited the first ever recorded maneuver kill and could not find anything. Anyone know any details regarding the first recorded maneuver kill?

That's why there are 4 wires, 1 for all four 201 tomcats. Conga line that shit.

My question is, what happens if you let the yearly subscription fee for the XR/VR 3 expire? Does the headset self-destruct? Refuses to power on? Shows you a literal paywall? Or you can use it, but no more updates to the sets firmware? A buddy of mine is offering to buy me the VR3 as thanks for getting his a** out of trouble. Not sure if he's serious, but I'm sort of entertaining the thought.

For me, VR definitely is "there", but it's not "there, there". It has juuuust enough positives that I will use it, but not enough positives that I won't find something that annoys me every time I do.

Yeah, but is it implemented correctly? I mean, what's the point of adding an additional 2 seconds till release if you can't stop the launch by releasing the trigger or the button before the 3 seconds are up? If the 1 second trigger and the 3 second trigger operates the same way, what's the point of having both triggers? Why not just have the 1 second trigger work under all conditions? Is this another +1800 closure rate mistake, where they glossed over a small detail and implemented one or the other trigger functions wrong?

I'm confused about the 3 second trigger. Are you supposed to hold the trigger/button for 3 seconds, then the command to release the missile is performed? And if you release the trigger or the button before the 3 seconds are complete, the command to launch is cancelled? Or is the trigger/button simply pulled or pushed and then 3 seconds later the command is given, regardless of if you released the trigger/button before the 3 seconds is up? I was working under the assumption that if you release the button before the 3 seconds are up, before the missile is released, the launch will not go through. I thought this was a safety feature to prevent sending a fox 3 if a friendly contact popped up or the contact you were launching on wasn't hostile, whatever, but that's not how it's implemented in HB's F-14. And is it implemented correctly? I mean, what's the point of adding an additional 2 seconds till release if you can't stop the launch by releasing the trigger or the button before the 3 seconds are up? If the 1 second trigger and the 3 second trigger operates the same way, what's the point of having both triggers? Why not just have the 1 second trigger work under all conditions? Is this another +1800 closure rate mistake, where they glossed over a small detail and implemented one or the other trigger functions wrong?

Even if you don't have a scale pit, I'd image it would still be useful. As you can see your keyboard, real kneeboard and your HOTAS controls. But I wonder if it really would develop in a few generations. VR is already so niche, that's why this is marketed towards companies. Unless they see a large amount of individuals buying these VR and XR headsets, I feel like it's unlikely they'll develop one for the home market.

VR3 and XR3 by Varjo seems to have come out with a VR headset that gets near natural eye resolution quality experience, Reviewers are making it seem it nearly if not completely eliminates blurriness on cockpit reading. It's just too bad it costs $7000 dollars, including oddly enough, some sort of yearly subscription. This is not counting the possibly $1000s of dollars necessary to upgrade your computer to power this headset. It also has a few issues and DCS doesn't support some of its features (but might in the future) and the FOV is the same as an index, so that's going to still be an unnatural limitation on your experience.

I feel you, I have a love/hate relationship with VR. Unfortunately, it seems like the only way to lessen these issues is to simply wait for very expensive new tech to make their way into the market, then shell out a tonne of money. My main issue is the unnaturally narrow FOV + the unnatural neck craning required to push a button or flip a switch that's right next to my hip.

Just as well, gives us time to save up a few thousand dollars for the necessary upgrades + VR headset. I'd also wait for a near natural FOV along with the current Near natural resolution. Also also, sounds like there are a number of issues they got to iron out, + DCS doesn't seem to support certain features on the XR3. (eye tracking)

So I RIO using SRS and started learning a bit more about radios, and While the intercom allows simultaneous talk and hearing for pilot rio comms, the half-duplex radio does not do that. I was wondering why the decision was made to use a half-duplex radio instead of duplex, cause I feel like it would eliminate the instances of people accidently talking over each other if they did.

Korea- we have the Mig and the Sabre, and we even have a campaign "over the Yalu River" that takes place on the Georgia map cause we don't have a Korea map. Not only that, with the current map sizes, we should be able to get most of Korea in there. The geography is also interesting, being surrounded on 3 sides by water, and hilly/mountainous terrain. I get Vietnam, but I would wait until destructible environments are available to map makers, it just doesn't feel right if you can't flatten forests with daisy cutters for impromptu landing zones for hueys, watch forest fires propagate after napalm strikes, etc... etc... We also don't have a lot of the Vietnam era stuff available in DCS, (Huey D, instead of Huey H) F4... etc etc...

So I noticed that the bullet impacts on ground and water in the Mosquito trailer were a lot more detailed and realistic. Did those changes get into the patch? Do we need to put a certain graphic setting into high to get them?

It is cold start, but I'm not sure how to align mag compass, the start up tutorial in DCS doesn't mention it.

In the ARGO campaign, first mission, I was told to fly heading 120 after leaving the boat and I did. After half an hour, I realized something was wrong and found that 120 on the HSI was more like 190 on the TACVIEW. Not sure if this is a bug or you're supposed to calibrate the HSI before takeoff.