Mars Exulte

Won't work. Drones don't have a head to aim at

Anything's possible, just have to experiment and see. But statistically... it's probably the garbage cable acting up. When it arrives, plug it in. If it magically starts working, you know it's that. If it doesn't, it's something else. Or you got another bad cable. Seriously, it's hard to tell with a failure rate that high. I didn't know they were that expensive. Damn. I literally have more cables than the headset is worth. That's insane.

I assume you mean C-130J. And no, it won't be a weaponised AC-130.

So, my Gunfighter (I believe Mk I) upon fresh boot, the axis are sporadic and trigger random button triggers until I unplug it and replug it from the base. I know firmware updates are generally discouraged unless you're having a problem, is this firmware worthy? Is there any significant difference between my older ones and the newer ones that I need to be aware of when doing an update? I'm a bit out of the loop on the hardware side. Tried to look over a few pages to see if anybody else had a similar experience.

That's a Flak88 isn't it? The only trouble it had was hitting a maneuvering target from 25000ft away reliably (which is expected as that's like 10-12 seconds of flight time). When operated in the ideal environment with a trained crew and synced gun directors, they were very accurate. They were supposed to all be wired in a directed semi-remotely, not manually aimed and calculated by individual gun crews.

From my understanding, most professional sims are designed for specific use cases, ie simulating a certain series of events and your response, switchology, etc. In this context flight model and especially graphics are irrelevant. They're rarely intended to recreate the "real thing" 1 to 1.

30 is "minimum for a decent experience", 60 is the gold standard. More than 60 begins to noticeably improve smoothness and reduce screen tearing when combined with a high refresh rate monitor up to 120/144ish. Once you start crossing that line it becomes completely irrelevant in 99.9% of contexts. Unless you're doing VR, in which case every frame counts. In a flight sim, that's less "millisecond reaction time" dependent, anything 30-45fps will usually be fine in 2d, but again, ideally you want 60ish as it's noticeably smoother.

I'd recommend a JetSeat over a buttkicker, for practical purposes they do the same thing, but JetSeat you can customise the individual effects being created with 6-8 motors (depending on what version of JetSeat you get, the new ones have

They're not going to do that They'll either do it exactly the same way they do everything else or not at all.

We should probably keep some in reserve, like grizzled survivalists hoarding canned goods and ammo.

If the headset light isn't on, and based on my own tumultuous relationship with my G2 a few weeks ago, I'd say it's a bad cable and it's not getting power. I'd check all your connections and make sure everything is firmly seated, also check the cable that plugs into the headset itself for damage from crimping/flexing when you raise or lower the visor. My first cable failed, then I got a brand new one, it failed a few days later, and then I got a third one and all my issues instantly stopped. HP's cables are absolute trash, even their new ones.

It is correct and described in detail in the manual nobody reads It's literally one of the very first things it goes into. Every rotor has an advancing blade and a retreating blade. Advancing blade generate slift, rereating blade loses it. This pushes the blades up on side and down on the other. The faster you go, the more pronounced the effect. This is normal and present on all helicopters, just not as glaringly obvious. Contra rotating systems like the Ka-50 uses attempt to cancel out the cons of helicopter rotors by rotating in opposite directions, so the aircraft has roughly neutral lift/loss on both sides. However this means the blades are very close together at high speeds as one is high/low and the other is low/high, potentially causing a blade strike at extremes of the envelope. These characteristics are one of the main limitations on helicopter forward flight, as the lift gets stronger on one side and loss greater on the other, the tendency to roll becomes impossible to prevent, all other considerations aside.

970 has 4gb. 980ti, some 1060 has 3gb & 6gb variants if I remember. Dunno about AMD but they probably have some, too.

As mentioned before, this thread is not about OpenXR support. You miss the point entirely.

It's still an awful lot of work for something that will be barely utilised by the community. Realistically, any more than two people is impractical and unnecessary. Three tops, depending on circumstances.

Eh, that's corporate task scheduling for you

PSA: Kediers sucks. I am determined to use this case, though, as I have passed the point where I can realistically get everything back in the box. If I had it to do over, I would not buy this damn thing. Looks nice and airflow will be very good, but there's so many just kind of dumb design decisions that just make no sense. What a collossal pain in the ass. Seriously. Major buyer's remorse. I had to bend the motherboard posts into position with pliers because they didn't line up right (also one appears stripped). The provision for cable routing is hit and miss, and I will probably put a black cloth or something over the tangled mess of power cables. Even being open air, I don't understand why they didn't at least optionally shroud the psu area. And why is every other case fan screw extra long? There's just no rhyme or reason to a lot of it. And why is the cutout for the motherboard not large enough to expose the back of the CPU mount? Just dumb. -edit And wtaf is with this AIO? What are these standoffs for and why they do not ACTUALLY GO WITH THE CASE? Like seriously, one side is fairly straightforward, the other? These projecting screw ends can't go in anything! Why are they even in this bag?! They're too big for the cooler holes, and too small for case fans! They're useless! -edit 14 hours of labor later, it's finished. The back fan doesn't match and dislikes the controller, but another is arriving tomorrow. The AIO gt ditched after too many issues. Went back to the air cooler I had.

You can't reliably get a copilot/gunner in the other modules. You think you're going to get 10? You're literally going to need to have a clan dedicated to crewimg a single B-17 taking turns on who gets to be pilot. If you try to rando it... well... we all know how that would go. 3 guys join, ones a noob, the other two are trolls that jettison your bombs and shoot off all the ammo.

It's supposedly on ED's to-do list after the Apache and BS3 are complete. Last I heard when all that was being debated, they were talking about an AH-1S

Can't you just use a 90' cable? I have done stuff like that with gpus that overhung them before. It's good to have a couple of them around for situations like that.

Yeah, the 400 is only a couple inches larger, and I seriously considered just doing that... then decided to go all in on doing something different :p I built one for my brother using Cougar Gemini which is really nice but don't want to copy him :p

I don't care if they make it the size of a minifridge and needs 1100w, but they shouldn't then pretend it is intended to go in a case Just make a free standing unit at that point, maybe with a long cable that goes to your PCIe port. Or maybe just change the layout of PCs altogether, tbh, the current form factor is suboptimal in a number of ways. The whole ''scheme'' needs a 2020s do-over instead of trying to make do with the same basic layout we've had from the 1980s.

I saw that thread and tried to hastily muddle through it. I'm about to have a four day vacation, on my todo list is finalising thee case swap and finetuning everything (along with hopefully visiting the OKC air museum and seeing a B-52 up close) Thanks for the offer! If I have any issues I may take you up on it.

Stuff like that can happen with SonicWave and some Asus utilities, too. That was when I learned to run a light system. If it isn't relevant to the task at hand, I don't let it run. People LOVE forcing a bunch of autoloading selfupdating random crap. Yesterday, I finally figured out which file was causing ''CyberLink Power Director'' crap to run all the time. I thought the file was a Windows function and never terminated it @@ Discovered the true purpose by chance.

Honestly, I'm surprised that never happened to me. I've dropped my glass panel a couple times and it didn't shatter or chip.