Mars Exulte

This is a factor on direct linkage setups, like old WWII warbirds, or cheaper civilian aircraft, where you are physically using the stick to move the control surfaces and are opposed by airflow. Most of the aircraft we have use hydraulic controls, so the resistance is artificial. You could fly them with a mouse and keyboard, but they do it this way to help prevent overcorrections and give feedback to the pilot. That said, a quick Google search says the F-18's force required at full aft deflection is about 40lbs, and 13lbs laterally. Bear in mind, it is not a desktop stick and is relatively long (18''). So, some force, but not a HUGE amount.

I knew it was competing against the A-29 and T-6 at one point, interesting to see it getting picked up afterall.

It's forever lurching from one issue to the next with this damn cockpit I built... One set resolved and now a new one. The Reverb thumbsticks can normally be used to rotate knobs, and as of a few days ago they worked normally. Last night, they suddenly stopped. Everything else works normally, but NOT the thumbsticks. I wiped the input folder to reset everything to ''default'' everywhere, but it made no difference. Double checked settings, etc. Has anybody else encountered this? Between the Reverb's jittery tracking and their medicore controllers, I'm really starting to eyeball other headsets -_-

I solved the issues finally. Dielectric grease on all connectors, cleaned out chrome flakes on the cams, updated BIOS, updated utilities, reset admin privileges. Works 100% now like new.

I wouldn't exactly call four years quick, but I now believe you really are some sort of project lead or middle manager with this kind of time management. Looks like you struck a nerve with that one. I can already sense Nineline and Bignewy closing in.

#1 Compression Files are heavily compressed for download, so it's faster, and then extracted afterward. #2 Patching files You may down 150MB of ''patches'' that must then apply to several hundred files totaling several gigabytes of rewrites. Basically, it's ''appending'' to a preexisting file, rather than replacing it outright. #3 Replacement vs addition You may download 25GB, but a lot of that will replace stuff you already have, rather than adding to it, so your actual total install may only increase 5GB, or not at all, or technically could even shrink if the new files are smaller. End result, download size is not directly related to the storage space required.

I believe I used to do this before by simply setting the AI to hold fire, unless that's changed. They would maneuver and evade, and even try to ''attack'' but not fire. Of course, eventually they run out of fuel and eject unless they get far enough away to disengage then they flew to the nerest base and landed. I used to do this with Predator drones, specifically, and I think F-5s.

Credit for tenacity in resuming a four year old argument. +1 internetz to you.

Just because you CAN do a thing in VR, does not mean you SHOULD do that thing.

Well, looks like I'm missing all the fun, sitting over here unupdated. I figured there was a 60% chance a major version update would bring some sort of insanity.

I would think by this point his bs only works on (rare) new guys. Anybody that's been here more than a couple weeks knows to ignore him

That's true, too. Fair only really exists in very specific games designed with that in mind and literally nowhere else in reality.

We're not in real aircraft, but the game is intended to represent them. You're in the wrong community with that approach, tbh. Striving for realism is indeed the objective of a simulation. You can here, too. Yes, you can, by using the tools available to you which exist specifically to compensate for these shortcomings. So clearly because it's not real life, we just throw the whole exercise out the window, Jesus @@ People create their own issues 90% of the time by being inflexible. Your 24'' monitor three feet in front of you, zoomed out so you can see the majority of your cockpit, is not representative of what you would see in real life. All bs aside, you need to adjust your field of view for the task at hand. If your fiddling with your cockpit instruments, lamding, etc you need to be zoomed out for more visibility and more instrumentation. When you're scanning the horizon for distant contacts, you don't need to be able to see your feet while doing so, so adjust your FoV to something more ''realistic'' scalewise and suddenly you'll notice everything is, shockingly, easier to see. This isn't ''cheating'' it's not ''unrealistic'' it's shifting from a fisheyed high fov for convenience to a more appropriate one representative of what you'd actually see. Failure to make use of this tool which has existed in every sim since the early 90's is unintuitive, obstinate, and backwards, but not indicative of a failure of the game engine. That said, things to improve visibility, contrast, and LoDs are always welcome (and many of the most glaring issues are related to improper LoDs) but people act like this is some impossible hurdle and blaming their monitor resolution is among the most asinine nonsense to ever wander across a gaming forum.

Haven't tried MSFS myself yet, so cannot say, but afaik it should work fine. Sounds like you've got some other issues. You definitely need a powered USB port though. N/s what else to try.

Nope, it is still triggering a range of ghost presses, even after reset. Plugging/unplugging does not consistently resolve the issue, either, and if it's behaving, it's apt to randomly stop taking keypresses again until plugged/replugged. I'm going to do a complete disassembly, and check the plugins.

I think in the Target software you can select which is which, but yeah, one will be left and one will be right, and you'd need to either physically move them or adjust their order in software/ingame. Correctomundo

Next time I fly it I will pay closer attention. It definitely used to do that, it was extremely obviously a short looping audio. When I was messing with it a day or so ago I didn't notice looping, so if it does it's not as bad as it used to be. You couldn't NOT notice it a year or two ago (I used to run a mod that fixed it). I really like the whining when moving throttle, and the cutout when you land. Very similar to the real thing. I couldn't comment on the exterior. I'm just now getting back into the game after most of two years away.

Yeah, as above. It's a recently refurbished AI model, so one of the best looking available. That's why it's in promotional material. They're not going to showcase the 35 poly Tu-95 from the 1990s.

The old sounds sucked. The new rework Razbam did is pretty good, and sounds very close to most videos I've seen. I think this is a case of people doing the audio equivalent of complaining that "afterburners in DCS don't look like the ones on YouTube!!11!!11!" Not every gamer rambling about stuff online knows what's he's talking about.

Strictly speaking, most modern fighters have a maximum roll rate up in that range. Now, whether they'll still do it with bombs, I don't know, but it's why they all have limitations on doing endless barrel rolls at high rate. Most of them have something like a prohibition against rolling more than a single full revolution, presumably due to structural or aerodynamic stability reasons.

Haha ''TUNDERIN' JAYZUS, 'ES 'UGE!!!''

The biggest problem with DCS and TM MFDs is DCS tries to forcibly autoassign them, unlike literally EVERY OTHER DEVICE and CANNOT BE OVERRIDEN. Generally, this is not such a problem, as the MFDs are normally configured correctly, but on occasion it is a nuisance. If it was me, I would fully expect to encounter this, and my first attempt at a solution would be finding a way to load them as generic USB game controllers instead of letting Windows identify them correctly as TM MFDs as doing so starts DCS off into ''helping''. If they were never id'd as TM MFDs then DCS wouldn't know to start screwing with them. A bit of unnecessary black magic work is required because they treat them differently, when they really, REALLY shouldn't. I would start off by trying to manually assign them device IDs and overriding Windows 'self identification'. Used to be this was fairly easy, but with each generation Windows has become more ''user friendly/idiot proof'' and removed less and less control. Tbh, I don't know how to go about it these days. I will experiment when I get home tomorrow and see if I can find a way. Part of the problem is also that TM MFDs are really designed to be used in pairs. I know it can be worked around, as I've seen others use them in triple configs, though.

Somewhat ot but since we're talking about simulators. This old school one was pretty impressive!

Even better if you film from a hot tub and bottle the water afterward. That's where the real money is.

Unfortunately, this drives 99% of online discourse these days. Ever wonder why people like/karma farm on websites with bots? So they can turn around and sell that bot with established ''credibility'' and use it to push marketing. Lovely dystopia we have here.