M1Combat

This is only the early access release sir... If you want something "without errors" you might choose to wait for the actual release of the module probably a year or so from now. Early access doesn't mean "Hey... if we finish it early then we'll let all the folks who paid already have it before the others..." It means you have access at some point BEFORE it is FINISHED.

@NineLine Seems an easy fix?? I love the Mustang...

Use other players in MP. Don't worry about your "KDR". Be disciplined. The 51 has some advantage at high altitude. Climb, look for targets, boom and zoom. Once you can do that while staying disciplined and high speed... You can maybe start turning a tiny bit... but generally stay high speed and don't fight under about 17K feet.

Week after next...

You can see it however you want and they may have said something about early autumn but that's beside the point (and I'd love to be proven wrong if you can do so...). What actually happened is that Wags mentioned that it was actually flyable in a video and the community came unhinged demanding that it be released right now (Not pointing the finger at you... not sure why you're taking this personally) and that they would surely not complain about the state of the module until the Hornet was in a good place. They "understand it's EA and the Hornet comes first etc etc...". So ED decided to let it fly. I agree whole heartedly that they shouldn't have... but the community was very vocal about it especially since people had paid for it already and it was "flyable". Well... we all know now that it was indeed "flyable" and that was about it. I'm not attempting to exonerate ED from mistakes they made. Don't get this twisted :). I'm only saying that ED did NOT plan to release the Viper the way it happened from the beginning. They planned on getting it further along (and you know even if they did mention autumn... they would have pushed that back... I mean seriously) before any EA took place. By EA I don't mean early purchase... I mean early "access". I get tired of hearing people say BS and throw ED under the bus when what REALLY happened is ED made a mistake and did what the community asked for. Then the community turned on them. Both the Viper and Hornet folks, but for different reasons. If you feel some details are off in my understanding... that's great... but the overall arc of the story... spot on sir. Spot on. That's what happened.

"After the F16 I'm in the 'once bitten twice shy' camp." The F16 is still in early access... It hasn't "dropped" yet. Early access doesn't mean "Hey if you pay us now we'll give you access to a finished product that we'll just arbitrarily add things to in order to make it over finished...". There STILL is no date for the Viper to be finished. I believe the best we have is "this year". It means it's far from finished. Regarding the viper specifically... ED had a release window a mile wide (like a year or more, just for an EA release... not even an actual release) and the community DEMANDED that they EA release it in SUPER early "it's just barely flyable at the moment" access. You have nothing to be shy about unless you didn't understand those things when you purchased... but it's pretty clear when you purchase IMO. Please don't feel like I'm just singling you out... I'm just tired of hearing the community complain about a problem they caused. I don't mean you individually... but the facts are there. The community raised a "stink" to get ED to release the Viper WAY early promising they would absolutely 100% NOT complain when it didn't get worked on until the Hornet was much further along. They (the community) did not hold up their end of the bargain which hindered the development of the Hornet AND made a large number of people upset with ED because their unrealistic expectations were unmet.

Of course you can feel how you like but you still miss an important point I made. ED didn't have a "release date" for EA for the Viper at first. Of course they had a EA release window. A "date" didn't come until they mentioned randomly that it was "flyable". Once that simple comment was said the community came unhinged and pressured ED into an EARLY early access release promising they wouldn't complain about it no matter how bad it was because they knew the focus had to be on the hornet for now... but "Just let us fly it" and we'll be fine and let you go about work on the Hornet. I mean I get it... not every single person who's ever installed DCS was on that train... but it was a pretty sizable train friend :)... It was... ED caved to the demands. The people did NOT hold up their end of the bargain. They immediately started complaining that "nothing was happening" with the Viper. So ED moved some devs to the Viper. Then the Hornet folks started saying "Hey wait a dang minute now..." so ED moved some devs back to the Hornet. Look all I'm saying is that ED's mistake was doing what the community demanded. Those are just facts. I'm not trying to say the Viper wasn't released WAY the eff too early. I'm only talking about WHY ED did that. It wasn't because they cooked up the idea on their own...

My bolding above - No Newy. No. People are NOT right to complain about the Viper launch. The Viper was only launched in that state because the people demanded it... Not because ED really wanted to. If there's something about the Viper launch that people should "rightly" complain about it was the very fact that people demanded it so loudly that ED ultimately released it almost certainly against their better judgement. OK... Maybe you can say it's right to complain about the Viper launch... but ONLY if it's properly couched in the context that the real problem was the people's demands and tehn the subsequent uproar from both the Viper folks saying "WTH it's not done WAAAH" AND the Hornet folks saying "Wait a dang minute... Are you even still working on the Hornet?". This was not "caused" by ED. You know all this and I'm sure at this point it's largely semantics where we disagree :)... but I am very firmly of the mindset that any complaining of the Viper launch absolutely MUST be put into that context. I do respect your interest in taking it on the chin so to speak and not telling the "folks" how it was their doing... So Kudos to that... But I'm happy to do it for you :). "release some of the pressure on the Apache deadline." Sir... There is no Apache "deadline". That only exists in the minds of people who find themselves disappointed by their lack of understanding of what Early Access means and the framework of how it works with Eagle Dynamics. ED suggested a likely "early" release timeframe. You created this "deadline" you speak of. All of that said... I'm SUPER happy to hear all of the gnashing of teeth over this. ONLY because it means the module is HOTLY anticipated and is going to sell "quite well" and will secure the future development and release of other modules that we all want in the combat sim community.

