M1Combat

It's super fun. Do it. Maybe don't try long distance sight seeing flights... It's a little slow for that... BUT... It will chase it's own tale... It's super fun from an aerobatics perspective :).

Hmmm... This was a bug along time ago that got fixed as I recall... I don't think mine do this. I'm running a good bit more system than you are but back when this was happening I was running a 970. All of a sudden with a patch the Vikhr wrecked framerate. Next patch it was fixed. I'm not saying that's what's going on here but I suspect you have something wrong. HAve you tried clearing the shader chaches? Any cockpit mods in the shark? Drivers updates?

"I think we need to start a collective effort to archive every single ED post because so many things get smoke and daggered away" LOL You mean the bit that says "SUBJECT TO CHANGE" or the rest of that stuff that's actually subject to the aforementioned changes? People try SOOOO hard to be victims these days. All us "boomers" knew this was coming and tried so hard to warm the population of this poor planet that giving all you little tikes a trophy for every little thing you did would backfire... hard... And here we are.

No... How much CPU overhead there is at the quality setting :). Sometimes sales brochures are a good thing... They just need to be vetted for context first.

I'd be interested to know how much average CPU overhead there is at the quality setting.

Exactly

The KA50 does pitch up just not until about 425KMH. At 550KMH you have to hold full stick forwards with super low blade pitch to keep it from doing the exact same thing the 24 does. Also... At those speeds it will show you why it's called the Shark ;). Gentle weave side to side :).

"For example on Ka-50 that doesn't happen because before your nose goes up your coaxial rotor blades already chopped themselves to pieces." It doesn't happen on the KA50 because it has coaxial rotors. They spin opposite direction so there's always lift on both sides no matter your speed. The blade chopping themselves to pieces is due to the pilot not reducing blade pitch at high speeds. The Shark can go "very fast" in a dive. Reduce the blade pitch. It's the dial to the left of and above your knee that goes to I think 13.

So can you do the shark style takeoff where you hold trim, increase power, stick forwards to keep the nose down, more power, stick forwards, more power, stick forwards etc etc until you can't quite keep it on the ground, then release trim, and pour on the power? By that I just mean something similar where you trim it to T/O trim basically... then just take off, but clearly with rudder input because it's not coaxial... I know the trim and forces involved aren't the same... but I assumed that you could trim it to a situation where you can just "dump the clutch" so to speak and bug out with rudder correction...

Well.. I googled it... And found nothing. So I googled it a number of different ways... Still nothing. So... Would you be willing to share or is asking someone ELSE a rule??

Well... Maybe also read where I said that ED probably also saw a few $$$ and allowed that to influence their decision... BUT... Either way if you feel like you'd rather dispute that as fact then by all means feel free to offer other facts that differ from mine :). I mean I think it will be pretty hard to dispute this... But feel free :). That DID happen... and the very best explanation I can come up with is that ED was trying to please the community. I mean... They did what the community asked. Aside from the aforementioned $$$ that may have helped sway their opinion (that I mentioned before as well) what else would have been their motivation??? Also... If you were TRULY just pointing out that one little teency sentence as what you disagreed with... Good work quoting the entire post and then mentioning your disagreement... It's cool though... I just misinterpreted your statement as being pointed at my entire account of the situation :)... All good... My bad ;). Oh also... If ED was trying to please the community... and the community was poking them with pitchforks... And both of those things do indeed seem to ME to be true... Then my opinion is actually a fact. I don't know ED's mind/decision making results around their executive team... but if I'm right... Then it's a fact :). On the pitchforks part... That's a fact. We all saw it. It's not a literal account of events mind you :).... I don't think anyone from ED went home physically bleeding :)... But it's a fact.

The main thread in the wishlist could use a bump if anyone is so inclined

well... That's the nice thing about facts... They aren't there for you to agree to or not... It's simply what happened :).

