{"data":{"id":14133,"title":"Arena Commander V0.9 Status Update","rsi_url":"https:\/\/robertsspaceindustries.com\/comm-link\/transmission\/14133-Arena-Commander-V09-Status-Update","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-links\/14133","api_public_url":"https:\/\/api.star-citizen.wiki\/comm-links\/14133","channel":"Undefined","category":"Undefined","series":"None","images":[{"id":2158,"name":"Screen_114.jpg","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/qnhdd7kp79b0vr\/source\/Screen_114.jpg","alt":"","size":268745,"mime_type":"image\/jpeg","last_modified":"2014-09-10T19:21:11+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/2158","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/2158\/similar"}],"images_count":1,"translations":{"en_EN":"Greetings Citizens,\nWe are getting close! This afternoon we will kick off a Release Candidate build of Arena Commander V0.9. What that means is that we presently believe that our engineering teams should have eliminated all of the remaining blocker and critical bugs identified by our internal QA teams.\n\nWhat happens next? The RC build process takes roughly eight hours. For those unfamiliar with software development, generating a build is sort of like baking a cake: we\u2019ve put together all the ingredients into a pan and it\u2019s now in the oven. Later tonight, we\u2019ll take that piping hot copy of Arena Commander V0.9 and hand it over to QA for a final round of internal testing.\n\nWhy does it take so long to bake this cake? As our codebase and asset sizes grow, the amount of time to build the code with full optimizations and do a full clean build of the assets into the pak files takes longer and longer. (We do a clean build for release candidates for QA to test to avoid compiler and toolchain bugs with incremental builds.)\n\nThen, to make the download smaller and faster for our backers, we run a patch building process that compares the previous release\u2019s files to the new release \u2013 this binary delta comparison is an expensive process that also takes longer as the size of the code and assets grow. This patching process makes it so backers don\u2019t need to download the whole game (or even whole files that have only been slightly changed) for the new release \u2013 just the differences.\n\nNext, we need to distribute this patch data to all of our studios over the Internet so QA and developers throughout the company can test the build. Unfortunately, all of these steps added together makes the whole process take many hours.\n\nBut while it takes eight hours today, the system will change in the future as Star Citizen gets bigger and more elaborate! We plan to make the process faster to decrease the build->test->fix->repeat cycle for release candidates \u2013 we have efforts both in-progress and planned for the future to decrease the amount of time the full clean release build process takes. These improvements will also help development efforts earlier in the development process by increasing the rate at with QA and developers receive test builds.\n\nUntil that happens, we do have an ace in the hole that helps maximize testing time! Since we have QA teams in Manchester and Austin, we can effectively test through the night. The UK team will pick up the Release Candidate to put it through its paces. By the time the teams in Austin and Santa Monica get into work on Thursday, we\u2019ll know how that testing cycle went. Should everything work as expected, the build is then propagated to the public release channel.\n\nAt that point, we\u2019re really, really close\u2026 but things can still go wrong. At this step QA will do a \u2018real life\u2019 test of the game: downloading it from the server just like a backer to make sure it works correctly in the wild. It\u2019s rare, but we\u2019ve seen new blockers appear at this step in the process before: aspects of the real server environment we can\u2019t emulate in the office that make themselves seen at the last minute.\n\nOnce QA gives us the final \u2018thumbs up\u2019 on the propagated build, we will flip the final switch and the patch will become available. If all goes as planned then you can expect to see Arena Commander V0.9 immediately thereafter. Should the unexpected happen, our bug smashers leap back into action to try and fix issues as quickly as possible\u2026 and then the Release Candidate cycle will begin again. We will keep you updated as to the status either way!","de_DE":"Gr\u00fc\u00dfe B\u00fcrger,\nWir sind nah dran! Heute Nachmittag werden wir einen Release Candidate Build von Arena Commander V0.9 starten. Das bedeutet, dass wir derzeit der Meinung sind, dass unsere Entwicklungsteams alle verbleibenden Blocker und kritischen Fehler, die von unseren internen QS-Teams identifiziert wurden, h\u00e4tten beseitigen sollen.\n\nWas passiert als n\u00e4chstes? Der RC-Build-Prozess dauert etwa acht Stunden. F\u00fcr diejenigen, die mit Softwareentwicklung nicht vertraut sind, ist das Erstellen eines Builds so etwas wie das Backen eines Kuchens: Wir haben alle Zutaten in einer Pfanne zusammengetragen und es ist jetzt im Ofen. Sp\u00e4ter am Abend werden wir diese hei\u00dfe Kopie von Arena Commander V0.9 nehmen und sie der Qualit\u00e4tssicherung f\u00fcr eine letzte Runde der internen Tests \u00fcbergeben.\n\nWarum dauert es so lange, diesen Kuchen zu backen? Mit zunehmender Gr\u00f6\u00dfe unserer Codebasis und unserer Assets dauert es immer l\u00e4nger, den Code mit vollst\u00e4ndigen Optimierungen zu erstellen und die Assets vollst\u00e4ndig sauber in die Pak-Dateien zu integrieren. (Wir f\u00fchren einen Clean Build f\u00fcr Release Candidates f\u00fcr QA durch, um Compiler- und Toolchain-Bugs mit inkrementellen Builds zu vermeiden.)\n\nUm den Download f\u00fcr unsere Geldgeber kleiner und schneller zu machen, f\u00fchren wir dann einen Patch-Building-Prozess durch, der die Dateien der vorherigen Version mit der neuen Version vergleicht - dieser bin\u00e4re Delta-Vergleich ist ein teurer Prozess, der auch l\u00e4nger dauert, je gr\u00f6\u00dfer der Code und die Assets werden. Dieser Patch-Prozess macht es so, dass die Geldgeber nicht das ganze Spiel (oder sogar ganze Dateien, die nur leicht ge\u00e4ndert wurden) f\u00fcr die neue Version herunterladen m\u00fcssen - nur die Unterschiede.\n\nAls n\u00e4chstes m\u00fcssen wir diese Patch-Daten an alle unsere Studios \u00fcber das Internet verteilen, damit QA und Entwickler im gesamten Unternehmen den Build testen k\u00f6nnen. Leider machen alle diese Schritte zusammengenommen den gesamten Prozess viele Stunden in Anspruch nehmen.\n\nAber w\u00e4hrend es heute acht Stunden dauert, wird sich das System in Zukunft \u00e4ndern, wenn Star Citizen gr\u00f6\u00dfer und aufw\u00e4ndiger wird! Wir planen, den Prozess zu beschleunigen, um den Build->Test->Fix->Wiederholungszyklus f\u00fcr Release-Kandidaten zu verk\u00fcrzen - wir haben sowohl in Arbeit als auch f\u00fcr die Zukunft Bem\u00fchungen geplant, um die Zeitspanne zu verk\u00fcrzen, die der vollst\u00e4ndige Clean-Release-Buildungsprozess ben\u00f6tigt. Diese Verbesserungen werden auch die Entwicklungsbem\u00fchungen zu einem fr\u00fcheren Zeitpunkt im Entwicklungsprozess unterst\u00fctzen, indem sie die Rate bei der Qualit\u00e4tssicherung erh\u00f6hen und Entwickler Testbuilds erhalten.\n\nBis das passiert, haben wir ein Ass im Loch, das hilft, die Testzeit zu maximieren! Da wir QS-Teams in Manchester und Austin haben, k\u00f6nnen wir die ganze Nacht \u00fcber effektiv testen. Das britische Team wird den Release Candidate abholen, um ihn auf Herz und Nieren zu pr\u00fcfen. Wenn die Teams in Austin und Santa Monica am Donnerstag in die Arbeit gehen, werden wir wissen, wie dieser Testzyklus verlaufen ist. Sollte alles wie erwartet funktionieren, wird der Build dann an den \u00f6ffentlichen Freigabekanal weitergeleitet.\n\nAn diesem Punkt sind wir uns wirklich, wirklich nahe.... aber die Dinge k\u00f6nnen immer noch schief gehen. In diesem Schritt f\u00fchrt QA einen 'real life' Test des Spiels durch: es wird wie ein Backer vom Server heruntergeladen, um sicherzustellen, dass es in der Wildnis korrekt funktioniert. Es ist selten, aber wir haben in diesem Schritt des Prozesses schon einmal neue Blocker gesehen: Aspekte der realen Serverumgebung, die wir im B\u00fcro nicht nachahmen k\u00f6nnen und die sich in letzter Minute zeigen.\n\nSobald die QA uns die letzten \"Daumen hoch\" f\u00fcr den propagierten Build gibt, werden wir den letzten Schalter umlegen und der Patch wird verf\u00fcgbar. Wenn alles wie geplant verl\u00e4uft, k\u00f6nnen Sie sofort danach mit Arena Commander V0.9 rechnen. Sollte das Unerwartete passieren, springen unsere Bug Smasher wieder in Aktion, um zu versuchen, Probleme so schnell wie m\u00f6glich zu beheben.... und dann beginnt der Release Candidate Zyklus von vorne. Wir werden Sie auf jeden Fall \u00fcber den Status auf dem Laufenden halten!","zh_CN":"Greetings Citizens,\nWe are getting close! This afternoon we will kick off a Release Candidate build of Arena Commander V0.9. What that means is that we presently believe that our engineering teams should have eliminated all of the remaining blocker and critical bugs identified by our internal QA teams.\n\nWhat happens next? The RC build process takes roughly eight hours. For those unfamiliar with software development, generating a build is sort of like baking a cake: we\u2019ve put together all the ingredients into a pan and it\u2019s now in the oven. Later tonight, we\u2019ll take that piping hot copy of Arena Commander V0.9 and hand it over to QA for a final round of internal testing.\n\nWhy does it take so long to bake this cake? As our codebase and asset sizes grow, the amount of time to build the code with full optimizations and do a full clean build of the assets into the pak files takes longer and longer. (We do a clean build for release candidates for QA to test to avoid compiler and toolchain bugs with incremental builds.)\n\nThen, to make the download smaller and faster for our backers, we run a patch building process that compares the previous release\u2019s files to the new release \u2013 this binary delta comparison is an expensive process that also takes longer as the size of the code and assets grow. This patching process makes it so backers don\u2019t need to download the whole game (or even whole files that have only been slightly changed) for the new release \u2013 just the differences.\n\nNext, we need to distribute this patch data to all of our studios over the Internet so QA and developers throughout the company can test the build. Unfortunately, all of these steps added together makes the whole process take many hours.\n\nBut while it takes eight hours today, the system will change in the future as Star Citizen gets bigger and more elaborate! We plan to make the process faster to decrease the build->test->fix->repeat cycle for release candidates \u2013 we have efforts both in-progress and planned for the future to decrease the amount of time the full clean release build process takes. These improvements will also help development efforts earlier in the development process by increasing the rate at with QA and developers receive test builds.\n\nUntil that happens, we do have an ace in the hole that helps maximize testing time! Since we have QA teams in Manchester and Austin, we can effectively test through the night. The UK team will pick up the Release Candidate to put it through its paces. By the time the teams in Austin and Santa Monica get into work on Thursday, we\u2019ll know how that testing cycle went. Should everything work as expected, the build is then propagated to the public release channel.\n\nAt that point, we\u2019re really, really close\u2026 but things can still go wrong. At this step QA will do a \u2018real life\u2019 test of the game: downloading it from the server just like a backer to make sure it works correctly in the wild. It\u2019s rare, but we\u2019ve seen new blockers appear at this step in the process before: aspects of the real server environment we can\u2019t emulate in the office that make themselves seen at the last minute.\n\nOnce QA gives us the final \u2018thumbs up\u2019 on the propagated build, we will flip the final switch and the patch will become available. If all goes as planned then you can expect to see Arena Commander V0.9 immediately thereafter. Should the unexpected happen, our bug smashers leap back into action to try and fix issues as quickly as possible\u2026 and then the Release Candidate cycle will begin again. We will keep you updated as to the status either way!"},"links_count":0,"comment_count":333,"created_at":"2014-09-10T00:00:00+00:00","created_at_human":"11 years ago"},"meta":{"processed_at":"2026-05-09 03:54:27","valid_relations":["images","links"],"prev_id":14132,"next_id":14134}}