Wow... That's a very large victim mentality and entitlement drive you two (and many others... don't get me wrong...) have going on there. The older I get the more amused I am by people walking THEMSELVES right through a door that hits them in the ass. It was inevitable I suppose. You know those vids on youtube where kids get taken out by stuff like maybe a cat pounces on them or they get run into by an RC car and wiped out or something... I love those vids. Makes sence that I enjoy kids getting butt hurt in other ways too I guess... Can we get one more delay after this one ED??? Just for the kids???

I like how people think it's just a "simple" different shader or something :)... When really every single object in the game has to be touched to add the heat signature, receive adjustment for time of day and specific cooling characteristics based on how long they've been shut down etc... This is the difference between a real "sim" and a game "sim" . I get it... it's a game... but the development approach is what matters and sets it apart. As I recall didn't the Viper already get the new FLIR but work on the related assets (every object in the game) to make it look right is still ongoing?

He didn't say anything about bullets or fuel type either. Probably can't even fly until we get fuel and I think likely the gun won't work at all... Also... he said "New Rotor Animations"... WTF @Wags Are we not going to have ANY other animations at ALLL?????!!1!11!!!ONE!!11!! I'm sorry. I couldn't help it.

"hand" tracking or controller tracking?

I mean you did see the yeah?? It was a bit tongue in cheek but yeah... Definition 2 is I'm sure hat he meant :).

"Basically, a different FCS software and no wing-fold mech allow the Hornet to sustain 9g." Sustain??? Did they put 11 more engines on it too?

Nah... Useless proprietary crap. Bad for the consumer. ED has the right stance on this. You can't see that though. The industry needs more competition not less. AMD's solution is not proprietary. It works on AMD and Nvidia GPU's and is just as good or close enough that unless you're benchmarking it doesn't matter. It promotes competition where it matters. GPU speed but not proprietary features. I've been watching the GPU wars unfold for long enough that I've realized AMD's approach to allowing their solutions to beneefit everyone is better... for everyone... Also... Built in VOIP will be huge. You can't see that either but it doesn't matter. It will be. Oh and I think I asked for it so... Yeah... Swing and a miss eh?

Native res will likely be better for DCS due to the idea that any time you use any AA or SS technique you're either interpolating data that isn't there or you're scaling data that is there... Because of that you can only lose or change data relative to where you started... And in both cases you can only reduce your ability to spot the enemy. You either miss them with AA or blur/camouflage them with SS (once it's scaled down). At least that's how I see it... It of course looks nice... For sure...

They turn it off on the ship becasue the ships movement messes with it.

OK @NineLine you're right that probably could have turned out negative but just understand that wasn't my point. I thought it would be fun... I'm assuming you moved it here...

OK... 8 hours in and we're at 2.6K views. I'm taking bets on how many views it gets before we get a 2022 update. Or more correctly how many views it has when I look at it after it gets an update. Very important distinction that... I'm going to say 11,500 and it will be Tuesday. Winner (closest guess on number of views but feel free to speculate about what day if you like, edited posts are disqualified) gets a single like, from me, on a post within THIS thread. Or I do nothing... My choice. I'll probably like a post though... But I can't promise it will be one of yours... If there are any conflicts about the rules.... Whatever. What I say goes. That's really the rule. Feel free to write a scathing post if you disagree but do NOT edit it as then I'll be forced to disregard.

Yeah... double edged sword though

"Has anybody else caught that he has trim set to default? " Hmm... It appears MAYBE you're the first to catch that LOL

Preferably no breaks, but all the brakes... Sorry...

I made a face gasket out of basically wet-suit material for my old HTC Vive... It worked GREAT and did exactly what this does via moving your eye closer to the lense. Honestly though... The primary benefit is NOT the FoV increase but the sweet spot size gets larger as well. Now that I think about it I can probably use my old Vive face gasket on my reverb... Why didn't I think of that? Oh yeah... because the reverb was soo much better than the vive to start with LOL... But I will now :).

I do find it helps to close DCS and re-open between MP servers... but not always.