"Yep! Very true. And I'm just expressing my opinion on the matter to give ED this customer's preference on EA(F-18 good F-16 bad). If others are happy just being able to fly it thats a valid opinion too. I'm sure I'll end up buying both modules, I'll just wait until I know I'll be happy with their development state" For sure... BUT... Let me just tap out my thoughts on that for a sec and please don't take it the wrong way. What really happened is they EA'd the Hornet... And all was good for a while. Then... they teased the 16. All was s till fine (I mean aside from regular unsettlement of the masses for sure ) Then... They mentioned that it's actually flyable and the flight model is pretty reasonable. The flight model and 3d model guys were pretty well along with the hornet so had some time to work on the Viper so they did... That's when it all went haywire. The COMMUNITY demanded that the F16 be released in ANY state... as long as it has a half decent flight model, an Aim-120 and MAYBE even an Aim9 of some sort. They roar of the crowd chanting VIPER VIPER VIPER was deafening. The crowd plomised (<-- 70's show reference) that if ED would just release the F16 so we could fly it and just get a glimpse... they would just stay quite patiently until the F18 was done or very done but for sure they would be quiet and server operators could just not put them in the servers if it was too OP and unrealistic... All these things were plomised by the community in an effort to convince ED that they could safely and without repercussion... release the WIP F16. I'm sure ED saw a few $$ also... That may have nudged them a little... sure... But then... They did it. After that the community that was Pro 16 went absolutely ape crap and then started demanding that the F16 be worked on a feverish pace with no breaks, drop the 18, no holidays, NOW, NOW, NOW!!!!1!1!11!!!!ONE!!!1!!!! NOW! We got SCREWED!!! Will ED EVER complete this stupid viper I paid for after demanding that I be able to pay for it WAY before it was finished and WAY before the prior module was finished??? WTH ED??? W T H? So... ED moved a few devs off the 18 to please people. Then... The pace of Hornet development slowed down a bit. Then... The F18 crowd started saying "hey wait... The crowd said they wouldn't do this... what happened to the 18??? ED forgot about it???" Then it went... "We got SCREWED!!! Will ED EVER complete this stupid Hornet I paid for that I bought before the Viper was even ANNOUNCED??? WTH ED??? W T H?" So... Then ED moved the devs back to the 18 (not all of them mind you) so they could try to make it right regarding what they had done and what the community had plomised to NOT do. So... What REALLY happened... Was ED trying to please the community at EVERY step... and the community poking them with pitch forks. At every step. So... Yes ED learned from the communities lack of honor AND their own mistaken belief that the community would uphold their end of the deal and wait patiently. Now... We have people starting the same stuff regarding the APache. I've got no love for someone who gives ED "too much" grief on this subject. WE made it happen. US. You and me sir :). Sit back. Relax. Ed makes WONDERFUL sim planes. Be patient :).

"Not really thrilled about how soon the Apache preorder is coming. After the viper release its concerning how close it will be to the hind." Do keep in mind that they've been working the Apache for some time... AND they delayed the Hind for quite a long time. I think all as a response, in some part anyhow, to the bitching of the Viper owners who both screamed for Viper release ASAP and then also raised a stink about how the progress was too slow and they had been ripped off. "Just get it flyable with a 120 and a 9x and we'll be happy for now until the 18 is done I plomise" was the chant as I recall. Can never please everyone I suppose... Literally posted as I was typing that... :)... "I wasn't happy with the vipers release and I'm not too happy with its pace of development." Don't take it wrong Jester :)... but thank you for making my point. Still not happy

I posted that thread in the main wishlist thread... It's for a change in how the mouse interacts with head movement in VR.

All good suggestions but for me a very much prefer using the mouse to click things. The VR controllers are just kinda gimicky and wonky. trying to click a row of switches is horrible (KA-50 startup) and trying to click switches way out of the general field of view is also difficult :).

The middle click could work for sure... BUT... I'm a fan of automation with this sort of thing in a sim specifically because in VR buttons are a bit scarce. So... I would prefer to keep MMB clear if it would be possible to automate the re-centering at the same time that the mouse cursor disappears.

Also... Please bump this thread when you do so more people can see it :).

Instead of shift... They could add an extra bit to the clickable area when selecting the weapon... Like so...

In VR one needs to hold their head super steady to operate a cockpit function. I assume this works the same way with TiR but I've never used it so I don't know. Over the years I've used VR I've gotten "fairly" used to this and can now reliably click the obogs in the F-18 and other similarly positioned switches... but it's always a hassle. My proposal would be to disconnect the mouse cursor from the player's head's VR rotation and translation and instead track the mouse via a radian based on the general location of the game pilot's head. I understand this may create parallax issues when the "pilot" head and "player" head are not fairly close to each other depending on the current distance to the cursor. If that's the case and it is insurmountable then having the radian based on the player head location, but still removing the rotational relation to the player's head would be the desired method. In this way... you could get the mouse cursor "lost" behind your head :). The solution to that would be to re-center the mouse to the center of the VR view after the same period of inactivity that currently causes the mouse cursor to disappear. this way once you've stopped moving the mouse... the next time you need it, it will be right there in the center of your view.

5ephir0th is saying it will stop crashing if you enable windows 8 compatibility mode.

That's pretty much how all software is... Have you used Windows before?

Yeah it's all about how you perceive it. My best recommendation is to turn on the pilot and adjust so that the pilot's feet/knees feel about like they look like where yours would be. It helps if you have a bit of a cockpit so that you're "feeling" like your legs are out front of you like that too... If it's off it will kinda feel like you've shrunk or grown taller somehow...

WTF is Ryzen master?? Looked it up... WTF? Why didn't I know about that? Installing when I get home. Does it only work on AMD brand motherboard or any AMD chipset?