DistantStatic

Why are you deflecting? This was obviously a stab a people who would not pre-order things they had no idea the end result would look like. ED clearly made a complete attempt to discredit a release date that was merely a week off to create more ambiguity as to the actual release of the product. It was stated in the previous weekend news the release date would be announced the following week. And then in the follow weekend news, you make no mention about it at all, instead post the youtube trailer where it states deep in the description the pre-order would end in 24 hours, 24 hours before the news post. :huh:??? Meanwhile people who were waiting to make an informed purchase? "Screw them. How dare they not give us money before we give a release date or release trailer!!" I'm glad I did not pre-order. I don't support business practices like this. I guess I'm the clown for religiously reading weekend news for over the past year scanning for any mention of the viper. Was even going to ask for an extension as I was at work when the news post was made, but later thought better of it. Learned my lesson real well. Never again.

Oh man. This is still going on? Maybe in December boys and girls :megalol:

Holy what a way to go. R.I.P. poor guy. Least he died doing something he loved.

I've come to the conclusion that nothing is ever being released. There's actually a better chance the world ends in nuclear war atm than ED dropping a module.:doh:

RAZBAM(EDIT: might be LN? this is confusing. Someone said something or speculated something or something something interest in something) apparently wanted to do it but got denied the licensing for unknown reasons. Russian military have been rather secretive recently so that's probably the reason for it.

Hey there Mirknir, not sure if someone has posted this already but something seems to be happening with spawns; the plane's hitboxes are colliding. Probably a DCS issue but can't be sure. First time this happened, I was taxi-ing out of the hanger and the hitbox for my plane came into contact with a currently spawning craft that was being generated inside of a hanger. Same thing just happened to me again, except this time I was the one spawning inside a hanger.

There's no conspiracy theory here. If you're referring to the claims about how delays and silence affect market performance it's simply knowing how markets operate (heck just look at recent prominent game releases although every situation is different it is not hard to see how lessons learned from them apply). I forgot to multiquote here (and I'm ridiculously lazy) But, delays create frustration, and you don't wanna bite the hand that feeds (ie. the paying consumer that makes all that year's work worth it. not sure if they turn a profit or not but the less of a profit it turns the more every dollar counts towards paying back all that time they spent away from their lives). In reality all I'm trying to say here is when big name modules like the F-14 and F-18 come about they will make a big splash, not just in our little niche gaming community. The F-14 is highly iconic in pop culture and its quite possible these releases may bring in new players to our small community of simmer (especially our even smaller community of combat simmers!). If said people were interested on buying the products it is a very real possibility (understatement) they'll forget it even exists. Also taking into account of advertising algorithms work, unless they keep coming back and accessing information based on a plane or sim within a certain amount of time, that news phases out of their ad scope which means it becomes increasingly more difficult to reach those consumers. All in all I'm not saying its easy for a small 3rd party developer to implement all these things and find that fine line between worst case scenario and best case scenario release time-frames or even how to market they product as effectively as other game industries can where there is money to pay for dedicated marketing specialists who dig through data all day. In fact, its I've been highly impressed with the amount of work each of these developer teams have been able to do (and thankful too!! :joystick::pilotfly:) I'm just saying what's going on now isn't working and offered some insight to a fellow forum poster. Sidenote: I've also realized I've turned to writing ridiculously long and detailed posts rather than lurking. But I'm just going to attribute that to my love for flying (all I do nowadays is fly planes, make music, and program) :helpsmilie:

Because people may be holding on to that money to give the module as a Christmas present, time constraints, some sort of expectation, reduced frustrations after day-to-day checking for news and seeing no Viggen, (off chance but still) maybe someone was holding off on vacation days and wanted to save them for the viggen release and go ham.... They will displease the community with delays? If they hold on to the product for an eternity after promising a release and never providing a timeframe or date it just seems like vaporware. Subliminally reduces the reality of the product at the same time hype goes down. Especially with silence, the standing of the developer goes down. This built up demoralization ends up making the "hype-leak" larger and draining more hype from the community. In the ends this ends up with more headaches for everyone with no benefit in the end (if anything more negatives). In the end this conditions the consumer to be frustrated from the time from announcement for development down to the actual release date with sharp increases during these times of delays. I'd rather be an informed and slightly disappointed consumer than frustrated and left in the dark. If they weren't prepared for a release, making announcements on products prematurely when they don't even have a demo reel of the aircraft is on them. Half these 3rd party developers just drop plane announcements randomly because they just felt they may work on that at some point. If each plane is going to take 1-2 years to complete, announcing development on 3 planes ends up being up to 3-6 years of development schedule baring delays and parallel development on updating, bugfixing, and unforeseen circumstances. Not only is it hard to find people who play the same game/simulator for years, but it is hard to ind a product that has survived 10 years without major overhauls etc... These developer also have to then bring their older aircraft to newer DCS standards in future DCS releases. This also brings up another point. Will DCS last 5 more years? 10 more years? will it end up being a different engine altogether where all previous aircraft and systems may also completely have to be redone due to new engine API's? There's plenty of good reason to NOT announce things until you're good and ready and giving time estimates is part of ANY job/career (Especially programming! I remember having to go through the trouble of finding my speed in my first development job compared to my proprietary projects which I could work on at my leisure). Understandably you have to deal with more bureaucratic red tape when requesting information on these combat aircraft, but its not their first rodeo per say. In fact, if there's announcements on development when necessary documentation (or anything pertinent for that matter) has not been secured for development then that's just irresponsibility. Don't use "Devil's advocate" as a way to excuse lack of critical thinking and research.

I wanna fly with my toes:joystick::mad::book::doh::music_whistling: :pilotfly:

I never installed any mods whatsoever and I am having the same issues. It is not his mods. Specific issues that are outstanding are the disappearing mouse which also leads to no backslash radio menu which renders the game unplayable in clickable modules. The extent of my experience in 1.5.5 is the KA-50 as I sat down and convinced myself to finally learn the module shortly before. side note: I don't understand why some people are so quick to try and pin the bugs on the user; especially after a substantial update.