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.
Hey there folks! As you all know, Discovery Freelancer is not an original game. Being a large expansion of 'Freelancer' made by Microsoft, we technically don't own a slot in the game world, as we're nothing more besides of a very large expansion of what was laid out to us by Microsoft.
We count on
you
as players to continue keeping this place alive and well. The mod was created for the players, and survives on the players. We're lucky to have a Dev team who still works on the game after the 9 years which this Mod has been in existence for. Public appeal is very, very important for us to keep living. ModDB is a large part of the players coming into Discovery.
A large variety of people have discovered us through ModDB, and have joined the community in some way or another soon afterwards. Sadly, right now our modDB page is rather inactive. Desolate. Not a very good sign for any players looking for a Freelancer mod. As of right now, the Discovery team already has our hands really full, and are unable to actively pay attention to the ModDB content, since we already have our hands full with other things going on internally on Discovery.
We believe that it's time to extend our hand out to the community for anyone who is willing to help us get a little public appeal. Content submitted by the community, having a good chance to show up publicly to appeal to the masses that the ModDB provides, targeting users who are looking for specific mods of their favorite games.
As of right now, we're looking for anyone who might have some cool content that would help spice up our slowly becoming desolate page. While the Staff will take care of the major stuff, such as the new updates and patches (The .88 announcement is going up today, that's late already) -- Player content is more than welcome.[/feedquote]
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
Note from the Chairman
Greetings Citizens,
Last week, Kotaku ran an article showcasing Arena Commander’s combat. While the focus was that dogfighting looks great in action, one other thing immediately stood out: the video was an Aurora pilot flying with a HOTAS and TrackIR setup… and he was schooling Hornet after Hornet! The video, embedded below, tells me that we’re on the right track in creating a skill based game where battles are decided by the abilities of the pilots just as much as the capabilities of their equipment.
One of the design tenets of Star Citizen is that it needs to be a complete experience regardless of what you have purchased. Someone buying a starter package needs to have exactly as much potential as someone supporting development by pledging for a new ship or a purchasing a new weapon. I do not want to make a game where you feel compelled to spend anything but time to continue playing.
In the Persistent Universe, that will be easy: you’ll earn credits flying missions, locating star systems, hauling goods, hunting bounties and through a dozen other activities. You’ll rapidly explore and expand your universe. But the pilots helping us develop our spaceflight in Arena Commander don’t have that ability… yet!
With Arena Commander 1.1, we intend to roll out a system called REC, or Rental Equipment Credits. In essence, you will be able to earn credits to rent equipment to use in Arena Commander by playing Arena Commander’s ranked modes. We want to reward backers for their time spent with the early game with a more expansive experience, not prevent them from accessing things that will be readily available in the Persistent Universe. You’ll still be able to support the development of the game by pledging for ships and weapons, and these will carry across into the Persistent Universe but you will no longer have to contribute additional money to fly a different ship or use a new weapon; You’ll have a choice. Spend time playing the game, which will earn REC to be spent on ships and weapons for use in Arena Commander or pledge for these items, supporting the ongoing development and running costs of the game. It’s the classic time vs money proposition and either way you’ll be helping making Arena Commander and Star Citizen better! This is always how the final game was intended to work and we’ve decided that we need to bring this dynamic into play sooner than later!
Star Citizen designer Calix Reneau details the system below, which we believe is a winner. Now, we’d like your feedback: is this the right direction for the system? Where would you like to see it go, in the near term and the long? Letting players earn credits in-game is a no-brainer, but working out the specifics is going to be an ongoing process no different from how we are continuing to work out flight controls and weapon balance!
From my perspective, Arena Commander is shaping up to be a fantastic standalone experience, something backers will want to continue to play in their new sim pods even after the Persistent Universe launches. I’m grateful for the testing and support the community has provided to get us to this point. It’s something every one of you should be proud of… and now let’s make it even better!
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
We’ve all been there: a budding young Aurora pilot loads up Arena Commander to play for the first time. That first battle isn’t a great success, but between the ‘First!’ medal bonus and a lucky missile, enough REC is earned that an F7C Hornet doesn’t seem that impossible to earn. A few matches later, the mechanics of space flight are starting to be understood, so the REC flows a bit easier and it isn’t much longer before even the Super Hornet is within reach. Diving all in for the big guns, our plucky hero has become death, destroyer of worlds… and it feels good! But as often happens, life gets in the way, and it’s over a week later before the Star Citizen logo comes back on screen. Imagine the surprise to find that Super Hornet still selectable in the Arena Commander start menu! A few matches later the rental use runs out, but it’s enough time to earn up the REC to take advantage that sweet renewal discount. Dogfighting is a great thrill of course, but eventually curiosity takes hold and the next rental is an M50. What a difference! Racing seemed so trivial before, but this thing can really fly. At this point, any new arrangement of ships or equipment is always attainable with just a little bit of focused play. Still, there was something special about that first Super Hornet, so maybe it’s worth keeping around…
What are REC?
REC, or Rental Equipment Credits, is a virtual currency that can be spent in Voyager Direct or the mobiGlas virtual store to rent software licenses on any equipment that can be used in the Sim-Pod (future iterations of Arena Commander will be accessed through a pod added to your Hangar.) Players earn REC through success in Sim-Pod activities – Arena Commander, the upcoming FPS Module, etc – with additional medals providing bonus REC and recurring incentives for progression.
REC is earned by playing competitive (ranked) multiplayer matches of Arena Commander, the FPS Module or any other Simulated Experience in Star Citizen. Each match awards REC from a common pot, awarding the greater share to the winners, which is then split among the members of the team based on performance. For example, in Arena Commander:
Squadron Battle: – REC is earned based on the number of kills plus the k:d if positive, weighted against the ticket difference.
Murray Cup: – REC is earned based on the final position multiplied by the proximity to World Record (by ship), weighted against Personal Best (by ship)
Capture the Core: – REC is earned based on personal score weighted against the score difference.
Players can also earn bonus REC from medals, which are awarded for various milestones – umber of kills earned, number of missiles dodged, total matches, etc. These medals track over multiple matches and are recurring, so players can always make some progression even if they only play a match or two here and there.
To prevent exploitation, this pot is associated with a total score expected from all participants, and scales REC yield based on the total score actually achieved. It also scales based on the number of participants. For example, a REC pot of 12,000 with a total score of 100,000 will only split 9600 REC if the players only collectively manage to score a total of 80,000 points. That same game will only split 4800 REC if the 10 player match only gets 5 participants.
All rented equipment is rented for one week of real time use – guaranteeing that you always get at least a little bit of time with the ship. Ships and weapons cost 10% of their UEC price, rounded up. Once an item has been rented, it can be renewed for another week at a 20% discount. Renewals can only be bought a week in advance. (Remaining rental time is visible in your RSI account and within the Sim-Pod HoloTable)
There are also broader goals available for the REC endgame – for example, we envision building a Community Chest into which players can donate REC that builds towards permanent prizes and other gameplay experiences. Imagine having the option between renting new equipment or helping the community earn something together… it should make for an interesting challenge!
Current Balance Plan
Averaged at 1800 REC per hour. Please note that this currently represents ‘back of the envelope’ thinking; actual balance will likely alter significantly after the system launches and we determine how players use the system. But the goal remains to create a system that makes renting additional equipment a fun challenge rather than an impossible chore.
Ship Cost: at 10% UEC, F7C rents for 14,000 REC. (7.7hr)
Weapon Cost: at 10% UEC, M4A rents for 800 REC. (26.6min)
Renewal Discount: at 20%, F7C renews for 11200 REC. (6.2hr)
Real Time Rented: 1 week.
Payout Pot (Per Game Mode): 10k for full Squad Battle, split 70-30.
Game Modes that Yield REC
Squadron Battle
Battle Royale
New Horizons Raceway
Capture the Core
Can I use rented ships and equipment in non-ranked modes?
Yes, and there will be no limit on such uses.
How do I spend REC?
REC is spent on ship and equipment rentals or Sim Pod unlocks. This can be done from Voyager Direct, the mobiGlas, or the Sim Pod. Once a ship/item is rented, it can be renewed for 1 additional week at a discount.
As the system is developed, REC can also be spent to unlock additions to your Sim Pod, such as aesthetic changes like different background images/theme in the menus, or gameplay changes like opt-in handicaps which can be taken to boost REC yield at the cost of additional gameplay restrictions. Finally, REC can also (eventually) be donated to the Community Chest, a mystery box that results in Community Events when enough total REC is accumulated. Community Events benefit all players who log on while they are in effect.
Will my equipment carry over into the Persistent Universe?
No, equipment rented in Arena Commander will be available only in your sim pod. When the Persistent Universe launches, you will have access only to upgrades purchased with UEC (or provided as gifts during the pledge campaign.) But we anticipate Arena Commander continuing to exist in the Star Citizen universe; it is, after all, a game played in SC’s future!
Why have rental items instead of permanent ones?
We know that choosing rental equipment instead of permanent AC-only unlocks will likely be the most controversial part of this plan. We’ve run through countless scenarios offering one, the other or a mix of both… and what we’ve decided is that at this time, rental is the way to go. What follows is the five key points we used to make this decision:
Arena Commander progression should NOT equal Persistent Universe progression. We believe strongly that players need to go out into the world to truly progress; a system that permanently rewards you for staying home and playing the simulator will reduce that experience in the long run.
It is a buffer against exploits. We fully expect players to discover bugs and loopholes in the REC system… but with a one-week rental deadline, the most damage they can do to the game is unbalancing it for one week.
It’s a first blush at future balance goals. The goal has always been to balance effort and convenience – whether you have time or money, you should be able to have a good experience. That’s going to take a lot of work to get right, so this is the earliest possible version of it to help us start to understand how this will work out in the wild.
It allows for a tool for ‘directing’ testing. If we are going to be working on a particular ship or item, we can put it on sale – a tactic that wouldn’t affect players who had already unlocked it.
It prevents stagnation during alpha. It should not ever be possible to “complete” (or win) this pre-alpha game.
What’s Next?
We envision enhancing the REC system alongside everything else in Arena Commander going forward! In addition to building the system out based on player feedback, we have several systems we hope to deploy in future patches:
Daily Challenges
REC can be earned by completing personal and community daily challenges. Community challenges pay out at the end of the day if they have been fulfilled, and reward all players who have contributed to the challenge at all. These also have the benefit of allowing new gameplay features to be highlighted.
Personal Challenge Examples
Get 10 kills at 50% throttle
Dodge 10 missiles without using countermeasures.
Capture the Core 10 times.
Community Challenge Examples
Kill 3000 vanduul in Coop Swarm
Complete 500 laps in Old Vanderval
5000 total kills.
Community Chest
The Community Chest accumulates with REC donated to it until it reaches 100%, when it activates a surprise Community Event that is available to all players during its duration (which can be set individually for each event, but which would generally last 2 weeks). When it reaches 100%, a Community Event begins and is available to all players during its duration.
Discounts / Bonus Yield
REC discounts on specific ships and equipment can be used to encourage users towards their use. Ships can also give bonuses to REC as additional incentive.
We are hoping to launch the REC system with Arena Commander’s next major patch, currently scheduled to be AC 1.1. This will allow backers to earn REC and spend them on store items. Additional functionality will be added as we go, just like the rest of the AC development process! Until then, please provide your feedback below. You’re helping us build Star Citizen AND Arena Commander, and we want to know what you think!
DISCLAIMER
As with any design post, this article represents our current thinking for the systems covered. All content is subject to change as a result of testing. The numbers provided here represent data that is current as of publication, but which will likely be altered in a number of ways before launch to create the best possible Star Citizen experience.
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
UPDATE
It looks like we managed to break Arena Commander’s matchmaking services! Cloud Imperium QA is on the case, and we’ll have a full report in the future. For the moment, though, it looks like it’s going to be impossible to play together this afternoon. We’re frustrated not to be able to play with the community today, but we’re grateful for your help in testing the game to (and in this case, beyond!) its limits. Today’s play test may not have included much dogfighting, but it has identified an issue we’ll need to work on immediately!
Greetings Citizens,
We want to dogfight with you! On Monday February 16th we will be having Devs Vs Community matches of Arena Commander on the live servers! (not the PTU) If you want to try and take down members of CIG both in Santa Monica and in Austin, including the Chairman himself Chris Roberts, all you have to do is load up Arena Commander at 4:00PM PST.
Pilots from CIG will be queuing into Battle Royale matches for an hour looking to see if anyone can withstand the might of the UEE.
We want as many people as we can playing to both test the serves and have some fun. Let’s break a record for most people playing at a time! Please come join us for the first official Devs Vs Community playtests.
In the future we will pick times more suitable for other parts of the world. We want as many people as possible to join in on the fun. Thank you citizens and we will see you in Arena Commander!
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
The February Subscriber Flair is the Gladius ship model, by Takuetsu Starships the most trusted name in ship models. Subscriber flair is a small gesture of our appreciation. The ship model should already be in your hangar!
This realistic ship model of the Gladius is the fifth in a collection of Star Citizen’s ships. Display your Gladius with pride, and then collect other models to complete the display. Includes stand and collector’s box.
The Gladius is an older design which has been updated over the years to keep up with modern technology. In military circles, the Gladius is beloved for its performance and its simplicity. A fast, light fighter with a laser-focus on dogfighting, the Gladius is an ideal interceptor or escort ship.
Takuetsu Starships is a leading die-cast model spaceship manufacturer based in Fujin City, Centauri founded in 2894. They hold the reproduction licenses from spaceship manufacturers and engineering companies such as RSI and Anvil Aerospace. Takuetsu are well known amongst collectors to make superior, highly detailed models. They produce perfect replicas of personal, commercial, military and even alien spaceships in various scales.
More information about subscriptions can be found here
Uncle Finn here, yet again. You missed me, didn't you -
So we've taken a look at the feedback concerning the Pirate ID, and feel some further changes should be added to the ID. Specifically, howe they deal with transports and freighters, as well as actions outside of House space, as listed in the rules section.
Moving forward, here is what the new Pirate ID will look like:
Quote:Pirate ID
Independent Pirates are people who want to make money by extorting it from others or through other unlawful means. An independent pirate acts only for his own benefit, and has no allegiance to anyone. Pilot carrying this unlawful ID is a Pirate, who:
- Can defend itself and ships of the same affiliation
- Can demand Credits or Cargo from Freighters, Transports and Liners in House space and attack them if they do not comply
- Can pirate any ships outside of House Space (Bold and Italic) and attack them if they do not comply
- Cannot ally with any lawfuls
- Cannot use any transports with more than 3,600 cargo.
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
Greetings Citizens,
New year, same job: make the Best Damn Space Sim Ever! In January, Star Citizen’s teams worked on all aspects of the game, with a focus on improving Arena Commander and preparing to launch First Person Shooter and the first ‘social module’ piece of the persistent universe (oh, wait: and Squadron 42! It’s the first month of a BIG year.)
We also held our first ever backer ‘town hall’ in San Antonio, and couldn’t be happier with how it went. You can see all five of the panels below, and the feedback we collected is already impacting Star Citizen’s long term plans.
Please read on for the latest from Cloud Imperium’s studios and outsource partners around the world.
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
Greetings Citizens!
Welcome back for another monthly report! The team came back from the holiday break refreshed and excited to continue the momentum from last year. January was an extremely productive month both on the development front and the planning front laying a solid foundation for 2015. Let’s continue to the discipline updates so we can let you know what all transpired and what we’re working on!
Engineering
With Engineering in January there was a fair amount of long term planning that was covered during a Technology Summit in the UK involving several members of the LA team. During the month of January our LA Engineering team has been working on quite a few things you will see being released over the next couple of months.
We’ve finalized our implementation of the paint system for all vehicles including the buggy. As many of you saw we released swappable buggy paint jobs during January. This was an important step because it finished off our implementation of the first pass of the vehicle paint system. Now that this technology has been finished, tested, and proven on the buggy the Art team can proceed with implementing swappable custom paint jobs for all of our ships which you’ll be seeing very soon. This was very important to us as it allows us to begin delivering on many of the custom skins sold or included with various packages during the original campaign.
Development has also continued on the missiles, countermeasures, and signals system. With the first introduction of this system in December there were some features that we weren’t able to quite finish such as emissive sources that can obscure sensors in a generalized area or direction. Things like nebulas or a star having impact in a broader way. For example you may in the future see that it is much harder to get an Heat lock on an enemy who is flying directly at the molten core on Dying Star because the of the heat from the core blinding the heat sensors on your ship and missiles relative to the lower output of the enemy ship you are attempting to target.
In addition to the features that weren’t quite ready for primetime there are also a fair number of gameplay balance issues and bugs that we’ve been working to resolve within these systems that were highlighted by players in 1.0.0 and 1.0.1. We’re continuing to improve and refine the system in Arena Commander so that by the time the PU comes about its polished and well balanced.
Another important focus for the Engineering team has been a refactor of the item port system. Sounds exciting right? Well it is! As you may or may not know we wrote a custom item way back towards the beginning of Star Citizens development. It is a system for handling networked, animating, and data driven items that are attached to other items or ship parts through what are called item ports. Stated differently, this is the system that makes it possible for your weapons, items, and ships to all attach to one another, update each other with their data (how much energy they draw, etc.), animate, and exhibit the same behavior on all clients over the network. This system is pretty cool and in use already, so why does it need a refactor you might ask… Well let’s explain!
As we’ve continued development on Star Citizen and moved on from the days when this system we’ve added a lot of new features that weren’t around back then. One of the things that we’re adapting the
item port system for is all the player characters. So when you’re Heavy Marine is running around in the upcoming FPS release he will be using the same unified system for his items and attachments as your ship. We’re defining item ports on the character just like ships that have rules about what size things can attach to them and hook up into the player’s data driven entity. So for example if you equip an energy pack to port 24 it feeds into the suit energy which can be drawn down by a personal shield in slot 15. This is just an example for illustrative purposes but it should convey the basic principles.
Where this gets really cool is as we move towards the integration of FPS and ship combat with things like multicrew ships. Because the characters and ships both use a unified item port system they can interact in ways that were never before possible. So for example now when you sit down in the cockpit of your Hornet we can plug in your character and attached items to the ship. I.E. if your EVA suit is low on power we can charge your suit off of your ships reactor via a plug in the cockpit. If you sit down into a turret that is supposed to display a physical screen if you don’t have a helmet the ship can now query your characters item ports and check against the presence of a helmet. If you have one it can pipe in the relevant targeting data from the ship to your visor or it can decide it needs to bring up a physical display instead. Pretty cool, right?
Speaking of the visor we’ve also been refactoring the current implementation of the HUD visor for ships so it is much more extensible, optimized, and completely unified and interchangeable with the FPS HUD. The idea being that you can now toggle between visor modes yourself or the game can switch you contextually based on what you are doing. Sitting in your ship and the ships HUD will pop up in your visor. Hop out and pull out your gun and the visor will flip over to FPS combat mode and bring up a different set of information within the same framework. All in all this will be a much more robust and optimized implementation of the HUD that supports the seamlessness that so critical for the immersion of Star Citizen.
Design
On the Design side, January saw the hiring of two additional Technical Designers here in LA, Matt Sherman and Kirk Tome. They’ve already proved invaluable at freeing up Design bandwidth to tackle some longer term goals without sacrificing continued iteration and polish on the currently released content. We’ve tackled the design and prototyping of several of the longer term systems during this month such as how cargo will work, not just a paper design but actual in-engine prototyping of the core principles of the system working based off the paper design. There has also been a fair amount of design focus on working with Engineering on the polish and development happening on the signature, missile, and countermeasure system that we covered above.
As you may know from the write up on the ship pipeline the Design team plays in important role in the development of every single ship that goes into the game from ideation all the way to final implementation. To that end we’ve kicked off a fair number of ships at the beginning of this year. Ships like the [REDACTED], [REDACTED], and [REDACTED] were all kicked off this month and are moving forward in the Concept phase and still more were greenlit to start moving into the Hangar and Flight Ready phases. The design team has been working diligently on whiteboxes and nailing down metrics for virtually every item onboard ships. This was a step that we added to the Ship Pipeline when we took it over here in LA back in September and it’s already been paying dividends in less mistakes and reworks down the pipe. It’s also proving to be one of the most important stages in ship development!
We’ve spent a lot of time in the past talking about the ship pipeline but what are ships without items? To this end the Design team has begun the large undertaking of mapping out the entirety of the long term plan for ship items. Not only all the functionality of each ship item/weapon but also what different items or weapons of the same type will do differently and mapping that to a particular manufacturer from brand consistency. So not only do we have a lot of new items and weapons designed coming out of January but there is a lot more focus on making them feel different from one another and have distinct advantages and disadvantages and having those relate to the various manufacturers across all the types of items and weapons they make. If it sounds like a massive undertaking, it has been, but we’re already seeing this time spent paying off as it creates a much more unified and interesting framework for items within Star Citizen.
Last but not least is the tuning! Virtually every day our Design team and QA team are discussing balance changes, scouring the forums reviewing player feedback, and discussing action plans for addressing the issues that are identified. It cannot be oversold how important this time spent iterating and collaborating with QA and the community is. During January there has been a lot of adjusting, tweaking, and tuning happening some of which you saw in 1.0.1 and a lot more that will be releasing with 1.0.2. The play experience of space combat is very important to us and very important to the game so just remember, if you don’t like something or have an idea for how we could improve something, voice your opinion and let us know. It may take some time to get feedback addressed but we are always changing and improving it.
Art
Our Art team has had an exciting January! This month we hosted all the global members of the ship team in LA for our first ever “Ship Summit”. It was a great opportunity for our global Art, Design, Animation, and Engineering leads on ships to get together and discuss the current pipeline, improvements/changes, best practices/techniques standardization and for some of them to meet in person for the first time. Coming out of the summit we’ve further refined our pipeline and established common gold standards and techniques around which everyone can align globally.
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
The fruits of this standardization and improvements to our modeling techniques are born out in the new items that are being introduced into the game. The new shield generators were all bit using the new pipeline for ship items/weapons and use the latest modeling and Tech Art techniques we’ve begun employing for all ship parts potentially other parts of the game as well. Our items have really come a long way from where they started and the visual improvement is pretty apparent, even for those who aren’t artistically inclined.
Furthering that our Art team has also been busy making use of the new paint system and the work done by Engineering and Design to get it so players can swap paintjobs. This is actually a great example of what makes open development so cool both for players and for developers. With the paint system
you’ve actually seen the first implementation for 1.0 with some ships having bespoke paintjobs using the new system. Then we iterated and for 1.0.1 added them to the buggy to prove the system was extensible and used that as an opportunity to put in the capability for swapping the paintjob at runtime. Once all that was complete we moved on to adding that swapping ability for players on the Aurora with some of the skins that we’ve promised as well as a fun one for the community in 1.0.2.
We’ve also begun concept, modeling, and flight readiness work on a number of upcoming ships. Some fan favorites like [REDACTED] and [REDACTED] are high on our list and progressing well towards hangar ready and flight ready respectively. Suffice to say that while January did not see the release of a new ship there are a lot of them running through the pipe right now and we’re excited to show them off once they’re ready!
Art, Design, and Engineering have been working collaboratively on some upcoming improvements to our damage system for ships that we look forward to sharing with you all once they’re all up and running. These improvements will vastly improve the fidelity of damage to ships while actually optimizing performance from the current state of the system. Coming out of the ship summit our internal team is looking forward to using the new system.
Last but certainly not least on the Art front are Characters. Following the Ship Summit we’ve been working on putting together a demo for the character team of where we can apply some of the best practices and techniques used by the Ship team to the character armors and other hard surface clothing/materials to continue to push the bar even higher for the visuals in Star Citizen and Squadron 42.
Animation
As many of you may already know, towards the end of last year we shot a lot of motion capture and performance capture at Imaginarium in London. What you may not know is that we’ve also created an entirely new and greatly improved rig for our characters this rig was created by the aptly named, John Riggs here in LA in close collaboration with the other members of the Character team globally. So, in the month of January we’ve spent a lot of time refining that rig with the new characters and new animation data from our recent shooting. So far progress has been great and the new visuals are looking very promising and we look forward to improving the animations in the game substantially for everyone as soon work concludes on this.
Well, that wraps up the department updates for this month and covers much of the progress that we’ve made this month. Before we let you go we just wanted to say that it is important to note that while each studio provides the community with a separate studio report much of what we’ve covered above wouldn’t be possible without our comrades around the globe. It cannot be stated enough that while there are multiple studios working on this project there is one team working together and it is only with each other that we’re able to make this the BDSSE.
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
Hi everyone!
The New Year is off to a great start and January has been a busy month as always. We’ve made some updates to Arena Commander, have been very focused on planning for the coming year’s development efforts, and we shared a ton of information at the PAX South event right in our back yard here in San Antonio. Many people from the Austin studio were able to attend and participate in the event, and I certainly enjoyed the time this gave to interact with many awesome members of our community. We had Ben and James here and filmed a lot of footage that you may have seen, or will see soon on Around the Verse! Here are some in-depth reports from other teams in the studio!
Persistent Universe Team
ART
Our Art Team this month has been primarily focusing on props, characters, and environments. Our character team, comprised of Megan Cheever, David Jennison, and Wilbur Lord, completed a few of the NPC’s you will be able to see ambling around ArcCorp Plaza when the Social Module launches soon. Specifically we finished up the Medic, Bartender, and one of the Bar Patrons. We’ve got a few more characters to finish up before the Social Module launches, but it is exciting getting to meet a few of the faces we will get to see in the Persistent Universe.
Some of our other artists are working on fleshing out some of the cool elements that will eventually be featured heavily when the game launches. Ted Beargeon has been spending much of his time concepting out a communication relay that will send information through Jump Points. Watch the PU Town Hall presentation to get a sneak peek! Patrick Thomas, our Sr. Artist, finished up modeling the Repair Drones that will appear outside of space stations. Ken Fairclough made some concepts of various medical props that will be found in the Medical Unit. Last but not least, our VFX artist Lee Amarakoon created some nifty fountains that will appear in Terra Tower on the Terra Prime landing zone.
This month we also played host to CIG’s Environment Summit. Artists and designers from Foundry 42, CIG LA, Behaviour, and Illfonic flew down to Austin to spend a week ironing out the kinks for how we build our environments across the project and solidifying crucial details for standardizing environment construction. The Art Directors all got together and spent some time discussing architectural styles for our environments. We’ve got some pretty interesting ideas for creating some interesting and diverse locales across the ‘verse.
DESIGN:
The Design Team spent much of this month creating LISTS! Between lists of props, lists of ship parts, and lists of NPC animations, there was plenty of list-making to go around. These lists will serve a variety of purposes, and all are beneficial. The props list will go to outsourcing to help provide direction when creating the art assets. The ship parts list will help when scheduling out the creation of ship parts and weapons to eventually get them into your hands this year. The NPC animations list will provide a basis for the upcoming motion capture shoots so our excellent animation team will be able to fill our universe with lively characters.
In other news, our alien language designs are now at a point where we can start recruiting graphic designers to help with establishing alphabets for each race. Pretty soon you guys will be able to not only speak Banu, but write it too!
We’ve also been heavily discussing implementation of player occupations, with the first one to garner focus being MINING. Establishing final design details for mining and the beginnings of implementation will be a major focus next month.
ENGINEERING
The Persistent Universe Engineering Team hit it out of the ballpark in January, setting the benchmark for their monthly milestones for the months to follow!
They have completed a proof-of-concept of the backend code for Multi-Player Hangars and getting hangars running on our servers. They still have their work cut out for them to get everything from this early stage to a playable first iteration…but they are extremely stoked for these next stages of development and making commendable progress working together with the UI Team over at Behaviour. All of this will be intertwined with the team’s first version of its Process Manager that is undergoing heavy early testing and iteration as you read this!
The team has also completed the initial backend work for a first version of our in-game Chat system, and is also working closely with the UI Team at Behaviour towards getting this feature ready for our Social Module coming early this year. If you are a chat “fiend” then this will be your dream come true!!
Meanwhile, our PU Engineering Team has been working closely with our boys over at Moon Collider in the UK on various editing tools to help give life to the NPCs that will populate our Social Module. This makes it an exciting time on both sides of the Atlantic.
And if all this didn’t keep the team busy enough…in conjunction with the brainiacs over at Wyrmbyte…they are also investigating methods to get more players into our maps, starting early work on Player Persistence and performing R&D on developing our Economy Server…truly essential elements that will contribute to making the Persistent Universe and Star Citizen a sincerely mind-blowing experience!
As for the upcoming month of February….love will definitely be in the air around the studio. The PU Engineering Team has every intention of focusing a lot of that loving energy into every bit of code that they write! We’re certain it will show through in their work! Have a great and romance-filled February!
Live Operations Team:
QA
Star Citizen QA hit the ground running for the month of January. Fresh from the break, everyone was determined to improve the state of Arena Commander. Immediately QA began sending daily emails to production reporting on the state of the build and highlighting the most severe issues.
The QA team from Foundry 42 in Manchester did an excellent job with an in depth investigation into missiles and counter measures. Jeffery Pease ensured all lobby issues were accounted for and Andrew Hesse worked closely with developers in Santa Monica reporting and testing ship related issues.
Christopher Hill and Tyler Witkin compiled and reported on feedback from the community which sparked some significant discussion by Chris and the rest of development.
Improvements have been made to how our two teams work together. We are now more aligned with our testing and processes. This has helped to make our QA coverage and hand-off process much more seamless.
Further developments have been made in automated testing. Melissa Estrada has made progress on the creation of custom Sandbox Editor levels that can be utilized to automate functionality. She is also currently training our Manchester team on this process as well as general use and testing of the Sandbox Editor.
This month we welcome our newest member to the QA team. Todd Raffray! Todd is a veteran of the industry. He has worked on such titles as Bioshock Infinite, Star Wars: The Old Republic, Wing Commander: Prophecy and Ultima Online. Todd will be working closely with design testing systems as they come online.
It is hard to believe January is already complete. We are incredibly happy we were able to fit so many bug fixes in release 1.0.1 and hotfix 1.0.1a. Now we look towards February with more bug fixing releases as well as FPS/Social Module testing.
IT/Operations
January has been a productive month for us. From providing the user support for multiple team wide summit meetings across multiple continents to designing new methods for reducing transport times for large data we feel like we’re making a difference. Our UK IT team headed up by Hassan has been providing support for our new office in Germany by acquiring, configuring, and installing all equipment from desks and workstations to servers and networking. Working closely with the rest of our IT teams, Hassan was able to bring that office on line on schedule which was no small task considering all the dependencies from outside vendors and suppliers.
We’re constantly working on ways to make life easier for the developers. This month we’ve rolled out a new VPN solution which has made a big impact in network performance for the remote users while further enhancing our overall network security. We’re also working very closely this month with the DevOps team on the ongoing project to improve our build/deployment cycle. This is an area that can be attacked from many different directions so we’re providing DevOps with volumes of analytics and data about all of our systems with one single goal in mind. “Make things faster!” We’ve already made dramatic improvements but we are just getting started. Without going in to too many details, early data is demonstrating modest reductions in build times and major improvements in deployment (takes way less time to upload a version for the public.)
While the largest improvements on this project will come from the DevOps team, all of us in IT find it highly rewarding to be a part of it.
Dev Ops:
The month of January has been a major planning and infrastructure testing time for the Dev Ops team. We have been evaluating configuration management tools, patching solutions, CDN solutions, metrics reporting, and continuous integration tools. Our team has built a plan to redesign and rebuild the Star Citizen build server and launcher. This should make developing the game easier and we will have faster turnaround times for our developers to review the changes they check into the game. We have also designed a plan to help the server team communicate more efficiently to our infrastructure layer which should reduce their work load and automate many of the manual process currently required with starting up and running our game server cluster.
With all the planning, testing, and evaluating going on, we also have launched the 1.0.1 PTU and 1.0.1 patch to live. We added a bunch of new analytic instrumentations and hooked them up to our own database so that our designers can begin looking at live player statistics to balance the game and make design decisions.
Finally, we have been working on a few new launcher versions that we hope to be releasing over the next couple weeks. The Dev Ops team has a bunch more projects they will be taking on over the next month, and are looking forward to releasing more content to the community in our upcoming patches!
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
Hi all,
Huge start to the new year. Not to waste time we worked over the Christmas period to set up a bunch of summits to kick off our plans for 2015, the first summit starting on our first day back from the holidays. In the UK we held both a Tech and Audio summit, which both went really well. We’ve broken down all our animation / cinematic needs for S42 in meetings this week, and the guys have been getting all the missions to a first pass playable state. Absolutely loads of new tech work going on, new environments and ship work, and we’re starting the big Wwise integration over the next weeks. This is going to be a big year with lots of updates and content to share with you guys throughout the year. Looking forward to sharing it with you all.
Cheers,
Erin
Programming
Happy New Year!!!!!!
Start of the year and straight back into it with a big tech summit over here in the UK. Over the Christmas period there was a last minute rush to get plane ticket and hotels booked for all the top tech engineers from the CIG Studios, Illfonic, BHVR and Wormbyte and getting everyone together for the first week of this month. One of the things that is great about these summits is that it gives us all a chance to meet up again in person and do some socialising with our far flung colleagues, and reinforce just what a great bunch of people we’ve got working on this project!
The summit itself was extremely productive, a full week discussing a multitude of topics from performance (general profiling, our new Zone system for spatializing everything from the universe down to each individual room in a ship, hierarchical LODs, GPU compute…), streaming, damage systems, UI, build systems, networking/backend, audio, perforce, new graphical effects, and much, much more. As you can see it was a busy, busy time! The upshot is we’ve now got a much better global overview and visibility of what the priorities are, both in terms of what needs to be worked on now, what is required in the medium and long term, and what is on the wish list. It also allows everybody to have a better understanding of which teams are working on what and how their work fits into the bigger picture.
Development side we’re doing various refactors of the code to help make it more reusable and maintainable. So for instance, seats in CryEngine have traditionally been tied very tightly with the vehicles, which is a pain if you want to use them in another location, say in a mining base or planetside. As a result we’re in the process ripping the seats from out of the vehicles and making them more generic. The vehicle seats will then become a specialised version of the new seat class.
Other than that it’s business as usual. Work has been progressing nicely on the various game mechanics such as the conversation system, take-off and landing, PAW, looting, and cameras, as well as continued work moving over to Wwise and general 1.0.1 support.
Design
A new year dawns on Star Citizen and it looks this will be a very interesting one for us. We are really pushing ahead with Squadron 42 and hope that we are zeroing in on what will be a very rewarding single player experience in the Star Citizen universe. The missions continue to get more layers of polish as they emerge from the White-Box stage and as new art work gets integrated they look more and more amazing. A lot of the systems that we require for Squadron 42 are starting to firm up well, and things like “Landing” and “Take-Off” are very close to being deliverable in Arena Commander. The conversation system has been getting a lot more design focus before Christmas and is coming along very nicely.
Arena Commander is in bug fix mode, and I know the guys working on this read the forums every day to pick up feedback from you all. There is a real challenge in getting the play balance right for a game that is in early development as I’m sure you are all aware. But having our community giving such precise feedback during its development is invaluable to us making this game what we all want it to be. Also, as the controls systems get more and more detailed, we have been working on a Tutorial for Arena Commander.
The Ship team have been working on balancing and we have a lot of new modules planned for existing ships like the Retaliator and the Redeemer that should allow players to customize their play experience to suit their style.
Overall a good month back after the Christmas break. Thanks again for all the marvellous support!
Art world!
It has been a fast and furious month, we had LA’s new Art Director visiting the studio followed by a visit from myself, Bjorn, Nathan and Ian to the USA to confirm pipeline updates and improvements; needless to say, all teams are moving in the same direction and we’re looking forward to seeing new content that not only beautiful but highly optimal!
Concept wise, we have hired two new artists who are already making great work for the team; the Cutlass variants and the personal Arc Welder PAW. Gavin has been continuing on the Starfarer interior and we’ll have more to show soon
Environment Art
The team has been working towards getting the Shubin Interstellar interior building set to Greybox complete. The main architectural elements are finished so now we are focusing on the smaller details. Our Vertical Slice level for Squadron 42 is looking really promising, we are still continuing to refine the layout as more assets get transformed from Whitebox to Greybox geometry and as design work on gameplay.
Characters
Barrelling along with creating the character pipeline, new base male, new base female, new base female head, 4 test heads to 3Lateral, Shubin miner and character customisation clothing limits, more
Ships and Weapons
Retaliator has continued to be worked on along with alterations to the ARGO Rescue Utility Vehicle, Idris exterior meshing tests and Gladiator damage preparation. As you know (or might not) we are underway with the development of new damage tech for the ships to help reduce memory bloat and art creation timescales, not long now till we have a final test up and running – can’t wait!
We have also started to look at FPS weapons and how to improve the pipeline and overall long term quality of assets, our first step being the PAW which is now concept complete!
VFX
There has been a major clean up and restructure happening with game content, this is never a glamourous task but always worth it in the end; With many of Sq42 levels being at a an early playable state (I mean early) we can now start to scope out the many VFX we’ll need to make this game shine – watch this space.
Animation
Been mostly organisation this month from animation. The re-target of skeleton on to the new final base character has taken up some time. There has been some behind the scenes naming convention changes and tidy up for handing ship animations back over to ATX with a flexible structure for moving forwards.
I have begun to break down our first animation drop from Imaginarium. We have also steadily continued work on the Gladius and Gladiator to get the landing gears etc in good working order for flight ready releases.
And of course we have been providing any support to AC we have been able to offer
Audio:
This month, the main event we had was a week long Audio Tech Summit that ran from Jan 19th to the 23rd. This was a whole week’s worth of in-depth discussion, gathering together our audio personnel from across multiple studio locations to meet here in Manchester (or video-conference where flying in wasn’t possible!).
This enabled us to hammer out ways to define or improve all aspects of our audio tech, from the ‘glamour’ of run-time audio systems (VoIP/porting, propagation, real-time effects, DSP, etc.) to implementation tools, to more mundane (but necessary) aspects like how best to build our Wwise project and roll it out internally, and other foundation work such as best practices for mapping out ships, planetside locations and so on. Readers of the audio thread on the ‘Ask A Developer’ forum will be pleased to know we included many concerns and questions raised there, in this summit, including how we might open things up to the modding community. We also looked at some third party tech solutions too for the likes of procedural audio and 3d audio solutions, of which there are many.
The overriding theme, if we can call it that, is the need for us to take system-driven approaches to the audio we deliver. With a game of indeterminate scale and potentially limitless quality and detail, we have to look to ensure whatever we do can expand and be built upon in a robust way. These systems need to be designed in a way that never compromises the quality we deliver, and need to allow us to override and apply an artistically-driven approach to sound wherever the system-lead doesn’t quite cut it.
We’ve welcomed another new sound designer to our ranks here in Manchester, which takes our audio ‘hub’ to five, not including a new audio programmer who’s based in Germany and a technical sound designer based in Austin. We’re still looking to expand, this year promises to be a very busy one.
As we’re concentrating on the move over to Wwise now, some of our next few updates (that are still in FMOD) may not be up to our usual quality bar; hopefully you’ll forgive us for that, we’ll try to make sure whatever we put out is as good as it can be but we hope you’ll all understand if things aren’t as good as they should be!
Otherwise in January we’ve been working on pre-prod and production for dialogue sessions, sound effects gathering, but mostly we’ve kept on keeping on with Fmod > Wwise migration. We’ll all be happier when we’re done with that so we can concentrate on making the ‘Best Damn Sounding Space Sim Ever’!
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
Design
Like we mentioned in the last report, elevators were a big push this month. These elevators are way more complex than they seem as they’ll allow you to go from your hangar to planetside and more importantly to other players’ hangars. In the same vein, design for the first iteration of the chat system and for the multiplayer experience in hangars has been defined.
More planetside locations have been whiteboxed, and they are now in the hands of our talented team of artists. Nyx is the next “planet”, or rather asteroid, we’ll tackle. We noticed that the pace is accelerating; the team’s hard work on the planning for reusable assets and locations is starting to pay off. While we’re on the subject, iterations on tools have also been made to help us work better and faster.
The mobiGlas AR design is changing quite a bit as we’re starting to implement it for realz. It’s really exciting to see these functions appearing in the game world. Progress on other apps have been slowed down due to our focus on other features.
On the Flair side, we’ve been working on the February Takuetsu Model and preparing a cool lineup for the future flairs that’ll allow subscribers to show off their dedication to the project.
Oh yeah, and don’t forget bug smashing, yeah we do that too! There are a lot of bugs in the ‘verse apparently.
UI
Back fresh from the holidays, the UI team has hit the ground running: chat UI, lobby work, elevator UI, loads of mobiGlas mock-ups, more control customization features, logos, banners…. the list goes on and on.
Engineering
We’ve continued working on CryEngine Tools that will help us create AI used for NPCs populating planetside locations, working specifically on allowing Game Designers to customize their activities based on a time schedule. We’ve also began to start investigating how to hook-up Conversations for those NPCs will have between themselves, as to provide a more immersive experience for the player. We’ve also been very hard at work on modifying the Hangars to allow you to invite friends over to your hangar. We are also working on new UI elements to support this invitation/joining process.
We’ve completed a prototype of the in-game star map, which will eventually be viewable inside your ship and also in your mobiGlas. We’ve fixed a great amount of bugs related to the Lobby and Contacts feature. We’ve also started integrating the possibility of doing FPS matches through a Lobby. Last but not least, we added some very cool Control Customization options, which will let you customize your control in a much more precise manner than before.
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
Concept
This month we focused on building one of the major tourism locations on Terra Prime: the Prime Tower.
Standing at a height of 2km, the Tower is definitely one of the most dominant landmarks on Terra III. It features a shopping mall with high-end shops and a park area at the top to rest and enjoy the view.
We’ve also started conceptualizing the Delamar landing zone, located in the NYX asteroid belt. It’s a former mining colony located under the asteroid surface, where rebels took refuge to hide from the UEE awhile ago. Nowadays, pirates have also settled in for the same reasons.
Finally, we’ve finished the Sim Pod concept arts and started the production so you can see it in your hangar soon!
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
Greeting Citizens! Has another month gone by already since the last report? I guess it has, but it sure doesn’t seem like it. The FPS team has been focused on getting all of the remaining features implemented and polished for the first release. We’re very close now and we’re super excited for all of you to play it and let us know what you think!
Engineering
The programmers have been putting the final touches on the zero-g push & pull system. This allows you to navigate an environment in zero-g without the need for a jetpack or other form of propulsion. You can grab and pull yourself along surfaces, then crumple your legs up and push off, headed towards another point in the level. This is all done procedurally so it can be done anywhere in any level, without the need for designers placing specific points to attach to. It’s all pretty slick but requires quite a bit of polish and bug-fixing to address all of the different edge cases involved.
Two new weapons were also hooked up, one large weapon that is capable of dealing damage to multiple foes and another that is good for taking out enemies at a distance. I will leave you to speculate over what they are. Work also continues on the HUD and making the 3D radar system work for players who are currently in zero-g, which should be finished soon.
Lastly, lots of bug-fixing has been happening. Mostly for the FPS module but we have also squashed a few of the bugs for the 1.0.1 release.
Animation
The animation team has been busy creating block-out animations for all of the new features, and they just received the brand-spanking-new mocap data from December’s shoot. They are now in the process of getting these animations hooked up in game, which should give us some much more realistic looking movements that are more fluid and natural than what was seen during the PAX Australia demo.
Design
The design team has been putting the final touches on our two whitebox Team Elimination maps. Playtesting and balancing now begins and final art added. Paper designs for future maps and game modes are in the works now. A balance pass is in the works for all of the weapons and gadgets along with the new grapple beam attachment which will be used in the zero-g specific Team Elimination map.
Art
Vents, that is the word of the month for the artists! Art assets are being modified to support the vent and crawlspace system… and there’s a lot of it. This basically entails taking a bunch of wall pieces and putting in vent spaces so they all fit together like nice puzzle pieces.
In addition to all the vent work, the artists have also been busy working on the zero-g specific level concept, which is now going in to full production.
The concept and block-out for the long range weapon I spoke of earlier has also been approved, and work has now begun on the high poly model and visual FX.
VFX
The biggest piece of news from the VFX department has been a new family member for one of our artists. Congratulations Matt! While his new little one has been keeping him busy, he has also managed to create visual FX for the new weaponry and the grappling beam. This work will be ongoing in to next month.
That about wraps it up for all of us here at IllFonic. Enjoy playing Arena Commander 1.0.1 and we will see you very soon!
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
Greetings, Citizens, From Terra’s snowiest landing zone.
It’s a new year, and it’s come with its changes. We’ve shown you a new homepage and tightened our integration with Arena Commander V1, we’ve wrapped up a lot of loose ends we’d had through 2014 and now we’re starting fresh with new goals and renewed excitement. Here’s a view of what we’ve been doing this month :
Community Hub
You’ve seen the new Homepage. It’s not final, we’ll be continuously tuning it based on you fans’ awesome feedback, but its goal will remain to appeal to newcomers and convey what Star Citizen is bound to become. That’s why we’re working on a new section, called the Community Hub (can you guess where it will be in the menu?). It will be able to cater to all SC fans, old and new alike. Function priming clearly over form, it will come packed with new features, that we’ll be detailing soon. Without spoiling it, we can say that if you already feel involved with Star Citizen, we’ll be taking it to a whole new level.
Starmap
Most of you caught a glimpse of the Starmap prototype we’ve been building during the holiday livestream. For now the prototype is Unity-based, and we’re working hard to make it as tightly linked to real-time game data as possible. This is a huge undertaking, conjointly with all teams involved in the Persistent Universe, and it will make sure that the Starmap is relevant and reliable. Once we’re done with linking the game and the map, and we’re confident that the map can answer questions like “Where am I?”, “Where can I re-sell my Stimulants shipment?” or “What’s the safest way to go from Goss II to Stanton I?”, we’ll port it into webGL and integrate it directly into the site, like the Holoviewer for ships.
What you can’t see
There’s also a lot of stuff that we do here that never shows up on the website, and it turns out that January has been pretty heavy with these operations. Since the website is also the Pledge gateway, we provide reports and financials to Cloud Imperium Games. We won’t go into any details, but every once in a while, like this month, we spend a bit of time reworking our business back-end system, our stats reporting engine, and the way we share player data with the game client.
Some stuff is not that obvious either but still has an impact : we’re setting up a global effort to optimize the website’s performance, and especially the way we handle smaller screen resolutions, mobile devices, and slower connections. Any feedback is welcome!
What’s to come
We’re always preparing for what’s ahead, and our Design team is already working on the next website updates. This includes new functionalities for Orgs, integrating Arena Commander stats into the Citizen Dossier, evolving the Contact List… and quite a few secrets we can’t really share right now. All to pave the way for the rest of the year and give the BDSSM a platform worthy of its scale. So stay tuned for more, and see you all in the ‘verse!
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
With major releases happening in multiple Star Citizen modules this year, all needing significant AI support, the Moon Collider team dived weapons hot into January in a way that would make John Woo proud. We’re really excited about all of the cool AI tech that will be featured in these upcoming releases.
One of the big challenges for us in the next few months is that with so much progress being made on all of the different modules, we need to make sure we get the necessary AI features in place in time for each module to make full use of them. In between Arena Commander, Squadron 42, and the persistent universe, it’s like we’re making the AI for three different games simultaneously! But this is Star Citizen, right? Ambitious goals are why we’re all here, so we’re working hard and we hope you’ll be thrilled with the results.
Design
We were able to send two people to join in on the tech summit in Manchester at the beginning of the month. I think all teams would agree that this was a really valuable event. Certainly on the AI side it was great to discuss some of the big tech challenges that we need to solve this year, and start making some progress towards working them out.
One of the main things we did design work on this month was working out how to support local coordinate systems inside Kythera. When an AI is standing inside a ship, we want to be able to define “up” in reference to the ship, which makes all kinds of calculations a lot easier. But what happens when that ship docks with a station or another ship where “up” is different? Or if an AI is standing on one ship aiming at something on another ship? We want to hide the complexity of the calculations in these situations as much as possible, so we did a lot of work towards figuring out how to make that happen.
On the FPS combat side, now that we have the AI able to perform basic combat, we’ve been working with the Squadron 42 designers to continue refining their behaviors and get them behaving more realistically. This means giving them a greater sense of self preservation, so that they stay in cover more and take fewer unnecessary risks, but without making combat frustrating for the player. We’re also looking at how the AI should work together as a group, such as with sharing information about where the player is, performing flanking actions, providing covering fire, and so on. We expect to do plenty more design work along these lines in the next couple of months as the Squadron 42 maps get refined.
Engineering
Foundry 42 has been doing great work on the Arena Commander tutorial and this month we were able to start providing some support for some specific features needed in particular places of the tutorial. Usually, we will try to identify when support for something specific can be implemented as a more generally useful feature, or if
it’s an opportunity to add a feature that’s already on our roadmap but we didn’t expect to need just yet.
So, for example, we can create a spline for AI to follow, but up to now, they weren’t using boost to help stay on track if the spline was too aggressively curved. Having them apply boost intelligently as needed is quite useful, and since a need for this arose in the tutorial (you’ll have to wait to find out what it is!), we’ve now added that support in. This now allows designers to author tight splines in places that the AI would have had difficulty flying through before.
There was a lot of persistent universe work done this month. I mentioned the local coordinate design work above, and a lot of this design was also implemented, along with increasing the precision of world positions from 32 to 64 bit, which will allow us to keep AI positions accurate in much larger spaces, something that is essential for the persistent universe. We solved all of this at once by refactoring the internal position/vector structures that Kythera uses. It was a big task and it has happened alongside a lot of similar work that other teams have been doing throughout the rest of the codebase. It’s always scary when you go and change one of the fundamental data structures in your code, but it actually went quite smoothly, largely thanks to taking the time to work out the design thoroughly up front. A big shout out to our resident uber-coder Mike Bell for making this happen!
Another big area of work for the persistent universe is the Usables system. This is the system that allows designers to mark up objects in the world to allow AI to interact with them, and to define what those objects do. It is a powerful system that forms one of the cornerstones for making AI in the persistent universe able to do interesting things. We’ve been relying on a simple prototype system up to now, but this month we were finally able to make real progress on getting the full Usable system in place for the designers to use. There’s still more features that we need to add, but it was great to make a solid start on it.
On the FPS combat side of things, we made various small improvements as we continue iterating on the behaviors of the AI and polishing the combat experience. This is being mostly driven by the needs of the Squadron 42 vertical slice at the moment. So last month we added the ability for AI to be tasked with defending a particular area. This month we added a couple more tasks for the AI: holding position, which makes them aggressively defend a specific spot; and combat move, which tells them to move to a particular place while intelligently taking cover and engaging with enemies along the way.
We also improved their standard combat behaviors to make them investigate the last known position of the player if they lose all trace of the player for a while. We still need to improve this behavior to make them coordinate as a group, and just send one or two poor unlucky guys out to find the player rather than several of them going, but that will come as we start to add various types of group coordination.
Up to now the AI characters have been far too accurate with their weapons, making it necessary to fight them in god mode for all but the most masochistic developers. So we added in some accuracy modification support, allowing designers now to tweak the accuracy of the AI and make fighting them a little fairer. It’s actually quite difficult to make AI inaccurate in a believable way, and our change isn’t quite there, so we will need to work on this some more in the future.
Finally, we did some general optimizations to the Kythera AI systems that will be useful across all of the Star Citizen modules. We now have enough core features in place and some good representative levels for each of the modules that we can get a good idea of performance troublespots under “real world” conditions, so we’ve been making significant reductions to the time per frame that Kythera is using when there are large numbers of AI in a level.
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
Hi Everyone! I’m incredibly excited to be able to add a Community section to this January report. I promise to keep these short and sweet, since by this point I’m just happy your eyeballs aren’t completely dried out. I hope to cover everything from past events to featured videos to inside jokes from our team, and grow this section with YOUR HELP. Like something? Want to see more? Let us know!
January’s ATV highlight comes from our community week in Austin. Ben, James and Thomas visited the Austin office and captured an extensive amount of PU goodness. On top of numerous interviews, Ben hosted an episode of Around the Verse with returning guest host Pete Mackay. Check out this special Texas-sized episode HERE.
After a quick drive down to San Antonio, our #StarCitizenTownHall during PAX South was a great success. Fans were treated to three panels, an ideas forum, and a special presentation by Chris Roberts. If you weren’t able to attend, or if you just want to relive all the Persistent Universe goodness, all five of the Town Hall panels are available HERE.
Beyond the panels, spending time with fellow citizens during the meet and greet was incredibly exciting. Meeting and talking with everyone in attendance only reinforced the fact that Star Citizen has the best community out there. Austin’s Ryan Archer snapped pics capturing the fun, and included his own blurb about the event. You can check that out HERE.
In the most comprehensive design post to-date, the Chairman presented mobiGlas. Immerse yourself in augmented reality using mobiGlas, and get your first taste of the Star Citizen universe through Chris Roberts’ vision. Words like “bonkers” and “stunning” can be found amongst the comments, but you need to check this one out for yourself HERE.
The forums added another piece of valuable info, thanks to moderator AngryPeas. He has created an info depot for new users that are looking to dig into Star Citizen. It was a great help to me, and I hope to pass along the knowledge to some of you. You can find it in the New Recruits section of the forums, or simply by clicking HERE.
Reverse the Verse is my personal highlight every week. Our team loves hanging out with the community in the immediacy created by Twitch. The #blamejames trend returned, and we’re actively working on getting the Austin office more integrated in RTV live streams. If you haven’t checked it out, we go live every Thursday…sometimes Friday. By following CIGcommunity on Twitch, you can be notified as soon as we go live! Come say hi! You can also check out past replays of Reverse the Verse HERE.
For our subscribers, we promise to bring you even more exclusive content in 2015. One aspect of that promise will be weekly updates to the Vault. Not a subscriber? Gain access by signing up HERE.
So much for keeping this “short.” Can’t wait to have more for you guys in February!
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
Greetings Citizens,
Arena Commander 1.0.2 is now available via the Star Citizen launcher! This is a smaller patch which focuses on bug fixes, balance updates and smaller additions to the game. Fixes include everything from lobby kicking issues to the missing glass in the Herald space globe’s cockpit!
One of the most visible additions will be the expansion of the skin system to the Aurora line. You can now select your Aurora’s skin in the holoviewer (two alternates are available now, with more to come!)
Arena Commander 1.0.2 also sets the stage for the shield customization system. Additional shield generators will be available in the Voyager Direct store tomorrow, along with a post detailing our design plans for shields going forward.
A complete list of additions, fixes and known issues is available in the patch notes, online here.
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
Squadron 214 is a multi-spacecraft equipped unit (technically, a “multi-level force applicator”) of the United Empire of Earth. The squadron was formally activated in 2675 as part of the military expansion that followed in the wake of Project Far Star. 214 has seen great success in their 270-year service history. The squadron is especially noted for the seven Medal of Imperial Valor winners on its roster, and for their success in short-range bombing missions, being proudly credited with the destruction of a dreadnaught, four battleships, nine “flat tops” and countless lesser fighters in their lengthy history. The 214th has also occasionally been a propaganda darling. “Twelve Went In,” a recruiting holovid, recounted the bombers’ 2720 all-out assault on a Harvester Dropship.
The origin of the squadron’s nom de guerre is shrouded in some confusion. Modern Black Crow pilots and their supporters claim that the name refers to the squadron’s cleverness and penchant for vengeance (Earth crows, now found on over a dozen worlds, are capable of remembering and attacking offending Human faces for years). Historians say that the truth is somewhat less valorous. The squadron was originally known as “Branton’s Braggarts,” a humorous reference to the unit’s overly-vocal pride over achieving the first perfect score in a HARD+ rated simulated bombing run under their first commanding officer, Captain Charlotte Branton. Fed up with the squadron’s braggadocio, ground crews began painting black birds on their spacecraft to show their distaste for 214’s ‘constant cawing.’ By the time Squadron 214 went into action, they were the Black Crows.
Today, 214 is an exclusively carrier-based squadron assigned two flights of Hornets, one flight of Gladius interceptors and an elite flight of Gladiator light bombers, though it is worth noting that one of the Hornet flights is currently inactive as its flight crews undergo transition training for the upcoming F8 Lightning space superiority fighter. The Black Crow’s bomber flights have flown every single-engine bomber in the UEEN arsenal, from the original Typhoon dive bombers to today’s craft, where 214’s illustrious Bravo Flight are using the Anvil Gladiator to further solidify their hard-earned reputation as one of the best bomber units actively operating.
Bravo Flight
The recent exploits of Bravo Flight in the Virgil Raid have become so well known that references to the Black Crows now almost exclusively refer to this distinguished bomber unit. The star of Squadron 214’s service record from the very beginning of training, Bravo Flight has been the exclusive designation of the unit’s elite bomber ships since the squadron’s inception. Bravo’s ground crews and flight engineers claim a spotless record, and only confirmed ace pilots and gunners are assigned to the unit.
Bravo garnered attention during the Vanduul push after 2681. Battling the encroaching horde from Orion to Tiber, their Gladiators pulled double duty as S&R craft up to the last minutes of the Tiber pullout. Since that time, the ‘bloodthirsty birds’ have found themselves forward-deployed to counter suspected Vanduul clan movements time and time again.
The Raid
Dateline: Vega System, just off the heavily guarded Virgil jump point. On the morning of August 9, 2932, a detached UEE Battle Group went to action stations. After a tense twelve hours with guns ready, the force issued an all-clear stand down. Aboard the UEEN Typhon, temporary home of the 214’s Bravo Flight, word quickly spread: Virgil’s aging Early Warning satellite network had relayed a distress signal from somewhere in the system. Admiral Bonds requested permission to jump his force to Virgil to investigate, but was ordered by High Command to abandon any investigation. Remote sensing had identified a 55% probable Vanduul clan in the system’s environs, and Command was not to risk personnel or materials investigating a system that had not been inhabited in a century.
The mood aboard ship was stricken. Here was a military rescue beacon deep in the heart of the site of one of the Empire’s bloodiest defeats. At best, they reasoned, command was letting a fellow pilot die, and at worst they were ignoring an opportunity to settle a very specific age-old score with the Vanduul. “We won’t forget,” flight leader Tam Thackston wrote in a delay-send message to his commanding officer as his crews universally agreed to break ranks and risk court martial to come to the aid of those in need.
Running with low-emission gear, the six Gladiators of Bravo Flight launched with full comm silence (and the suspected collusion of the Typhon’s flight deck officer). Three retained their standard torpedo loadout, while three others were configured with autodocs and other search and rescue equipment. Passing by UEE radar stations and tracking buoys, they were prepared to meet with resistance, but were only met with encouragement and wishes of luck from their fellow starmen. The unit made a low-flash jump to Virgil, and once across, Bravo triangulated the signal and determined it to be coming from the surface of the innermost planet.
Thackston opted to use a larger amount of fuel and proceed in a roundabout manner rather than heading directly to the planet and risking giving away the location of the jump point to the Vanduul. Unfortunately, his caution proved costly: the extended flight plan ran Bravo directly into an enemy patrol. A battle broke out, with the Gladiators attempting to eliminate a quartet of Scythe and a command-and-communications ship before they could call for reinforcements. The fight was over quickly, but with heavy losses: Bravo 3 sustained a direct blade collision during the fracas, killing gunner Paul Ransom and leaving his ship dead in space. The surviving pilot conducted a difficult combat EVA and boarded the S&R equipped Bravo 5.
Once past the Vanduul, the surviving Gladiators approached the planet’s equatorial zone, the apparent location of the now-silent beacon. The flight leader’s ship touched down near the source while the remaining ships provided a makeshift combat air patrol. There, the charred fuselage of a long-lost Wildcat deep space fighter was located in a clearing where its impact had knocked down several of Virgil’s giant trees. Investigating the wreck, Thackston discovered a pair of Human skeletons, one in a tattered flight suit, both wearing Black Crow patches. This ship must have been lost decades earlier in one of Squadron 214’s prior battles with the Vanduul. With some searching, the source of the signal was discovered: the Wildcat’s black box recorder, apparently re-activated in a recent lightning strike.
Thackston hurriedly buried the remains, first removing the dog tags so they could be returned to Kilian, and took off to rejoin his flight, the Wildcat’s flight recorder securely stowed aboard his Gladiator. Believing they had permanently shamed their squadron’s honorable history, they returned home fully expecting to be drummed out of the service for their disloyalty, but upon arrival they discovered that public opinion had come down harshly against Navy command once news of the beacon had spread. With the sack of Virgil still a sore point in Human memory, the pilots of Bravo Flight were feted as incredible heroes for having helped put a small part of that dark day in history to rest, along with revealing the incredible fate of their fallen comrades: the Wildcat and her crew had bravely perished when they opted to stay behind and cover the desperate evacuation in Virgil’s final hours. Together, they are just two more reasons that the Black Crows of Squadron 214 deserves to crow.
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
Squadron 214 is a multi-spacecraft equipped unit (technically, a “multi-level force applicator”) of the United Empire of Earth. The squadron was formally activated in 2675 as part of the military expansion that followed in the wake of Project Far Star. 214 has seen great success in their 270-year service history. The squadron is especially noted for the seven Medal of Imperial Valor winners on its roster, and for their success in short-range bombing missions, being proudly credited with the destruction of a dreadnaught, four battleships, nine “flat tops” and countless lesser fighters in their lengthy history. The 214th has also occasionally been a propaganda darling. “Twelve Went In,” a recruiting holovid, recounted the bombers’ 2720 all-out assault on a Harvester Dropship.
The origin of the squadron’s nom de guerre is shrouded in some confusion. Modern Black Crow pilots and their supporters claim that the name refers to the squadron’s cleverness and penchant for vengeance (Earth crows, now found on over a dozen worlds, are capable of remembering and attacking offending Human faces for years). Historians say that the truth is somewhat less valorous. The squadron was originally known as “Branton’s Braggarts,” a humorous reference to the unit’s overly-vocal pride over achieving the first perfect score in a HARD+ rated simulated bombing run under their first commanding officer, Captain Charlotte Branton. Fed up with the squadron’s braggadocio, ground crews began painting black birds on their spacecraft to show their distaste for 214’s ‘constant cawing.’ By the time Squadron 214 went into action, they were the Black Crows.
Today, 214 is an exclusively carrier-based squadron assigned two flights of Hornets, one flight of Gladius interceptors and an elite flight of Gladiator light bombers, though it is worth noting that one of the Hornet flights is currently inactive as its flight crews undergo transition training for the upcoming F8 Lightning space superiority fighter. The Black Crow’s bomber flights have flown every single-engine bomber in the UEEN arsenal, from the original Typhoon dive bombers to today’s craft, where 214’s illustrious Bravo Flight are using the Anvil Gladiator to further solidify their hard-earned reputation as one of the best bomber units actively operating.
Bravo Flight
The recent exploits of Bravo Flight in the Virgil Raid have become so well known that references to the Black Crows now almost exclusively refer to this distinguished bomber unit. The star of Squadron 214’s service record from the very beginning of training, Bravo Flight has been the exclusive designation of the unit’s elite bomber ships since the squadron’s inception. Bravo’s ground crews and flight engineers claim a spotless record, and only confirmed ace pilots and gunners are assigned to the unit.
Bravo garnered attention during the Vanduul push after 2681. Battling the encroaching horde from Orion to Tiber, their Gladiators pulled double duty as S&R craft up to the last minutes of the Tiber pullout. Since that time, the ‘bloodthirsty birds’ have found themselves forward-deployed to counter suspected Vanduul clan movements time and time again.
The Raid
Dateline: Vega System, just off the heavily guarded Virgil jump point. On the morning of August 9, 2932, a detached UEE Battle Group went to action stations. After a tense twelve hours with guns ready, the force issued an all-clear stand down. Aboard the UEEN Typhon, temporary home of the 214’s Bravo Flight, word quickly spread: Virgil’s aging Early Warning satellite network had relayed a distress signal from somewhere in the system. Admiral Bonds requested permission to jump his force to Virgil to investigate, but was ordered by High Command to abandon any investigation. Remote sensing had identified a 55% probable Vanduul clan in the system’s environs, and Command was not to risk personnel or materials investigating a system that had not been inhabited in a century.
The mood aboard ship was stricken. Here was a military rescue beacon deep in the heart of the site of one of the Empire’s bloodiest defeats. At best, they reasoned, command was letting a fellow pilot die, and at worst they were ignoring an opportunity to settle a very specific age-old score with the Vanduul. “We won’t forget,” flight leader Tam Thackston wrote in a delay-send message to his commanding officer as his crews universally agreed to break ranks and risk court martial to come to the aid of those in need.
Running with low-emission gear, the six Gladiators of Bravo Flight launched with full comm silence (and the suspected collusion of the Typhon’s flight deck officer). Three retained their standard torpedo loadout, while three others were configured with autodocs and other search and rescue equipment. Passing by UEE radar stations and tracking buoys, they were prepared to meet with resistance, but were only met with encouragement and wishes of luck from their fellow starmen. The unit made a low-flash jump to Virgil, and once across, Bravo triangulated the signal and determined it to be coming from the surface of the innermost planet.
Thackston opted to use a larger amount of fuel and proceed in a roundabout manner rather than heading directly to the planet and risking giving away the location of the jump point to the Vanduul. Unfortunately, his caution proved costly: the extended flight plan ran Bravo directly into an enemy patrol. A battle broke out, with the Gladiators attempting to eliminate a quartet of Scythe and a command-and-communications ship before they could call for reinforcements. The fight was over quickly, but with heavy losses: Bravo 3 sustained a direct blade collision during the fracas, killing gunner Paul Ransom and leaving his ship dead in space. The surviving pilot conducted a difficult combat EVA and boarded the S&R equipped Bravo 5.
Once past the Vanduul, the surviving Gladiators approached the planet’s equatorial zone, the apparent location of the now-silent beacon. The flight leader’s ship touched down near the source while the remaining ships provided a makeshift combat air patrol. There, the charred fuselage of a long-lost Wildcat deep space fighter was located in a clearing where its impact had knocked down several of Virgil’s giant trees. Investigating the wreck, Thackston discovered a pair of Human skeletons, one in a tattered flight suit, both wearing Black Crow patches. This ship must have been lost decades earlier in one of Squadron 214’s prior battles with the Vanduul. With some searching, the source of the signal was discovered: the Wildcat’s black box recorder, apparently re-activated in a recent lightning strike.
Thackston hurriedly buried the remains, first removing the dog tags so they could be returned to Kilian, and took off to rejoin his flight, the Wildcat’s flight recorder securely stowed aboard his Gladiator. Believing they had permanently shamed their squadron’s honorable history, they returned home fully expecting to be drummed out of the service for their disloyalty, but upon arrival they discovered that public opinion had come down harshly against Navy command once news of the beacon had spread. With the sack of Virgil still a sore point in Human memory, the pilots of Bravo Flight were feted as incredible heroes for having helped put a small part of that dark day in history to rest, along with revealing the incredible fate of their fallen comrades: the Wildcat and her crew had bravely perished when they opted to stay behind and cover the desperate evacuation in Virgil’s final hours. Together, they are just two more reasons that the Black Crows of Squadron 214 deserves to crow.
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.
Questions covered in Episode 52: 2:28 – Custom Crew Uniforms. 3:24 – Banu & Xi’An embassies. 4:30 – Missions for more than one ship. 5:04 – How inventories work. 7:22 – Purchasable voice packs. 8:27 – Org contracts. 9:42 – Planetary quarantines. 10:50 – FPS dungeons/instances 13:19 – Tevarin update 14:21 – Organization leader tools
It has recently occured that a sizeable chunk of users are unable to use the launcher and are met with this error. This error is due to your IP being considered as harmful by Cloudflare and is most of the time due to your ISP using Dynamic IPs and someone using it at some point got caught doing bad stuff with it resulting in a blacklisted IP. The other common reason is the use of a proxy.
Rest assured that we are working on a solution for the users affected by this problem. We will release a new installer probably tomorrow containing an updated DSLauncher. It will also contain all updates we've released up to now.
For the users that aren't affected, the update will be deployed through DSLauncher, so you have nothing to do.
It has recently occured that a sizeable chunk of users are unable to use the launcher and are met with this error. This error is due to your IP being considered as harmful by Cloudflare and is most of the time due to your ISP using Dynamic IPs and someone using it at some point got caught doing bad stuff with it resulting in a blacklisted IP. The other common reason is the use of a proxy.
Rest assured that we are working on a solution for the users affected by this problem. We will release a new installer tonight containing an updated DSLauncher. It will also contain all updates we've released up to now.
For the users that aren't affected, the update will be deployed through DSLauncher, so you have nothing to do.[/feedquote]
Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
Greetings Citizens,
As we announced two weeks ago, RSI is moving into Europe with the formation of Roberts Space Industries International Ltd. To accomplish this change, we have made a major revision to the pledge store’s functionality, which includes the addition of an international store run by RSI International. As a result of this store change, all backers will be required to accept a new ToS, Privacy Policy, and EULA when connecting to Star Citizen game or pledging through the store (these will vary depending on which store you access.)
Also, the RSI International pledge store will begin charging VAT on orders placed by backers in the European Union. In order to reduce the impact of the VAT changes for users paying in Euros, we are keeping the dollar-to-euro exchange rate steady rather than matching it to the recent loss of value to the USD. While it may become necessary to adjust the exchange rate in the future, the immediate impact should will be positive for many European backers and offset a large part of the VAT tax! While this does not impact backers now being able to pay in GBP, the launch of the international store does mean they will no longer be charged a foreign transaction and currency conversion fees.
