{"data":{"id":16294,"title":"Monthly Studio Report: November 2017","rsi_url":"https:\/\/robertsspaceindustries.com\/comm-link\/transmission\/16294-Monthly-Studio-Report-November-2017","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-links\/16294","api_public_url":"https:\/\/api.star-citizen.wiki\/comm-links\/16294","channel":"Undefined","category":"Undefined","series":"Monthly Reports","images":[{"id":6347,"name":"RutoShop_01.png","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/fhbv5ctm8f7i9r\/source\/RutoShop_01.png","alt":"","size":2660234,"mime_type":"image\/png","last_modified":"2017-10-05T21:57:53+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6347","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6347\/similar"},{"id":6552,"name":"M_heavy_marine_keyshot_front1-002.jpg","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/2dsuwnhqfqeuer\/source\/M_heavy_marine_keyshot_front1-002.jpg","alt":"","size":1556507,"mime_type":"image\/jpeg","last_modified":"2017-11-30T15:16:23+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6552","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6552\/similar"},{"id":6553,"name":"Hurricane_001.jpg","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/qyuxcev5inlbhr\/source\/Hurricane_001.jpg","alt":"","size":141928,"mime_type":"image\/jpeg","last_modified":"2017-11-29T19:35:06+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6553","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6553\/similar"},{"id":6554,"name":"Hurricane_002.jpg","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/713w1kvvihs8or\/source\/Hurricane_002.jpg","alt":"","size":109370,"mime_type":"image\/jpeg","last_modified":"2017-11-29T19:36:01+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6554","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6554\/similar"},{"id":6555,"name":"Hurricane_003.jpg","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/5ndd3eqlx9c3br\/source\/Hurricane_003.jpg","alt":"","size":107163,"mime_type":"image\/jpeg","last_modified":"2017-11-29T19:35:09+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6555","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6555\/similar"},{"id":6556,"name":"Hurricane_004.jpg","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/b85uw73w38v8ir\/source\/Hurricane_004.jpg","alt":"","size":85558,"mime_type":"image\/jpeg","last_modified":"2017-11-29T19:35:10+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6556","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6556\/similar"},{"id":6557,"name":"Shopkeep1.jpg","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/ftvu6yxtknx2nr\/source\/Shopkeep1.jpg","alt":"","size":567845,"mime_type":"image\/jpeg","last_modified":"2017-11-30T15:43:02+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6557","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6557\/similar"},{"id":6558,"name":"Shopkeep4.jpg","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/e8rjxhk77vvggr\/source\/Shopkeep4.jpg","alt":"","size":416048,"mime_type":"image\/jpeg","last_modified":"2017-11-30T15:43:04+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6558","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6558\/similar"},{"id":6559,"name":"Gladiator_pilot.jpg","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/ywmo80t8vv2q1r\/source\/Gladiator_pilot.jpg","alt":"","size":508070,"mime_type":"image\/jpeg","last_modified":"2017-11-30T15:42:58+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6559","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6559\/similar"},{"id":6560,"name":"IMG_29112017_174514_0.png","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/tj23c2wkv15rxr\/source\/IMG_29112017_174514_0.png","alt":"","size":1918911,"mime_type":"image\/png","last_modified":"2017-11-30T15:43:11+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6560","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6560\/similar"},{"id":6561,"name":"IndustrialZone_Composition_001.jpg","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/h2bh6sohfm9oyr\/source\/IndustrialZone_Composition_001.jpg","alt":"","size":4712854,"mime_type":"image\/jpeg","last_modified":"2017-11-29T21:44:07+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6561","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6561\/similar"},{"id":6562,"name":"Hammerhead_01.jpg","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/s82nhf2v8mslir\/source\/Hammerhead_01.jpg","alt":"","size":1089920,"mime_type":"image\/jpeg","last_modified":"2017-11-29T21:11:27+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6562","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6562\/similar"},{"id":6563,"name":"Hammerhead_03.jpg","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/ges9mbi051vjxr\/source\/Hammerhead_03.jpg","alt":"","size":1717143,"mime_type":"image\/jpeg","last_modified":"2017-11-29T21:11:31+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6563","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6563\/similar"},{"id":6564,"name":"600i_Bridge.jpg","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/uekll5qzl3ti4r\/source\/600i_Bridge.jpg","alt":"","size":118639,"mime_type":"image\/jpeg","last_modified":"2017-11-29T21:25:28+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6564","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6564\/similar"},{"id":6566,"name":"600i_Landing_Gear.jpg","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/bkpy73y8mjrusr\/source\/600i_Landing_Gear.jpg","alt":"","size":50969,"mime_type":"image\/jpeg","last_modified":"2017-11-29T21:25:28+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6566","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6566\/similar"},{"id":6567,"name":"Void_02.jpg","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/7yj2jtm2xdb88r\/source\/Void_02.jpg","alt":"","size":666244,"mime_type":"image\/jpeg","last_modified":"2017-11-29T21:28:58+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6567","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6567\/similar"},{"id":6568,"name":"Carrack_engine_room_greybox.jpg","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/qoubpoali1t8ir\/source\/Carrack_engine_room_greybox.jpg","alt":"","size":1260645,"mime_type":"image\/jpeg","last_modified":"2017-11-29T21:32:08+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6568","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6568\/similar"},{"id":6569,"name":"Hurston_wip-1.png","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/p7fnm1dr3jgaer\/source\/Hurston_wip-1.png","alt":"","size":4846498,"mime_type":"image\/png","last_modified":"2017-11-29T21:35:19+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6569","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6569\/similar"},{"id":6571,"name":"Monthly_report_November17_2.jpg","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/5rbjzhkfmt0htr\/source\/Monthly_report_November17_2.jpg","alt":"","size":496077,"mime_type":"image\/jpeg","last_modified":"2017-11-29T21:40:31+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6571","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6571\/similar"},{"id":6573,"name":"Monthly_report_November17.jpg","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/bugdnh88t4meyr\/source\/Monthly_report_November17.jpg","alt":"","size":654725,"mime_type":"image\/jpeg","last_modified":"2017-11-29T21:40:31+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6573","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6573\/similar"},{"id":6575,"name":"Notts_shoot_01.jpg","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/hywk1ob4rwl4tr\/source\/Notts_shoot_01.jpg","alt":"","size":2871918,"mime_type":"image\/jpeg","last_modified":"2017-11-29T22:00:27+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6575","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6575\/similar"},{"id":6577,"name":"Notts_shoot_02.jpg","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/41xevnixkjeh0r\/source\/Notts_shoot_02.jpg","alt":"","size":2049951,"mime_type":"image\/jpeg","last_modified":"2017-11-29T22:00:27+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6577","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6577\/similar"},{"id":6578,"name":"Volunteers.jpg","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/g7b688eht2dfhr\/source\/Volunteers.jpg","alt":"","size":2743313,"mime_type":"image\/jpeg","last_modified":"2017-11-29T22:00:35+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6578","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6578\/similar"},{"id":6579,"name":"DE_Update_Lightin_GrimHex.jpg","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/68em8ztgupxl6r\/source\/DE_Update_Lightin_GrimHex.jpg","alt":"","size":382472,"mime_type":"image\/jpeg","last_modified":"2017-11-29T23:26:13+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6579","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6579\/similar"},{"id":6581,"name":"DE_Update_Weapons_msr_amrs.jpg","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/rfabtmszt7w3cr\/source\/DE_Update_Weapons_msr_amrs.jpg","alt":"","size":668472,"mime_type":"image\/jpeg","last_modified":"2017-11-29T22:55:47+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6581","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6581\/similar"},{"id":6582,"name":"DE_Update_Weaponsmsr_h29.jpg","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/odbcvwo3xavl6r\/source\/DE_Update_Weaponsmsr_h29.jpg","alt":"","size":188537,"mime_type":"image\/jpeg","last_modified":"2017-11-29T22:55:39+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6582","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6582\/similar"},{"id":6583,"name":"DE_Update_Lighting_Shop_01.jpg","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/46yx73yafrhh5r\/source\/DE_Update_Lighting_Shop_01.jpg","alt":"","size":527723,"mime_type":"image\/jpeg","last_modified":"2017-11-29T23:00:07+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6583","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6583\/similar"},{"id":6584,"name":"DE_Update_Lighting_Shop_02.jpg","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/r15adkt6mzz6pr\/source\/DE_Update_Lighting_Shop_02.jpg","alt":"","size":366826,"mime_type":"image\/jpeg","last_modified":"2017-11-29T23:00:07+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6584","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6584\/similar"},{"id":6585,"name":"DE_Update_VFX_SDF_Raw_Image.jpg","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/wm1ksptgcsdqvr\/source\/DE_Update_VFX_SDF_Raw_Image.jpg","alt":"","size":1008478,"mime_type":"image\/jpeg","last_modified":"2017-11-29T23:14:23+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6585","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6585\/similar"},{"id":6586,"name":"DE_Update_VFX_SDF_Ship_Surface.jpg","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/fekqt9979uh6jr\/source\/DE_Update_VFX_SDF_Ship_Surface.jpg","alt":"","size":1190137,"mime_type":"image\/jpeg","last_modified":"2017-11-29T23:14:29+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6586","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6586\/similar"},{"id":6587,"name":"DE_Update_VFX_SDF_Textures_Normalised.jpg","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/sex47bq2in9e3r\/source\/DE_Update_VFX_SDF_Textures_Normalised.jpg","alt":"","size":937762,"mime_type":"image\/jpeg","last_modified":"2017-11-29T23:14:35+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6587","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6587\/similar"},{"id":6588,"name":"DE_Update_AI_Subsumption.jpg","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/pmjt0ye1izp20r\/source\/DE_Update_AI_Subsumption.jpg","alt":"","size":59203,"mime_type":"image\/jpeg","last_modified":"2017-11-29T23:24:40+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6588","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6588\/similar"},{"id":6589,"name":"Promo_newsletter.jpg","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/daja1pri70aldr\/source\/Promo_newsletter.jpg","alt":"","size":309401,"mime_type":"image\/jpeg","last_modified":"2017-11-24T00:04:39+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6589","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6589\/similar"},{"id":6590,"name":"Spectrum-038-Custom-Emojiss.png","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/a84mez4qp28x5r\/source\/Spectrum-038-Custom-Emojiss.png","alt":"","size":1747793,"mime_type":"image\/png","last_modified":"2017-11-30T16:08:09+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6590","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6590\/similar"},{"id":6591,"name":"Spectrum-038-Custom-Roles.png","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/4msct9dxxbmi5r\/source\/Spectrum-038-Custom-Roles.png","alt":"","size":1763559,"mime_type":"image\/png","last_modified":"2017-11-30T16:08:16+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6591","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6591\/similar"},{"id":6592,"name":"Hammerhead-Sale.png","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/z5vdq9462e5czr\/source\/Hammerhead-Sale.png","alt":"","size":5732612,"mime_type":"image\/png","last_modified":"2017-11-30T16:18:18+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6592","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6592\/similar"},{"id":6593,"name":"Observer-Test.png","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/mybh7z2hoo4xvr\/source\/Observer-Test.png","alt":"","size":1500406,"mime_type":"image\/png","last_modified":"2017-11-30T16:18:11+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6593","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6593\/similar"},{"id":6594,"name":"Media_sneak_peek.png","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/42wcmxlaoc2otr\/source\/Media_sneak_peek.png","alt":"","size":1384956,"mime_type":"image\/png","last_modified":"2017-11-30T21:37:27+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6594","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6594\/similar"},{"id":6597,"name":"Citcon2947_sabre.jpg","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/7gcsh2rwt19g2r\/source\/Citcon2947_sabre.jpg","alt":"","size":220565,"mime_type":"image\/jpeg","last_modified":"2017-11-30T21:45:45+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6597","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6597\/similar"},{"id":6598,"name":"Evocati_Tests_11-09-17.png","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/flb7b99fpeiulr\/source\/Evocati_Tests_11-09-17.png","alt":"","size":1321756,"mime_type":"image\/png","last_modified":"2017-11-30T16:25:52+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6598","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6598\/similar"},{"id":6601,"name":"Hammerhead_Missile_Fire_2.jpg","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/p5wtf1c38l3eer\/source\/Hammerhead_Missile_Fire_2.jpg","alt":"","size":4983251,"mime_type":"image\/jpeg","last_modified":"2020-05-14T17:56:38+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6601","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/6601\/similar"},{"id":30963,"name":"source.png","rsi_url":"https:\/\/media.robertsspaceindustries.com\/vjhp2njbokvxb\/source.png","alt":"","size":4895804,"mime_type":"image\/png","last_modified":"2023-05-02T18:53:45+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/30963","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/30963\/similar"},{"id":31194,"name":"source.png","rsi_url":"https:\/\/media.robertsspaceindustries.com\/dyu8i559admn1\/source.png","alt":"","size":3831731,"mime_type":"image\/png","last_modified":"2023-06-06T16:13:24+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/31194","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/31194\/similar"},{"id":31403,"name":"source.png","rsi_url":"https:\/\/media.robertsspaceindustries.com\/p34sp3q2kl01b\/source.png","alt":"","size":3014864,"mime_type":"image\/png","last_modified":"2023-07-04T13:35:01+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/31403","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/31403\/similar"},{"id":31536,"name":"source.png","rsi_url":"https:\/\/media.robertsspaceindustries.com\/6u5x9e23ftrw7\/source.png","alt":"","size":3531870,"mime_type":"image\/png","last_modified":"2023-08-01T14:29:26+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/31536","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/31536\/similar"},{"id":31783,"name":"source.png","rsi_url":"https:\/\/media.robertsspaceindustries.com\/gaazjx0n1kop2\/source.png","alt":"","size":3223870,"mime_type":"image\/png","last_modified":"2023-09-12T14:59:52+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/31783","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/31783\/similar"},{"id":32961,"name":"source.png","rsi_url":"https:\/\/media.robertsspaceindustries.com\/8m2c1vusdb0hj\/source.png","alt":"","size":4757052,"mime_type":"image\/png","last_modified":"2023-10-03T12:11:38+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/32961","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/32961\/similar"},{"id":32962,"name":"source.jpg","rsi_url":"https:\/\/media.robertsspaceindustries.com\/4x3lw5w4vk3o4\/source.jpg","alt":"","size":584749,"mime_type":"image\/jpeg","last_modified":"2023-10-31T19:13:02+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/32962","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/32962\/similar"},{"id":38000,"name":"source.jpg","rsi_url":"https:\/\/media.robertsspaceindustries.com\/x5aus9nndxu4s\/source.jpg","alt":"","size":1186506,"mime_type":"image\/jpeg","last_modified":"2025-02-05T13:01:54+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/38000","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/38000\/similar"},{"id":38060,"name":"source.jpg","rsi_url":"https:\/\/media.robertsspaceindustries.com\/fe6j2ifv3ash4\/source.jpg","alt":"","size":1773870,"mime_type":"image\/jpeg","last_modified":"2025-03-04T15:04:48+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/38060","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/38060\/similar"},{"id":38084,"name":"source.jpg","rsi_url":"https:\/\/media.robertsspaceindustries.com\/pgmk7f9gt3j9y\/source.jpg","alt":"","size":2091105,"mime_type":"image\/jpeg","last_modified":"2025-04-01T17:29:16+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/38084","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/38084\/similar"},{"id":40391,"name":"source.png","rsi_url":"https:\/\/media.robertsspaceindustries.com\/svep7j1purh1f\/source.png","alt":"","size":5543040,"mime_type":"image\/png","last_modified":"2025-07-01T15:37:40+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/40391","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/40391\/similar"}],"images_count":86,"translations":{"en_EN":"Greetings Citizens!\n\n\nWelcome to the Monthly Studio Report, where we collect updates from our various studios around the world to show you what they\u2019ve been working on this past month. As many of you know, there\u2019s been a concerted push among our various studios to get the Alpha 3.0 to the community. Since our last report, we\u2019ve gone to Evocati and begun a staggered release to the PTU, so the team\u2019s busy fixing bugs discovered by the testers and working on overall stability and performance. With that, let\u2019s get to it. CLOUD IMPERIUM: LOS ANGELES\n\nENGINEERING\nLA Engineering has been racing towards 3.0 at a breakneck pace, with the primary focus being on resolving bugs from Evocati and PTU and adding final polish to features like cargo, item components, atmosphere systems and more. Part of this work has been integrating all the item systems in ships with UI in order to bring a real sense of control to the cockpits. Lastly, updating Quantum Travel has been an area of focus for several weeks, pushing to deliver a more immersive experience.\n\nTECH DESIGN\nThis month, LA Tech Design spent the bulk of their time closing down tasks and knocking out the remaining bugs for the Item 2.0 Ship Setup. They\u2019ve solved several issues with the 300 series, Mustang, Nox, Starfarer, and Scythe while identifying some more dependencies on the final lighting setup as well. The updated animations for the Gladiator were delivered this month so a total setup refactor has been completed.\n\nIn addition, the team also finished setup on all the ship headlights as well as the \u201cSaveGameLogOut\u201d functionality that allows for logging out anywhere there\u2019s a bed.\n\nART\nThis November, the Character Team spent a lot of time polishing the cast of Squadron 42. They also polished many new Star Citizen characters and assets that they are excited to release with 3.0.0 while working on developing concepts for clothing, finalizing the legacy armor sets and more.\n\nThe LA Ship Art team has spent much of November updating a lot of ships to take advantage of new tech. In particular, the ships now use new Light Groups set-up, new fog tech, new Render-to-Texture screens and to made proxies airtight now that oxygen has been introduced to Star Citizen. They\u2019ve been juggling these various tasks with fixing a lot of art bugs in preparation for ships included in the Alpha 3.0 release. Additionally, they\u2019ve made progress on the art for future releases, including the Anvil Hurricane, Tumbril Cyclone and the Consolidated Outland Mustang update.\n\n\n\n\n\nNARRATIVE\nIn addition to working with the PU design team on polishing Alpha 3.0 mission content, the Narrative team continued to expand the Xi\u2019an language with the help of the community, and worked with the cinematics team to create the Galactic Tour Hammerhead piece. For Squadron 42, they spent time discussing additional set dressing with the prop and art teams to help further expand environmental storytelling in the game. Looking ahead, the team also spent time this month continuing to plan out narrative content goals for 2018\u2019s quarterly updates.\n\nTECH CONTENT\nFor Environments, the Global Technical Content team has been continuing work on the features that were revealed at the GamesCom Procedural Tech Demo. In addition to supporting asset and code performance improvements, they have been investigating bugs with lighting and visareas, and have been working side by side with the graphics team to develop scripts and shader tech to help catch performance issues as well as improve other areas like the procedural cities. They\u2019ve also worked in conjunction with our tech animation team on animated environment assets, and with engineering and design on new tech for Derelict Systems, Outpost Locations and a Planetary Placement Systems.\n\nFor Ships, the team has been busy handling damage implementation for the new ships coming down the pipeline for the 3.0 release. All of this whilst juggling a variety of ship bugs related to UV2 damage, landing gear compression, visareas and log spam errors. Progress was made to support gas effects for the incoming Breaching feature. They\u2019ve also been supporting Tech Design and the Ship Art teams with some new tech for ship lighting and ship proxies. On the Weapons front, the team has continued to work on new weapons in the pipeline, including working on Mannequin set-ups, weapon bugs, an adjustable stock, and some exciting R&D on animated weapon attachments which will have many additional uses beyond just weapons.\n\nA lot of work for the Tech Animators was in support of Squadron 42, rigging and simulating new costumes coming down the Character & Heads Pipeline. As with the other areas of focus, ample time has been spent on fixing bugs, mainly related to skinning and character item implementation.\n\nThe team has also been making great progress tracking, trimming and solving a vast amount of MoCap data for Squadron 42. The list of accomplishments rounds out nicely with the implementation of new health checks, a CIG Tools Installer, Tools management\/migrations, and a ton of support for facial animation, usables, wildlines and cinematics.\n\nFinally, there was a lot of miscellaneous support that the team had their hands on, including technical direction for WAF asset builds (which reduce build times significantly!), website development, R&D and some due diligence on a prospective upgrade to our internal DCC tools Max and Maya and MoBu.\n\nQUALITY ASSURANCE\nLAQA\u2019s primary focus was testing lighting and the new light groups, LOD\u2019s, breaching mechanics, character art, the myriad of new updates to the code base made by the engineering team, and the way Item Ports were set up by tech design. They also aided the global QA team with publishing checks for PTU and Evocati deployments and several live internal gameplay reviews.\nCLOUD IMPERIUM: AUSTIN\n\nDESIGN\nThe ATX design team have been tackling all things shopping to get the game ready for the PTU Release of the 3.0 build. There have been two core elements that we\u2019ve been focused on since the handing off the Mission Givers implementation tasks to the design team in Frankfurt. The team also outlined the desired income per hour goals and has adjusted both the mission reward calculator and the item prices accordingly. This work has also included the ship respawn time and prices. While we expect to dial in these values over the next several Alpha builds based on player feedback and analytics that we collect, we feel like this is a good representation of where we want it to be.\n\nMeanwhile, the rest of the team tidied up all the physical shops in the three major locations: Port Olisar, Grim HEX, and Levski. In total, there are roughly fifteen separate places where players will be able to buy items in the game and we\u2019ve been able to spread the items around the different shops with very little overlap. The team also worked with the LA Programmers and the UI team to add some new features for the shopping experience. Among these new features are: AR Markers have now been replaced by the new item highlighting system to fall in line with the overall loot system.\n\nInner Thought is now being used on the objects where Try On, Inspect or Buy are concerned.\n\nArmor can now be purchased as separate pieces.\n\nAll Item names are now unique\n\nFirst pass of shopkeepers are now in.\n\nThe shopping UI has been cleaned up.\n\nWhile there are still have many new features they wish to add, or existing ones they wish to clean up, the team hopes that the new shopping experience will make all players happy, and they look forward to continuing the refinement of the shopping experience in the new year.\n\nART\nThe ship team knocked out 3.0 bugs for the Drake Herald and Cutlass Black, including fixing up their lighting states and visareas. They also finished up the whitebox modeling and a first pass at interior lighting of the Constellation Phoenix, so it\u2019s now in game and can be walked through. In other Constellation news, the Andromeda and Aquila had their interior and exterior lighting states updated and their LODs were refactored to be much more efficient. Several other ships went through similar updates, including the Hornet (F7C, F7CM), 300i (and variants), M50, Scout and Nox. The team continued their work polishing and optimizing the materials on all the ATX ships. Work also began on the whitebox modeling process of the Anvil F8 Lightning.\n\nBACKEND SERVICES\nServer Engineering team focused on helping with features and issues in 3.0. The team has been tuning parts of the back-end services to accommodate the volume of data that flows between game servers, persistence caches and the database, and solved several issues, including the ability to reconnect to the same instance if you lose your network connection. Over the course of the month, they also improved data integrity if a server or service would go down, improved caching services functionality to allow items to exist in the universe outside of the player\u2019s possession, and lastly solved many login and connectivity issues.\n\nLooking to the future, the engineering team has been building the next generation of back-end services. The team is aiming to split up all larger services into smaller stateless services and enhancing the service architecture and Ooz scripting language to comply with the ever-growing requirements the game demands.\n\nANIMATION\nThis month, the Ship Animation Team fine-tuned the player bed enters and exits as part of our persistent save system, which will allow the player to enter a bed and exit the game while saving their location in the universe. Next time when you load the game, you\u2019ll wake up in your bed with your ship in its last location. In addition to this, the team finished updating the Gladiator enter and exits as part of the cockpit experience sprint. The speed and technical setup of the Gladiator has vastly cut down the time to enter and exit the pilot and copilot seats. The Austin studio also held a motion capture shoot to capture animations for the Tumbril Cyclone.\n\nMeanwhile, the PU Animation Team helped support work on Squadron 42 and worked closely with Design to make all usables fully functional and bug free. Some of the challenges the team faced included syncing props to animate with characters, such as chairs sliding as a character sits down and getting a female version of every animation implemented into the game. The goal is to have a large batch of the Usable animation assets polished and finalized by the end of the year.\n\nOPERATIONS\nThe DevOps Team worked around the clock to support our internal teams and the Evocati as we closed in on our 3.0 goals. In addition to publishing at least one game version every day, they have been able to complete some major internal projects designed to massively improve build times and error handling.\n\nATX QA\nSince CitizenCon, 3.0 has been an all-consuming focus for the QA team as incremental updates were released to Evocati and to the first wave of PTU. Between Evocati and the PTU, there have been 26 builds published so far under Austin\u2019s belt for 3.0 and 2 publishes for our sister team in UK. QA has been gathering fresh performance captures for our engineers with each new build that goes to PTU to focus on stability. The team worked with the LiveOpS cohorts to compile all the various new client and server crashes with metrics to show which has the greatest impact. With so many new missions in 3.0 and new gameplay mechanics associated with them, the team ensured they function both in ideal scenarios and when a server is at full capacity. At the same time, they\u2019ve been testing various new configurations with UK QA and the engineering teams to increase the player cap. Squadron 42 testing has been proceeding at a brisk pace, with regular tests of levels run on new builds each day.\n\nFor leadership, the focus has been training new hires and keeping in constant communication with the other departments, talking to Production to ensure that the right bugs are on their radar for PTU and Live triage, attending stand-ups with the Development teams to find out what needs to be tested coming out of the sprints, and working with Player Relations and Issue Council every day to keep up to date on the latest feedback and reports from backers. All these different avenues combined to ensure QA is consistently on the same page across the company.\n\nPLAYER RELATIONS\nThe month of November kept the Player Relations team on its toes. After assisting and moderating a phenomenal CitizenCon, the team rolled right into helping backers with their interest in our game-changing Pioneer. The team also worked with Evocati every day to publish new 3.0 builds, run playtests, assess stability, and gather crucial feedback. With the push to PTU, they wanted to thank all our relentless Avocados who are always there to answer the call! Lastly, the team expanded in Austin and Frankfurt as their list of duties continues to increase. They are excited to hire our first full time German support staff, as well as roll out moderation support in several new languages.\nFOUNDRY 42: UK\n\nGRAPHICS\nThe graphics team spent their time bug fixing 3.0. When QA\/Evocati get their hands on completed features and assets there\u2019s always the usual influx of unexpected issues. This included numerous problems related to rotating planets\/moons because much of the older rendering code made assumptions about things being stationary, and especially doesn\u2019t cope well with changing the frame of reference when moving in\/out of orbit.\n\nThe team also created a new glass shader that provided a great visual improvement over the past one, and they were really keen to see it implemented as soon as possible. A pass was done across all ship canopies.\n\nThey also closed down some minor feature work for 3.0, such as RTT functionality for ship MFDs and the ability for game code to control the camera\u2019s exposure to make the mobiGlas more legible in bright lighting conditions (though more improvements are coming for holographic displays). In parallel, two team members continued their longer-term R&D tasks on the new shield effect, which uses particles rather than meshes, and improvements to the volumetric ray-tracing tech (gas clouds & fog), which is nearing the point where they can share some pretty cool visuals!\n\nSHIPS\nHammerhead\nThe Hammerhead has made rapid progress in a short time period. Work on the exterior was prioritized for its Galactic Tour appearance. After receiving the concept mesh, the team did more than trace over the shapes but also made sure the mesh was efficient and game ready. Now that the Aegis brand is so well established they have a wealth of shaders and assets to pull from for quick iteration.\n\n600i\nThe 600i\u2019s interior corridors were fully fleshed out, making sure they capture the higher class feel that is Origin. Further work was done with the exploration module, along with passes on materials and lighting. The block out of the bridge is done and work on it has started. For the exterior, the thrusters are almost complete and the landing gear should be wrapped up shortly.\n\nIdris\nThe Idris has entered a polish and bug fixing phase. The team supported design with useables set up and are starting to see interactive items such as seats, benches and beds being useable by the player and AI.\n\nVoid\nVanduul Void art is complete. Damage and LODs are being set up.\n\nCarrack\nThey chipped away at a more detailed greybox by picking two areas to focus on \u2014 engineering and habitation. The plan is to take these sections to final geometry before going into engine to create materials and lighting. This approach is taken to maximize the time spent being creative with the designs at the start and lays the groundwork for future tasks.\n\nCONCEPT ART\nNovember saw the concept team finish and deliver two spaceships, the Anvil Hawk and the Aegis Hammerhead, with another ship and vehicle in development. They also reshuffled artists and moved some people to new disciplines to keep things fresh and reduce the risk of burnout. As you know, the team pumps out a huge amount of work and it\u2019s important to stay on top!\n\nOn the environment side, they further explored areas of Hurston, landing sites, hangars and general building look dev, and some high-level exploration of Microtech. They continued with weapon development, making the first of the Associated Science and Development Distortion repeaters and refining the Hurston Electron Beam cannon.\n\nVFX\nLong-planned work on shield improvements finally commenced this month. This included the generation of \u2018signed distance fields\u2019 by our team in Frankfurt and a R&D-intensive collaboration with the Graphics team to generate energy effects that closely conform to the hull of a ship. This work was previously mentioned in Around the Verse and can be used to improve numerous ship-specific effects, like atmospheric entry burn-up and Quantum Travel.\n\nSpeaking of QT, recent design changes required the team to rebuild the effects so they fit the new code \u2018hooks\u2019 (triggers that call upon the effects to be activated). Once the timings and functionality were back in place, they continued to polish\/optimize the effects. This was a time-consuming process and required careful collaboration with Design and Game-Code, but was worth it given the results.\n\nThis month has seen a company-wide push to clean-up log spam. For the VFX team, this is a case of removing references to missing textures or finding particle libraries that were moved\/had their name changed, as reported by the editor when loading a level. It\u2019s one of the less glamorous sides of the job but actually very satisfying to whittle away the error logs.\n\nThey also conducted our usual \u201csanity pass\u201d for 3.0 by checking every effect in the game and making sure they work as expected. This is where QA is invaluable, as it simply wouldn\u2019t be possible for the VFX artists to check through all the game\u2019s effects in such a time-frame. They are still working through these checks due to the size of our VFX library!\n\nLast but certainly not least, lots of Squadron 42 specific tasks were tackled. As usual, the team can\u2019t go into too many details but work ranged from Coil-specific plasma experiments, to mysterious debris clusters, and distant storms brewing.\n\nAUDIO\nCIG Audio has been all about working towards delivering 3.0 and making improvements to the player experience sound great and work as solidly as possible. Thus, bug-fixing and optimization has been taking up time for everyone between feature work (and often because of feature work!) in addition to the continued work on Squadron 42.\n\nOn the music side of things, the team have rolled out a new music composition pipeline to help step up productivity and improve communication for persistent universe music production. In addition to that, they are also working on a new logic-based music system to cater for points of interest such as space stations and moons with outposts \u2013 part of a move to make music transition more seamlessly overall.\n\nIn sound design, the pressurization system coming online is something that\u2019s a big step forward. When on foot and EVA, you\u2019ll find space doesn\u2019t necessarily sound as if it has an atmosphere now. There are still a few teething issues to readdress a lot of sounds and ensure they\u2019re set-up correctly within our Wwise bus structure, but when complete, it will add a lot more to the dynamics of the audio in-game and goes hand-in-hand with our \u2018sound sim\u2019 lore that justifies sonic feedback when in-cockpit.\n\nDoor and elevator sounds have also undergone much maintenance and re-work in response to upstream system changes. Outposts have had their foundational work done to account for different power states. Weapons \u2013 on both ship and human-scale \u2013 have been iterated upon, with some great work done on the HDR tech for those. The Character Foley system has been extended to account for landing\/jumps more elegantly. Ships have been continually addressed and Quantum Travel, having been refactored upstream, has been improved and extended. In-game displays and MFDs now also emit their sounds in 3D from their perceived point of origin.\n\nWhere dialogue is concerned, ship computer voices have undergone some extensive rework with a lot of emphasis on producing runtime effects to simulate speakers and other playback mechanisms diegetically (which will prove especially satisfying once players can use them with live input from their own FOIP set-ups\/mics). The team\u2019s also continuing to improve the dialogue mix, add more dialogue to mission givers and NPCs, and making improvements in dialogue spatialisation.\n\nAs well as the above, the team has been making lots of incremental improvements and as always, it\u2019d be great to get your feedback on the forums in case there\u2019s anything in particular you would like them to address.\n\nENVIRONMENT ART\nThe team worked hard on this year\u2019s CitizenCon demo. The positive response was great for the team to hear. They have been planning the tech roadmap for further city development work, as making a living and breathing cityscape has many complexities. Memory budgets, engine rendering, city building shaders, and day\/night sequences are all being developed.\n\nThey also made sure that the 3.0 release build was as stable as possible. There were only a handful of bugs so this should be a very strong environmental experience for the player. The team continued to refine tools to enable more efficient workflows. An example of this is an automatic dropping system for landscape POI\u2019s, like outposts, being implemented to remove a lot of the brute force work which was previously required. Also, after internal playtesting, they wanted to improve the experience at outposts on the dark side of a moon. The lighting engineers worked on a solution to provide these areas with more light so players could see what they are doing. They also started converting all the old shops in Area18 to the new systems for things like usable, doors, etc. The new layout not only improves the plaza\u2019s performance but enables it to be filled with more NPCs and allows the team to add some new beautiful areas where you can take in the vistas of ArcCorp.\n\nDERBY ANIMATION\nThe Derby Studio was super busy with tasks for 3.0 and the Anniversary Sale. They ran the in-house headcam system for a motion capture shoot in Nottingham for the Galactic Gear Hammerhead segment.\n\nFace scanning at CitizenCon 2947 was a great success. The scanner went from in pieces to fully built on a new frame in two weeks. It was tight but we did it! The rig took an epic 12-hour ferry journey to get to mainland Europe, then a 300-mile drive in the \u201cScan-Van\u201d to Frankfurt. A massive thanks to all the volunteers who helped set up and tear down the scanner. The team couldn\u2019t have done it without you! All 10 scan winners enjoyed their scan sessions and it was great to meet a bunch of super enthusiastic SC gamers.\n\nFinally, the team is excited to see the characters in 3.0 and are currently working through the levels to polish and improve their facial animations.\n\nENGINEERING\nNovember was focused on 3.0, getting it to Evocati and then to PTU. This means there were a lot of bug fixes and optimizations, as well as the finishing of features like persistent spawning, player interaction, missions, and so on. However, this doesn\u2019t mean they didn\u2019t get to work on any new features. The team was split into those that support the PTU and its requirements, and those working on new tech to incorporate into future builds when it\u2019s ready.\n\nFor example, there\u2019s a team working on the making the social AI have more life and feel less robotic. This started with the NPCs delivering wildlines, one off lines of dialogue dependent on the situation. These could be simple greetings, if they already know you or other NPCs, or a warning that they\u2019re coming through when jogging and coming across another character. They were also given a bit more interest in the environment, glancing at items as they walk around or if nothing\u2019s taking their fancy just looking at where they\u2019re going. Layered on top of that are fidgets, where a character will scratch their head or look at their watch to help break up a repetitive animation. They\u2019ve also been adding in custom locomotion sets for different characters so everybody doesn\u2019t have the same walk\/run gait.\n\nThe team also looked at cinematics in an effort to polish them so they look their best. They explored how the cinematic team can better control the lighting whilst in a scene without breaking it for the rest of the environment and how to dial in the depth of field and field of view. This is to give that cinematic feel and show off the characters without negatively impacting the control of the player. Other than that, there were lots of gameplay sprints and getting through all the functionality required.\n\nANIMATION\nThe animation team has been working in tandem with design to focus on combat AI \u2013 chopping assets up to fit new metrics, providing placeholder assets to prove systems out, cleaning up existing assets. They have also been going through the performance capture data and creating game ready locomotion, idle & fidget assets for cast characters. The Idris armory has had a full sweep, so that design have all the animation assets for the master-at-arms and his weapon interactions. In line with this work, they worked hard to create some cool first weapon selects.\n\nOutside of feature development, the team did bug fixing and debugging issues that are currently in 3.0 and beyond.\nFOUNDRY 42: DE\n\nWEAPONS\nThis month the weapons team completed the final touches on the Kastak Arms Custodian skins, which were made together with attendees at the CitizenCon demo stand. The FPS team also started production on two new weapons: the Gemini H29 HMG and the Torral Aggregate Kahix Missile Launcher. The ship weapons team has started production on the A&R Laser Cannons (Size 1-6) and the Gallenson Tactical Ballistic Gatlings (Size 1-3), which should allow them to replace another big batch of legacy ship weapons with shiny new ones in the near future.\n\nLIGHTING\nThe DE lighting team focused on finishing our remaining 3.0 lighting tasks, which involved more polish and performance items in Levski. In addition to other general 3.0 bugs, they supported the shop team to help differentiate lighting in shops based on the location. A large amount of focus will now shift to various areas for Squadron 42.\n\nQUALITY ASSURANCE\nThe DE QA team did a wide range of testing this month to focus on issues found in the Evocati builds and testing the 3.0 branch in general. This included a streaming issue that occurred after being connected to a server for an extended period and the black screen some encountered when initially loading into Stanton. These issues were speculated to be the result of potential memory corruption and required more testing with Page Heap to provide the engineers with additional information to fix them. The fixes will ultimately increase the overall stability of the full game.\n\nSubsumption testing also continued with new features and bug fixes going into the Subsumption tool weekly. The team collaborated with Design to learn their workflows in an effort to better test the varying uses of the Subsumption tool. This will expand the scope of QA subsumption testing to include test cases outlining how the Subsumption Editor works with our other tools used by the Design Teams, such as Dataforge and the Lumberyard Editor. Additional focused testing was also spent on the Sabre Raven\u2019s EMP and its effects on other ships. These effects were recorded for multiple types of ships and reviewed by Design to make sure there weren\u2019t any discrepancies between the design and how it\u2019s currently working.\n\nDE QA also worked closely with Marco Corbetta to get to the bottom of ships falling through the planet surface when players powered off and exited their ship. This was particularly tricky to reproduce as it only occurred on Shipping builds and could not be reproduced on internal Development builds. The Engine team discovered that the Shipping builds were specifically missing certain .r16 files which contain sample displacement textures made by artists. These are also used by the server for generating collision data but not for rendering. The issue was resolved by Build Ops and confirmed fixed the next day.\n\nENGINE\nThis past month, the Frankfurt Engine team tackled numerous fronts, such as wrapping up new items for 3.0, investigating and addressing existing bugs, as well as general optimizations.\n\nThe team made a lot of progress optimizing for both the server and client, and started conducting routine network stress tests to better understand how the engine scales on the server with a large number of players and learn what areas are still expensive and need optimization. With the increased number of players on the server and more code being moved to jobs for parallel execution, changes were made to the job system to allow utilization of more than 16 worker threads on servers without introducing extra overhead in job distribution. This is needed to allow an increasing number of player counts. This change to the job system will also translate to the client, so people with high-end CPUs will see extra performance benefits in areas where they are typically CPU bound. On the low-level optimization side, they changed the signaling mechanism of the core threading synchronization object on Linux from semaphore to futexes. This change spares one syscall in 99% of the cases, which provides a small performance boost.\n\nArea Management was optimized by disregarding an Octree for Areas they never search in. An \u201carea\u201d is a special markup for the designers which tracks all objects inside a specific location, such as a bar. The system now allows them to send Events when an object (like a player) enters an Area (the bar), on which the game code can then react. They also support spatial queries against those areas (using the same code as the Zonesystem, as this allows them to support areas of nearly arbitrary size). This behavior requires that for each moving object, they check if it is no longer in any area or if it entered a new one. On top of this, and for them to have efficient spatial queries, they need to maintain an octree per Area. The team realized that many of those areas were never used for spatial queries, which means they had numerous unneeded computations with the octree\u2019s. This is now fixed and they only maintain the octree when actively searching in an area.\n\nThey also spent some time investigating memory leaks, and developed a lightweight memory tracking system which can be run on the server in the background with an acceptable performance impact. They can then review the results in an effort to analyze and fix specific memory leaks people encounter. The team also did some minor bugfixes for the Patcher Library, which implements the functionality for the delta patching. Improvements were made to the new temporal antialiasing technique to improve overall image sharpness and preserve luminance of bright objects. Additionally, motion vectors for software skinned meshes were fixed, so that postprocessing technique can properly take them into account (temporal antialiasing, motion blur, etc).\n\nRegarding skinning and characters, the team fixed code to allow mesh compression on skin meshes with morph targets. Since faces are very detailed, this will result in substantial memory savings and lower rendering overhead. Lastly, with respect to future engine improvements and memory savings, they made good progress in implementing GPU based ray intersection tests to offload these types of computations from the CPU and reuse the already existing high-fidelity render mesh on GPU for precise intersection test. The results of those computations are provided asynchronously as to not block the CPU mid-frame and can be used on any type of effect that doesn\u2019t need server authority (anti cheat measure).\n\nLEVEL DESIGN\nThe Level Design team polished the locations for 3.0 with the focus being bug fixing for Levski and surface outposts. As that work was completed, they turned towards the future and to something called \u201cCommon Elements.\u201d These are components that each location will use, like hangars, garages, housing, offices and so on that will be tied into our modular system and combined with the various tilesets. The team will quickly be able to use them to add essential components to locations. They also looked into train stations and monorails for our flagship landing zones, as well as early work on city Space Ports.\n\nVFX\nThe DE VFX team worked on particles and VFX that are used throughout the universe. They\u2019ve gone over almost every existing visual effect again to ensure there are no issues. One recent challenge has been staying on top of the physics system for particles. With such an active development cycle, sometimes things that previously worked need to be modified to accommodate the updated system(s). They also continued to flesh out the GPU particles system and added new features to it. The team is approaching the point where the old CPU based system can be phased out and rely solely on the GPU for most effects throughout the levels and universe. They also worked on applying signed distance fields to our particle effects. These are 3d textures that specify the distance to the surface of an object. With these textures, they can reconstruct the interior and exterior of geometry and have the motion of the particles affected by the SDF. It can be used for collision detection as well as allowing particles to flow over the surface of the SDF.\n\nSYSTEM DESIGN\nThe System Design team took over the mission givers behaviors, finalizing the implementation and making sure all the edge cases matched the design. The first case was to finalize Miles Eckhart so they could utilize the same defined template for future mission givers. Another related task was to implement the admin officers behaviors and integrate it into the mission system. The admin officer\u2019s main job is to deliver mission items to the player and to accept deliveries of incoming mission items. FPS AI combat saw major improvements, as the system design team worked with AI to make sure the characters enter, exit, peek, and shoot from cover and that their behavior looks as natural as possible. They also addressed bugs and tweaked things required for 3.0 with the focus being on AI, usables, doors, rooms & breathing.\n\nENVIRONMENT ART\nThe Environment team polished areas that are used in 3.0, making sure that players get the best possible visual experience and encounter no visual bugs. Next to polishing, the team focused on what will be coming after 3.0. A glimpse at this post-3.0 Environment work was shown during the CitizenCon demo and is just a small example of what will eventually be on Hurston. A whole new range of ecosystems are being worked on that are visually very different from what\u2019s been seen before. They\u2019ve also been hard at work on unique vegetation, large trash mesas, and the city of Lorville, which is another major landing zone using the procedural city tech.\n\nTECH ART\nThe DE Tech Art team spent the month tackling content creation, new tool building, and supporting various teams, while also addressing issues for 3.0. They added a new Usable for both AI and Player characters, and fixed bugs for existing Usables such as minor animation popping. For characters, they did various skinning tasks that will be used for both the PU and Squadron 42, which will help with character variants. They developed a tool which can help artists export animated geometry into engine more efficiently. This tool combines multiple manual processes into one and error checks before export, making the process much quicker and less prone to human error. For weapons, they finalized the setup for the Gemini R97 shotgun and prepped the Torral Aggregate Kahix Missile Launcher for production. The tech art team also grew by one member and time was spent getting him familiar with the toolset, workflow, and best practices. His focus will be to improve and extend our internal character editor, as well as enhance our existing systems for cloth, hair simulation, and similar physics-based secondary animation effects on all characters.\n\nAI\nThe AI team split their attention between different in-game functionalities and raising the bar on numerous aspects at the same time. Regarding Subsumption, they worked on improving features related to the usability of the tool and exposed new functionalities to the design team. Subsumption conversations now allow designers to specify multiple input parameters and not just the input participants. This allows the creation of a more complex abstraction of logic and more complex conversation branching. They also introduced two new subsumption functionalities \u2014 the support for Event Parameters and Trackview scenes. Event parameters simplify the logic, exposing sub parameters for each event, which then allows designers or programmers to create more complex logic using events to carry more information across different actors. The Trackview support requests the execution of Trackview scenes as needed and tied to the conversation logic which allows the alternative option to create scenes using Trackview to achieve the best visual results, but still allows the Subsumption logic to react or take over when necessary.\n\nThe team also continued to refactor the way the AI controls different vehicles. In the future, behaviors won\u2019t run anymore on the spaceships themselves, but the different seat operators will control the different items they have on any given ship and have the appropriate behaviors. Different operator skills can now directly influence the different actions, and vehicles like multi-crew ships can benefit from the different NPCs operating the various seats. They also worked on manned and automated turrets. Both of those possible controllers will take care of executing all the required operations to turn on the turrets, activate their functionalities, search for targets using the radar, predict where to shoot and so on. Work on NPC on-foot AI mostly focused on human combat, polishing the different entries\/exits to move into\/out of cover, and the different actions that can be performed while in cover (peeking, shooting from different sides of the cover, changing body directions and so on).\n\nRegarding the other systems, a huge number of fixes and improvements went into the Mission System, offering all the functionalities requested by designers for the current missions. The Spawning Manager received lots of optimizations and new improvements, especially on the environmental validation to spawn elements correctly and safely in space and on the ground.\nTURBULENT\n\nA new release of Spectrum, a major milestone for the Launcher and additional 3.0 launch support kept Turbulent very busy for the month. Here\u2019s what we\u2019ve been working on:\n\nSPECTRUM\nThe release of Spectrum 3.7.1 consisted of bug fixes, quality of life improvements and unnoticeable changes to sustain long term development and maintenance. Let\u2019s talk about latter first.\n\nThe team is improving the code base and release process so that launching new versions remains a frictionless process as much as possible. Spectrum also adopted a new versioning scheme to better communicate the scope of a release and then proceeded to update a lot of internal dependencies to avoid potential future breaking changes. There\u2019s also discussions about bumping React to the latest version as well as migrating the code base to TypeScript. Those changes would allow us to trap more bugs before going into production and refactor parts of the project without affecting stability.\n\nAlso, the team set to improving how to handle change requests, better manage priorities coming from different sources (Jira, Issue Council, Forums, internal communications, etc.) and get better at tracking\/communicating progress.\n\nLast, here\u2019s summary of the latest application changes: * Addressed several pain points for Android device users where entering text would produce unpredictable results. * Spectrum now suggests a list of mentions based on the authors of the last messages in a lobby when typing \u2018@\u2019. * Embedded Twitch clips will no longer automatically play. * Significant progress has been made on Custom Emojis and Custom Roles and with the hope to deliver those for 3.8.\n\nLAUNCHER\nLauncher testing started in October with the release of the RSI Launcher 1.0.0-alpha.20 to Evocati for testing. This is the first exposure public users have had with the Delta Patcher.\nUsers have been very happy with the Delta Patcher, as some patches are as little as 100 megabytes! Pretty dramatic reduction in patch sizes compared to the previous technology used to deploy Star Citizen Alpha 2.6 and below.\n\nWith help from the great Evocati, the team has been able to gain exposure to a multitude of user setups, hardware configuration, Windows versions and personal user preferences that affect the function and operation of the launcher. Most of the following weeks have been spent iterating on issues found during this phase and fixing bugs that affect patching and gameplay. Most notably, issues related to Windows N and file permissions have taken a lot of time to figure out. As always, the Issue Council has been our greatest ally in getting the bugs vetted, verified and checked before being tackled.\n\nThe application will now properly trap game crashes and application errors.\n\nThe game library polling mechanism have been tuned to a real world case with many users listening for updates.\n\nThe application will now properly repair permissions on the game library if a permission error is detected.\n\nDuring a \u201cVerify Files\u201d the launcher will also check for an update!\n\nThe sound system has been expanded to provide a better sonic experience in the launcher. Volume slider!\n\n5 new background music tracks have been added from the SC soundtrack!\n\nOnly one major item remains for 1.0.0 of the launcher \u2014 the specific handling of the initial download, which is a problem with the new object based Delta Patcher. A game build is comprised of many files (upwards of 300k-400k) many of which are smaller files. Currently, when patching from scratch, your launcher will fetch all those files. This process is not only highly inefficient but also slow and error prone. The team is currently working on solving this by allowing the distribution of a \u201cKick Start\u201d pack that will contain all small files and the base assets to start the game minimally. This base pack can then be fetched first, with a multi-threaded range downloader, if you have no pack files on disk. Once the kick start pack is downloaded, a normal delta patch can be applied to bring you to the latest version.\nThe team plans on tracking on base pack file per minor release (semver) of the game, which will always keep it fresh and fast.\nThey\u2019re excited to get this in your hands as they believe this significantly improves the onboarding and update experience of Star Citizen.\n\nANNIVERSARY SALE\nThis month, the Turbulent team brought to life the 2017 Anniversary sale. The sale unveiled two concept ships: the Anvil Hawk a small, light fighter with an emphasis on weaponry, and the Aegis Hammerhead an impressive patrol ship with multiple turrets designed to combat fighters. These two concept ships were just the start, as each day passed they released a chance to nab some your favorite ships, including a limited allotment of the Idris and Javelin.\n\nAlong with this sale, the team created the Observer test, which was your chance to test your knowledge of all-star citizen ships. The test proved to be too easy for our most die-hard fans, however it was still great to see the community brag on spectrum with their gold badges.\n\nSITE RE-DESIGN\nThe team is happy to reveal a new website with the Live release of 3.0. The design and development team have been working hard to tie up loose ends and are extremely excited to release the new designs and continue building on the new and improved platform.\n\nIn addition to the re-design they are taking the opportunity to add a new Production Roadmap. Its purpose is for you, the community to be able to better track the features that are important to you. This is will be vastly different than our text version of the production schedule. Community\n\n\nThe second half of the year is traditionally a busy period for all things Star Citizen and this year was no exception. A lot has happened since the last report back in September with CitizenCon 2947 surely being the highlight on the community side.\n\nAlmost 1000 Citizens gathered in Frankfurt to explore new worlds, experience the latest technologies, get together and speak to the developers of their favorite Space Sim. During the show, Intel showcased their new Optane 9 SSD and with it, the brand-new Sabre Raven. The team also revealed our capital-sized Consolidated Outland Pioneer and with it the new gameplay mechanic of staking your claim and building outposts.\n\nAnother highlight over this month was the release of Alpha 3.0 to the Evocati and eventually the PTU. After burning down the remaining issues and bugs, we released our latest update to a selected group of testers, who helped us to iron out the kinks of 3.0 to release to an even broader audience, the Public Test Universe.\n\nThe team\u2019s continuing to make steady progress on Alpha 3.0 by releasing new builds with our delta patcher and reviewing the improvements made. With the PTU in the community\u2019s hands, the devs are not only polishing features but also addressing the bugs that come in thanks to this expanded group.\n\nEveryone here wants to thank all our testers who helped to make this possible with stress tests during ungodly hours and myriads of bug reports sent in. Keep testing and stay awesome!\n\nAs a special anniversary perk, our Subscribers had the pleasure to take five ships on tour during October, namely the Constellation Andromeda, Aurora MR, Freelancer, Hornet F7C, and 300i. Currently, they\u2019re enjoying the MISC Starfarer & Origin M50 as the two ships of the month. November\u2019s town hall featured Senior Systems Designer Will Maiden, Lead Gameplay Engineer Chad McKinney, and Associate Gameplay Engineer Spencer Johnson as they answered your questions about cargo and hauling. If you missed the show, catch it on Youtube with all our other shows; from Citizens of the Stars and Bugsmashers to newcomers like Xi\u2019an language lessons with Britton Watkins. So, if your response to a \u201c.ath .u m.uexy.oa?\u201d still is a \u201ce yo nai\u201d, you might want to catch up.\n\nLast week, the Anniversary Special kicked off with eight episodes of ATV each highlighting a ship manufacturer. It welcomed some new additions, too: Anvil Aerospace\u2019s Hawk, a light fighter with a diverse arsenal of weapons and the Aegis Hammerhead, a fast and light warship.\n\nTo close this month\u2019s report, here\u2019s a look at what will be next.\n\nMake your vote count! Join our upcoming live stream (12\/1 at 12 pm PST) and help us decide on a Drake ship to add to Star Citizen. If you haven\u2019t yet, also check the new episodes of Galactic Tour and the return of Ship Shape, featured in our ATV Anniversary Specials. We\u2019ll be saying goodbye to 2947 with our Holiday livestream where we\u2019ll focus on Squadron 42and share our roadmap for completion.\n\nUntil then, we\u2019ll see you in the \u2018Verse! WE\u2019LL SEE YOU NEXT MONTH\u2026","de_DE":" Ort, wie z.B. eine Bar. Das System erlaubt es ihnen nun, Events zu senden, wenn ein Objekt (z.B. ein Spieler) einen Bereich (die Leiste) betritt, auf den der Spiel-Code dann reagieren kann. Sie unterst\u00fctzen auch r\u00e4umliche Abfragen gegen diese Bereiche (mit dem gleichen Code wie das Zonensystem, da sie dadurch nahezu beliebig gro\u00dfe Bereiche unterst\u00fctzen k\u00f6nnen). Dieses Verhalten erfordert, dass sie f\u00fcr jedes sich bewegende Objekt pr\u00fcfen, ob es sich nicht mehr in einem Bereich befindet oder ob es ein neues Objekt eingegeben hat. Dar\u00fcber hinaus m\u00fcssen sie, damit sie effiziente r\u00e4umliche Abfragen durchf\u00fchren k\u00f6nnen, einen Octree pro Fl\u00e4che pflegen. Das Team stellte fest, dass viele dieser Bereiche nie f\u00fcr r\u00e4umliche Abfragen verwendet wurden, was bedeutet, dass sie zahlreiche nicht ben\u00f6tigte Berechnungen mit den Oktaven hatten. Dies ist nun behoben und sie erhalten den Oktaree nur noch, wenn sie aktiv in einem Bereich suchen.\nSie verbrachten auch einige Zeit damit, Speicherlecks zu untersuchen und entwickelten ein leichtgewichtiges Speicherverfolgungssystem, das auf dem Server im Hintergrund mit einer akzeptablen Leistungsauswirkung ausgef\u00fchrt werden kann. Sie k\u00f6nnen dann die Ergebnisse \u00fcberpr\u00fcfen, um bestimmte Speicherlecks zu analysieren und zu beheben, denen Menschen begegnen. Das Team hat auch einige kleinere Bugfixes f\u00fcr die Patcher Library gemacht, die die Funktionalit\u00e4t f\u00fcr das Delta-Patching implementiert. Verbesserungen wurden an der neuen zeitlichen Antialiasing-Technik vorgenommen, um die Gesamtsch\u00e4rfe des Bildes zu verbessern und die Leuchtdichte heller Objekte zu erhalten. Zus\u00e4tzlich wurden Bewegungsvektoren f\u00fcr softwareh\u00e4utige Netze festgelegt, so dass die Nachbearbeitungstechnik diese angemessen ber\u00fccksichtigen kann (zeitliche Antialiasing, Bewegungsunsch\u00e4rfe, etc.).\nWas Skinning und Charaktere betrifft, so hat das Team den Code so festgelegt, dass die Mesh-Kompression auf Skin-Netzen mit Morph-Zielen erm\u00f6glicht wird. Da die Gesichter sehr detailliert sind, f\u00fchrt dies zu erheblichen Speichereinsparungen und einem geringeren Rendering-Overhead. Schlie\u00dflich haben sie im Hinblick auf zuk\u00fcnftige Motorverbesserungen und Speichereinsparungen gute Fortschritte bei der Implementierung von GPU-basierten Strahlenkreuzungstests gemacht, um diese Art von Berechnungen von der CPU zu entladen und das bereits vorhandene High-Fidelity-Rendermesh auf dem GPU f\u00fcr pr\u00e4zise Kreuzungstests wiederzuverwenden. Die Ergebnisse dieser Berechnungen werden asynchron zur Verf\u00fcgung gestellt, um die CPU-Mittelframe nicht zu blockieren und k\u00f6nnen f\u00fcr jede Art von Effekt verwendet werden, der keine Serverautorit\u00e4t ben\u00f6tigt (Anti-Cheat-Ma\u00dfnahme).\nLEVEL DESIGN\nDas Level Design Team hat die Standorte f\u00fcr 3.0 poliert, wobei der Schwerpunkt auf der Fehlerbehebung f\u00fcr Levski und Oberfl\u00e4chenau\u00dfenposten lag. Als diese Arbeit abgeschlossen war, wandten sie sich der Zukunft und etwas zu, das als \"Gemeinsame Elemente\" bezeichnet wird. Dies sind Komponenten, die jeder Standort verwenden wird, wie Hangars, Garagen, Wohnungen, B\u00fcros usw., die in unser modulares System eingebunden und mit den verschiedenen Tilesets kombiniert werden. Das Team wird in k\u00fcrzester Zeit in der Lage sein, damit wesentliche Komponenten an den Standorten hinzuzuf\u00fcgen. Sie untersuchten auch Bahnh\u00f6fe und Einschienenbahnen f\u00fcr unsere Flaggschiff-Landezonen sowie fr\u00fche Arbeiten an st\u00e4dtischen Raumh\u00e4fen.\nVFX\nDas DE VFX-Team arbeitete an Partikeln und VFX, die im gesamten Universum eingesetzt werden. Sie haben fast jeden bestehenden visuellen Effekt noch einmal \u00fcberpr\u00fcft, um sicherzustellen, dass es keine Probleme gibt. Eine der j\u00fcngsten Herausforderungen war es, auf dem neuesten Stand der Physik f\u00fcr Partikel zu bleiben. Bei einem so aktiven Entwicklungszyklus m\u00fcssen manchmal Dinge, die bisher funktioniert haben, an die aktualisierten Systeme angepasst werden. Sie verfeinerten auch weiterhin das GPU-Partikelsystem und f\u00fcgten ihm neue Funktionen hinzu. Das Team n\u00e4hert sich dem Punkt, an dem das alte CPU-basierte System auslaufen kann und sich ausschlie\u00dflich auf den Grafikprozessor f\u00fcr die meisten Effekte auf den Ebenen und im Universum verl\u00e4sst. Sie arbeiteten auch daran, signierte Abstandsfelder auf unsere Partikeleffekte anzuwenden. Dies sind 3D-Texturen, die den Abstand zur Oberfl\u00e4che eines Objekts angeben. Mit diesen Texturen k\u00f6nnen sie das Innere und \u00c4u\u00dfere der Geometrie rekonstruieren und die Bewegung der vom SDF betroffenen Partikel erzeugen. Es kann sowohl zur Kollisionserkennung als auch zur Partikelstr\u00f6mung \u00fcber die Oberfl\u00e4che des SDF eingesetzt werden.\nSYSTEM-DESIGN\nDas System Design Team \u00fcbernahm das Verhalten der Missionsgeber, finalisierte die Implementierung und stellte sicher, dass alle Edge Cases dem Design entsprachen. Der erste Fall war, Miles Eckhart fertig zu stellen, damit sie die gleiche definierte Vorlage f\u00fcr zuk\u00fcnftige Missionsgeber verwenden konnten. Eine weitere damit verbundene Aufgabe war es, das Verhalten der Administratoren zu implementieren und in das Missionssystem zu integrieren. Die Hauptaufgabe des Administrators besteht darin, dem Spieler Missionselemente zu liefern und Lieferungen von eingehenden Missionselementen anzunehmen. Der Kampf gegen die FPS KI wurde erheblich verbessert, da das Systemdesignteam mit der KI zusammenarbeitete, um sicherzustellen, dass die Charaktere in das Deckungsgebiet eintreten, es verlassen, es ansehen und aus dem Deckungsgebiet schie\u00dfen und dass ihr Verhalten so nat\u00fcrlich wie m\u00f6glich aussieht. Sie befassten sich auch mit Bugs und optimierten Dingen, die f\u00fcr 3.0 erforderlich waren, wobei der Schwerpunkt auf KI, Benutzerfreundlichkeit, T\u00fcren, R\u00e4umen und Atmung lag.\nUMWELTKUNST\nDas Umweltteam hat Bereiche poliert, die in 3.0 verwendet werden, um sicherzustellen, dass die Spieler das bestm\u00f6gliche visuelle Erlebnis erhalten und keine visuellen Fehler entdecken. Neben dem Polieren konzentrierte sich das Team auf das, was nach 3.0 kommen wird. Ein Blick auf diese Arbeiten nach 3.0 wurde w\u00e4hrend der CitizenCon-Demo gezeigt und ist nur ein kleines Beispiel daf\u00fcr, was letztendlich auf Hurston passieren wird. Es wird an einer ganz neuen Reihe von \u00d6kosystemen gearbeitet, die sich optisch stark von dem unterscheiden, was bisher gesehen wurde. Sie waren auch hart bei der Arbeit an einzigartiger Vegetation, gro\u00dfen M\u00fcllmesas und der Stadt Lorville, die eine weitere gro\u00dfe Landezone mit prozeduraler Stadttechnologie ist.\nTECH ART\nDas DE Tech Art Team verbrachte den Monat damit, sich mit der Erstellung von Inhalten, der Entwicklung neuer Tools und der Unterst\u00fctzung verschiedener Teams zu befassen und sich gleichzeitig mit Themen f\u00fcr 3.0 zu befassen. Sie haben ein neues Usable f\u00fcr KI- und Player-Charaktere hinzugef\u00fcgt und Fehler f\u00fcr bestehende Usables behoben, wie z.B. kleines Animationspausen. F\u00fcr Charaktere \u00fcbernahmen sie verschiedene Skinning-Aufgaben, die sowohl f\u00fcr die PU als auch f\u00fcr die Staffel 42 verwendet werden, die bei Charaktervarianten helfen werden. Sie entwickelten ein Tool, das K\u00fcnstlern helfen kann, animierte Geometrie effizienter in die Engine zu exportieren. Dieses Tool kombiniert mehrere manuelle Prozesse in einem und Fehlerpr\u00fcfungen vor dem Export, wodurch der Prozess viel schneller und weniger anf\u00e4llig f\u00fcr menschliche Fehler wird. F\u00fcr Waffen finalisierten sie das Setup f\u00fcr die Gemini R97 Schrotflinte und bereiteten den Torral Aggregate Kahix Raketenwerfer f\u00fcr die Produktion vor. Das Tech Art Team wuchs ebenfalls um ein Mitglied und es wurde Zeit damit verbracht, ihn mit dem Toolset, dem Workflow und den Best Practices vertraut zu machen. Sein Fokus liegt auf der Verbesserung und Erweiterung unseres internen Charakter-Editors sowie der Verbesserung unserer bestehenden Systeme f\u00fcr Stoff-, Haarsimulationen und \u00e4hnliche physikalisch basierte sekund\u00e4re Animationseffekte auf alle Charaktere.\nKI\nDas KI-Team teilt seine Aufmerksamkeit auf verschiedene Funktionen im Spiel und legt gleichzeitig die Messlatte f\u00fcr zahlreiche Aspekte h\u00f6her. In Bezug auf Subsumption arbeiteten sie an der Verbesserung der Funktionen im Zusammenhang mit der Benutzerfreundlichkeit des Tools und stellten dem Designteam neue Funktionalit\u00e4ten zur Verf\u00fcgung. Absichtsgespr\u00e4che erm\u00f6glichen es Designern nun, mehrere Eingabeparameter und nicht nur die Eingabeteilnehmer anzugeben. Dies erm\u00f6glicht die Schaffung einer komplexeren Abstraktion der Logik und einer komplexeren Verzweigung der Konversation. Sie f\u00fchrten auch zwei neue Unterordnungsfunktionalit\u00e4ten ein - die Unterst\u00fctzung von Ereignisparametern und Trackview-Szenen. Ereignisparameter vereinfachen die Logik, indem sie Subparameter f\u00fcr jedes Ereignis freigeben, was es Designern oder Programmierern erm\u00f6glicht, komplexere Logik mit Ereignissen zu erstellen, um mehr Informationen \u00fcber verschiedene Akteure hinweg zu \u00fcbertragen. Der Trackview-Support fordert die Ausf\u00fchrung von Trackview-Szenen bei Bedarf an und ist an die Konversationslogik gebunden, die die alternative Option erm\u00f6glicht, Szenen mit Trackview zu erstellen, um die besten visuellen Ergebnisse zu erzielen, aber dennoch die Subsumptionslogik reagieren oder bei Bedarf \u00fcbernehmen kann.\nDas Team hat auch weiterhin die Art und Weise, wie die KI verschiedene Fahrzeuge steuert, \u00fcberarbeitet. In Zukunft wird das Verhalten nicht mehr auf den Raumschiffen selbst ablaufen, sondern die verschiedenen Sitzbetreiber werden die verschiedenen Gegenst\u00e4nde, die sie auf einem bestimmten Schiff haben, steuern und das entsprechende Verhalten haben. Unterschiedliche Bedienerf\u00e4higkeiten k\u00f6nnen nun direkt auf die verschiedenen Aktionen Einfluss nehmen, und Fahrzeuge wie Mehrmannschiffe k\u00f6nnen von den verschiedenen NSCs profitieren, die die verschiedenen Sitze bedienen. Sie arbeiteten auch an bemannten und automatisierten Gesch\u00fctzt\u00fcrmen. Beide dieser m\u00f6glichen Controller k\u00fcmmern sich um die Ausf\u00fchrung aller erforderlichen Operationen, um die Gesch\u00fctzt\u00fcrme einzuschalten, ihre Funktionalit\u00e4ten zu aktivieren, nach Zielen mit dem Radar zu suchen, vorherzusagen, wo geschossen werden soll und so weiter. Die Arbeit an der KI des NSC zu Fu\u00df konzentrierte sich haupts\u00e4chlich auf den menschlichen Kampf, das Polieren der verschiedenen Ein- und Ausg\u00e4nge, um in die Deckung zu gelangen, und die verschiedenen Aktionen, die w\u00e4hrend der Deckung durchgef\u00fchrt werden k\u00f6nnen (Schauen, Schie\u00dfen von verschiedenen Seiten der Deckung, \u00c4ndern der K\u00f6rperrichtung und so weiter).\nWas die anderen Systeme betrifft, so wurde eine Vielzahl von Korrekturen und Verbesserungen in das Missionssystem aufgenommen, die alle von den Designern f\u00fcr die aktuellen Missionen geforderten Funktionalit\u00e4ten bieten. Der Spawning Manager erhielt viele Optimierungen und neue Verbesserungen, insbesondere bei der Umweltvalidierung, um Elemente korrekt und sicher im Raum und am Boden zu spawnen.\nTURBULENT\n\nEine neue Version von Spectrum, ein wichtiger Meilenstein f\u00fcr den Launcher und zus\u00e4tzliche Unterst\u00fctzung f\u00fcr den 3.0-Start hielten Turbulent f\u00fcr den Monat sehr besch\u00e4ftigt. Hier ist, woran wir gearbeitet haben:\nSPEZTRUM\nDie Ver\u00f6ffentlichung von Spectrum 3.7.1 bestand aus Bugfixes, Verbesserungen der Lebensqualit\u00e4t und nicht wahrnehmbaren \u00c4nderungen, um die langfristige Entwicklung und Wartung zu gew\u00e4hrleisten. Lassen Sie uns zuerst \u00fcber letzteres sprechen.\nDas Team verbessert die Codebasis und den Freigabeprozess, so dass die Einf\u00fchrung neuer Versionen so weit wie m\u00f6glich ein reibungsloser Prozess bleibt. Spectrum hat auch ein neues Versionierungsschema eingef\u00fchrt, um den Umfang eines Releases besser zu kommunizieren, und dann viele interne Abh\u00e4ngigkeiten aktualisiert, um m\u00f6gliche zuk\u00fcnftige \u00c4nderungen zu vermeiden. Es gibt auch Diskussionen \u00fcber Bumping React auf die neueste Version sowie die Migration der Codebasis nach TypeScript. Diese \u00c4nderungen w\u00fcrden es uns erm\u00f6glichen, mehr Bugs zu fangen, bevor wir in die Produktion gehen, und Teile des Projekts zu refaktorieren, ohne die Stabilit\u00e4t zu beeintr\u00e4chtigen.\nAu\u00dferdem hat sich das Team zum Ziel gesetzt, die Handhabung von \u00c4nderungsanfragen zu verbessern, Priorit\u00e4ten aus verschiedenen Quellen (Jira, Issue Council, Foren, interne Kommunikation usw.) besser zu verwalten und den Fortschritt besser zu verfolgen\/zu kommunizieren.\nSchlie\u00dflich finden Sie hier eine Zusammenfassung der letzten \u00c4nderungen an der Anwendung: * Behebt mehrere Probleme f\u00fcr Benutzer von Android-Ger\u00e4ten, bei denen die Eingabe von Text zu unvorhersehbaren Ergebnissen f\u00fchren w\u00fcrde. Spectrum schl\u00e4gt nun eine Liste von Erw\u00e4hnungen vor, die auf den Autoren der letzten Nachrichten in einer Lobby basieren, wenn Sie '@' eingeben. Eingebettete Twitch-Clips werden nicht mehr automatisch abgespielt. Bei den Custom Emojis und Custom Roles wurden erhebliche Fortschritte erzielt, und es besteht die Hoffnung, dass die f\u00fcr 3.8. erforderlichen Fortschritte erzielt werden.\nLAUNCHER\nDie Tests des Launcher starteten im Oktober mit der Freigabe des RSI Launcher 1.0.0-alpha.20 an Evocati zum Testen. Dies ist die erste Exposition, die \u00f6ffentliche Anwender mit dem Delta Patcher hatten.\nDie Benutzer waren sehr zufrieden mit dem Delta-Patcher, da einige Patches nur 100 Megabyte gro\u00df sind! Ziemlich dramatische Reduzierung der Patch-Gr\u00f6\u00dfen im Vergleich zur vorherigen Technologie, die f\u00fcr den Einsatz von Star Citizen Alpha 2.6 und darunter verwendet wurde.\n\nMit Hilfe der gro\u00dfen Evocati konnte das Team eine Vielzahl von Benutzer-Setups, Hardware-Konfigurationen, Windows-Versionen und pers\u00f6nlichen Benutzerpr\u00e4ferenzen kennenlernen, die sich auf die Funktion und Bedienung des Launcher auswirken. Die meisten der folgenden Wochen wurden damit verbracht, \u00fcber die in dieser Phase gefundenen Probleme nachzudenken und Fehler zu beheben, die sich auf das Patching und das Gameplay auswirken. Vor allem Probleme im Zusammenhang mit Windows N und Dateiberechtigungen haben viel Zeit in Anspruch genommen, um dies herauszufinden. Wie immer war der Issue Council unser gr\u00f6\u00dfter Verb\u00fcndeter, um die Fehler zu \u00fcberpr\u00fcfen, zu verifizieren und zu \u00fcberpr\u00fcfen, bevor sie in Angriff genommen werden.\n\nDie Anwendung wird nun Spielabst\u00fcrze und Anwendungsfehler ordnungsgem\u00e4\u00df einschlie\u00dfen. Der Polling-Mechanismus der Spielebibliothek wurde auf einen realen Fall abgestimmt, bei dem viele Benutzer nach Updates suchen. Die Anwendung repariert nun ordnungsgem\u00e4\u00df die Berechtigungen in der Spielebibliothek, wenn ein Berechtigungsfehler festgestellt wird. W\u00e4hrend eines \"Verify Files\" sucht der Launcher auch nach einem Update! Das Soundsystem wurde erweitert, um ein besseres Klangerlebnis im Launcher zu erm\u00f6glichen. Lautst\u00e4rkeregler! Es wurden 5 neue Hintergrundmusik-Tracks aus dem SC-Soundtrack hinzugef\u00fcgt! F\u00fcr 1.0.0.0 des Launcher bleibt nur noch ein Hauptpunkt \u00fcbrig - die spezifische Handhabung des initialen Downloads, was ein Problem mit dem neuen objektbasierten Delta Patcher darstellt. Ein Spielbau besteht aus vielen Dateien (ab 300k-400k), von denen viele kleinere Dateien sind. Wenn Sie derzeit von Grund auf neu patchen, holt Ihr Launcher alle diese Dateien. Dieser Prozess ist nicht nur sehr ineffizient, sondern auch langsam und fehleranf\u00e4llig. Das Team arbeitet derzeit daran, dies zu l\u00f6sen, indem es die Verteilung eines \"Kick Start\"-Pakets erm\u00f6glicht, das alle kleinen Dateien und die Basis-Assets enth\u00e4lt, um das Spiel minimal zu starten. Dieses Basispaket kann dann zuerst mit einem Multithreaded Range Downloader abgerufen werden, wenn Sie keine Packdateien auf der Festplatte haben. Sobald das Kick-Start-Paket heruntergeladen wurde, kann ein normaler Delta-Patch angewendet werden, um Sie auf die neueste Version zu bringen.\nDas Team plant, die Basis-Pack-Datei pro kleinerer Version (Semver) des Spiels zu verfolgen, was es immer frisch und schnell h\u00e4lt.\nSie sind begeistert, dies in Ihre H\u00e4nde zu bekommen, da sie glauben, dass dies die Onboarding- und Update-Erfahrung von Star Citizen erheblich verbessert.\nJUBIL\u00c4UMSVERKAUF\nIn diesem Monat hat das Turbulent Team den Jubil\u00e4umsverkauf 2017 ins Leben gerufen. Der Verkauf enth\u00fcllte zwei Konzeptschiffe: die Anvil Hawk, ein kleines, leichtes Jagdflugzeug mit Schwerpunkt Waffen, und die Aegis Hammerhead, ein beeindruckendes Patrouillenschiff mit mehreren T\u00fcrmen zur Bek\u00e4mpfung von K\u00e4mpfern. Diese beiden Konzeptschiffe waren nur der Anfang, da sie jeden Tag die Chance hatten, sich einige Ihrer Lieblingsschiffe zu schnappen, einschlie\u00dflich einer begrenzten Anzahl von Idris und Speerwurf.\nZusammen mit diesem Verkauf hat das Team den Observer-Test erstellt, der Ihre Chance war, Ihr Wissen \u00fcber All-Star-B\u00fcrgerschiffe zu testen. Der Test erwies sich f\u00fcr unsere eingefleischten Fans als zu einfach, aber es war trotzdem toll, die Community mit ihren goldenen Abzeichen auf dem Spektrum zu sehen.\nWEBSITE-REDESIGN\nDas Team freut sich, eine neue Website mit dem Live-Release 3.0 zu pr\u00e4sentieren. Das Design- und Entwicklungsteam hat hart daran gearbeitet, offene Fragen zu kl\u00e4ren und freut sich sehr, die neuen Designs zu ver\u00f6ffentlichen und weiterhin auf der neuen und verbesserten Plattform aufzubauen.\nZus\u00e4tzlich zum Re-Design nutzen sie die Gelegenheit, eine neue Produktions-Roadmap hinzuzuf\u00fcgen. Sein Zweck ist es, dass Sie, die Community, die Funktionen, die f\u00fcr Sie wichtig sind, besser verfolgen k\u00f6nnen. Dies wird sich erheblich von unserer Textversion des Produktionsplans unterscheiden. Community\n\nDie zweite Jahresh\u00e4lfte ist traditionell eine arbeitsreiche Zeit f\u00fcr alles, was Star Citizen zu bieten hat, und dieses Jahr war keine Ausnahme. Seit dem letzten Bericht im September ist viel passiert, wobei die CitizenCon 2947 sicherlich das Highlight auf Gemeindeebene ist.\nFast 1000 B\u00fcrger versammelten sich in Frankfurt, um neue Welten zu erkunden, die neuesten Technologien zu erleben, sich zu treffen und mit den Entwicklern ihrer Lieblings-Space-Sim zu sprechen. W\u00e4hrend der Messe pr\u00e4sentierte Intel seine neue Optane 9 SSD und damit den brandneuen Sabre Raven. Das Team enth\u00fcllte auch unseren kapitalgro\u00dfen Consolidated Outland Pioneer und damit den neuen Gameplay-Mechanismus, mit dem Sie Ihren Anspruch sichern und Au\u00dfenposten bauen k\u00f6nnen.\nEin weiteres Highlight in diesem Monat war die Freigabe von Alpha 3.0 an die Evocati und schlie\u00dflich an die PTU. Nachdem wir die verbleibenden Probleme und Fehler abgebrannt hatten, haben wir unser letztes Update f\u00fcr eine ausgew\u00e4hlte Gruppe von Testern ver\u00f6ffentlicht, die uns geholfen haben, die Knicke von 3.0 zu beseitigen, um es einem noch breiteren Publikum, dem Public Test Universe, zug\u00e4nglich zu machen.\nDas Team macht weiterhin kontinuierliche Fortschritte bei Alpha 3.0, indem es neue Builds mit unserem Delta-Patcher ver\u00f6ffentlicht und die erzielten Verbesserungen \u00fcberpr\u00fcft. Mit der PTU in den H\u00e4nden der Community, sind die Entwickler nicht nur dabei, Features zu polieren, sondern auch die Fehler zu beheben, die dank dieser erweiterten Gruppe auftreten.\nJeder hier m\u00f6chte sich bei allen unseren Testern bedanken, die dazu beigetragen haben, dies mit Stresstests w\u00e4hrend der gottlosen Stunden und unz\u00e4hligen Fehlerberichten zu erm\u00f6glichen. Testen Sie weiter und bleiben Sie fantastisch!\nAls besonderen Jubil\u00e4umsvorteil hatten unsere Abonnenten im Oktober das Vergn\u00fcgen, f\u00fcnf Schiffe auf Tour zu nehmen, n\u00e4mlich die Constellation Andromeda, Aurora MR, Freelancer, Hornet F7C und 300i. Derzeit genie\u00dfen sie die MISC Starfarer & Origin M50 als die beiden Schiffe des Monats. Im November stand im Rathaus der Senior Systems Designer Will Maiden, Lead Gameplay Engineer Chad McKinney und Associate Gameplay Engineer Spencer Johnson, als sie Ihre Fragen zu Ladung und Transport beantworteten. Wenn du die Show verpasst hast, schau sie dir auf Youtube mit all unseren anderen Shows an; von Citizens of the Stars und Bugsmashers bis hin zu Newcomern wie Xi'an Sprachunterricht mit Britton Watkins. Wenn also Ihre Antwort auf eine \".ath.u m.uexy.oa?\" immer noch ein \"e yo nai\" ist, sollten Sie vielleicht aufholen.\nLetzte Woche startete das Jubil\u00e4ums-Special mit acht Episoden von ATV, in denen jeweils ein Schiffshersteller vorgestellt wurde. Er begr\u00fc\u00dfte auch einige neue Erg\u00e4nzungen: Anvil Aerospace's Hawk, ein leichter K\u00e4mpfer mit einem vielf\u00e4ltigen Waffenarsenal und die Aegis Hammerhead, ein schnelles und leichtes Kriegsschiff.\nUm den Bericht dieses Monats abzuschlie\u00dfen, hier ein Blick auf das, was als n\u00e4chstes kommt.\nLassen Sie Ihre Stimme z\u00e4hlen! Nehmen Sie an unserem kommenden Live-Stream teil (12\/1 um 12.00 Uhr PST) und helfen Sie uns, uns f\u00fcr ein Drake-Schiff zu entscheiden, das Star Citizen hinzugef\u00fcgt werden soll. Wenn du es noch nicht getan hast, schau dir auch die neuen Episoden der Galactic Tour und die R\u00fcckkehr von Ship Shape an, die in unseren ATV Jubil\u00e4ums-Specials vorgestellt werden. Wir verabschieden uns von 2947 mit unserem Holiday Livestream, wo wir uns auf die Staffel 42 konzentrieren und unsere Roadmap zur Fertigstellung teilen werden.\nBis dahin sehen wir uns in der Strophe! WIR SEHEN UNS N\u00c4CHSTEN MONAT..... Gr\u00fc\u00dfe B\u00fcrger!\n\nWillkommen zum monatlichen Studio-Report, wo wir Updates von unseren verschiedenen Studios auf der ganzen Welt sammeln, um Ihnen zu zeigen, woran sie im letzten Monat gearbeitet haben. Wie viele von euch wissen, gab es einen gemeinsamen Ansto\u00df zwischen unseren verschiedenen Studios, den Alpha 3.0 in die Community zu bringen. Seit unserem letzten Bericht sind wir zu Evocati gegangen und haben eine gestaffelte Freigabe f\u00fcr die PTU begonnen, so dass die besch\u00e4ftigten Fehler des Teams, die von den Testern entdeckt wurden, behoben wurden und an der Gesamtstabilit\u00e4t und Leistung gearbeitet wurde. Damit kommen wir zur Sache. WOLKENIMPERIUM: LOS ANGELES\nMASCHINENBAU\nLA Engineering rast in rasantem Tempo auf 3.0 zu, wobei der Schwerpunkt auf der Behebung von Fehlern von Evocati und PTU liegt und die Verfeinerung von Features wie Ladung, Artikelkomponenten, Atmosph\u00e4rensystemen und mehr. Teil dieser Arbeit war die Integration aller Itemsysteme in Schiffen mit Benutzeroberfl\u00e4che, um ein echtes Gef\u00fchl der Kontrolle in die Cockpits zu bringen. Schlie\u00dflich steht seit einigen Wochen die Aktualisierung von Quantum Travel im Mittelpunkt und dr\u00e4ngt darauf, ein immer intensiveres Erlebnis zu bieten.\nTECH DESIGN\nDiesen Monat verbrachte LA Tech Design den gr\u00f6\u00dften Teil seiner Zeit damit, Aufgaben zu schlie\u00dfen und die restlichen Fehler f\u00fcr das Item 2.0 Ship Setup auszuschalten. Sie haben mehrere Probleme mit der 300er Serie, Mustang, Nox, Starfarer und Scythe gel\u00f6st und gleichzeitig einige weitere Abh\u00e4ngigkeiten von der endg\u00fcltigen Beleuchtungsanordnung identifiziert. Die aktualisierten Animationen f\u00fcr den Gladiator wurden diesen Monat ausgeliefert, so dass ein kompletter Setup-Refaktor abgeschlossen ist.\nDar\u00fcber hinaus hat das Team auch die Einrichtung aller Schiffsscheinwerfer sowie die \"SaveGameLogOut\"-Funktionalit\u00e4t abgeschlossen, mit der man sich \u00fcberall dort ausloggen kann, wo es ein Bett gibt.\nKUNST\nIm November dieses Jahres verbrachte das Charakter-Team viel Zeit damit, die Besetzung der Staffel 42 zu polieren. Sie haben auch viele neue Star Citizen-Charaktere und Assets poliert, die sie mit 3.0.0.0 ver\u00f6ffentlichen wollen, w\u00e4hrend sie an der Entwicklung von Konzepten f\u00fcr Kleidung, der Fertigstellung der alten R\u00fcstungssets und vielem mehr arbeiten.\nDas LA Ship Art Team hat einen Gro\u00dfteil des Monats November damit verbracht, viele Schiffe zu aktualisieren, um die Vorteile der neuen Technologie zu nutzen. Insbesondere verwenden die Schiffe nun eine neue Lichtgruppenanordnung, eine neue Nebeltechnologie, neue Render-to-Texture-Siebe und die M\u00f6glichkeit, Proxies luftdicht zu machen, nachdem Star Citizen mit Sauerstoff versorgt wurde. Sie haben diese verschiedenen Aufgaben mit der Behebung vieler Kunstfehler in Vorbereitung auf Schiffe, die in der Alpha 3.0-Version enthalten sind, verglichen. Dar\u00fcber hinaus haben sie Fortschritte bei der Entwicklung zuk\u00fcnftiger Releases gemacht, einschlie\u00dflich des Anvil Hurricane, Tumbril Cyclone und des Consolidated Outland Mustang Updates.\n\nNARRATIV\nZus\u00e4tzlich zur Zusammenarbeit mit dem PU-Designteam beim Polieren von Alpha 3.0-Missionsinhalten arbeitete das Narrative Team mit Hilfe der Community weiter an der Erweiterung der Xi'an-Sprache und arbeitete mit dem Cinematics-Team an der Entwicklung des Galactic Tour Hammerhead St\u00fcckes. F\u00fcr die Staffel 42 verbrachten sie Zeit damit, zus\u00e4tzliche B\u00fchnendekorationen mit dem Requisiten- und Kunstteam zu besprechen, um das Erz\u00e4hlen von Umweltgeschichten im Spiel weiter auszubauen. Mit Blick auf die Zukunft verbrachte das Team auch diesen Monat Zeit damit, die Ziele f\u00fcr narrative Inhalte f\u00fcr die viertelj\u00e4hrlichen Updates 2018 weiter zu planen.\nTECH INHALT\nF\u00fcr Umgebungen hat das Global Technical Content Team die Arbeit an den Features fortgesetzt, die bei der GamesCom Procedural Tech Demo enth\u00fcllt wurden. Zus\u00e4tzlich zur Unterst\u00fctzung von Verbesserungen der Anlagen- und Code-Performance haben sie Fehler bei der Beleuchtung und den Visabereichen untersucht und Seite an Seite mit dem Grafikteam an der Entwicklung von Skripten und Shader-Technologie gearbeitet, um Performance-Probleme zu erkennen und andere Bereiche wie die Prozessst\u00e4dte zu verbessern. Sie haben auch in Zusammenarbeit mit unserem Tech-Animationsteam an animierten Umgebungsressourcen sowie an der Entwicklung und Konstruktion neuer Technologien f\u00fcr Verwahrlosungssysteme, Au\u00dfenpostenstandorte und Planetenplatzierungssysteme gearbeitet.\nF\u00fcr Schiffe war das Team damit besch\u00e4ftigt, die Schadensimplementierung f\u00fcr die neuen Schiffe zu \u00fcbernehmen, die f\u00fcr das Release 3.0 die Pipeline herunterkommen. All dies beim Jonglieren mit einer Vielzahl von Schiffsfehlern im Zusammenhang mit UV2-Sch\u00e4den, Fahrwerkskompressionen, Visabereichen und Protokollspamfehlern. Es wurden Fortschritte bei der Unterst\u00fctzung von Gaseffekten f\u00fcr die eingehende Brechfunktion erzielt. Sie haben auch Tech Design und die Ship Art Teams mit neuer Technologie f\u00fcr Schiffsbeleuchtung und Schiffsproxies unterst\u00fctzt. An der Waffenfront hat das Team weiterhin an neuen Waffen in der Pipeline gearbeitet, einschlie\u00dflich der Arbeit an Mannequin-Setups, Waffenk\u00e4fern, einem verstellbaren Schaft und einigen spannenden F&E-Arbeiten an animierten Waffenanbauten, die \u00fcber die reine Waffe hinaus viele zus\u00e4tzliche Einsatzm\u00f6glichkeiten haben werden.\nEine Menge Arbeit f\u00fcr die Tech Animators war die Unterst\u00fctzung der Staffel 42, die neue Kost\u00fcme, die die Character & Heads Pipeline hinunterkommen, manipuliert und simuliert. Wie bei den anderen Schwerpunktbereichen wurde viel Zeit mit der Behebung von Fehlern verbracht, haupts\u00e4chlich im Zusammenhang mit dem Skinning und der Implementierung von Charakterelementen.\nDas Team hat auch gro\u00dfe Fortschritte beim Tracking, Trimmen und L\u00f6sen einer gro\u00dfen Menge von MoCap-Daten f\u00fcr Staffel 42 gemacht. Die Liste der Errungenschaften rundet sich gut ab mit der Implementierung neuer Gesundheitschecks, einem CIG Tools Installer, Tools Management \/ Migration und einer Menge Unterst\u00fctzung f\u00fcr Gesichtsanimationen, Usables, Wildlines und Cinematics.\nSchlie\u00dflich gab es eine Menge verschiedene Unterst\u00fctzung, die das Team in die H\u00e4nde bekam, darunter die technische Leitung f\u00fcr WAF Asset Builds (die die Buildzeiten deutlich verk\u00fcrzen!), Website-Entwicklung, F&E und einige Sorgfaltspflichten bei einem zuk\u00fcnftigen Upgrade auf unsere internen DCC-Tools Max und Maya und MoBu.\nQUALIT\u00c4TSSICHERUNG\nLAQAs Hauptaugenmerk lag auf dem Testen der Beleuchtung und der neuen Lichtgruppen, LOD's, verletzender Mechanik, Charakterkunst, der Vielzahl neuer Aktualisierungen der Codebasis durch das Engineering-Team und der Art und Weise, wie Item Ports von Tech Design eingerichtet wurden. Sie unterst\u00fctzten das globale QS-Team auch bei der Ver\u00f6ffentlichung von \u00dcberpr\u00fcfungen f\u00fcr PTU- und Evocati-Implementierungen und bei mehreren internen Live-Gameplay-Reviews.\nWOLKENIMPERIUM: AUSTIN\nDESIGN\nDas ATX-Designteam hat sich mit allen Dingen des Einkaufens besch\u00e4ftigt, um das Spiel f\u00fcr das PTU-Release des 3.0 Build vorzubereiten. Es gibt zwei Kernelemente, auf die wir uns konzentriert haben, seit die Implementierungsaufgaben der Mission Giver an das Designteam in Frankfurt \u00fcbergeben wurden. Das Team skizzierte auch die gew\u00fcnschten Ziele f\u00fcr das Stundeneinkommen und hat sowohl den Missions-Belohnungsrechner als auch die Artikelpreise entsprechend angepasst. Diese Arbeit beinhaltet auch die Zeit und die Preise f\u00fcr die Wiederbelebungszeit des Schiffes. Obwohl wir erwarten, dass wir diese Werte in den n\u00e4chsten paar Alpha-Builds auf der Grundlage von Spielerfeedback und Analysen, die wir sammeln, einlesen werden, sind wir der Meinung, dass dies eine gute Darstellung dessen ist, wo wir es haben wollen.\nUnterdessen r\u00e4umte der Rest des Teams alle physischen Gesch\u00e4fte an den drei gro\u00dfen Standorten auf: Port Olisar, Grim HEX und Levski. Insgesamt gibt es etwa f\u00fcnfzehn verschiedene Orte, an denen Spieler Gegenst\u00e4nde im Spiel kaufen k\u00f6nnen, und wir konnten die Gegenst\u00e4nde mit sehr geringer \u00dcberschneidung auf die verschiedenen Gesch\u00e4fte verteilen. Das Team arbeitete auch mit den LA Programmers und dem UI-Team zusammen, um einige neue Funktionen f\u00fcr das Einkaufserlebnis hinzuzuf\u00fcgen. Zu diesen neuen Funktionen geh\u00f6ren: AR-Marker wurden nun durch das neue Item-Highlighting-System ersetzt, um dem gesamten Loot-System gerecht zu werden. Inner Thought wird nun auf die Objekte angewendet, wenn es um Anproben, Pr\u00fcfen oder Kaufen geht. R\u00fcstung kann jetzt als separate Teile gekauft werden. Alle Item-Namen sind jetzt eindeutig Erster Pass der Ladenbesitzer ist jetzt in. Die Einkaufsoberfl\u00e4che wurde bereinigt. Obwohl es noch viele neue Funktionen gibt, die sie hinzuf\u00fcgen oder bestehende, die sie bereinigen m\u00f6chten, hofft das Team, dass das neue Einkaufserlebnis alle Spieler gl\u00fccklich macht, und sie freuen sich darauf, die Verbesserung des Einkaufserlebnisses im neuen Jahr fortzusetzen.\nKUNST\nDas Schiffsteam schlug 3.0 Bugs f\u00fcr den Drake Herald und Cutlass Black aus, einschlie\u00dflich der Reparatur ihrer Beleuchtungszust\u00e4nde und Visareas. Sie haben auch die Whitebox-Modellierung und einen ersten Durchgang bei der Innenbeleuchtung des Sternbildes Phoenix abgeschlossen, so dass es jetzt im Spiel ist und man es durchgehen kann. In weiteren Nachrichten von Constellation haben die Andromeda und Aquila ihren Innen- und Au\u00dfenbeleuchtungszustand aktualisiert und ihre LODs wurden \u00fcberarbeitet, um viel effizienter zu sein. Mehrere andere Schiffe durchliefen \u00e4hnliche Aktualisierungen, darunter die Hornet (F7C, F7CM), 300i (und Varianten), M50, Scout und Nox. Das Team setzte seine Arbeit mit dem Polieren und Optimieren der Materialien auf allen ATX-Schiffen fort. Auch am Whitebox-Modellierungsprozess des Anvil F8 Lightning wurde gearbeitet.\nBACKEND-SERVICES\nDas Server-Engineering-Team konzentrierte sich auf die Unterst\u00fctzung bei Funktionen und Problemen in 3.0. Das Team hat Teile der Backend-Services auf die Datenmenge abgestimmt, die zwischen Spielservern, Persistenz-Caches und der Datenbank flie\u00dft, und mehrere Probleme gel\u00f6st, darunter die M\u00f6glichkeit, sich wieder mit derselben Instanz zu verbinden, wenn Sie Ihre Netzwerkverbindung verlieren. Im Laufe des Monats verbesserten sie auch die Datenintegrit\u00e4t, wenn ein Server oder Dienst ausfallen w\u00fcrde, verbesserten die Funktionalit\u00e4t der Caching-Dienste, damit Elemente im Universum au\u00dferhalb des Besitzes des Spielers existieren konnten, und beendeten schlie\u00dflich viele Login- und Verbindungsprobleme.\nMit Blick auf die Zukunft hat das Engineering-Team die n\u00e4chste Generation von Backend-Services aufgebaut. Das Team strebt danach, alle gr\u00f6\u00dferen Dienste in kleinere zustandslose Dienste aufzuteilen und die Service-Architektur und die Skriptsprache Ooz zu verbessern, um den st\u00e4ndig wachsenden Anforderungen des Spiels gerecht zu werden.\nANIMATION\nIn diesem Monat hat das Ship Animation Team die Feinabstimmung des Spielerbettes als Teil unseres best\u00e4ndigen Sicherheitssystems vorgenommen, das es dem Spieler erm\u00f6glicht, ein Bett zu betreten und das Spiel zu verlassen, w\u00e4hrend er seinen Standort im Universum speichert. Wenn du das n\u00e4chste Mal das Spiel l\u00e4dst, wachst du in deinem Bett auf, mit deinem Schiff an seinem letzten Platz. Dar\u00fcber hinaus hat das Team die Aktualisierung der Gladiator Ein- und Ausg\u00e4nge im Rahmen des Cockpit Experience Sprints abgeschlossen. Die Geschwindigkeit und der technische Aufbau des Gladiators haben die Zeit zum Ein- und Aussteigen aus den Piloten- und Copilotsitzen erheblich verk\u00fcrzt. Das Austin-Studio veranstaltete auch ein Motion-Capture-Shooting, um Animationen f\u00fcr den Tumbril-Zyklon aufzunehmen.\nIn der Zwischenzeit half das PU-Animationsteam bei der Unterst\u00fctzung der Arbeit an Staffel 42 und arbeitete eng mit Design zusammen, um alle Benutzeroberfl\u00e4chen voll funktionsf\u00e4hig und fehlerfrei zu machen. Einige der Herausforderungen, denen sich das Team stellte, waren die Synchronisation von Requisiten zur Animation mit Charakteren, wie z.B. St\u00fchle, die beim Hinsetzen eines Charakters rutschen und eine weibliche Version jeder Animation in das Spiel integrieren. Das Ziel ist es, eine gro\u00dfe Menge der verwendbaren Animationsressourcen bis Ende des Jahres zu polieren und fertigzustellen.\nBETRIEB\nDas DevOps-Team arbeitete rund um die Uhr, um unsere internen Teams und die Evocati bei der Erreichung unserer 3,0-Tore zu unterst\u00fctzen. Neben der Ver\u00f6ffentlichung von mindestens einer Spielversion pro Tag konnten sie einige wichtige interne Projekte abschlie\u00dfen, die darauf abzielen, die Buildzeiten und die Fehlerbehandlung massiv zu verbessern.\nATX QA\nSeit CitizenCon ist 3.0 ein allumfassender Fokus f\u00fcr das QS-Team, da inkrementelle Updates f\u00fcr Evocati und die erste Welle der PTU ver\u00f6ffentlicht wurden. Zwischen Evocati und der PTU wurden bisher 26 Builds unter Austins G\u00fcrtel f\u00fcr 3.0 und 2 f\u00fcr unser Schwester-Team in Gro\u00dfbritannien ver\u00f6ffentlicht. QA hat mit jedem neuen Build, der an PTU geht, um sich auf Stabilit\u00e4t zu konzentrieren, neue Leistungsdaten f\u00fcr unsere Ingenieure gesammelt. Das Team arbeitete mit den LiveOpS-Kohorten zusammen, um alle verschiedenen neuen Client- und Serverabst\u00fcrze mit Metriken zusammenzustellen, um zu zeigen, welche die gr\u00f6\u00dfte Wirkung haben. Mit so vielen neuen Missionen in 3.0 und den damit verbundenen neuen Spielmechaniken stellte das Team sicher, dass sie sowohl im Idealfall als auch bei voller Kapazit\u00e4t eines Servers funktionieren. Gleichzeitig haben sie verschiedene neue Konfigurationen mit der britischen QA und den Ingenieurteams getestet, um die Spielst\u00e4rke zu erh\u00f6hen. Die Tests der Staffel 42 verliefen z\u00fcgig, wobei t\u00e4glich regelm\u00e4\u00dfige Leveltests mit neuen Builds durchgef\u00fchrt wurden.\nF\u00fcr die F\u00fchrung lag der Schwerpunkt auf der Schulung neuer Mitarbeiter und der st\u00e4ndigen Kommunikation mit den anderen Abteilungen, dem Gespr\u00e4ch mit der Produktion, um sicherzustellen, dass die richtigen Fehler f\u00fcr PTU- und Live-Triagings auf dem Radar sind, der Teilnahme an Stehaktionen mit den Entwicklungsteams, um herauszufinden, was aus den Sprints getestet werden muss, und der t\u00e4glichen Zusammenarbeit mit dem Player Relations and Issue Council, um \u00fcber das neueste Feedback und die Berichte der Geldgeber auf dem Laufenden zu bleiben. All diese verschiedenen M\u00f6glichkeiten kombiniert, um sicherzustellen, dass die Qualit\u00e4tssicherung im gesamten Unternehmen einheitlich auf der gleichen Seite steht.\nSPIELERBEZIEHUNGEN\nDer Monat November hielt das Player Relations-Team auf Trab. Nachdem das Team eine ph\u00e4nomenale CitizenCon unterst\u00fctzt und moderiert hatte, half es den Geldgebern bei ihrem Interesse an unserem wegweisenden Pionier. Das Team arbeitete auch jeden Tag mit Evocati zusammen, um neue 3.0-Builds zu ver\u00f6ffentlichen, Spieltests durchzuf\u00fchren, die Stabilit\u00e4t zu bewerten und wichtiges Feedback zu erhalten. Mit dem Push zu PTU wollten sie sich bei all unseren unerbittlichen Avocados bedanken, die immer da sind, um den Anruf zu beantworten! Schlie\u00dflich wurde das Team in Austin und Frankfurt erweitert, da die Aufgabengebiete immer umfangreicher werden. Sie freuen sich darauf, unseren ersten deutschen Vollzeit-Support einzustellen und den Moderations-Support in mehreren neuen Sprachen einzuf\u00fchren.\nGIE\u00dfEREI 42: GRO\u00dfBRITANNIEN\nGRAFIK\nDas Grafikteam verbrachte seine Zeit damit, den Fehler 3.0 zu beheben. Wenn QA\/Evocati die fertigen Features und Assets in die Finger bekommt, kommt es immer wieder zu unerwarteten Problemen. Dies beinhaltete zahlreiche Probleme im Zusammenhang mit rotierenden Planeten\/Monden, da ein Gro\u00dfteil des \u00e4lteren Rendering-Codes Annahmen dar\u00fcber traf, dass die Dinge station\u00e4r sind, und vor allem nicht gut damit zurechtkommt, den Bezugsrahmen zu \u00e4ndern, wenn man sich in den Orbit hinein und heraus bewegt.\nDas Team entwickelte auch einen neuen Glas-Shader, der im Vergleich zum vorherigen eine gro\u00dfe optische Verbesserung brachte, und sie waren sehr daran interessiert, dass er so schnell wie m\u00f6glich implementiert wurde. Ein Pass wurde \u00fcber alle Schiffs\u00fcberdachungen gef\u00fchrt.\nSie schlossen auch einige kleinere Featurearbeiten f\u00fcr 3.0, wie z.B. die RTT-Funktionalit\u00e4t f\u00fcr Schiffs-MFDs und die M\u00f6glichkeit, die Belichtung der Kamera durch Spielcode zu steuern, um das mobiGlas bei hellen Lichtverh\u00e4ltnissen besser lesbar zu machen (obwohl weitere Verbesserungen f\u00fcr holographische Displays kommen). Parallel dazu setzten zwei Teammitglieder ihre l\u00e4ngerfristigen F&E-Aufgaben mit dem neuen Schild-Effekt fort, der Partikel statt Netze verwendet, und mit der Verbesserung der volumetrischen Ray-Tracing-Technologie (Gaswolken & Nebel), die sich dem Punkt n\u00e4hert, an dem sie einige ziemlich coole Visuals teilen k\u00f6nnen!\nSCHIFFE\nHammerkopf\nDer Hammerhai hat in kurzer Zeit rasante Fortschritte gemacht. Die Arbeiten an der Au\u00dfenseite wurden f\u00fcr den Auftritt der Galactic Tour priorisiert. Nach Erhalt des Konzeptnetzes hat das Team nicht nur die Formen verfolgt, sondern auch sichergestellt, dass das Netz effizient und spielbereit ist. Nun, da die Marke Aegis so gut etabliert ist, verf\u00fcgen sie \u00fcber eine F\u00fclle von Shadern und Assets, aus denen sie sich f\u00fcr eine schnelle Wiederholung bedienen k\u00f6nnen.\n600i\nDie inneren G\u00e4nge des 600i wurden vollst\u00e4ndig ausgearbeitet und sorgen daf\u00fcr, dass sie das Gef\u00fchl der h\u00f6heren Klasse, n\u00e4mlich Origin, einfangen. Weitere Arbeiten wurden mit dem Erkundungsmodul sowie der Weitergabe von Materialien und Beleuchtung durchgef\u00fchrt. Der Block aus der Br\u00fccke ist fertig und die Arbeit daran hat begonnen. F\u00fcr das \u00c4u\u00dfere sind die Triebwerke fast fertig und das Fahrwerk sollte in K\u00fcrze eingewickelt werden.\nIdris\nDer Idris hat eine Polier- und Fehlerbehebungsphase begonnen. Das Team unterst\u00fctzte das Design mit der Einrichtung von Verbrauchsmaterialien und beginnt zu sehen, dass interaktive Elemente wie Sitze, B\u00e4nke und Betten f\u00fcr den Spieler und die KI nutzbar sind.\nUng\u00fcltig\nDie Vanduul Void Kunst ist vollst\u00e4ndig. Sch\u00e4den und LODs werden eingerichtet.\nKarosserie\nSie haben sich eine detailliertere Graybox ausgedacht, indem sie zwei Bereiche ausgew\u00e4hlt haben, auf die sie sich konzentrieren wollten - Technik und Wohnen. Der Plan ist, diese Abschnitte zur endg\u00fcltigen Geometrie zu bringen, bevor man in den Motor geht, um Materialien und Beleuchtung zu erzeugen. Dieser Ansatz wird verfolgt, um die Zeit, die mit der Kreation der Designs am Anfang verbracht wird, zu maximieren und die Grundlage f\u00fcr zuk\u00fcnftige Aufgaben zu schaffen.\nKONZEPT ART\nIm November beendete das Konzeptteam die Fertigstellung und lieferte zwei Raumschiffe, die Anvil Hawk und die Aegis Hammerhead, ein weiteres Schiff und Fahrzeug in der Entwicklung. Sie haben auch K\u00fcnstler neu gemischt und einige Leute in neue Disziplinen versetzt, um die Dinge frisch zu halten und das Risiko eines Burnout zu reduzieren. Wie Sie wissen, ist das Team sehr arbeitsintensiv und es ist wichtig, an der Spitze zu bleiben!\nAuf der Umweltseite erkundeten sie weiter Gebiete von Hurston, Landepl\u00e4tze, Hangars und allgemeine Geb\u00e4udeausstattungen sowie einige hochrangige Erkundungen der Mikrotechnik. Sie setzten die Waffenentwicklung fort, machten die ersten der dazugeh\u00f6rigen Science and Development Distortion Repeater und verfeinerten die Hurston Elektronenstrahlkanone.\nVFX\nDie lang geplanten Arbeiten zur Verbesserung des Schildes begannen schlie\u00dflich in diesem Monat. Dazu geh\u00f6rten die Erzeugung von \"signierten Distanzfeldern\" durch unser Team in Frankfurt und eine forschungsintensive Zusammenarbeit mit dem Grafikteam zur Erzeugung von Energieeffekten, die dem Rumpf eines Schiffes nahe kommen. Diese Arbeit wurde bereits in Around the Vers erw\u00e4hnt und kann verwendet werden, um zahlreiche schiffsspezifische Effekte zu verbessern, wie z.B. atmosph\u00e4risches Burn-up des Eingangs und Quantum Travel.\nApropos QT, die letzten Design\u00e4nderungen erforderten, dass das Team die Effekte so umbaute, dass sie in den neuen Code \"hooks\" passen (Ausl\u00f6ser, die die zu aktivierenden Effekte aufrufen). Sobald die Timings und Funktionen wieder vorhanden waren, haben sie die Effekte weiter verfeinert und optimiert. Dies war ein zeitaufw\u00e4ndiger Prozess und erforderte eine sorgf\u00e4ltige Zusammenarbeit mit Design und Game-Code, aber es hat sich angesichts der Ergebnisse gelohnt.\nIn diesem Monat wurde eine unternehmensweite Kampagne zur Bereinigung von Log-Spam durchgef\u00fchrt. F\u00fcr das VFX-Team geht es darum, Verweise auf fehlende Texturen zu entfernen oder Partikelbibliotheken zu finden, die verschoben wurden bzw. deren Namen ge\u00e4ndert wurden, wie der Editor beim Laden eines Levels berichtet. Es ist eine der weniger glamour\u00f6sen Seiten des Jobs, aber eigentlich sehr befriedigend, die Fehlerprotokolle abzuschneiden.\nSie f\u00fchrten auch unseren \u00fcblichen \"Sanity Pass\" f\u00fcr 3.0 durch, indem sie jeden Effekt im Spiel \u00fcberpr\u00fcften und sicherstellten, dass sie wie erwartet funktionierten. Hier ist QA von unsch\u00e4tzbarem Wert, da es f\u00fcr die VFX-K\u00fcnstler einfach nicht m\u00f6glich w\u00e4re, alle Effekte des Spiels in einem solchen Zeitrahmen zu \u00fcberpr\u00fcfen. Aufgrund der Gr\u00f6\u00dfe unserer VFX-Bibliothek arbeiten sie noch an diesen Pr\u00fcfungen!\nLast but not least wurden viele spezifische Aufgaben der Staffel 42 gel\u00f6st. Wie \u00fcblich kann das Team nicht auf zu viele Details eingehen, sondern die Arbeit reichte von spulenspezifischen Plasmaversuchen \u00fcber mysteri\u00f6se Tr\u00fcmmercluster bis hin zu entfernten St\u00fcrmen.\nAUDIO\nBei CIG Audio ging es darum, 3.0 zu liefern und Verbesserungen am Spielerlebnis gro\u00dfartig klingen zu lassen und so solide wie m\u00f6glich zu arbeiten. So hat die Fehlerbehebung und -optimierung f\u00fcr jeden zwischen den Featurearbeiten (und oft wegen der Featurearbeit!) zus\u00e4tzlich zu den weiteren Arbeiten an Squadron 42 Zeit in Anspruch genommen.\nAuf der musikalischen Seite hat das Team eine neue Musikkompositionspipeline gestartet, um die Produktivit\u00e4t zu steigern und die Kommunikation f\u00fcr eine nachhaltige Universumsmusikproduktion zu verbessern. Dar\u00fcber hinaus arbeiten sie an einem neuen logikbasierten Musiksystem, das f\u00fcr Sehensw\u00fcrdigkeiten wie Raumstationen und Monde mit Au\u00dfenposten sorgt - im Rahmen eines nahtlosen Musik\u00fcbergangs.\nIm Sound-Design ist das Druckhaltesystem, das online kommt, ein gro\u00dfer Schritt nach vorne. Wenn man zu Fu\u00df und mit EVA geht, wird man feststellen, dass der Raum nicht unbedingt so klingt, als h\u00e4tte er jetzt eine Atmosph\u00e4re. Es gibt noch ein paar Anfangsprobleme, um viele Sounds neu zu adressieren und sicherzustellen, dass sie innerhalb unserer Wwise Busstruktur korrekt eingerichtet sind, aber wenn sie fertig sind, wird sie der Dynamik des Audio-Ingame viel mehr hinzuf\u00fcgen und geht Hand in Hand mit unserer 'Sound Sim'-Kunde, die akustisches Feedback im Cockpit rechtfertigt.\nT\u00fcr- und Aufzugsger\u00e4usche wurden ebenfalls stark gewartet und \u00fcberarbeitet, um auf \u00c4nderungen des vorgelagerten Systems zu reagieren. Au\u00dfenposten haben ihre grundlegende Arbeit leisten lassen, um verschiedene Machtzust\u00e4nde zu ber\u00fccksichtigen. Waffen - sowohl auf Schiffs- als auch auf Menschenebene - wurden wiederholt, und zwar mit gro\u00dfartiger Arbeit an der HDR-Technologie. Das Character Foley-System wurde erweitert, um Landungen\/Spr\u00fcnge eleganter zu gestalten. Schiffe wurden kontinuierlich angesprochen und Quantum Travel, das im Vorfeld \u00fcberarbeitet wurde, verbessert und erweitert. In-Game-Displays und MFDs senden ihre Kl\u00e4nge nun auch in 3D von ihrem wahrgenommenen Ursprungsort aus.\nWas den Dialog betrifft, so wurden die Schiffscomputerstimmen einer umfangreichen \u00dcberarbeitung unterzogen, wobei der Schwerpunkt auf der Erzeugung von Laufzeiteffekten zur Simulation von Lautsprechern und anderen Wiedergabemechanismen lag (was sich als besonders zufriedenstellend erweisen wird, wenn die Spieler sie mit Live-Input aus ihren eigenen FOIP-Setups\/Mikros nutzen k\u00f6nnen). Das Team verbessert auch weiterhin den Dialogmix, f\u00fcgt den Missionsgebern und NSCs mehr Dialog hinzu und verbessert die Verr\u00e4umlichung des Dialogs.\nZus\u00e4tzlich zu den oben genannten Punkten hat das Team viele schrittweise Verbesserungen vorgenommen, und wie immer w\u00e4re es toll, Ihr Feedback in den Foren zu erhalten, falls es etwas Bestimmtes gibt, das Sie von ihnen wissen m\u00f6chten.\nUMWELTKUNST\nDas Team arbeitete hart an der diesj\u00e4hrigen CitizenCon-Demo. Die positive Resonanz war gro\u00dfartig f\u00fcr das Team. Sie haben die Tech-Roadmap f\u00fcr die weitere Stadtentwicklung geplant, da die Gestaltung eines lebendigen und atmenden Stadtbildes viele Komplexit\u00e4ten aufweist. Speicherbudgets, Engine Rendering, City Building Shader und Tag\/Nacht-Folgen werden entwickelt.\nSie sorgten auch daf\u00fcr, dass der Build des 3.0-Release so stabil wie m\u00f6glich war. Es gab nur eine Handvoll Bugs, also sollte dies eine sehr starke Umwelterfahrung f\u00fcr den Spieler sein. Das Team entwickelte die Werkzeuge weiter, um effizientere Arbeitsabl\u00e4ufe zu erm\u00f6glichen. Ein Beispiel daf\u00fcr ist ein automatisches Abwurfsystem f\u00fcr Landschafts-POI's, wie Au\u00dfenposten, das implementiert wird, um einen Gro\u00dfteil der bisher erforderlichen rohen Gewaltarbeit zu beseitigen. Au\u00dferdem wollten sie nach einem internen Spieltest die Erfahrung an Au\u00dfenposten auf der dunklen Seite eines Mondes verbessern. Die Lichttechniker arbeiteten an einer L\u00f6sung, um diese Bereiche mit mehr Licht zu versorgen, damit die Spieler sehen konnten, was sie tun. Sie begannen auch damit, alle alten Gesch\u00e4fte in Area18 auf die neuen Systeme f\u00fcr Dinge wie Nutzbarkeit, T\u00fcren usw. umzustellen. Das neue Layout verbessert nicht nur die Leistung des Platzes, sondern erm\u00f6glicht es auch, ihn mit mehr NSCs zu f\u00fcllen und erm\u00f6glicht es dem Team, einige neue sch\u00f6ne Bereiche hinzuzuf\u00fcgen, in denen Sie die Ausblicke von ArcCorp genie\u00dfen k\u00f6nnen.\nDERBY-ANIMATION\nDas Derby Studio war super besch\u00e4ftigt mit Aufgaben f\u00fcr 3.0 und den Jubil\u00e4umsverkauf. Sie betrieben das hauseigene Headcam-System f\u00fcr einen Motion Capture Shoot in Nottingham f\u00fcr das Segment Galactic Gear Hammerhead.\nDas Gesichtsscannen auf der CitizenCon 2947 war ein gro\u00dfer Erfolg. Der Scanner wurde in zwei Wochen von Einzelteilen auf einem neuen Rahmen komplett aufgebaut. Es war eng, aber wir haben es geschafft! Die Anlage unternahm eine epische 12-st\u00fcndige F\u00e4hrfahrt zum europ\u00e4ischen Festland, dann eine 300-Meilen-Fahrt im \"Scan-Van\" nach Frankfurt. Ein gro\u00dfes Dankesch\u00f6n an alle Freiwilligen, die beim Auf- und Abbau des Scanners geholfen haben. Das Team h\u00e4tte es ohne dich nicht geschafft! Alle 10 Scan-Gewinner genossen ihre Scan-Sessions und es war gro\u00dfartig, einen Haufen super enthusiastischer SC-Spieler zu treffen.\nSchlie\u00dflich ist das Team begeistert, die Charaktere in 3.0 zu sehen und arbeitet sich derzeit durch die Levels, um ihre Gesichtsanimationen zu verfeinern und zu verbessern.\nMASCHINENBAU\nDer November konzentrierte sich auf 3.0, um es an Evocati und dann an PTU zu \u00fcbergeben. Das bedeutet, dass es viele Bugfixes und Optimierungen gab, sowie die Fertigstellung von Features wie persistentes Spawning, Spielerinteraktion, Missionen und so weiter. Das bedeutet jedoch nicht, dass sie nicht an neuen Funktionen gearbeitet haben. Das Team wurde aufgeteilt in diejenigen, die die PTU und ihre Anforderungen unterst\u00fctzen, und diejenigen, die an neuen Technologien arbeiten, um sie in zuk\u00fcnftige Builds zu integrieren, wenn sie fertig sind.\nZum Beispiel gibt es ein Team, das daran arbeitet, dass die soziale KI mehr Leben hat und sich weniger roboterhaft anf\u00fchlt. Dies begann damit, dass die NSCs Wildlinien lieferten, eine von der Situation abh\u00e4ngige Dialoglinie. Dies k\u00f6nnen einfache Gr\u00fc\u00dfe sein, wenn sie dich oder andere NSCs bereits kennen, oder eine Warnung, dass sie beim Joggen durchkommen und auf einen anderen Charakter sto\u00dfen. Sie wurden auch ein wenig mehr f\u00fcr die Umwelt interessiert, indem sie auf Gegenst\u00e4nde starrten, w\u00e4hrend sie herumlaufen oder wenn nichts ihren Geschmack verliert, nur um zu sehen, wohin sie gehen. Dar\u00fcber liegen Zappelphiken, bei denen sich ein Charakter den Kopf kratzt oder auf die Uhr schaut, um eine sich wiederholende Animation aufzul\u00f6sen. Sie haben auch in benutzerdefinierten Lokomotionssets f\u00fcr verschiedene Charaktere hinzugef\u00fcgt, so dass nicht jeder den gleichen Gang hat.\nDas Team hat sich auch mit Filmen besch\u00e4ftigt, um sie so zu polieren, dass sie am besten aussehen. Sie erforschten, wie das Filmteam die Beleuchtung in einer Szene besser steuern kann, ohne sie f\u00fcr den Rest der Umgebung zu unterbrechen, und wie man die Tiefensch\u00e4rfe und das Sichtfeld ein w\u00e4hlt. Dies soll das filmische Gef\u00fchl vermitteln und die Charaktere zur Geltung bringen, ohne die Kontrolle \u00fcber den Spieler negativ zu beeinflussen. Abgesehen davon gab es viele Gameplay-Sprints und das Durchspielen aller erforderlichen Funktionen.\nANIMATION\nDas Animationsteam hat zusammen mit dem Design gearbeitet, um sich auf die Bek\u00e4mpfung der KI zu konzentrieren - das Zerhacken von Assets, um sie an neue Metriken anzupassen, das Bereitstellen von Platzhalter-Assets, um Systeme zu testen, das Bereinigen bestehender Assets. Sie haben auch die Leistungserfassungsdaten durchgegangen und spielbereite Fortbewegungs-, Leerlauf- und Zappelanlagen f\u00fcr Darsteller erstellt. Die Waffenkammer von Idris hat eine vollst\u00e4ndige Durchsicht gehabt, so dass das Design \u00fcber alle Animationsm\u00f6glichkeiten f\u00fcr den Waffenmeister und seine Waffeninteraktionen verf\u00fcgt. Im Rahmen dieser Arbeit arbeiteten sie hart daran, einige coole erste Waffenauswahlen zu entwickeln.\nAu\u00dferhalb der Feature-Entwicklung hat das Team Fehlerbehebungen und Debugging-Probleme durchgef\u00fchrt, die derzeit in 3.0 und h\u00f6her liegen.\nGIE\u00dfEREI 42: DE\nWEAPONS\nIn diesem Monat hat das Waffenteam die letzten Handgriffe an den Kastak Arms Custodian Skins vorgenommen, die zusammen mit den Teilnehmern am CitizenCon-Demostand vorgenommen wurden. Das FPS-Team begann auch mit der Produktion von zwei neuen Waffen: der Gemini H29 HMG und dem Torral Aggregate Kahix Raketenwerfer. Das Schiffswaffenteam hat mit der Produktion der A&R-Laserkanonen (Gr\u00f6\u00dfe 1-6) und der Gallenson Tactical Ballistic Gatlings (Gr\u00f6\u00dfe 1-3) begonnen, die es ihnen erm\u00f6glichen sollen, in naher Zukunft eine weitere gro\u00dfe Serie von alten Schiffswaffen durch gl\u00e4nzende neue zu ersetzen.\nLICHT\nDas DE-Beleuchtungsteam konzentrierte sich auf die Fertigstellung der verbleibenden 3.0-Beleuchtungsaufgaben, die mehr Polier- und Leistungselemente in Levski beinhalteten. Neben anderen allgemeinen 3.0-Fehlern unterst\u00fctzten sie das Shop-Team dabei, die Beleuchtung in Gesch\u00e4ften ortsabh\u00e4ngig zu differenzieren. Ein gro\u00dfer Teil des Fokus wird sich nun auf verschiedene Bereiche der Staffel 42 verlagern.\nQUALIT\u00c4TSSICHERUNG\nDas DE QA-Team hat in diesem Monat eine breite Palette von Tests durchgef\u00fchrt, um sich auf Probleme zu konzentrieren, die in den Evocati-Builds gefunden wurden, und um den 3.0-Zweig im Allgemeinen zu testen. Dies beinhaltete ein Streaming-Problem, das auftrat, nachdem es \u00fcber einen l\u00e4ngeren Zeitraum mit einem Server verbunden war, und den schwarzen Bildschirm, auf den einige beim ersten Laden nach Stanton stie\u00dfen. Diese Probleme wurden spekuliert, um das Ergebnis einer m\u00f6glichen Speicherbesch\u00e4digung zu sein und erforderten mehr Tests mit Page Heap, um den Ingenieuren zus\u00e4tzliche Informationen zur Verf\u00fcgung zu stellen. Die Korrekturen werden letztendlich die Gesamtstabilit\u00e4t des gesamten Spiels erh\u00f6hen.\nDie Subsumptionstests wurden auch mit neuen Funktionen und Bugfixes fortgesetzt, die w\u00f6chentlich in das Subsumption-Tool einflie\u00dfen. Das Team arbeitete mit Design zusammen, um ihre Arbeitsabl\u00e4ufe zu erlernen, um die unterschiedlichen Einsatzm\u00f6glichkeiten des Subsumption-Tools besser zu testen. Dadurch wird der Umfang der QA-Unterordnungstests auf Testf\u00e4lle ausgeweitet, in denen beschrieben wird, wie der Unterordnungseditor mit unseren anderen von den Designteams verwendeten Tools wie Dataforge und dem Lumberyard Editor arbeitet. Zus\u00e4tzliche fokussierte Tests wurden auch f\u00fcr das EMP des Sabre Raven und seine Auswirkungen auf andere Schiffe durchgef\u00fchrt. Diese Effekte wurden f\u00fcr verschiedene Schiffstypen aufgezeichnet und von Design \u00fcberpr\u00fcft, um sicherzustellen, dass es keine Diskrepanzen zwischen dem Design und seiner aktuellen Funktionsweise gibt.\nDE QA arbeitete auch eng mit Marco Corbetta zusammen, um den Schiffen auf den Grund zu gehen, die durch die Planetenoberfl\u00e4che fallen, wenn die Spieler ihr Schiff ausschalteten und verlie\u00dfen. Dies war besonders schwierig zu reproduzieren, da es nur bei Schifffahrtsversionen auftrat und nicht bei internen Entwicklungsversionen reproduziert werden konnte. Das Engine-Team entdeckte, dass den Shipping-Builds bestimmte.r16-Dateien fehlten, die beispielhafte Verdr\u00e4ngungstexturen von K\u00fcnstlern enthalten. Diese werden vom Server auch zur Erzeugung von Kollisionsdaten, nicht aber zum Rendern verwendet. Das Problem wurde von Build Ops behoben und am n\u00e4chsten Tag best\u00e4tigt.\nMOTOR\nIm vergangenen Monat hat das Team der Frankfurt Engine zahlreiche Herausforderungen gemeistert, wie z.B. das Einpacken neuer Elemente f\u00fcr 3.0, die Untersuchung und Behebung bestehender Fehler sowie allgemeine Optimierungen.\nDas Team machte gro\u00dfe Fortschritte bei der Optimierung sowohl f\u00fcr den Server als auch f\u00fcr den Client und begann mit der Durchf\u00fchrung von Routine-Netzwerk-Stresstests, um besser zu verstehen, wie die Engine auf dem Server mit einer gro\u00dfen Anzahl von Spielern skaliert und zu erfahren, welche Bereiche noch teuer sind und optimiert werden m\u00fcssen. Mit der gestiegenen Anzahl von Spielern auf dem Server und der Verlagerung von mehr Code in Jobs zur parallelen Ausf\u00fchrung wurden \u00c4nderungen am Jobsystem vorgenommen, um die Nutzung von mehr als 16 Worker-Threads auf Servern ohne zus\u00e4tzlichen Overhead in der Jobverteilung zu erm\u00f6glichen. Dies ist notwendig, um eine steigende Anzahl von Spielern zu erm\u00f6glichen. Diese \u00c4nderung des Job-Systems wirkt sich auch auf den Client aus, so dass Menschen mit High-End-CPUs zus\u00e4tzliche Leistungsvorteile in Bereichen erhalten, in denen sie typischerweise CPU-gebunden sind. Auf der Low-Level-Optimierungsseite haben sie den Signalisierungsmechanismus des Core Threading Synchronisationsobjekts unter Linux von Semaphore auf Futexe ge\u00e4ndert. Diese \u00c4nderung erspart in 99% der F\u00e4lle einen Syscall, was einen kleinen Leistungsschub bedeutet.\nDas Fl\u00e4chenmanagement wurde optimiert, indem ein Octree f\u00fcr Bereiche, in denen sie nie suchen, ignoriert wurde. Ein \"Bereich\" ist ein spezielles Markup f\u00fcr die Designer, das alle Objekte innerhalb eines bestimmten Bereichs verfolgt.","zh_CN":"Greetings Citizens!\n\n\nWelcome to the Monthly Studio Report, where we collect updates from our various studios around the world to show you what they\u2019ve been working on this past month. As many of you know, there\u2019s been a concerted push among our various studios to get the Alpha 3.0 to the community. Since our last report, we\u2019ve gone to Evocati and begun a staggered release to the PTU, so the team\u2019s busy fixing bugs discovered by the testers and working on overall stability and performance. With that, let\u2019s get to it. CLOUD IMPERIUM: LOS ANGELES\n\nENGINEERING\nLA Engineering has been racing towards 3.0 at a breakneck pace, with the primary focus being on resolving bugs from Evocati and PTU and adding final polish to features like cargo, item components, atmosphere systems and more. Part of this work has been integrating all the item systems in ships with UI in order to bring a real sense of control to the cockpits. Lastly, updating Quantum Travel has been an area of focus for several weeks, pushing to deliver a more immersive experience.\n\nTECH DESIGN\nThis month, LA Tech Design spent the bulk of their time closing down tasks and knocking out the remaining bugs for the Item 2.0 Ship Setup. They\u2019ve solved several issues with the 300 series, Mustang, Nox, Starfarer, and Scythe while identifying some more dependencies on the final lighting setup as well. The updated animations for the Gladiator were delivered this month so a total setup refactor has been completed.\n\nIn addition, the team also finished setup on all the ship headlights as well as the \u201cSaveGameLogOut\u201d functionality that allows for logging out anywhere there\u2019s a bed.\n\nART\nThis November, the Character Team spent a lot of time polishing the cast of Squadron 42. They also polished many new Star Citizen characters and assets that they are excited to release with 3.0.0 while working on developing concepts for clothing, finalizing the legacy armor sets and more.\n\nThe LA Ship Art team has spent much of November updating a lot of ships to take advantage of new tech. In particular, the ships now use new Light Groups set-up, new fog tech, new Render-to-Texture screens and to made proxies airtight now that oxygen has been introduced to Star Citizen. They\u2019ve been juggling these various tasks with fixing a lot of art bugs in preparation for ships included in the Alpha 3.0 release. Additionally, they\u2019ve made progress on the art for future releases, including the Anvil Hurricane, Tumbril Cyclone and the Consolidated Outland Mustang update.\n\n\n\n\n\nNARRATIVE\nIn addition to working with the PU design team on polishing Alpha 3.0 mission content, the Narrative team continued to expand the Xi\u2019an language with the help of the community, and worked with the cinematics team to create the Galactic Tour Hammerhead piece. For Squadron 42, they spent time discussing additional set dressing with the prop and art teams to help further expand environmental storytelling in the game. Looking ahead, the team also spent time this month continuing to plan out narrative content goals for 2018\u2019s quarterly updates.\n\nTECH CONTENT\nFor Environments, the Global Technical Content team has been continuing work on the features that were revealed at the GamesCom Procedural Tech Demo. In addition to supporting asset and code performance improvements, they have been investigating bugs with lighting and visareas, and have been working side by side with the graphics team to develop scripts and shader tech to help catch performance issues as well as improve other areas like the procedural cities. They\u2019ve also worked in conjunction with our tech animation team on animated environment assets, and with engineering and design on new tech for Derelict Systems, Outpost Locations and a Planetary Placement Systems.\n\nFor Ships, the team has been busy handling damage implementation for the new ships coming down the pipeline for the 3.0 release. All of this whilst juggling a variety of ship bugs related to UV2 damage, landing gear compression, visareas and log spam errors. Progress was made to support gas effects for the incoming Breaching feature. They\u2019ve also been supporting Tech Design and the Ship Art teams with some new tech for ship lighting and ship proxies. On the Weapons front, the team has continued to work on new weapons in the pipeline, including working on Mannequin set-ups, weapon bugs, an adjustable stock, and some exciting R&D on animated weapon attachments which will have many additional uses beyond just weapons.\n\nA lot of work for the Tech Animators was in support of Squadron 42, rigging and simulating new costumes coming down the Character & Heads Pipeline. As with the other areas of focus, ample time has been spent on fixing bugs, mainly related to skinning and character item implementation.\n\nThe team has also been making great progress tracking, trimming and solving a vast amount of MoCap data for Squadron 42. The list of accomplishments rounds out nicely with the implementation of new health checks, a CIG Tools Installer, Tools management\/migrations, and a ton of support for facial animation, usables, wildlines and cinematics.\n\nFinally, there was a lot of miscellaneous support that the team had their hands on, including technical direction for WAF asset builds (which reduce build times significantly!), website development, R&D and some due diligence on a prospective upgrade to our internal DCC tools Max and Maya and MoBu.\n\nQUALITY ASSURANCE\nLAQA\u2019s primary focus was testing lighting and the new light groups, LOD\u2019s, breaching mechanics, character art, the myriad of new updates to the code base made by the engineering team, and the way Item Ports were set up by tech design. They also aided the global QA team with publishing checks for PTU and Evocati deployments and several live internal gameplay reviews.\nCLOUD IMPERIUM: AUSTIN\n\nDESIGN\nThe ATX design team have been tackling all things shopping to get the game ready for the PTU Release of the 3.0 build. There have been two core elements that we\u2019ve been focused on since the handing off the Mission Givers implementation tasks to the design team in Frankfurt. The team also outlined the desired income per hour goals and has adjusted both the mission reward calculator and the item prices accordingly. This work has also included the ship respawn time and prices. While we expect to dial in these values over the next several Alpha builds based on player feedback and analytics that we collect, we feel like this is a good representation of where we want it to be.\n\nMeanwhile, the rest of the team tidied up all the physical shops in the three major locations: Port Olisar, Grim HEX, and Levski. In total, there are roughly fifteen separate places where players will be able to buy items in the game and we\u2019ve been able to spread the items around the different shops with very little overlap. The team also worked with the LA Programmers and the UI team to add some new features for the shopping experience. Among these new features are: AR Markers have now been replaced by the new item highlighting system to fall in line with the overall loot system.\n\nInner Thought is now being used on the objects where Try On, Inspect or Buy are concerned.\n\nArmor can now be purchased as separate pieces.\n\nAll Item names are now unique\n\nFirst pass of shopkeepers are now in.\n\nThe shopping UI has been cleaned up.\n\nWhile there are still have many new features they wish to add, or existing ones they wish to clean up, the team hopes that the new shopping experience will make all players happy, and they look forward to continuing the refinement of the shopping experience in the new year.\n\nART\nThe ship team knocked out 3.0 bugs for the Drake Herald and Cutlass Black, including fixing up their lighting states and visareas. They also finished up the whitebox modeling and a first pass at interior lighting of the Constellation Phoenix, so it\u2019s now in game and can be walked through. In other Constellation news, the Andromeda and Aquila had their interior and exterior lighting states updated and their LODs were refactored to be much more efficient. Several other ships went through similar updates, including the Hornet (F7C, F7CM), 300i (and variants), M50, Scout and Nox. The team continued their work polishing and optimizing the materials on all the ATX ships. Work also began on the whitebox modeling process of the Anvil F8 Lightning.\n\nBACKEND SERVICES\nServer Engineering team focused on helping with features and issues in 3.0. The team has been tuning parts of the back-end services to accommodate the volume of data that flows between game servers, persistence caches and the database, and solved several issues, including the ability to reconnect to the same instance if you lose your network connection. Over the course of the month, they also improved data integrity if a server or service would go down, improved caching services functionality to allow items to exist in the universe outside of the player\u2019s possession, and lastly solved many login and connectivity issues.\n\nLooking to the future, the engineering team has been building the next generation of back-end services. The team is aiming to split up all larger services into smaller stateless services and enhancing the service architecture and Ooz scripting language to comply with the ever-growing requirements the game demands.\n\nANIMATION\nThis month, the Ship Animation Team fine-tuned the player bed enters and exits as part of our persistent save system, which will allow the player to enter a bed and exit the game while saving their location in the universe. Next time when you load the game, you\u2019ll wake up in your bed with your ship in its last location. In addition to this, the team finished updating the Gladiator enter and exits as part of the cockpit experience sprint. The speed and technical setup of the Gladiator has vastly cut down the time to enter and exit the pilot and copilot seats. The Austin studio also held a motion capture shoot to capture animations for the Tumbril Cyclone.\n\nMeanwhile, the PU Animation Team helped support work on Squadron 42 and worked closely with Design to make all usables fully functional and bug free. Some of the challenges the team faced included syncing props to animate with characters, such as chairs sliding as a character sits down and getting a female version of every animation implemented into the game. The goal is to have a large batch of the Usable animation assets polished and finalized by the end of the year.\n\nOPERATIONS\nThe DevOps Team worked around the clock to support our internal teams and the Evocati as we closed in on our 3.0 goals. In addition to publishing at least one game version every day, they have been able to complete some major internal projects designed to massively improve build times and error handling.\n\nATX QA\nSince CitizenCon, 3.0 has been an all-consuming focus for the QA team as incremental updates were released to Evocati and to the first wave of PTU. Between Evocati and the PTU, there have been 26 builds published so far under Austin\u2019s belt for 3.0 and 2 publishes for our sister team in UK. QA has been gathering fresh performance captures for our engineers with each new build that goes to PTU to focus on stability. The team worked with the LiveOpS cohorts to compile all the various new client and server crashes with metrics to show which has the greatest impact. With so many new missions in 3.0 and new gameplay mechanics associated with them, the team ensured they function both in ideal scenarios and when a server is at full capacity. At the same time, they\u2019ve been testing various new configurations with UK QA and the engineering teams to increase the player cap. Squadron 42 testing has been proceeding at a brisk pace, with regular tests of levels run on new builds each day.\n\nFor leadership, the focus has been training new hires and keeping in constant communication with the other departments, talking to Production to ensure that the right bugs are on their radar for PTU and Live triage, attending stand-ups with the Development teams to find out what needs to be tested coming out of the sprints, and working with Player Relations and Issue Council every day to keep up to date on the latest feedback and reports from backers. All these different avenues combined to ensure QA is consistently on the same page across the company.\n\nPLAYER RELATIONS\nThe month of November kept the Player Relations team on its toes. After assisting and moderating a phenomenal CitizenCon, the team rolled right into helping backers with their interest in our game-changing Pioneer. The team also worked with Evocati every day to publish new 3.0 builds, run playtests, assess stability, and gather crucial feedback. With the push to PTU, they wanted to thank all our relentless Avocados who are always there to answer the call! Lastly, the team expanded in Austin and Frankfurt as their list of duties continues to increase. They are excited to hire our first full time German support staff, as well as roll out moderation support in several new languages.\nFOUNDRY 42: UK\n\nGRAPHICS\nThe graphics team spent their time bug fixing 3.0. When QA\/Evocati get their hands on completed features and assets there\u2019s always the usual influx of unexpected issues. This included numerous problems related to rotating planets\/moons because much of the older rendering code made assumptions about things being stationary, and especially doesn\u2019t cope well with changing the frame of reference when moving in\/out of orbit.\n\nThe team also created a new glass shader that provided a great visual improvement over the past one, and they were really keen to see it implemented as soon as possible. A pass was done across all ship canopies.\n\nThey also closed down some minor feature work for 3.0, such as RTT functionality for ship MFDs and the ability for game code to control the camera\u2019s exposure to make the mobiGlas more legible in bright lighting conditions (though more improvements are coming for holographic displays). In parallel, two team members continued their longer-term R&D tasks on the new shield effect, which uses particles rather than meshes, and improvements to the volumetric ray-tracing tech (gas clouds & fog), which is nearing the point where they can share some pretty cool visuals!\n\nSHIPS\nHammerhead\nThe Hammerhead has made rapid progress in a short time period. Work on the exterior was prioritized for its Galactic Tour appearance. After receiving the concept mesh, the team did more than trace over the shapes but also made sure the mesh was efficient and game ready. Now that the Aegis brand is so well established they have a wealth of shaders and assets to pull from for quick iteration.\n\n600i\nThe 600i\u2019s interior corridors were fully fleshed out, making sure they capture the higher class feel that is Origin. Further work was done with the exploration module, along with passes on materials and lighting. The block out of the bridge is done and work on it has started. For the exterior, the thrusters are almost complete and the landing gear should be wrapped up shortly.\n\nIdris\nThe Idris has entered a polish and bug fixing phase. The team supported design with useables set up and are starting to see interactive items such as seats, benches and beds being useable by the player and AI.\n\nVoid\nVanduul Void art is complete. Damage and LODs are being set up.\n\nCarrack\nThey chipped away at a more detailed greybox by picking two areas to focus on \u2014 engineering and habitation. The plan is to take these sections to final geometry before going into engine to create materials and lighting. This approach is taken to maximize the time spent being creative with the designs at the start and lays the groundwork for future tasks.\n\nCONCEPT ART\nNovember saw the concept team finish and deliver two spaceships, the Anvil Hawk and the Aegis Hammerhead, with another ship and vehicle in development. They also reshuffled artists and moved some people to new disciplines to keep things fresh and reduce the risk of burnout. As you know, the team pumps out a huge amount of work and it\u2019s important to stay on top!\n\nOn the environment side, they further explored areas of Hurston, landing sites, hangars and general building look dev, and some high-level exploration of Microtech. They continued with weapon development, making the first of the Associated Science and Development Distortion repeaters and refining the Hurston Electron Beam cannon.\n\nVFX\nLong-planned work on shield improvements finally commenced this month. This included the generation of \u2018signed distance fields\u2019 by our team in Frankfurt and a R&D-intensive collaboration with the Graphics team to generate energy effects that closely conform to the hull of a ship. This work was previously mentioned in Around the Verse and can be used to improve numerous ship-specific effects, like atmospheric entry burn-up and Quantum Travel.\n\nSpeaking of QT, recent design changes required the team to rebuild the effects so they fit the new code \u2018hooks\u2019 (triggers that call upon the effects to be activated). Once the timings and functionality were back in place, they continued to polish\/optimize the effects. This was a time-consuming process and required careful collaboration with Design and Game-Code, but was worth it given the results.\n\nThis month has seen a company-wide push to clean-up log spam. For the VFX team, this is a case of removing references to missing textures or finding particle libraries that were moved\/had their name changed, as reported by the editor when loading a level. It\u2019s one of the less glamorous sides of the job but actually very satisfying to whittle away the error logs.\n\nThey also conducted our usual \u201csanity pass\u201d for 3.0 by checking every effect in the game and making sure they work as expected. This is where QA is invaluable, as it simply wouldn\u2019t be possible for the VFX artists to check through all the game\u2019s effects in such a time-frame. They are still working through these checks due to the size of our VFX library!\n\nLast but certainly not least, lots of Squadron 42 specific tasks were tackled. As usual, the team can\u2019t go into too many details but work ranged from Coil-specific plasma experiments, to mysterious debris clusters, and distant storms brewing.\n\nAUDIO\nCIG Audio has been all about working towards delivering 3.0 and making improvements to the player experience sound great and work as solidly as possible. Thus, bug-fixing and optimization has been taking up time for everyone between feature work (and often because of feature work!) in addition to the continued work on Squadron 42.\n\nOn the music side of things, the team have rolled out a new music composition pipeline to help step up productivity and improve communication for persistent universe music production. In addition to that, they are also working on a new logic-based music system to cater for points of interest such as space stations and moons with outposts \u2013 part of a move to make music transition more seamlessly overall.\n\nIn sound design, the pressurization system coming online is something that\u2019s a big step forward. When on foot and EVA, you\u2019ll find space doesn\u2019t necessarily sound as if it has an atmosphere now. There are still a few teething issues to readdress a lot of sounds and ensure they\u2019re set-up correctly within our Wwise bus structure, but when complete, it will add a lot more to the dynamics of the audio in-game and goes hand-in-hand with our \u2018sound sim\u2019 lore that justifies sonic feedback when in-cockpit.\n\nDoor and elevator sounds have also undergone much maintenance and re-work in response to upstream system changes. Outposts have had their foundational work done to account for different power states. Weapons \u2013 on both ship and human-scale \u2013 have been iterated upon, with some great work done on the HDR tech for those. The Character Foley system has been extended to account for landing\/jumps more elegantly. Ships have been continually addressed and Quantum Travel, having been refactored upstream, has been improved and extended. In-game displays and MFDs now also emit their sounds in 3D from their perceived point of origin.\n\nWhere dialogue is concerned, ship computer voices have undergone some extensive rework with a lot of emphasis on producing runtime effects to simulate speakers and other playback mechanisms diegetically (which will prove especially satisfying once players can use them with live input from their own FOIP set-ups\/mics). The team\u2019s also continuing to improve the dialogue mix, add more dialogue to mission givers and NPCs, and making improvements in dialogue spatialisation.\n\nAs well as the above, the team has been making lots of incremental improvements and as always, it\u2019d be great to get your feedback on the forums in case there\u2019s anything in particular you would like them to address.\n\nENVIRONMENT ART\nThe team worked hard on this year\u2019s CitizenCon demo. The positive response was great for the team to hear. They have been planning the tech roadmap for further city development work, as making a living and breathing cityscape has many complexities. Memory budgets, engine rendering, city building shaders, and day\/night sequences are all being developed.\n\nThey also made sure that the 3.0 release build was as stable as possible. There were only a handful of bugs so this should be a very strong environmental experience for the player. The team continued to refine tools to enable more efficient workflows. An example of this is an automatic dropping system for landscape POI\u2019s, like outposts, being implemented to remove a lot of the brute force work which was previously required. Also, after internal playtesting, they wanted to improve the experience at outposts on the dark side of a moon. The lighting engineers worked on a solution to provide these areas with more light so players could see what they are doing. They also started converting all the old shops in Area18 to the new systems for things like usable, doors, etc. The new layout not only improves the plaza\u2019s performance but enables it to be filled with more NPCs and allows the team to add some new beautiful areas where you can take in the vistas of ArcCorp.\n\nDERBY ANIMATION\nThe Derby Studio was super busy with tasks for 3.0 and the Anniversary Sale. They ran the in-house headcam system for a motion capture shoot in Nottingham for the Galactic Gear Hammerhead segment.\n\nFace scanning at CitizenCon 2947 was a great success. The scanner went from in pieces to fully built on a new frame in two weeks. It was tight but we did it! The rig took an epic 12-hour ferry journey to get to mainland Europe, then a 300-mile drive in the \u201cScan-Van\u201d to Frankfurt. A massive thanks to all the volunteers who helped set up and tear down the scanner. The team couldn\u2019t have done it without you! All 10 scan winners enjoyed their scan sessions and it was great to meet a bunch of super enthusiastic SC gamers.\n\nFinally, the team is excited to see the characters in 3.0 and are currently working through the levels to polish and improve their facial animations.\n\nENGINEERING\nNovember was focused on 3.0, getting it to Evocati and then to PTU. This means there were a lot of bug fixes and optimizations, as well as the finishing of features like persistent spawning, player interaction, missions, and so on. However, this doesn\u2019t mean they didn\u2019t get to work on any new features. The team was split into those that support the PTU and its requirements, and those working on new tech to incorporate into future builds when it\u2019s ready.\n\nFor example, there\u2019s a team working on the making the social AI have more life and feel less robotic. This started with the NPCs delivering wildlines, one off lines of dialogue dependent on the situation. These could be simple greetings, if they already know you or other NPCs, or a warning that they\u2019re coming through when jogging and coming across another character. They were also given a bit more interest in the environment, glancing at items as they walk around or if nothing\u2019s taking their fancy just looking at where they\u2019re going. Layered on top of that are fidgets, where a character will scratch their head or look at their watch to help break up a repetitive animation. They\u2019ve also been adding in custom locomotion sets for different characters so everybody doesn\u2019t have the same walk\/run gait.\n\nThe team also looked at cinematics in an effort to polish them so they look their best. They explored how the cinematic team can better control the lighting whilst in a scene without breaking it for the rest of the environment and how to dial in the depth of field and field of view. This is to give that cinematic feel and show off the characters without negatively impacting the control of the player. Other than that, there were lots of gameplay sprints and getting through all the functionality required.\n\nANIMATION\nThe animation team has been working in tandem with design to focus on combat AI \u2013 chopping assets up to fit new metrics, providing placeholder assets to prove systems out, cleaning up existing assets. They have also been going through the performance capture data and creating game ready locomotion, idle & fidget assets for cast characters. The Idris armory has had a full sweep, so that design have all the animation assets for the master-at-arms and his weapon interactions. In line with this work, they worked hard to create some cool first weapon selects.\n\nOutside of feature development, the team did bug fixing and debugging issues that are currently in 3.0 and beyond.\nFOUNDRY 42: DE\n\nWEAPONS\nThis month the weapons team completed the final touches on the Kastak Arms Custodian skins, which were made together with attendees at the CitizenCon demo stand. The FPS team also started production on two new weapons: the Gemini H29 HMG and the Torral Aggregate Kahix Missile Launcher. The ship weapons team has started production on the A&R Laser Cannons (Size 1-6) and the Gallenson Tactical Ballistic Gatlings (Size 1-3), which should allow them to replace another big batch of legacy ship weapons with shiny new ones in the near future.\n\nLIGHTING\nThe DE lighting team focused on finishing our remaining 3.0 lighting tasks, which involved more polish and performance items in Levski. In addition to other general 3.0 bugs, they supported the shop team to help differentiate lighting in shops based on the location. A large amount of focus will now shift to various areas for Squadron 42.\n\nQUALITY ASSURANCE\nThe DE QA team did a wide range of testing this month to focus on issues found in the Evocati builds and testing the 3.0 branch in general. This included a streaming issue that occurred after being connected to a server for an extended period and the black screen some encountered when initially loading into Stanton. These issues were speculated to be the result of potential memory corruption and required more testing with Page Heap to provide the engineers with additional information to fix them. The fixes will ultimately increase the overall stability of the full game.\n\nSubsumption testing also continued with new features and bug fixes going into the Subsumption tool weekly. The team collaborated with Design to learn their workflows in an effort to better test the varying uses of the Subsumption tool. This will expand the scope of QA subsumption testing to include test cases outlining how the Subsumption Editor works with our other tools used by the Design Teams, such as Dataforge and the Lumberyard Editor. Additional focused testing was also spent on the Sabre Raven\u2019s EMP and its effects on other ships. These effects were recorded for multiple types of ships and reviewed by Design to make sure there weren\u2019t any discrepancies between the design and how it\u2019s currently working.\n\nDE QA also worked closely with Marco Corbetta to get to the bottom of ships falling through the planet surface when players powered off and exited their ship. This was particularly tricky to reproduce as it only occurred on Shipping builds and could not be reproduced on internal Development builds. The Engine team discovered that the Shipping builds were specifically missing certain .r16 files which contain sample displacement textures made by artists. These are also used by the server for generating collision data but not for rendering. The issue was resolved by Build Ops and confirmed fixed the next day.\n\nENGINE\nThis past month, the Frankfurt Engine team tackled numerous fronts, such as wrapping up new items for 3.0, investigating and addressing existing bugs, as well as general optimizations.\n\nThe team made a lot of progress optimizing for both the server and client, and started conducting routine network stress tests to better understand how the engine scales on the server with a large number of players and learn what areas are still expensive and need optimization. With the increased number of players on the server and more code being moved to jobs for parallel execution, changes were made to the job system to allow utilization of more than 16 worker threads on servers without introducing extra overhead in job distribution. This is needed to allow an increasing number of player counts. This change to the job system will also translate to the client, so people with high-end CPUs will see extra performance benefits in areas where they are typically CPU bound. On the low-level optimization side, they changed the signaling mechanism of the core threading synchronization object on Linux from semaphore to futexes. This change spares one syscall in 99% of the cases, which provides a small performance boost.\n\nArea Management was optimized by disregarding an Octree for Areas they never search in. An \u201carea\u201d is a special markup for the designers which tracks all objects inside a specific location, such as a bar. The system now allows them to send Events when an object (like a player) enters an Area (the bar), on which the game code can then react. They also support spatial queries against those areas (using the same code as the Zonesystem, as this allows them to support areas of nearly arbitrary size). This behavior requires that for each moving object, they check if it is no longer in any area or if it entered a new one. On top of this, and for them to have efficient spatial queries, they need to maintain an octree per Area. The team realized that many of those areas were never used for spatial queries, which means they had numerous unneeded computations with the octree\u2019s. This is now fixed and they only maintain the octree when actively searching in an area.\n\nThey also spent some time investigating memory leaks, and developed a lightweight memory tracking system which can be run on the server in the background with an acceptable performance impact. They can then review the results in an effort to analyze and fix specific memory leaks people encounter. The team also did some minor bugfixes for the Patcher Library, which implements the functionality for the delta patching. Improvements were made to the new temporal antialiasing technique to improve overall image sharpness and preserve luminance of bright objects. Additionally, motion vectors for software skinned meshes were fixed, so that postprocessing technique can properly take them into account (temporal antialiasing, motion blur, etc).\n\nRegarding skinning and characters, the team fixed code to allow mesh compression on skin meshes with morph targets. Since faces are very detailed, this will result in substantial memory savings and lower rendering overhead. Lastly, with respect to future engine improvements and memory savings, they made good progress in implementing GPU based ray intersection tests to offload these types of computations from the CPU and reuse the already existing high-fidelity render mesh on GPU for precise intersection test. The results of those computations are provided asynchronously as to not block the CPU mid-frame and can be used on any type of effect that doesn\u2019t need server authority (anti cheat measure).\n\nLEVEL DESIGN\nThe Level Design team polished the locations for 3.0 with the focus being bug fixing for Levski and surface outposts. As that work was completed, they turned towards the future and to something called \u201cCommon Elements.\u201d These are components that each location will use, like hangars, garages, housing, offices and so on that will be tied into our modular system and combined with the various tilesets. The team will quickly be able to use them to add essential components to locations. They also looked into train stations and monorails for our flagship landing zones, as well as early work on city Space Ports.\n\nVFX\nThe DE VFX team worked on particles and VFX that are used throughout the universe. They\u2019ve gone over almost every existing visual effect again to ensure there are no issues. One recent challenge has been staying on top of the physics system for particles. With such an active development cycle, sometimes things that previously worked need to be modified to accommodate the updated system(s). They also continued to flesh out the GPU particles system and added new features to it. The team is approaching the point where the old CPU based system can be phased out and rely solely on the GPU for most effects throughout the levels and universe. They also worked on applying signed distance fields to our particle effects. These are 3d textures that specify the distance to the surface of an object. With these textures, they can reconstruct the interior and exterior of geometry and have the motion of the particles affected by the SDF. It can be used for collision detection as well as allowing particles to flow over the surface of the SDF.\n\nSYSTEM DESIGN\nThe System Design team took over the mission givers behaviors, finalizing the implementation and making sure all the edge cases matched the design. The first case was to finalize Miles Eckhart so they could utilize the same defined template for future mission givers. Another related task was to implement the admin officers behaviors and integrate it into the mission system. The admin officer\u2019s main job is to deliver mission items to the player and to accept deliveries of incoming mission items. FPS AI combat saw major improvements, as the system design team worked with AI to make sure the characters enter, exit, peek, and shoot from cover and that their behavior looks as natural as possible. They also addressed bugs and tweaked things required for 3.0 with the focus being on AI, usables, doors, rooms & breathing.\n\nENVIRONMENT ART\nThe Environment team polished areas that are used in 3.0, making sure that players get the best possible visual experience and encounter no visual bugs. Next to polishing, the team focused on what will be coming after 3.0. A glimpse at this post-3.0 Environment work was shown during the CitizenCon demo and is just a small example of what will eventually be on Hurston. A whole new range of ecosystems are being worked on that are visually very different from what\u2019s been seen before. They\u2019ve also been hard at work on unique vegetation, large trash mesas, and the city of Lorville, which is another major landing zone using the procedural city tech.\n\nTECH ART\nThe DE Tech Art team spent the month tackling content creation, new tool building, and supporting various teams, while also addressing issues for 3.0. They added a new Usable for both AI and Player characters, and fixed bugs for existing Usables such as minor animation popping. For characters, they did various skinning tasks that will be used for both the PU and Squadron 42, which will help with character variants. They developed a tool which can help artists export animated geometry into engine more efficiently. This tool combines multiple manual processes into one and error checks before export, making the process much quicker and less prone to human error. For weapons, they finalized the setup for the Gemini R97 shotgun and prepped the Torral Aggregate Kahix Missile Launcher for production. The tech art team also grew by one member and time was spent getting him familiar with the toolset, workflow, and best practices. His focus will be to improve and extend our internal character editor, as well as enhance our existing systems for cloth, hair simulation, and similar physics-based secondary animation effects on all characters.\n\nAI\nThe AI team split their attention between different in-game functionalities and raising the bar on numerous aspects at the same time. Regarding Subsumption, they worked on improving features related to the usability of the tool and exposed new functionalities to the design team. Subsumption conversations now allow designers to specify multiple input parameters and not just the input participants. This allows the creation of a more complex abstraction of logic and more complex conversation branching. They also introduced two new subsumption functionalities \u2014 the support for Event Parameters and Trackview scenes. Event parameters simplify the logic, exposing sub parameters for each event, which then allows designers or programmers to create more complex logic using events to carry more information across different actors. The Trackview support requests the execution of Trackview scenes as needed and tied to the conversation logic which allows the alternative option to create scenes using Trackview to achieve the best visual results, but still allows the Subsumption logic to react or take over when necessary.\n\nThe team also continued to refactor the way the AI controls different vehicles. In the future, behaviors won\u2019t run anymore on the spaceships themselves, but the different seat operators will control the different items they have on any given ship and have the appropriate behaviors. Different operator skills can now directly influence the different actions, and vehicles like multi-crew ships can benefit from the different NPCs operating the various seats. They also worked on manned and automated turrets. Both of those possible controllers will take care of executing all the required operations to turn on the turrets, activate their functionalities, search for targets using the radar, predict where to shoot and so on. Work on NPC on-foot AI mostly focused on human combat, polishing the different entries\/exits to move into\/out of cover, and the different actions that can be performed while in cover (peeking, shooting from different sides of the cover, changing body directions and so on).\n\nRegarding the other systems, a huge number of fixes and improvements went into the Mission System, offering all the functionalities requested by designers for the current missions. The Spawning Manager received lots of optimizations and new improvements, especially on the environmental validation to spawn elements correctly and safely in space and on the ground.\nTURBULENT\n\nA new release of Spectrum, a major milestone for the Launcher and additional 3.0 launch support kept Turbulent very busy for the month. Here\u2019s what we\u2019ve been working on:\n\nSPECTRUM\nThe release of Spectrum 3.7.1 consisted of bug fixes, quality of life improvements and unnoticeable changes to sustain long term development and maintenance. Let\u2019s talk about latter first.\n\nThe team is improving the code base and release process so that launching new versions remains a frictionless process as much as possible. Spectrum also adopted a new versioning scheme to better communicate the scope of a release and then proceeded to update a lot of internal dependencies to avoid potential future breaking changes. There\u2019s also discussions about bumping React to the latest version as well as migrating the code base to TypeScript. Those changes would allow us to trap more bugs before going into production and refactor parts of the project without affecting stability.\n\nAlso, the team set to improving how to handle change requests, better manage priorities coming from different sources (Jira, Issue Council, Forums, internal communications, etc.) and get better at tracking\/communicating progress.\n\nLast, here\u2019s summary of the latest application changes: * Addressed several pain points for Android device users where entering text would produce unpredictable results. * Spectrum now suggests a list of mentions based on the authors of the last messages in a lobby when typing \u2018@\u2019. * Embedded Twitch clips will no longer automatically play. * Significant progress has been made on Custom Emojis and Custom Roles and with the hope to deliver those for 3.8.\n\nLAUNCHER\nLauncher testing started in October with the release of the RSI Launcher 1.0.0-alpha.20 to Evocati for testing. This is the first exposure public users have had with the Delta Patcher.\nUsers have been very happy with the Delta Patcher, as some patches are as little as 100 megabytes! Pretty dramatic reduction in patch sizes compared to the previous technology used to deploy Star Citizen Alpha 2.6 and below.\n\nWith help from the great Evocati, the team has been able to gain exposure to a multitude of user setups, hardware configuration, Windows versions and personal user preferences that affect the function and operation of the launcher. Most of the following weeks have been spent iterating on issues found during this phase and fixing bugs that affect patching and gameplay. Most notably, issues related to Windows N and file permissions have taken a lot of time to figure out. As always, the Issue Council has been our greatest ally in getting the bugs vetted, verified and checked before being tackled.\n\nThe application will now properly trap game crashes and application errors.\n\nThe game library polling mechanism have been tuned to a real world case with many users listening for updates.\n\nThe application will now properly repair permissions on the game library if a permission error is detected.\n\nDuring a \u201cVerify Files\u201d the launcher will also check for an update!\n\nThe sound system has been expanded to provide a better sonic experience in the launcher. Volume slider!\n\n5 new background music tracks have been added from the SC soundtrack!\n\nOnly one major item remains for 1.0.0 of the launcher \u2014 the specific handling of the initial download, which is a problem with the new object based Delta Patcher. A game build is comprised of many files (upwards of 300k-400k) many of which are smaller files. Currently, when patching from scratch, your launcher will fetch all those files. This process is not only highly inefficient but also slow and error prone. The team is currently working on solving this by allowing the distribution of a \u201cKick Start\u201d pack that will contain all small files and the base assets to start the game minimally. This base pack can then be fetched first, with a multi-threaded range downloader, if you have no pack files on disk. Once the kick start pack is downloaded, a normal delta patch can be applied to bring you to the latest version.\nThe team plans on tracking on base pack file per minor release (semver) of the game, which will always keep it fresh and fast.\nThey\u2019re excited to get this in your hands as they believe this significantly improves the onboarding and update experience of Star Citizen.\n\nANNIVERSARY SALE\nThis month, the Turbulent team brought to life the 2017 Anniversary sale. The sale unveiled two concept ships: the Anvil Hawk a small, light fighter with an emphasis on weaponry, and the Aegis Hammerhead an impressive patrol ship with multiple turrets designed to combat fighters. These two concept ships were just the start, as each day passed they released a chance to nab some your favorite ships, including a limited allotment of the Idris and Javelin.\n\nAlong with this sale, the team created the Observer test, which was your chance to test your knowledge of all-star citizen ships. The test proved to be too easy for our most die-hard fans, however it was still great to see the community brag on spectrum with their gold badges.\n\nSITE RE-DESIGN\nThe team is happy to reveal a new website with the Live release of 3.0. The design and development team have been working hard to tie up loose ends and are extremely excited to release the new designs and continue building on the new and improved platform.\n\nIn addition to the re-design they are taking the opportunity to add a new Production Roadmap. Its purpose is for you, the community to be able to better track the features that are important to you. This is will be vastly different than our text version of the production schedule. Community\n\n\nThe second half of the year is traditionally a busy period for all things Star Citizen and this year was no exception. A lot has happened since the last report back in September with CitizenCon 2947 surely being the highlight on the community side.\n\nAlmost 1000 Citizens gathered in Frankfurt to explore new worlds, experience the latest technologies, get together and speak to the developers of their favorite Space Sim. During the show, Intel showcased their new Optane 9 SSD and with it, the brand-new Sabre Raven. The team also revealed our capital-sized Consolidated Outland Pioneer and with it the new gameplay mechanic of staking your claim and building outposts.\n\nAnother highlight over this month was the release of Alpha 3.0 to the Evocati and eventually the PTU. After burning down the remaining issues and bugs, we released our latest update to a selected group of testers, who helped us to iron out the kinks of 3.0 to release to an even broader audience, the Public Test Universe.\n\nThe team\u2019s continuing to make steady progress on Alpha 3.0 by releasing new builds with our delta patcher and reviewing the improvements made. With the PTU in the community\u2019s hands, the devs are not only polishing features but also addressing the bugs that come in thanks to this expanded group.\n\nEveryone here wants to thank all our testers who helped to make this possible with stress tests during ungodly hours and myriads of bug reports sent in. Keep testing and stay awesome!\n\nAs a special anniversary perk, our Subscribers had the pleasure to take five ships on tour during October, namely the Constellation Andromeda, Aurora MR, Freelancer, Hornet F7C, and 300i. Currently, they\u2019re enjoying the MISC Starfarer & Origin M50 as the two ships of the month. November\u2019s town hall featured Senior Systems Designer Will Maiden, Lead Gameplay Engineer Chad McKinney, and Associate Gameplay Engineer Spencer Johnson as they answered your questions about cargo and hauling. If you missed the show, catch it on Youtube with all our other shows; from Citizens of the Stars and Bugsmashers to newcomers like Xi\u2019an language lessons with Britton Watkins. So, if your response to a \u201c.ath .u m.uexy.oa?\u201d still is a \u201ce yo nai\u201d, you might want to catch up.\n\nLast week, the Anniversary Special kicked off with eight episodes of ATV each highlighting a ship manufacturer. It welcomed some new additions, too: Anvil Aerospace\u2019s Hawk, a light fighter with a diverse arsenal of weapons and the Aegis Hammerhead, a fast and light warship.\n\nTo close this month\u2019s report, here\u2019s a look at what will be next.\n\nMake your vote count! Join our upcoming live stream (12\/1 at 12 pm PST) and help us decide on a Drake ship to add to Star Citizen. If you haven\u2019t yet, also check the new episodes of Galactic Tour and the return of Ship Shape, featured in our ATV Anniversary Specials. We\u2019ll be saying goodbye to 2947 with our Holiday livestream where we\u2019ll focus on Squadron 42and share our roadmap for completion.\n\nUntil then, we\u2019ll see you in the \u2018Verse! WE\u2019LL SEE YOU NEXT MONTH\u2026"},"links_count":0,"comment_count":62,"created_at":"2017-11-30T00:00:00+00:00","created_at_human":"8 years ago"},"meta":{"processed_at":"2026-05-07 23:38:58","valid_relations":["images","links"],"prev_id":16293,"next_id":16295}}