Um alle Funktionen des Forums nutzen zu können, sollten Sie sich registrieren. Wenn Sie schon regstriert sind, sollten Sie sich anmelden.
Datenschutzerklärung: Hier
Einstellungsmöglichkeiten zur Privatsphäre finden Sie in Ihren Einstellungen.
Einen maschinenlesbaren Export Ihrer Daten können Sie in Ihrem Profil anfordern. Hier
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
Star Citizen 1.1 is here! Today’s release adds a number of new features and new ships… and sets the stage for big things to come.
IMPORTANT : To play 1.1 you will need to reinstall Star Citizen entirely. More on why and how to do it, including detailed instructions in English, French and German, in this post.
New Ships
Star Citizen 1.1 includes the addition of two new ships to your armada! The Aegis Dynamics Retaliator will now appear in the Hangar and the Gladius light fighter is now available for combat in Arena Commander. If you fly a Gladius, we’re eager to hear how you think it stacks up in combat!
The Aegis Retaliator
The Aegis Gladius
New Manual
In honor of today’s release, we have issued a new version of the Arena Commander manual, which is now available here.
New Controls
Starting with 1.1, you no longer access Arena Commander through your ships. Instead, every Hangar is now equipped with a SimPod that will let you play Arena Commander and, soon, Star Marine.
New Systems
Most importantly, Star Citizen 1.1 includes the launch of a number of new systems. Some, like the 64-bit conversion, are entirely ‘under the hood,’ while others are available for use today. The game now includes a new character rig, with smoother and better animations. The new dynamic damage system has been launched with the Gladius, and will eventually be applied to all old and new ships. Arena Commander also now features a landing system (detailed below), a new Mounts system with the introduction of Gimbal Mounts to the store and, likely most interesting for today’s pilot, the launch of the REC system. This is our first pass at rental credits, aimed to allow payment-free progression in Arena Commander. You can expect plenty of balancing in the coming days, so get out there and provide your feedback! As promised, all existing backers will get 5,000 REC to start things off!
You can see the entire change list in the 1.1 patch notes here.
Landing your Starship
Introducing the new Landing System. It’s a first pass and, as usual, your feedback will be invaluable, but it is the foundation from which we will build from.
Toggled quickly on and off, the Landing System switches the ship’s targeting system from combat targets to nearby landing zones. Any nearby zones are highlighted in world and on the radar. The closest zone is automatically targeted, but can be cycled with the usual targeting keys.
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
There are two types of landing zone: governed and ungoverned.
Governed points require the requesting of permission to land, ungoverned don’t.
For testing purposes, the landing zones in Free Flight have been set up as governed, meaning pilots should request permission to land. Obviously there is nothing preventing players from landing without permission, but they should expect to be punished if trying this in Star Citizen – whether by monetary fine or, in extreme circumstances, death by automated turrets.
To request permission to land ships must be in range of the zone. In Free Flight players will be granted permission automatically. On receiving permission, the radar will be replaced with a landing helper interface. This first guides the ship to the landing zone and then, once the ship is inside the bounds of the zone, provides the ship with guidance on positioning and orientation.
The landing system can be switched between two modes: Automated and Manual.
Automated: Once inside the bounds of the landing zone the ship will decelerate, align, position and land itself without the need for pilot input.
Manual: Practiced pilots may find they are able to achieve a quicker touchdown in Manual mode than would be possible in the more safety-conscious Automated mode, but they will have to do so without any autopilot assists.
Pilots can switch between these modes at any point during the landing process in case they become overwhelmed by the demands of Manual mode or frustrated by Automated mode’s hand-holding.
Take-off
To take-off from governed landing zones pilots should request launch permission. They can of course ignore protocol and launch without permission by simply strafing vertically, but this may be punished in Star Citizen.
Once permission has been granted your ship will automatically raise itself to a safe launch height before your choice of mode (Manual, Assisted and Automated) kicks in.
Future releases
We will continue to iterate and expand upon this basic system. In future releases we intend to include more complex landing and take-off situations such as hangars and vertical shafts through airlocks. This system will also be extended to docking and work in exactly the same way.
It is to be noted that there will be plenty of places in the PU which are not designated landing zone, but which can be landed on regardless. In these cases the ship’s landing gear deploys automatically allowing you to set down on most flat surfaces.
1. Play public Arena Commander matches (minus Free Flight) to earn REC. Completing objectives and winning matches earn more.
2. REC total and a log for an accounts REC changes can be found in the billing section of the website HERE
3. Once enough REC is earned, ships and their components can be rented HERE
4. After something is purchased, the account will need to log out and then log back in to initialize the changes (it also helps to delete the user folder any time something changes on an account)
5. Upon logging back in, the ship or components will be available for use.
6. Each rental can be used for 7 days.
A day will be consumed any time an account logs into an Arena Commander game mode
This happens in both single and multiplayer to prevent unlimited item rentals
This will cause a 24 hour timer to start that can be viewed on the website
Another day cannot be consumed while items have a 24 hour timer active
This occurs regardless if they use the rented item or not and will activate the timer for all rented items on the account
The information for this is communicated 30 seconds after a match starts
7. If someone wants to keep track of what ships and components they have rented as well as which items have an active timer, that information can be found HERE
8. This location also allows the amount of days that are left on a rental to be renewed for a discounted price. This can be found by clicking on the arrow at the right to expand the menu
With the launch of Star Citizen 1.1, we are asking that backers re-install the game rather than update using the older launcher. The game features an all-new installer, which will make for a more solid installation. Think of this as spring cleaning for Star Citizen, clearing out over a year’s worth of accumulated data generated by previous patches.
The Star Citizen QA team has put together instructions for this process, available below in English, French and German. We understand the inconvenience, and would only ask this if it were necessary for the best possible Star Citizen experience.
Star Citizen 1.1 Installation Guide (English)
How Re-Installing Star Citizen will help you:
After 2 years of development Star Citizen has grown and matured considerably. Unfortunately, this hasn’t been the case with installing or patching.
However, today with the release of the 1.1.0 build, we are attempting to clean up some of the problems players have been seeing when trying to download and play the game.
We have released a new installer and switched our CDN to Amazon Cloudfront. Over 80% of our Metafile issues will be fixed with this, and it’s also the foundation for a future update to eliminate the notorious “Delete your USER folder” fix.
On a more technical level:
The new installer fixes many small installation bugs, crashes, and bad data errors players were seeing.
The installer no longer defaults a player’s install to the “My Documents” folder, but the standard Program Files folder.
With the new CDN, we have done away with the hundreds of incremental patches that were stored on our old provider. These hundreds of patches represented almost 600gigs of possible problems that players could encounter, leading to Metafile errors, Manifest errors, and other squirrely behavior.
After today, there will only be two patches on our CDN; 1.0.3 -> 1.1.0 and Nothing -> 1.1.0. Also, download speed should have been significantly improved with this switch to Cloudfront, as well as many closer locations to download from.
We hope the relatively clean slate and lower error rate will make up for the inconvenience of having to reinstall the game. There are more improvements on the horizon as well. We are working towards a new and significantly cleaner launcher that should make this whole experience more seemless.
We strongly advise players follow these instructions step-by-step to minimize the chance of any unexpected technical issues.
INSTRUCTIONS:
Below are the instructions for how to uninstall and reinstall Star Citizen using the new launcher. These instructions work for both Windows 7 and Windows 8.
Click the Start button at the bottom left of Windows.
Click on All Programs, then click on the Star Citizen folder.
Click Uninstall.
At this point, a User Account Control window will pop up asking:
“Do you want to allow the following program from an unknown publisher to make changes to this computer?”
Click Yes. A Star Citizen Uninstall window will pop up asking:
“Are you sure you want to completely remove StarCitizen and all of its components?
Click Yes and the Star Citizen Uninstall Wizard will start. Click Uninstall and the previous version of the launcher and the client will be completely removed. You will see the last window informing you “Star Citizen has been removed from this computer.”
Now we’re ready to get the new launcher from our new CDN!
IMPORTANT: You’ll need to use Firefox or Chrome to download the new installer. Using Firefox or Chrome, head to https://robertsspaceindustries.com/download to grab the newest version of the launcher. Once downloaded, run the installer to install the launcher. We recommend (but not require) that you install to the default directory provided.
As part of the install, you’ll be asked to install and setup DirectX. DirectX is required to play games on Windows.
Please note: As part of the DirectX installation, Microsoft will offer you an option to install Bing Bar. Please know you do NOT need install Bing Bar to play Star Citizen.
You may get a popup at this point asking to Repair or Remove Microsoft Visual C++ 2010 ×64 Redistributable. This is normal… select Repair and click Next and your DirectX install will be complete.
At this point, the Star Citizen launcher is installed, so make sure the checkbox is checked, click Finish, and the launcher will run.
Once the launcher is up on your screen, use your normal RSI login and password to log in and begin patching!
Star Citizen 1.1 Patch Installation Guide (French)
Pourquoi réinstaller Star Citizen :
Après 2 ans de développement, Star Citizen a pris en taille et en maturité. Malheureusement, l’installation et la mise à jour du jeu ont été laissés pour compte. Mais aujourd’hui, avec le lancement de la version 1.1.0, nous amorçons le nettoyage de certains problèmes rencontrés par les joueurs lors de l’installation ou du jeu lui-même.
Nous avons donc publié un nouvel installateur et nous avons fait passer notre CDN chez Amazon Cloudfront. Cela aura pour effet de résoudre plus de 80% des problèmes liés aux Metafiles, et pose la base d’une future mise à jour qui se débarrassera définitivement de la maintenant fameuse méthode “Delete your USER folder”.
D’un point de vue plus technique :
Le nouvel installateur résout de nombreux petits bugs, crashes et erreurs de données rencontrées par les joueurs lors de l’installation.
L’installateur ne choisit plus le dossier “Mes Documents” par défaut, mais le dossier “Programmes” standard.
Avec le nouveau CDN, nous avons mis de côté les centaines de patchs incrémentaux stockés chez notre ancien fournisseur. Ces centaines de patchs représentaient plus de 600 Go de problèmes que les joueurs rencontraient et qui amenaient à des erreurs de Metafile, de Manifeste et autres comportements erratiques.
Dès aujourd’hui, seuls deux patchs seront présents sur notre CDN : 1.0.3 -> 1.1.0 et Rien -> 1.1.0. De plus, la vitesse de téléchargement devrait devenir bien meilleur avec ce changement vers Cloudfront, qui possède également plus d’emplacements de sources plus rapprochées.
Nous espérons que cette table presque rase ainsi que des erreurs beaucoup moins fréquentes pourront compenser le désagrément d’avoir à réinstaller le jeu entier. D’autres améliorations se profilent également. Nous travaillons sur un nouveau programme de lancement du jeu qui s’annonce beaucoup plus propre, et qui devrait rendre l’expérience dans son ensemble plus fluide.
Nous recommandons fortement à tous les joueurs de suivre les instructions ci-dessous pour minimiser les risques d’erreur technique inattendue.
INSTRUCTIONS:
Voici les instructions pour désinstaller et réinstaller Star Citizen en utilisant le nouveau programme de lancement. Ces instructions fonctionnent autant pour Windows 7 que Windows 8.
Cliquer sur Démarrer, en bas à gauche de Windows.
Cliquer sur “Tous les Programmes” puis sur le dossier Star Citizen
Cliquer sur Uninstall ou Désinstaller.
À ce moment vous obtiendrez une fenêtre de Contrôle de Compte vous demandant :
“Do you want to allow the following program from an unknown publisher to make changes to this computer?” // “Voulez-vous autoriser le programme suivant provenant d’un développeur non-identifié à effectuer des changements sur cet ordinateur?”
Cliquer sur Oui. Une fenêtre de Désinstallation de Star Citizen apparaîtra, demandant :
“Are you sure you want to completely remove StarCitizen and all of its components?” // “Êtes-vous certain de vouloir complètement supprimer Star Citizen et tous ses composants?”
Cliquer sur Oui et l’assistant de désinstallation de Star Citizen démarrera. Cliquer sur Désinstaller // Uninstall et le programme de démarrage et client du jeu précédents seront entièrement effacés. Une dernière fenêtre vous informera que “Star Citizen has been removed from this computer.” // “Star Citizen a été effacé de cet ordinateur.”
Vous êtes maintenant prêt à télécharger le nouveau programme de lancement de notre nouveau CDN!
IMPORTANT : Vous devrez utiliser Firefox ou Chrome pour télécharger le nouvel installateur. Avec Firefox ou Chrome, rendez-vous à https://robertsspaceindustries.com/download pour récupérer la dernière version du programme de lancement. Une fois téléchargé, lancer l’installateur pour installer le programme de lancement. Nous vous recommandons (mais ce n’est pas obligatoire) d’installer dans le dossier suggéré par défaut.
Lors de l’installation, on vous demandera d’installer et de configurer DirectX, qui est nécessaire pour jouer à des jeux sous Windows.
Note : Lors de l’installation de DirectX, Microsoft vous offrira l’option d’installer la barre Bing. Sachez qu’il n’est PAS nécessaire d’installer la barre Bing pour jouer à Star Citizen.
Il est possible qu’une fenêtre vous demande de Réparer ou de Supprimer Microsoft Visual C++ 2010 ×64 Redistribuable. Ceci est parfaitement normal : sélectionner Réparer et cliquer sur Next // Suivant et votre installation sera finie.
À ce point, le programme de lancement de Star Citizen est installé, assurez-vous donc de cocher la case, cliquez sur Finish // Terminer et le programme de lancement sera démarré.
Une fois que le programme de lancement est visible sur votre écran, utilisez votre login et mot de passe usuel RSI et la mise à jour se lancera!
Star Citizen 1.1 Patch Installation Guide (German)
Wie eine Neuinstallierung von Star Citizen Dir helfen kann:
Nach einer zweijährigen Entwicklungsphase hat sich Star Citizen vergrößert und ist um einiges ‘erwachsener’ geworden. Leider ist dies mit unserem Installtions- und Patchvorgang nicht unbedingt der Fall gewesen.
Allerdings, bringt die heutige Veröffentlichung des 1.1.0 Builds ein ernsten Versuch die Probleme zu beseitigen, die Spielern bei Installtion und spiel widerfahren, mit sich.
Wir haben nun einen neuen Installer veröffentlicht und unser CDN zu Amazon Cloudfront gewechselt. Über 80% der ‘Metafile’ Probleme werden somit gelöst. Dieses bildet auch das Fundament für zukünftige Updates die den berühmt-berüchtigten ‘Delete your USER folder’ fix eliminieren werden.
Auf der mehr technischen Seite:
Der neue Installer löst viele der keinen Installationsbugs, Abstürze und ‘bad data’ Fehler.
Der Installer installiert Star Citizen nicht mehr in das ‘My Documents’/‘Eigene Datein’ Verzeichnis sondern in das normale ‘Programmdatein’ Verzeichnis.
Mit dem neuen CDN habe wir hunderte der inkrementellen Patches, welche bei unserem alten Provider gespeichert waren, eliminiert. Diese zahlreichen Patches beherbergten fast 600 Gigabyte von potentiellen Problem die Spielern widerfahren konnten. Diese konnten zu Metafile und Maifest Problemen (und andere lästige Probleme) führen.
Von Heute an wird es nur zwei Patches auf unsrem CDN geben: 1.0.3 -> 1.1.0 und Nichts -> 1.1.0. Auch sollten Downloadgeschwindigkeiten sich mit dem Wechsel zu Cloudfront drastisch verbessern. Weiter bietet dieser Wechsel eine breitere Wahl an Downloadorten.
Wir hoffen das dieser relativer Neuanfang und eine niedrigere Fehlerrate die Unannehmlichkeiten einer Neuinstalltion wett machen. Es sind auch weitere Verbesserung am Horizont. Wir arbeiten zu einem neuen und wesentlich sauberen Launcher hin, welcher die ganze Erfahrung etwas nahtloser macht.
Wir empfehlen stark das Spieler die folgenden Anweisungen Schritt für Schritt befolgen um die Chance etwaiger technischer Probleme zu minimieren.
Anweisungen wie man Star Citizen mittels dem Launcher deinstallieren und erneut installieren kann folgen nun. Diese Anweisungen funktionieren für Windows 7 und Windows 8.
Klicke Windows-Start am linken unteren Bildschirmrand.
Klicke auf Alle Programme und dan auf den Star Citizen Ordner
Klicke auf deinstallieren.
An dieser Stelle ist es möglich das eine User Account Control (Benutzerkontensteuerung) Warnung erscheint, welche erfragt ob der Benutzer dem Programm erlaubt Änderungen am Computer vorzunehmen. Dieses Dialogfenster bitte mit ja beantworten.
Als nächstes erscheint ein Star Citizen Deinstallation Dialogfenster welche erfragt ob mit der Deinstallation fortgefahren werden kann, diese bitte mit ja beantworten.
Der Star Citizen Deinstallation Wizard startet nun. Hier auf Deinstallieren klicken – die vorige Version des Launchers und Klienten wird hiermit komplett entfernt. Als letztes erscheint eine Bestätigung das Star Citizen nun von dem Computer entfernt wurde.
Nun sind wir bereit den neuen Launcher vom CDN herunter zu laden!
WICHTIG: Es muss Firefox oder Chrome benutzt werden um die Installationsdatei herunter zu laden. Unter Benutzung von Firefox oder Chrome die neueste Version vom Installer hier, https://robertsspaceindustries.com/download, herunter laden.
Sobald diese herunter geladen ist, doppel klicken um das Programm zu starten und den Launcher zu installieren. Wir empfehlen das das vorgegebene Verzeichnis gewählt wird, dies ist aber nicht notwendig.
Als Teil der Installation wird eine DirectX Installation initiiert. DirectX ist erforderlich um auf Windows Spiele zu spielen.
Es sei wohlgemerkt das Microsoft, als Teil der DirectX Installation, bietet die Bing Toolbar zu installieren. Es ist NICHT notwendig diese Toobar zu installieren um Star Citizen zu spielen.
Es ist möglich das während des Installationsprozesses erfragt wird ob ‘Microsoft Visual C++ 2010 ×64 Redistributable’ repariert oder entfernt werden soll, dies ist völlig normal.. einfach Repair (Reparieren) auswählen und Next (Weiter) klicken – die DirectX Installation ist hiermit erfolgreich abgeschlossen.
An diese Stelle ist der Star Citizen Launcher installiert. Stelle nun sicher das die Tickbox getickt ist, klicke Finish (Fertigstellen) und der Launcher startet.
Sobald der Launcher gestartet ist, benutze Deine normalen RSI Login-Informationen um Dich ein zu loggen und den Patchvorgang zu starten!
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
As we started the week with one event, we end with another. We hope everyone has a happy and safe SXSW, and we can’t wait to see you this Sunday at the party!!
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
Greetings Citizens,
Simple to play, difficult to master: it’s a well-accepted philosophy that forms the core of great game design. And with Star Citizen’s ships and their components, it’s a mission statement. The ultimate goal for Arena Commander (and ultimately a persistent universe) is that it will be simple for a player to pick up a ship, launch off into space and enjoy the experience. At the same time, we are building a customization system that allows for near-infinite complexity and a constant sense of progression. You don’t HAVE to drill down to specifics like weapons mounts or technology overclocking… but you can, and the game will reward you for it.
Balance is also a massively important issue in a skill-based combat scenario like Arena Commander. You need an experience with progression—players striving to earn a better ship, gun, reward—alongside the desire never to have a single ‘best’ endgame. Everyone should want to continue developing their ships, but no one should ever have a universal advantage for doing so. Over the past months, we’ve been studying the results of early iterations of Arena Commander, we’ve been observing matches, reading backer comments, following the endless ‘input type’ battles and more.
As the next stage in space combat evolution, in Star Citizen 1.1, you can expect to see changes on how weapons and hardpoints will function. The idea of balancing gimbaled hardpoints has been in the plans since the beginning, and with 1.1 we’re introducing it into the wild. The end result is that players will have more choice over what weapons they can attach… but with more of an impact on gameplay resulting from those choices.
Why? Increased granularity in weapons makes for the best possible experience and a system that rewards skilled pilots for forgoing certain creature comforts is good for balance all around. We want to see players forced to make meaningful decisions about their loadouts in relation to their personal play style rather than simply having them pick the ‘best’ gun or missile. Expect to see further changes to this balance as other aspects of Arena Commander’s flight model come online; for example, gun functionality will be defined not only by size, but by aspects like their power requirements, electromagnetic signature and more.
Weapon Sizes
The first, simpler change relates to weapon size. In the past, weapons have been defined by a type (class 1, class 2, etc.) and a size (size 1, size 2.) This allowed us a certain amount of control over the base loadouts: you can’t put a huge gun on a tiny ship, you can’t put a missile where a gun is intended to go and so on. But this system has some issues, chief among them the fact that in addition to confusing new pilots, it doesn’t make natural sense; why is a missile rack class 3 or a turret class 4? Or even worse some weapon hardpoint classes were really for different sizes of the same type of item – class 5, 6 and 7 hardpoints were all for different sized manned turrets (from the Constellation to a Capital ship turret that you may see on a Bengal Carrier)
The old system of weapon hardpoint “classes” was invented before we had implemented the actual hardpoint system in the game code. The system implemented in the game, which everyone has been using since Arena Commander v0.8, is called the itemport system and classifies what can accepted on the port by a “type” (an itemport is able to have multiple types it can accept) and “size”. Every item in the game has a type and a size in its item definition. If the item type and size match what the itemport has for its allowed type and size then you can mount the item onto your ship at that itemport. This is universal for all items you can attach to your ship – not just weapons and turrets but thrusters, power plants, fuel tanks, scanners, coolers, avionics and so on. Internally there is no class X weapon hardpoint, so starting today we’re retiring the obsolete naming convention for weapon hardpoints!
Instead it will be a Size 1 Gun or a Size 3 Unmanned Turret, or a Size 2 Pylon or a Size 4 Manned Turret and so on.
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
So to clarify all items and itemports (think of this like a socket you plug the item into) are defined by three key pieces of information –
1) TYPE
2) SIZE
3) PIPE
We’ve talked about the concept of Pipes before – these are the connections between items and the ship that carry things like Heat, Data, Power, Fuel and so on. So for an item to be compatible with an itemport beside the size and type needing to match up the Pipe(s) need to match up – so if a Turret has an input for “Power” and “Data” (say for auto targeting) and output of “Heat”, the itemport will also need to have hookups for these three pipes.
One other interesting point is that going forward the size value for all weapons will be uniform, and scale to every ship in the galaxy. The new system will handle everything from the smallest possible weapon, Size 1 (1 meter) to the largest, Size 10 (40 meters) and gives us much more room to scale between the Merlin and the Bengal. The system is also expandable; if we ever need a gun that’s more than forty meters long, we have the ability to generate it in Star Citizen!
Simply reorganizing how weapons are sized is more of an internal change; players will take note of it and it unifies the language and makes things simpler to understand but it doesn’t immediately impact gameplay.
What DOES change is how you set your loadouts are the changes we are making to ships’ weapons itemports for 1.1.
We are changing most Size 2 and up weapon itemports to be able to accept either a gun OR an Unmanned Turret (sometimes called a gimbal). Not all Size 2+ weapon itemports will be this way due to either Pipe requirements or logical ones (a fixed size 3 gun built into a spaceship’s nose would not be suitable for a Turret) but most will.
Every joystick user is probably going; “Oh, no! Even more gimbaled weapons :-(” as they read this… But this is where the balance comes in!
When you mount a Turret/Gimbal to an itemport, the size(s) of the weapon that the Turret/Gimbal are reduced. So if you mount a Size 2 Gimbal to the Size 2 weapon itemport, the weapon itemport on the Gimbal can only be a Size 1.
The rule on sizes for secondary itemports (these are itemports on an item plugged into another item port) is that they have to at least drop a size. So you can only plug a size 1 item into a size 2 item and so on. In the case of Turrets this is additive, so if you have a size 3 Turret it could mount two Size 1 guns or one Size 2 gun (note this doesn’t mean you have the choice on each Turret, its more that you may have the option of buying a Size 3 Turret with two Size 1 weapon itemports or a Size 3 Turret with one Size 2 weapon itemport.)
A Manned Turret loses one more Size point. So the smallest Manned Turret could be is Size 3 and it would have a Size 1 weapon item port). The Manned Turrets on the Retaliator are Size 4, allowing for 2 Size 1 guns on each Turret.
So you have a choice; Mount a bigger, more powerful gun or mount a smaller gun that has greater accuracy / gunnery control. Joystick players will probably stick more with fixed guns and have greater hitting power as it’s easier for them to maneuver their ship to get a bead on their target whereas a mouse user may opt for gimbaled weapons due to the aiming accuracy of the mouse but will be giving up the hitting power of a larger gun.
These aren’t the only limits we’ll be using to balance guns in Star Citizen! Things like Power and Data are required for Turrets and factor into your overall ship needs; you may not have enough CPU cycles on your ship’s computer to run the targeting computer and four gimbaled guns! There could be weapon itemports that allow you mount a Gun, a Missile Rack or a Turret. With this increased customization comes increased choice and increased tradeoffs!
It’s an intricate system, but all those parameters allow us to tune ships towards a specific purpose, while still allowing players to skew that purpose towards their own goals. We want players who are using their piloting skill to have the best advantage in terms of guns; if you’re a sharpshooter, you’ll be rewarded for choosing fixed guns. If you choose gimbaled or turreted mounts, you’ll have an easier time hitting your target… but your weapons won’t cause as much damage as an equivalent fixed set.
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
We know that many backers are curious about more than just how things work in Star Citizen, they want to know why they work. What follows is a more detailed dive into some of the background and more detailed requirements of the updated weapons system.
Weapon Size has been refactored to correlate to volume, which scales by a decreasing factor – by the time you get to the capital ship scale, jumps between sizes are enormous, but we still need to differentiate clearly between a Size 1 (0.25m^3) and a Size 2 (0.73m^3). That Size 10? A whopping 1394.5m^3! Volume is weird. The reason it’s correlated to volume is to allow our artists the freedom to define guns with their own distinctive forms, while still guaranteeing that weapons of the same size will always fit.
Now that infinite complexity has been added to these weapons (volume is preserved through ratios, which are capped at 7:1 and 2:1 – but there’s still every number in between), the system is returned to sanity by sitting down with the artists and enumerating the exact ratios that apply to each weapon type, providing those weapons with a particular personality and profile to aid visual identification. New weapon designs are thus provided a size and a ratio, defining an exact bounding box within which to generate the awesome visuals that define these items.
The weapon mounts scale up accordingly. With the attaching faces of weapons guaranteed to be a certain size, we can always be assured the gun will look right when placed on a mount. Since all attaching faces are now unified, all correctly sized mounts can be placed in hardpoints that accept that size – fixed, gimbal, manned turret, rocket pod, missile rack, fuel container, etc. Naturally, that’s not how ships are actually made. In the extreme example, a fuel container is pretty useless without a fuel pipe connected to that hardpoint, and a manned turret won’t accomplish much without a seat available to man it. Since the hardpoint still defines the high level restrictions, ships can still be balanced individually without messing too much with the item ecosystem.
Again, these hardpoints and mounts have limits to their performance – increased mass constraints at the cost of gimbal speed, for example. Particularly at the larger sizes, mass begins to be a real balancing act when trying to drag the most firepower around the universe. Some hardpoints won’t be able to accept certain mounts because of their nature – a fixed gun built into the hull of a ship won’t be swappable with a gimbal, no matter how much the numbers say it fits. Ultimately, getting the most out of your ship will come down to understanding your ship, and finding your style of flying to match.
The Future
You will start to see this system in place with Arena Commander 1.1. In fact, gimbaled weapons mounts are available for backers to try in the Voyager Direct and Electronic Access stores now. It’s not the complete system today, but it’s a good indication of the work we intend to introduce. Some of this is still being worked out (the design trade-offs between mounting a weapon or a missile, for example), but it marks the beginning of a unified system for weapons and mounts across all the ships in the game.
With that foundation, we can move forward on some of the deeper designs planned. Unique targeting behaviors, such as remote access or point defense solutions; attachments that augment the performance of weapons, or that alter their effects; retractable mounts that disappear into the hull of the ship; it’ll take some time to bring together all of these distinct elements under one roof, but doing so will bring a whole new level of meaningful choice to weapon loadouts.
- Unione Corse rephack toward KSP and Samura removed.
- Pirate ID rephack toward Rogues removed.
- Rephack between Bundschuh and Liberty Navy removed.
- Junker Marauders rephack toward Ageira changed to -0.3.
- Generic ID access to Gaian tech removed.
- Hellfire Legion access to Liberty lawful (90%) and Mollys (75%) snubs restored.
- TAZ access to Order tech (90%) replaced with Coalition tech.
- Bundschuh tech cells changed to 75% to Order and 90% to Coalition (rates swapped)
Agreed, pending implementation
- Hogosha ID Clarification
- Gaian ID ZoI Update
There are other requests under discussion. In addition a ticketing system is being discussed so things are not missed in an attempt to more efficiently handle this area.
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
Our thirty-fifth episode features an interview with Director of Game Operations Jeremy Masker and an update from our Customer Service team! We’ll also spotlight the latest news from Cloud Imperium and the amazing work the fan community is doing!
1:02 – Intro/News 3:34 – News from Around the Verse 16:37 – Bugsmashers 27:23 – MVP 28:23 – Customer Service 29:52 – Jeremy Masker Interview 40:48 – Outro 41:45 – Sneak Peek
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
There’s so much stuff going on right now, we can barely keep up ourselves! We hope everyone in Boston is enjoying PAX East, and for those who cannot attend be on the look out for updates next week! In the meantime, catch up on this week in Star Citizen!
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
There’s so much stuff going on right now, we can barely keep up ourselves! We hope everyone in Boston is enjoying PAX East, and for those who cannot attend be on the look out for updates next week! In the meantime, catch up on this week in Star Citizen!
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
Company History
Founded at the turn of the century, Accelerated Mass Design gained renown as a high-end electronics design and tuning companies. AMD has been responsible for dozens of commonplace (but disparate) technological items used in consumer spaceflight, as well as most recently the development of their own starship variant, the Mustang Omega.
In 2899, Sander Katt and a team of six other engineers left their design positions with Ayre Semisonic to form a new corporation focused on high-level design. In 2901, the company released its first product: the UE-9300 expansion card. Designed for near-absolute-zero operation, the UE-9300 was an immediate high-end replacement for the aging CarthSys Multidock, piquing the collective interests of both luxury and military spacecraft manufacturers.
For the first dozen years of operation, Katt’s team dedicated their time to streamlining and increasing the efficiency of existing technology. By 2908, a specific bureau had been established for taking in other companies’ standard production technologies and tweaking them past their design limitations. AMD-branded versions of everything from escape hatches to laser cannons became a sought-after accessory for ship owners of means.
In 2920, the conglomerate signed a two-decade development deal with Anvil Aerospace, providing high-level circuitry for a number of military spacecraft in exchange for exclusive branding. While initially considered an unusual deal for a company seeking to position itself as a civilian lifestyle brand, the value behind the agreement quickly became apparent as Anvil began to launch civilian-branded variants of their Hornet and Gladiator lines. AMD took in billions in revenue as Anvil ships spread brand awareness and a need for expansion of their technology support chain.
By the late thirties, however, the limitations offered by the Anvil deal had begun to chafe. The demand for F7C Hornets had overshadowed AMD’s capacity to manufacture internal parts, leading Anvil to begin to source outside the company (as allowed by contract). Their brand began to be associated with subpar parts rather than top-of-the-line components, and all projections indicated that their own production could never keep pace with spacecraft demand. Ultimately turning down a massive offer to sign for a third decade, AMD threw caution to the wind once again, serving as a free-agent ship component synthesizer.
Racing Ahead
Seeking to renew their appeal in the youth market (and now free of their exclusive Anvil deal), Accelerated Mass Design teamed with Consolidated Outland in 2940 during the early stages of the Mustang development program. AMD financed a significant, undisclosed portion of Koerner’s spacecraft prototyping, in exchange for exclusive branding rights to create their own dedicated racing variant of the ship.
The corporation embedded a pair of their top designers with Silas Koerner’s Mustang team. Bryce Halliday and Jennifer Aykers, both hired away from MISC’s auspicious spacecraft design bureau, sat with the Mustang team through every step of the spacecraft’s design. Engineers involved report that the duo had a significant uncredited role in the creation of the Mustang lineup, although they were only technically observers. Halliday and Aykers spent four years ‘roughing it’ on the frontier, often finding themselves at odds with Koerner’s demanding personality … but the results of their work speaks for itself.
On its own, the Mustang (which Aykers described in a dispatch as looking like a “battle butterfly”) outpaces the Roberts Space Industries Aurora in over a dozen categories, chief among them speed and maneuverability. The early choice to lock down an exclusive racing version seems to have offered significant recompense: Mustangs are now the de facto choice of young racers, with the Gamma model alone looking to outsell the Origin M50 in its first quarter on the market.
The most notable feature of the AMD-exclusive spacecraft, dubbed the Mustang Omega, was the addition of a ramped-up fuel intake for faster hydrogen recycling. This allows the Mustang to ‘double down’ on the existing boost system, enhancing its overall straight speed. Some critics have claimed that the standard Mustang racer, the Gamma, is simply a ‘cut down’ version of AMD’s Omega. The truth is that the Gamma and the Omega were developed independently, and the existence of the Gamma in the first place likely owes itself to AMD’s desire to be associated with racing. (It is also worth noting that the materials cost of the enhanced boost system equal almost the entire hull of the Mustang Gamma.)
Further aiming to attract the younger, affluent spacecraft-buying audience, Accelerated Mass Design enlisted the efforts of underground artist Sektor8 to design a distinctive “cherry pie” red paint scheme that evokes nothing 32short of the Origin M50, the reigning racing spacecraft. Seeking to brand the AMD logo as a lifestyle icon, the sigil is featured prominently on the spacecraft’s hull. Sektor8 was paid an astounding three million UEC for the job, which he insisted be donated to an aquatic animal rescue organization on Helios.
A limited number of Mustang Omega hulls have been constructed, many of which have been seeded to top racing teams and (after a lengthy search) promising newcomers on the Murray Cup circuit. Both Accelerated Mass Design and Consolidated Outland are hoping that this investment will pay off in 2945, with the powerful new Mustangs poised to place highly in all major competitions. The only reason there isn’t an Omega with a Murray Cup, a company spokesman recently opined, is because this year’s contest hasn’t happened yet.
The Future
The terms of the Consolidated Outland deal are unknown, but given the recent reappearance of AMD-badged missile pylon connectors it is likely they are not as restrictive as the Anvil contract. Industry rumors even claim that the company is strongly considering taking their experience with Consolidated Outland to the next level and designing their own spacecraft. Recent hirings, which have brought engineers away from both Roberts Space Industries and MISC, seem to support this idea. Could Accelerated Mass Design create their own kit spacecraft, or even a dedicated luxury vehicle produced in extremely limited numbers? Perhaps — the sky is the limit!
As some of you may have seen from the recent sneak peek on Around the Verse or the Foundry 42 monthly updates, we’ve been hard at work for some time to improve the damage system on the ships. We’ve already shown in Arena Commander our very powerful and flexible system for controlling the damage on your ships, which combined with some awesome artwork gives some great results. But your ships are such a big part of the Star Citizen universe we felt we had to go several steps further.
So we took a top down look our damage system to review what we could improve, and although there is great satisfaction in peeling off each part of an enemy ship when they take major damage, we felt we could better represent the specific location and type of damage inflicted. Whether it be a projectile weapon, an energy weapon, an explosion or scratching your ship after a dodgy landing, we want you to be able to differentiate them just from looking at your ship. We felt this was going to be especially important in our game as we want each ship to tell a story of what’s is been through.
Two other areas we wanted to improve on were the time it takes our artist to create the numerous damage states for each part of the ship, and the hefty memory cost these meshes come with, which could prove to be a problem as we scale up the game. The reason the damage states are so labour intensive is that each ship has over ten main parts, and each of these requires five damage states to represent the different levels of damage, then each of these requires up to five simplified meshes that we use when they’re further from the camera to save performance. This equates to over 200 meshes per ship!
When you examine the current damage states in Arena Commander you’ll notice that the first two damage states tend to just contain minor dents, some burn damage, and perhaps a few panels that have been blown off exposing some internals. It’s only when you get to the 75% and 100% damage states you start seeing major silhouette changes, however the earlier damage states still carry the same memory cost. So our goal was to try and achieve the minor damage without having to create whole new meshes, saving both memory and artist time. To do this we decided to record the impacts on the ship within an extra set of textures that wrap around the entire ship, and to then use these in the shaders to dynamically add the dents and burn in precisely the location your ship took the damage. However rather than just opting to blend in a simple damaged texture in these areas, we instead chose to model the type of damage much more accurately by recording four different quantities:
Temperature
The current temperature of the hull
Burn
The maximum temperature the hull has been burnt with
Thickness
How much of the outer hull remains. Paint comes off first, then the underlying metal
Deformation
How much physical force the hull has taken to bend and distort it
Using these four damage values we can make the hull glow with heat, make paint burn and bubble, peel paint off to expose the underlying metal, dent and deform the surface, and even cut holes through the hull to expose the internal wiring and mechanics. Rather than the internals of the ship only being modeled in specific locations we now model the internals under the vast majority of the hull. You might expect this would involve a lot of work for the artists, but they’ve come up with several methods of adding these internals very efficiently and the overall damage state setup is now significantly quicker than before.
Your ship’s life story
The really interesting thing about us having access to four different measures of damage is that these can be imprinted on your ship in a pattern and strength that is unique to each weapon, explosive or type of impact. So while lasers will cause your hull to light up for several seconds leaving burnt paint and exposed metal, a powerful ballistic might tear a hole straight through your hull. We’re just scratching the surface of how far we can go with this system, and we plan to soon upgrade the weapon/ammo code to expose more unique and physically realistic damage behaviors.
We’ve trialed this tech on the Gladius, and you’ll see for yourselves in 1.1.0 that the results are great. What you might not see is that the Gladius uses four times less memory than the other ships, and this equates to better performance for the backers. Our artists are happy as this will allow them to make ships more quickly, which ultimately gets this game in your hand sooner! You’ll also be glad to know we’ll be rolling this tech out on every new ship, and also retrofitting the older ships as we go along.
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
Additional tech needed to be developed for placing our Particle and Squib Effects to complete the look of our new damage pipeline. When a part such as a Wing detaches from the ship, Squibs and Particles detonate along the edge of the separation. The Squibs, when detonated, specifically cause holes and burn damage to appear on the skin of the ship, revealing the ‘guts’ of the ship underneath so that the piece of the ship looks like it was torn away from the body. Particles also fire off as pieces break off from the ship, adding dramatic smoke, explosions and sparks. A specialized art tool, developed by Matt Intrieri, was created to convert helper objects in 3DSMax into XML code to add the effect in-game. CIG’s Effects Artist, Mike Snowdon, used the tool to add the Particles and Squibs to the ship along the edges of each part of the ship, creating dynamic and realistic effects based on the ship’s systems at each location.
Next Steps
But this isn’t the end of the road for this tech, there’s still several major features we’re working on. One of these is particle effects that are created, simulated and rendered entirely on the GPU, and this gives them two huge advantages. The first is performance, we can spawn 10-100 times more GPU particles than CPU particles for the same cost. The other benefit is that they tie in perfectly with the precise damage you’ve taken, so as the hull burns you’ll get glowing embers falling off, when it takes physical damage you’ll see shards of metal fly off, and when you blow out a large section of the hull you’ll see space littered with the debris. We’re also working on some major optimizations using to the damage system using DirectX 11 features to ensure that it’ll still run fast when there’s twenty fighters attacking a capital ship!
The first thing we did when we got this system working was to have some fun and write our names into a ship with a Gatling gun! Now it’s your turn to have a play and we’re keen to hear what you all think of this new tech so please let us know on the forums.
The Future
With our new damage technology now in place, we continue to strive for even more realistic and efficient methods to push our graphics in all areas. We’ll be adding more effects under the skin of the ship as gaping holes are revealed, adding touches like sparks on damaged equipment under the skin. Several lighting and particle setups are being prototyped to take our ship interiors through Healthy, Damaged, Critical and Flatline states that will inform and immerse our players during battle. Our new state machine being developed called GOST, will determine the healthy (or unhealthy) flow of energy around the ships systems and will have a big impact on our multi-crew interactions and the effect of ship damage on them. Given the complexity of our largest ships, that are really like floating levels, big questions remain about hull breaches and how to portray critical damage in the vacuum of space and how this will affect players inside. And optimizations in all areas will allow us to add more and more players simultaneously to create massive multiplayer battles. We are very pleased and excited to be releasing this first iteration of our newly optimized damage technology and hope the players feel the same.
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
Greetings Citizens,
February is a short month, but it was a full one for Star Citizen’s development! As you read this, Arena Commander 1.1 is hitting the PTU, and we expect to make it available on the live server in the very near future. Once we pass that milestone, it’ll be time for the first public release of FPS… so stay tuned, exciting things are coming! But for everything you can play today, there’s a hundred other aspects of the game in other stages of development. Read on to find out how everything from the imminent FPS module to the Persistent Universe is shaping up!
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
Greetings Citizens,
As always, we are glad to have you with us as we welcome in the month of March by first reporting on the successes of February. In fact, it may interest some of you to know that not only do we write these reports each month for the community, but we also have internal monthly reports for our teams as well. At the end of each month we review our success against the previous month’s goals for the team and recommit to the next month’s goals. Anyhow, the reason we mention it is because February had a very high completion rate indicative of the focused nature of the team with upcoming large releases.
This month saw our team working heavily on stabilizing the build for the 1.1.0 release. Generally in software development there is what’s referred to as “Main.” This is the primary repository for all the game’s code and data/assets within the content management system, which in our case is Perforce. Inside Main is generally where all developers are working. This also means that it is getting the most changes (commits) every day. While it is great for everyone to be working quickly and committing regularly, it also greatly increases the chances of introducing a new bug into the system. So, as we approach release we create what is called a “branch.” Using the metaphor of a tree, Main would be the trunk and a branch would be, a branch. It is a copy of Main where developers reside – working on changes specifically intended for that release. This greatly reduces the risk of unintended bugs being introduced that could threaten the release; it is also the time at which we generally switch focus from feature development to stabilization and bug fixing. This allows development for things like Squadron 42, new ships, FPS, and persistent universe to continue unabated in Main while Arena Commander gets stabilized in preparation for release in a branch.
So, without further ado let’s review the areas of focus for each department.
Engineering
Throughout February our engineers have been primarily focused on bug fixing and refining their systems for the upcoming releases. Last month we talked a bit about the new item port system. That system was completed this month, including bug fixing, and is going to be included with the soon to be released 1.1.0. As it is a fairly large extension of the system and interacts with several other systems in significant ways, it takes some time not only to finish the implementation of the system but then to also find and fix any bugs and edge cases that are exposed over time. Some of these bugs are memorable. For example, our light marine has a tactical shoulder lamp. After the implementation of the new item port system QA began reporting that the pilot would sometimes randomly die for no reason. After some investigation it was discovered that under certain conditions the tactical light (which is now attached with the new item port system) was colliding suddenly getting a velocity of 0 while the pilot was flying, and would then collide with the pilot at 200+ M/S and kill them. This is just one example of the strange but critical, and sometimes funny, issues that arise while implementing a new system.
On the Graphics Engineering side, our sole graphics engineer in the Santa Monica studio was working with his counterparts in the UK office to finish the first phase implementation of the new ship damage system which debuts on the Gladius. Among the many bug fixes and development work that went into the system this month, one of the interesting improvements to the system was the dynamic modification of normals. When the ship is shot and damaged, the system is now able to modify the normal around the impact area to curve the edges of a hole caused by a physical projectile, creating a realistic looking impact and penetration effect.
Design
The design team has had several areas of focus this month. They’ve been working closely with QA, forum feedback, and internal playtests on the balance of ship health, weapons, and items. This is an important ongoing process and occupies an ongoing focus. Similar to our engineering team, our Tech Designers have been working on resolving issues with the technical setup of ships, weapons, and items by fixing bugs and improving on functionality. Our design team has also been very involved with setting up new ships that are being released soon. Getting a ship set up to appear and work properly in the hangar, especially getting it flight ready, is very involved and requires a lot of time and attention.
The team has also been very busy with the ship pipeline operating at full capacity. Not just with setting up the ships that have been created, but also defining the specifications for new ships that they want to see created and introduced into the game. The design team has created briefs for numerous new spacecraft this month that are being slotted into the pipeline and some have already entered concept.
Our designers also put a big emphasis this month on the metrics for items, weapons, and their manufacturers. One of the most challenging things about creating our ships is the level of realistic engineering principals that go into them. So, our design team spent time this month working out a system of metrics for all the items and all the per item type size ranges that fit onto our spacecraft. Be on the look out for a revised hardpoint classification, weapon size classification, and thruster size classification schema. We will be sharing with the community as soon as it is completed.
Art
Our Art team in Santa Monica is currently focused on new ship development. From our concept artists, to modelers, to our tech artists, everyone is working on their aspect of a new ship. Similar to the other teams, there has been some bug fixing and preparation occurring for the upcoming release of 1.1.0, but a majority of the work has been going toward creating ships that we’ve previously announced.
We’ve also begun concept work on new variations of body armor for UEE forces as well as civilian and outlaw/pirate individuals. The character pipeline led out of the UK office has been moving forward and gathering steam, so much so we’ve expanded our capacity for high quality concept out of the Santa Monica office! Under Star Citizen’s supervising art director Lance Powell, we aim to deliver the best characters possible with current technology.
The art team has been working closely with design this month to collaborate on the metrics and item guidelines that we’ve mentioned above. It was important with the refactor to the system to meet designs needs while also maintaining the ability for artistic creativity and uniqueness. In the end we’ve landed on a system that satisfies the needs of both groups and should provide the best pairing of visual quality and gameplay.
That rounds out the department updates for this month. The team has been working diligently to stabilize and prepare for the 1.1.X series of releases that will be starting soon. We cannot wait to share with the community all that we have in store. It is very exciting for the team to release more content quickly and to start showing off some of the entirely new gameplay that has been in development. As these modules that comprise Star Citizen are starting to come together, we hope that you too enjoy the process of watching our shared dream get built. Thank you as always for your support. None of this would be possible without this awesome community backing us up in the quest to make the BDSSE!
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
Hi everyone!
February has absolutely flown by as the Austin team has been hard at work preparing multiple launches to Live and burning the midnight oil in preparation for March and April. We are looking forward to a variety of SXSW events here in Austin this month and spending time with the community who will be attending. Stay tuned for lots of exciting content coming your way in upcoming weeks and months. There are too many things to report in a summary, so here’s some real detail from the team!
Persistent Universe Team:
ART:
The month of February saw the art team in Austin get a lot of love. Our character team was featured on Around the Verse AND Meet the Devs, so everyone got to see just how awesome those guys are. Not only are they awesome people, but they are awesome artists as well! David and Billy have been polishing our characters for the upcoming FPS and Social Module releases while Megan has been working on defining the look and feel of what our NPC’s will look like on Terra Prime. We’ve also got a few new faces you’ll get to meet in the game come March. Look forward to seeing some pretty swanky styles when you land on this truly awesome landing zone.
Speaking of Terra, the legend himself Mark Skelton has been working with Behaviour to provide art direction for the ArcCorp, Terra, and Nyx landing zones. All three of these locations are extremely different from one another and it’s exciting to see the variety of locations taking shape. Mark has also been defining new architectural styles that will add even more diversity and flavor to the Persistent Universe in the future.
We’re all about props this month. With hundreds of props being created by RedHotCG, Virtuos, and our own internal artists, it is amazing to see the difference filling an environment with props makes. With the help of our artists, pretty soon our NPCs will be able to sit in chairs, drink from mugs, move crates, admire sculptures, play shuffleboard, and even mop a floor.
For every prop an NPC requires an animation to go along with it, and our animators have been working hard on implementing animations received from Imaginarium. We’ve got NPCs dancing, chilling against the wall, and chatting it up at the bar, among other things. Our animation team has also been fixing up the ship cockpits, as our recent skeleton improvements have required adjustments to the cockpits to allow for our character to fit properly. We’ve made progress in standardizing our cockpit layouts, bringing the total cockpit types down from 17 to 7! This will help us build ship cockpits more efficiently in the future.
DESIGN:
This month our artists and designers have been working on a major part of the Persistent Universe which many of you are chomping at the bit to try out: MINING! We’ve made major strides in solidifying the design for how mining will work in the PU and Tony Zurovec wrote up an awesome doc on the minutia of the occupation. If you missed the post on the website a while ago, you can find it HERE. Thanks to artwork from Ken Fairclough and Chris Olivia, as well as the concepts for the Orion created by George Hull; we are now able to visualize our first occupation to be developed by the PU team here in Austin.
Our design team has also been setting up NPC activities for the Social Module, fleshing out the shopping experience for Cubby Blast and Astro Armada, and making major updates to the Thruster Calculator, which will make it much easier to – you guessed it – calculate the thrust of our ships going forward. David Ladyman has received some major progress back from our linguists developing the alien languages for Star Citizen and is planning on running the first draft of the Vanduul language by Chris Roberts fairly soon.
ENGINEERING:
It was another great month for the PU programming team. The team braved a few days of freezing weather to ensure they did not miss a beat in working to bring you all one step closer to visiting your friends in our upcoming Social Module. And although they spent Valentine’s Days with their sweeties, many of them have reported that their hearts were elsewhere… infatuated with the awesome Star Citizen Community!
Working with our friends at Wyrmbyte we got an early iteration of our Universe Simulator up and running. Chris Roberts was “wowed” when we shared an early demo with him. The programming team also worked very closely with our DevOps team on our process manager. Never before have team members come together in such a well-oiled manner, and as a result an exciting revamp of our process manager spec is now in hand.
Progress towards the first iteration of multiplayer hangars is also looking swell. Our programmers have been working closely with our pals at Behaviour to get the first iteration of this feature up and running. While this will continue being improved upon and polished, we have reached the point where players can now visit their friends’ hangars! And if that’s not enough, we also have chat and emotes incoming. The boys here in ATX have co-mingled their efforts with Behaviour to get the base chat service in place, which they will continue to work on until we have a solid first iteration to provide to you.
Let’s make sure not forget our amazing programmers working on our AI tool sets. They have been working feverishly to create some of the most stunning AI tools out there, all in order to bring the Persistent Universe to life!
Finally, as an added bonus, the team has been able to get the ball really rolling in putting our plan together for real Player Persistence! The final week of this month we had an engineering “Meeting of the Minds” between our Austin and Santa Monica studios. March will be the month where the explosion of ideas that came out of this historic sync will begin to come to fruition.
Stay tuned for more updates next month, and until then be sure to enjoy the Star Citizen presentations at PAX East and SXSW—brought to you by the one and only Chris Roberts!
Live Operations:
QA :
Star Citizen QA has been keeping very busy this month testing releases 1.0.2 and 1.0.3. We are excited that we we’re able to include so many fixes and updates in these releases. We have also been busy testing the upcoming FPS Module. Glenn Kneale in our Manchester studio and Tyler Witkin in our Austin studio have done a great job ensuring the FPS Module is continually tested by the QA team. At the end of each day, they provide a full report on the state of the FPS Module, report any new issues found and provide relevant feedback.
With help from DevOps, a new process was created to ensure that builds available to development are stable and able to be worked on. This process will help maintain developments’ ability to continue working without being hindered by an unstable build. QA has also been testing new features such as Matthew Delanty who has been working very closely with designer Luke Pressley on a new tutorial mode. Jeffrey Pease, Andrew Hesse and Melissa Estrada continued their tests with the lobby, ships, and the Sandbox Editor respectively while Steven Brennon has continued to gather very valuable feedback from all of you guys. This feedback is incredibly helpful to the team.
We have made an important change in the Austin team: Gerard Manzanares has officially been promoted to QA Lead in the Austin studio. Gerard will be responsible for leading QA operations in Austin as well as maintaining Austin QA coordination with our counterpart QA teams around the globe.
For the month of March, QA is looking forward to PAX East, SXSW, and releasing Arena Commander 1.1.0. Some of us from our Austin studio will be present at the SXSW Gaming Expo. If you happen to see us feel free to stop by and say hi.
IT/Operations:
February marks another awesome month for the IT/Operations team. IT was able to complete a major internet upgrade for our office in Germany. This project was headed up by our UK IT Manager, Hassan with support from members of the Austin, TX IT staff. Upgrades included bringing in a much needed fiber upgrade providing them with increased bandwidth and a major improvement to their firewall and VPN capabilities. Additional work was done to improve the studio’s internal network and server infrastructure.
In Santa Monica, IT Manager, Dennis has been hard at work deploying new hardware and software upgrades to his team while at the same time evaluating and documenting numerous hardware solutions ensuring that all aspects of Star Citizen function correctly on the new technology. Throughout his testing Dennis enjoys going in game and shooting it out with anyone who’s playing in Arena Commander at the time. Keep an eye out for him.
The Austin team continued its relentless pursuit for better performance in the build/development cycle. Storage was expanded again to keep up with the furious pace of the rock star development team and this allowed IT to implement new methods of optimizing storage utilization by the build servers for performance. By poring through stacks of analytics we’re already able to see marked improvements, but, we’re still not finished. Testing of new data layouts and storage formats are showing some very interesting results.
Working in concert with the DevOps team, IT also deployed a completely revamped game delivery system which allows us to get test builds out to all the connected studios in North America and Europe in a fraction of the time it took before. What used to take hours to transfer now takes minutes.
February has been exciting but we can’t wait to get out and meet some of the citizens at PAX East and SXSW in March.
Dev Ops:
This month the Dev Ops team has been setting up the foundations of our operational infrastructure. We are working with the server engineering team to build a provisioning layer that will supply the servers centralized “brain”, a steady stream of information about the health of the services running, and a place for that “brain” (named Process Manager) to request new processes, services, or vms to be created in case some crash or population load grows. In future phases we will start making more logic based decisions on this data and also spin down services, move them around, and gather more information on them. We are also now building out our configuration management tools after spending January evaluating several options.
Dev Ops is also building out all the logging for internal, PTU and production servers so that we can react quickly to issues, and also supply other engineers with details about problems.
Work on the new launcher is progressing, and evaluation of new SSN code for an improved version of patching is also underway. Some of the team is over in our German office working with engineers there to finish rebuilding the build server. They are making excellent progress on that, and it should be ready for development use in March.
On top of all that, we have deployed 1.0.2 and 1.0.3 to PTU and Live.
Finally, we have been working with Google to learn all we can about different technologies we can use to make sure that the Star Citizen architecture is as scalable and dynamic as we possibly can make it. Our goal is to minimize player impact and maximize uptime. The team is looking forward to the extremely busy month of March with PAX and SXSW!
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
DESIGN
Another very busy month on Star Citizen and Squadron 42. We are starting to see the S42 campaign coming together well, with lots of focus on the motion capture shoot that is about to happen at Imaginarium Studios. A lot of the work has been focused on the correct prop sizes so the actors can interact with our digital assets in a believable way. You would be amazed at the amount of planning that has to go into make sure everything is set up correctly for the shoot. Chris will be over in the UK to direct the performance capture for our cut-scenes, so we are making every effort to give them all the relevant information needed to make the scenes work well.
As you will all probably know, you begin the S42 campaign flying off the Idris Frigate; we got our grey-box version populated with AI this month to see how it was working as an interstitial HUB and once we added a few extra crew we came up with something that felt really satisfying and believable. Once the conversation system can be implemented we feel it will really be something special. Obviously we made good progress on the rest of the chapters and with involvement from the Frankfurt team, who are now coming online, we are starting craft some of the scenarios into immersive and fun gameplay sections. It’s been really helpful to get a fresh perspective from Todd and his design team.
As for Arena Commander, we are making good progress on the tutorial element, which we hope to release very soon. The leaderboards now have the addition of ‘Rating’, and multiplayer ‘Free-Flight’ is working well. We have focused on improving the ‘holo-table’ usability and functionality, with lots of good suggestions from the community being worked on. Lastly, we created a simple spawning map as a ‘stress-test’ for the Devs to work with.
All in all, another good month in design with good progress being made in all areas. Thanks again for making all this possible!
ENGINEERING
February in the North West of the UK and, not to pander to stereotypes, it’s wet, cold, grey and miserable. So no excuse for not cracking on with Arena Commander and Squadron 42 development then!
With the 1.1.0 release of Arena Commander just around the corner that has been a big focus for us. There are a couple of new modes which we’ve been developing here in the UK. The first is the new tutorial system to help ease the new recruits into playing what can be quite a complicated flight system. This required getting the AI “teacher” pilot to be able to perform the different maneuvers they’re teaching the player very precisely, being able to make sure the player is following correctly, and being able to time events very accurately. It’s can be surprisingly fiddly. The second is the multiplayer free flight, which will allow multiple people to hang out without having to engage in a game. Although in some ways it was quite straightforward to set up – after all we’ve got the other multiplayer modes already – there are some things you can do in freeplay that you can’t in the other modes which gives it some different challenges. It’s also going to be the first time we show off the new take-off and landing system.
Now the levels for Squadron 42 are starting to come together we’re in a position where we’ve started getting the game flow into our single player campaign and make it feel more like a game rather than just a collection of levels. At the basic level you go from one part of the game to the next, like what happens when you select “New Game”, or if you die in a mission, saving your progress, or loading back in again and so forth. The main challenge is the saving and loading systems, especially with a game as complicated as the one we’re creating, and will no doubt create lots and lots of bugs as QA try and break the system! Obviously the CryEngine has a lot of the game saving and loading already implemented on the FPS side, but with all the new functionality (and small things like space combat!) there are a lot of new systems that will need fixing up.
Other than that it’s continued work on all the other mechanics. The conversation system is coming along nicely, along with our StoryForge script writing tool. It’s very much in the iteration stage where we’re coming up with lots of different things to try and make it feel as natural as possible, which is important for the immersion. For example, getting the player to realize somebody wants to talk to you, not with a speech bubble over their head, but by their body language. Getting that right is a challenge. Too subtle and you won’t notice, too much and it’ll just look weird. And starting a conversation maybe by how you then interact with that character, rather than having to press a key, without it feeling clumsy. The hard work is not so much getting the initial system working, but the time and effort it takes to refine it with the combined efforts of the animators, script writers, designers, and engineers to get it to feel just right.
ART
Concept
Its been on all fronts again. Characters, ship interiors, ship exteriors, props, you name it – we seem to have touched it all this month! Hiring? Yes – always, we are staffing up our FPS weapons team
Environment Team – Ian
This month has seen the Shubin Interstellar interior building set hit Greybox complete, which means all the building components have a good amount of mesh detail and are looking lovely. We’ve also been building the PBR master shader library for this set – plastics, metals, glass etc, and applying them to an established beautification corner. This is where we take a corner of a level up to final art so that the Art Director can see a good representation of how the finished set will look. A modular pass has also been done on the exterior of Shubin to enable the design team to create other space station facilities.
Ship Team – Bjorn
This month, the Foundry 42 ship is hard at work finalizing 3 Ships, making them ready for either Hangar or Arena Commander!!
On top of that, we are very excited to release our first pass of our new damage prototype
which will hopefully impress you guys. It’s a completely new approach on how we handle damage for ships, mainly to future proof ourselves, improve memory usage, and give you guys more eye candy to look at when you shoot our ships to smithereens.
This is the first iteration, and is still a work in progress, but the results are already very satisfying!
The Gladius is being prepared for flight ready state. Neil is finalizing the art work, as well as implementing all the needed changes to have it working with the new damage prototype.
Matt has been working hard on the Gladiator, which will also feature the new damage model!
Then we also have the long awaited hangar release of the Retaliator!
I know you guys have been waiting for this one for a while, and you won’t be disappointed!
Nathan, Jay and Phil have been working hard to get this ship ready for you guys, pulling long nights to make sure everything is top notch!
Once we finalized these ships, there is no rest for the ship team at F42. We are jumping straight into cap ship production and the final production of the Starfarer, Idris, and Javelin. This will be a very complex production , so please bear with us on these massive ships!
After that we are going to focus on a full Vanduul Fleet in addition to a revamp of the Bengal Carrier to give you guys what you want.. the best D*mn space sim ever!
Characters:
Character pipeline – it’s a long and complicated road! Sculpting, crafting, chiseling, ripping, photographing, scanning, reworking – and that’s just one for one benchmark character.
VFX:
The VFX team had a great summit. All the team members met here in Manchester to further define the way forward for SC effects, Besides that there have been massive improvements in the damage system, coupled with some tricky techniques developed by the ship guys. The damaged ships are really starting to look cool and be efficient. Arena Commander has also received additional VFX as well as polishing the ones already in place.
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
Design
Since we’ve already posted more than enough words on this site this month, such as our mobiGlas Deep Dive, here’s a condensed report for BHVR design team to balance it out.
The design team was implicated in the UI summit. Some answers were found and the attack plan was refined.
Lots of effort was put towards the social module. Shops were populated, maps were refined, elevators were fixed, bar glasses were cleaned.
Even more effort was put towards planetside. Designers were busy with working on paper design, whiteboxing, and general support for more and more locations.
The mobiGlas deep dive article was written and posted. Hope you liked it! If you haven’t seen it I assure you it’s worth your while.
And last but not least, some of us got the chance to participate in our first Star Citizen panel for IGDA Montreal! It was a great experience and we got to meet some of the fans, which is always an honor for us! You can find out more info here!
Art
This is what art was up to this month:
We did a quick optimization pass on Terra to make sure that our work stays clean during the whole creation process. We began working on the paper layout for the additional Terra sectors and polished some of the old shops while optimizing the performance for each.
ArcCorp was revisited to merge new shops, polish some of the visuals, and to make sure that the frame rate is stable.
Nyx’s paper layout and WhiteBox was finished.
Finally, we spent some time dressing a tutorial map.
Concept-wise, we’ve been refining certain key areas of Levsky, the former mining colony based in the Nyx system, such as the Grand Barter, which is the equivalent of the TDD for this location and visually represented as a flea market.
We also worked on a prefab system that QV Planet Services used to use when they were trying to mine the asteroid. It’s composed of platforms that hook up into the rocky tunnels with hydraulic columns to support the heavy ceilings, beams, clamps, etc…
UI
This month Behaviour hosted a UI summit with invitees travelling from Austin, LA, Denver, and UK . What an experience! It was great to finally get everyone in the same room to talk about UI across the entire game. Exciting stuff!
We also continued to work on chat UI, contact list, multiplayer hangar UI, various logo design tasks, decals, and the pause screen also got some love.
Additionally we worked on mock-ups for a new and improved holotable experience, and started work on branding the mobiGlas depending on which shop you are visiting.
Programming
This month we’ve put a lot of effort into solidifying the multiplayer experience. Specifically, we’ve added UI Elements to provide more guidance and feedback to the players regarding the whole “Invite a friend to my Hangar” process. We’ve also greatly improved the stability of the actual multiplayer hangar as well as looking into the multiplayer planetside experience. A good deal of time was also spent on the chat implementation which is starting to look pretty good, and soon will be ready for an eventual release. We’ve also gotten back to working, ever so slightly, on the mobiGlas in order to fine tune the shopping experience that we hope to demo fairly soon.
You should soon be able to get your hands on a few changes to the holotable including control customization. Your favorite interactive gadget should be a bit easier to use with the addition of automatic filtering and sorting. As far as control customization is concerned, you should have more control than ever on controlling continuous inputs with the addition of a new curve editing tool. This tool will allow you to easily remap how the input should affect specific control options.
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
How’s it going Citizens? Here at IllFonic we’ve been working feverishly to get the FPS module in a good state for showing at PAX East. This has been quite the challenge as a few new things came online recently which introduced quite a few new bugs that required a slew of items and animations to be reworked. Luckily, we had Mr. Bender from CIG Santa Monica on site to help out on the animation side of things. He has been instrumental in getting all of the new animations squared away with our local team. Beyond that, he came during the worst snow we’ve had in over a year, so… Who knows? He might even become a local!
Engineering
Squashing bugs, bugs, and more bugs. The engineers have also been polishing the zero-g push & pull system, which has been a challenge, but is coming along nicely. A large amount of work has been done on the HUD and UI, including elements to support the FPS game modes. Lastly, programmers have also been supporting the animation team, which has been quite a bit since most of the mechanics are driven by the animation system.
Art
Squashing bugs, bugs, and more bugs. The art team has also been putting the final touches in terms of lighting and performance tweaking on the levels that will be shown at PAX East and release with the module. Final models were done on our new weapons and gadgets, and material work for these models is now under way.
Animation
Boy oh boy have these guys been busy. Over the last month they have been hooking up all of the new animations with the new rig. This literally means that every animation needs to be re-targeted and exported so it’s quite a bit of work. Steve Bender has been here to help out and make sure that everything looks great in both 1st person and 3rd person perspectives. They have also been busy squashing bugs, bugs, and more bugs.
Design
Squashing bugs, bugs, and more bugs. The designers have also been focused on tweaking weapon balance, the aiming model, and play-testing the levels. In addition to the work being done for PAX, progress continues on the new game modes and maps that will be coming after the initial release of the FPS module.
VFX
On the VFX side, new visual effects were created for the grappling device while all other weapon FX were revisited and polished up. Everybody is happy with how they are looking now and we hope all of you Citizens will enjoy them too.
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
Greetings Citizens,
It’s been a busy and exciting month for us here in Montreal. It turns out that coding does indeed keep you warm… So here’s a quick look at what we’ve been doing this February.
The Homepage
The end of last year was marked with a rework of the website’s homepage. Like we announced then, this was only the first step of the global rework we’ve undertaken : this month saw the arrival of step “1.5” with the new Fly Now flow, a quick and easy way to start with the project and get going fast. Its success and the recent increase in new backers show just how much newcomers were in need of some guidance, and we’d like to welcome the (over) 10,000 new backers who joined the community this February.
We’ve taken quite some time to rework the homepage itself. RSI is quite unique in the amount of content produced by Cloud Imperium as a whole, and this new version will aim at giving comm-links a better and clearer layout. At the same time we’re working on a better hub for comm-links themselves, with a focus on series and the search engine for comm-links as a whole.
The Community Hub
These steps will be completed by the new Community Hub that went through its design phase in February. As we announced previously, this new Hub’s mission is to give, at a glance, a broad sense of how the Star Citizen Community lives and breathes. It comes with a set of new tools and functionality that will put your involvement to the test: all fans will get a chance to show their own vision of the project through what will essentially be your hub.
New Storefront
Soon, you’ll be able to use credits earned in Arena Commander to try out any ships or ship components you don’t yet have. This is the third storefront we’re giving you (after the Pledge Store and Voyager Direct), and of course many aspects of the website are impacted : you’ll be able to manage your gear and the credits you earn directly in the website from the My Account section, and this is now the second interface we’ve set up that is being fed directly from the game servers (the first being the Leaderboards a few months back).
The Orion Minigame
Most of you have seen the amazing design that is the RSI Orion mining platform. We took this chance to bring you another minigame (the Carrack had seen the first one) which explored space mining in the Star Citizen universe. We plan to have a minigames section in the site very soon if you’d like to replay it.
What’s next
February was heavy on the design side of Turbulent, and now’s the time to implement all that and let you experience it. All while we’re still working on the highly anticipated Starmap. Our current task is to set up a thorough user interface that will do justice to the density and complexity of data we’re plugging into. More on that soon… plus a few surprises along the way.
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
February has been quite a heavy planning month for Moon Collider. With the Cloud Imperium Frankfurt studio taking on some new members focused on FPS and AI, we spent quite a bit of time helping them get up to speed with the current state of things, figuring out new processes, and reworking our roadmap for features that we will be delivering for the various modules this year.
A lot of our time gets spent in planning and communication, and as you can imagine, with quite a small team here in Edinburgh that can have quite an impact on the amount of time we have to work on cool features. So the addition of Todd Papy and Francesco Roccucci means more dedicated resources at Cloud Imperium to help with the very difficult job of planning and prioritizing all of the AI features needed by the different Star Citizen modules.
We’re also expecting Francesco and Chris Nolan, both veteran AI behavior designers, to help get our FPS character behaviors up to an awesome level of polish over the coming months. Getting character combat behaviors right can be really time consuming, so we’re thrilled to have such talented people added to the Cloud Imperium team.
So, while we got a bit less engineering work done this month than we normally do, we think these additional AI resources for Star Citizen are going to make a huge difference in the coming months, allowing us to deliver higher quality AI faster, and that’s good news for all of us!
Design
We had a brief AI summit in Manchester this month to get Todd, Francesco and Chris up to speed on the current state of the AI. During that time we also took the opportunity to have discussions with designers for Squadron 42 and Arena Commander to figure out which AI features they’re needing most. It’s always really rewarding to sit down in the same room with designers and play through a level to see what is and isn’t working from their point of view.
Following the summit we had Francesco visit our Edinburgh office for several days for a lot of discussions about our feature roadmap and how best to prioritize across the different modules. This was also an important opportunity to help him get an in-depth understanding of our Kythera AI framework so that he will be able to help providing support to the rest of the Cloud Imperium team.
A lot of specific design discussions happened to look at ways to improve some areas of our AI framework, such as our behavior tree and higher level tasks systems; improvements to our cover system and how to streamline the workflow for level designers when setting up new areas; how to link different parts of a level together to allow AI to navigate with things like ladders or climbing up and jumping down; and a lot more. Expect to hear more about these features as we move from design to implementation over the next few months.
Engineering
Replacing our prototype smart object system with the more fully featured Usables system has been a big focus since the start of the year, and this month we got the first version of the new system into the hands of designers. The feedback so far has been good and you will be seeing the first results of this in the upcoming Social Module. Whenever you see NPCs interacting with objects in the world, that’s the Usables system in action, so keep an eye out for it!
Speaking of the Social Module, we’ve also been doing some work on improving the performance of our AI code to allow huge numbers of characters to be active at once while still retaining a good framerate. We did a bunch of profiling to see where the slowest parts of the code were, and luckily we’ve had a few easy wins so far that gave some pretty nice performance gains. It’s still early days for the persistent universe so we expect to be doing a lot more of this in the future as features progress, but for programmers, it’s always a joy to make a change to the code and see those milliseconds go down rather than up!
We’ve been making various improvements and doing fixes for Arena Commander 1.1, with a particular focus on the upcoming tutorial. Because of the semi-scripted nature of a tutorial, we’ve found designers needing to do things with ships that they haven’t had to do previously, and so we did some work to allow the designers to get the results they were after. For example, you’d think that if you’ve got well tuned AI flight behavior for ship to ship combat, then just making a ship fly slowly inside a hangar would be a piece of cake, right? Well, it turns out that AI tuned for high speed evasive maneuvers doesn’t do so well trying to fly really slow in a confined space, at least not without a bit of persuading.
For the tutorial, we also found that we needed to implement some special attack modes for ships that need to do something very specific in order to teach the player how to perform certain actions. So for example, we created a behavior that makes a ship just sit on the spot and aim at the player’s ship, and another that makes the AI fire a single missile. It’s not something you’d want to see in a frantic session of Vanduul Swarm, but in a tutorial context it’s just what you need.
We’re quite happy with what the ships are now able to do in the AC 1.1 tutorial, and we think the community are really going to enjoy this release.
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
Hello everybody! Assistant Community Manager Will here to bring you this month’s Community Report! February has been quite busy for the Communiteam. Based on your feedback we have continued to tweak all of our weekly shows, and have even created an entirely new one! We’ve also introduced new initiatives such as our #HelpTheHerald campaign. We are always listening to your feedback and appreciate it as we continue to try new things.
Shows
Each episode of Around the Verse we aim to try new things to improve the show. This month we changed our News from Around the Verse segment to include each studio discussing their weekly contributions. In addition, we’ve added two new segments titled Sandi Goes to Flight School and Empire Report. We are happy that these have been received well and we plan on making both Empire Report and Sandi Goes to Flight School re-occurring segments.
In our weekly stream, Reverse the Verse, we realized that our discussions focused on the Santa Monica team which wasn’t fair to our other offices. So we’ve now integrated the Austin and UK offices to take turns appearing on the show. This has led to a more diverse set of questions and we are happy to bring a new element to the stream.
Don’t worry, we didn’t forget 10 for the Chairman! We realized that you enjoyed seeing the images during our news segment in Around the Verse, so we’ve integrated that format into Chris’ answers. Additionally, the Sneak Peek segment in Around the Verse is a fan favorite so we’ve doubled our effort and we are proud to say that 10FTC now features a sneak peek as well.
This month we also debuted Wonderful World of Star Citizen. Hosted by the community’s own Disco Lando, this monthly show highlights videos, podcasts, and other amazing creations from the community. Feedback for the first episode has exceeded our expectations and we are certain that you will all enjoy the next episode.
Fan Videos
February has been an amazing month for fan videos. FiendishFeather has begun a new series titled Bulkheads. Inspired from the popular Red vs. Blue series, Bulkheads will feature two hapless citizens as the traverse the verse. While a bit sillier than his popular pirate video Pieces of Eight, we can’t wait to watch this series unfold.
Yearsonehundred, the creator of the original Imagine trailer, has returned and once again blown us away with his new video, The Fighter Pilot. The first entry in his new Star Citizen Career video series, The Fighter Pilot is a collaboration between multiple community members, including our favorite voice actor Trendane and musical guru Pedro Camacho. At less than one and a half minutes, this video is a must see for any Star Citizen out there.
February was quite a busy month for us, but we have much more planned for you all in March. We value your feedback and we continue use it to get better each and every week. Thanks and we’ll see you next month!
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
Chris Roberts answers your questions about Star Citizen in the latest edition of Ten for the Chairman! Chris answers ten questions chosen from development subscribers in each show. Want your question considered? Learn more about subscriptions here.
3:09 – Org recruiting NPCs. 5:29 – NPCs using different loadouts. 6:45 – Traveling without the quantum drive. 8:21 – Left helpless in space. 9:22 – Performance changes in engine. 12:10 – Replay Squadron 42 missions. 12:37 – Other handheld weapons. 14:29 – Resources respawn in the PU. 16:13 – NPC & Human scanning. 16:59 – 64-bit transition update.
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
Chris Roberts answers your questions about Star Citizen in the latest edition of Ten for the Chairman! Chris answers ten questions chosen from development subscribers in each show. Want your question considered? Learn more about subscriptions here.
3:09 – Org recruiting NPCs. 5:29 – NPCs using different loadouts. 6:45 – Traveling without the quantum drive. 8:21 – Left helpless in space. 9:22 – Performance changes in engine. 12:10 – Replay Squadron 42 missions. 12:37 – Other handheld weapons. 14:29 – Resources respawn in the PU. 16:13 – NPC & Human scanning. 16:59 – 64-bit transition update.
