Larkis

And? Maybe you could see goof old stennis too from this perspective? Maybe its just bether contrast. Ma by its just a LOD/Size fix and now its more realistic? Maybe wait and see for yourself before you run into the forum before blaming ED for adding visiual cheats?

Maybe you can say you want a Case3 Approach?

I think it would make sense that the signal charlie call put the carrier into recovery mode

If you dont use it you only get fair ratings

The exact Problem is Ticket bug/DoCarr-2588. Status "In progress" and label is Blocker.

Sometimes i do. Last week i thanks thev worker in our local supermarket. A year ago i think a similar way. But my currently employment is really good in give me the feeling "you do great work, your work is important for our business, we appriciate your efford, THANK YOU". And it feels so good and motivate so much. Since them i also try to finde nice words or at lest be polite and nice, even when i talking to support cause my internet crashed again. Be nice and kind, respecting other peoples work. That is something that seems lost these days- In special in those corona says which a really hard for everyone. Bringing extra effort on easter-weekend to release on time is something that should be mentioned. To be honest, as a Developer Point of view. Transparency is the worst. 99,9% of all customers can't understand what we want them to tell. To me this "Communication Problem" is natural behaviour. Its bussiness as usual that a few days before release the board is full of bugs. Even 10 BLocker Bugs menas nothing if they could fixxed them until release. Beeing a blocker dont meant it is hard to fix. Giving this infos to customers make them think they understand what happens. Then thy start to ask questions, they start to give suggestions. then the Devs need to talk to them, need to explain why there ideas are bullshit. In my experienciese you loose 40-50% efficiency in bug fixxing when you need to talk to other people about what you do. In my eyes ED react very good. They tell that there are problems, they tell that they still aim on 15 but maybe it wont happen. And until there see a chance to release it on time they try there best. And when it dont happens, they take a depth breath, relaxe 1-2 days, and restart bugfixxing again. And dont forget we talk about open beta branch and not stable. Its called open beta for a reason, even 99% of the community seems forget about that. Im not a fan of such comparisons cause it build up the feeling that some mentions are more worth then others. But be my guest: F18 F14 Supercarrier Harrier A10C Viggen Mi-8 Huey Black Shark Gazelle SU-27 F15-C NTTR Map Persion Gulf Map Nomandy Map WW2 Asset pack Combined Arms Think you outperform me by 6 modules. Gratulation

I think if they had a date that is 100% possilbe they would talk it to us.

Do speak honestly. Yes i do. Im a also a software developer and it happens much more often then i want to admit. More like "ok everything works fine now. Let us make a last test with condorion X abd Y abd then... oh shi...." Sometimes its just murphys law. An example that really happened last week: some Guy made an routine update to pur servers. That guy has some unnoticed errors in his update. Cause of this errors our live database get cleaned up completly. No problem just roll in the yesterday backup and... what do you mean the auto-backup-function is broken and the last backup is feom early march? In the end we frankensteined a backup from different local dev repositories but it was so rushed that we need to restart the QA of 3 softwares to check everything still work as accepted. What mist peopke dont know is that QA is not only a one way test. They must retest everything to check that a big fix dont break anything else. Sometimes it happebs that an important bugfix crash something other that works fine before. You had one last bug on the list, fix it and you get 3 new blocker bugs. That happens too.

Do you ask ATC for landing clearense? Do you bolter before the ship went dark?

Hey Wags, thanks gor the answer. Any ideas how big the Delay will be?

There is an easy answer. They thought they could make it in time. They allways said "they aim on the 15th". That means there are bugs that would prevent a release but they are confident to fix them in time.

+1 Singleplayer Release :)

No need for a crunch would be an awesome dream. But sadly it dont match with reality. The point is that you really cant estimate how long a project need to be finished. Mostly you can guess it but there could allways be something that put you off the rail. But mostly deathlines are fix and not changeable. So you need to crunch. that is how the job works. Simple examples: You build websites and sell them. Example 1: Your customer is a restaurant which change the food and styling and want his website to match that. So on reopening day the new website must go online. Now you got ill for 2 Weeks, klling a lot time you need to finish the website. Now you need to crunch to get erverything right. Example 2: You get an order for a website with some fance stuff. You estimate 60 Days for production and calculate the payment on it. Now if you need longer then 60h you loose money. Then the fancy stuff is fancier then calculatet prior, you need 80h to finish it. What are you do? Working unpayed overtime or start to rush things to keep inside the 60hours. Even on that basic level you cant avoid the crunch. Its part of the job.

I presume its all on one supercarrier-branch

I dont think that an awacs ca do this. Ground clutter on Pulsesingle would be to extreme and i dont think that vehicles or solderis are fast enough to pass the Pulsedouble filter

Maybe we can get then only an singleplayer release? :D "just kidding"

Then Annoucememt comes when it comes. Imo its a goof sign that there still was none.

Maybe cause i am also a software developer. I know what it means to crunch the final day before release. When there is that last sucker of a blocker bug which dont go away. When you have a perfect branch and the merge into master produce dozens of merge conflicts killing the release plan in the last 10 minutes before cheduled release. I know how it feels. And cause of that a BIG THANK YOU from me. I really appriciate that the developer don't go the easy way and just delay it. I appriciate that they work trough the night to get it done. For us. For your community. Sadly there are a lot childich impatient persons around but be sure that not everyone is like this and i hope there are enough persons wo acknowledge the effort you put into this module this night. I wish you a good hunt and a well sleep after the crunch is over. I can wait until its done. Maybe tomorrow, maybe next week? I waited so long, i can wait a little bit longer. Greetings Larkis

Why waiting?

Ich benutze den Movemaster nur für Radio (und halt die Außenansichten wenn kein Radio offen ist um das Hauptmenü zu öffnen) Ansonsten habe ich alles entweder auf dem Hotas liegen oder benutze die Maus.

You dont need Case 1 Pattern to train fly the ball. Just start the Case1 Quickstart and do a Case3 Approach

I think it terms on role. The Mi8 need 3 persons and is a really click-switch-porn while the Huey is very very simplistic and very fast to start.

Do you use a catapult to start from the carrier? And you dont need to reset trimm. Just raise flaps and gear and hold afterburner until you are above 250kn. Use the stick to hold the nose down and dont climb above 500ft until you are 8nm away.

Ich nutze den Movemaster: https://www.movemaster.biz/ Mit den Fingern nbesieke ich F1-F10 nsch vorne Schieben ist Comm1 und nach hinten Comm2

But maybe... just an idea.... they are at home with there family and are on holiday?