February saw Cloud Imperium devs around the world working hard to deliver the incredible content for the soon-to-be-released Alpha 3.5 patch. Progress was made everywhere, from locations like ArcCorp to the gameplay developments afforded by the New Flight Model. Read on for the full lowdown from February’s global workload.
Star Citizen Monthly Report: February 2019
AI – Character
February’s roundup starts with the AI Team, who made improvements to the existing character collision avoidance system. The changes began with adjustments to the smooth locomotion path, with the data now coming from the collision avoidance calculation to make sure the character has enough free space.
Time was spent generalizing the options a vendor can use so that designers no longer have to write them into the behaviors. Instead, the correct options are automatically selected based on the environment and (eventually) from the shop services.
They’re also restricting combat behavior to allow better scalability when adding new tactics and are investigating some of the bugs found in the Alpha 3.4 release.
AI – Ships
Throughout February, the AI Team improved various aspects of dogfighting gameplay, including evasive maneuvers. Now, when an AI pilot has an enemy on its tail, it will try to utilize different break-aways with increasing and varied angles. It will also try to keep momentum and chain together attack maneuvers. To achieve this, the team exposed new ‘SmoothTurning’ subsumption tasks to the behavior logic.
When detecting enemy fire, AI pilots will utilize evasive maneuvers to create a diversion.
They also implemented automatic incoming/outgoing ship traffic over planetary landing areas. They are currently generalizing ship behaviors to enable the designers to easily set up traffic on multiple cities, capital ships, and so on.
Last month, Animation provided the remaining animation sets for previous characters already found in the Persistent Universe (PU), including Hurston, Battaglia, and Pacheco. They also finished off a new batch of animations for the ship dealer. Work continues on animations for future yet-to-be-announced characters too, which includes getting approval for the initial poses and animations before going forward with the final clean-up.
American Sign Language (ASL) emotes are being added to the game and are currently being improved with the addition of facial animations.
Finally, Animation is currently syncing with Cinematics for a few interesting segments that backers will get to enjoy soon…
Art – Tech
Tech Art invested significant effort into optimizing rig assets so that they work better with the facial runtime rig logic and the ‘look at’ and ‘mocap’ re-direction components. Since eye contact is one of the fundamental means of human communication, any error or tiny deviation can cause the ‘uncanny valley’ effect and immediately break immersion.
“If the eyes of an actor converge just slightly too much, they appear cross-eyed. However, if they don’t converge enough, they appear to look through you, as if distracted. If the eyelids occlude the character’s iris just a little too much, which, depending on the distance, could amount to just 2-3 pixels vertically, they look sleepy or bored. Conversely, if they expose too much of the cornea, they appear more alert, surprised, or outright creepy.”
So, the alignment of the virtual skeleton’s eye joints with respect to the eyeball and eyelid geometry is of utmost importance. Likewise, the ‘look-at’ system needs to control all relevant rig parameters and corrective blendshapes (not just the rotation of the eyeballs themselves) to create truly-believable runtime re-directions of the mocap animations.
Alongside facial work, the team completed several weapons-related tasks, such as fixing offsets during reload animations and locomotion issues for the pistol set. They also completed R&D related to playing animations in sync with character usables within cinematic scenes and helped Design to unify the character tags in Mannequin.
Art – Environment
Predictably, the Environment Team is racing towards the completion of ArcCorp and Area 18 – they’re currently working with and implementing the custom advertising provided by the UI department. The planet itself is in the final art stage and now includes skyscrapers rising above the no-fly zone to provide the player with landing opportunities and interesting buildings to fly around.
Concurrently, the ‘Hi-Tech’ common elements are steadily progressing, with the transit, habitation, and security areas all moving to the art pass stage. Players will see these common elements (alongside garages and hangars) when they’re added to microTech’s landing zone, New Babbage.
The new transit connection between Lorville’s Teasa spaceport and the Central Business District (CBD) is almost ready for travellers. This route will allow players to move directly between the two locations and bypass L19, cutting travel time for high-end shoppers.
Work on organics is ongoing, as are improvements to planet tech, with the artists hard at work creating a library of exotic-looking flora to fill the biomes of New Babbage with. Players can see it for themselves towards the end of the year.
The community can also look forward to upcoming information on the early work the team has done on procedural caves.
Both the Audio Code Team and the sound designers finished their work on the new camera-shake and ship-vibration systems. Now, when an engine kicks in, the ship shakes and hums. This also extends to the player, with events like a ship powering up causing minor camera shake.
The sound designers also added new sound samples to a range of ships as part of the rollout of the New Flight Model. By adding ‘one-shot’ samples to each of the various thrusters, they brought out more complexity in the sounds heard during flight.
The Audio Team spent the majority of the month creating the sounds of Area 18. Due to the melting pot of ideas and themes present in the new area, the sound designers tested new methods to bring out the unique atmosphere. Additionally, they created the sound profiles and samples for the Gemini S71 assault rifle and Kastak Arms CODA pistol, both of which will appear in the PU and SQ42.
Currently, the Audio Code Team is working towards an updated tool that better allows the sound designers to implement created assets in-engine whilst simultaneously testing how they sound.
Backend Services continued to lay the foundation for the new diffusion network to help scalability for the backend structure of the game. Emphasis is on ensuring the Dedicated Game Servers (DGS) correctly connect to the new diffusion services, particularly the variable, leaderboard, and account services.
February marked the near-end of work on the new Item Cache Service (a massive portion of the backend has now turned micro-service) and began the end-point between DGS and this service, too. As work is completed on the new diffusion services, testing will ensure a smooth transition to the new network.
Support was also added for subsumption services to read directly into the DataCore P4k system for increased efficiency and unification.
With the approaching publish of Alpha 3.5, Backend Services began work on logistics, syncing closely with DevOps to ensure that new services are up and running correctly while maintaining legacy services where necessary.
The team celebrated Valentine’s Day with community-made cards and limited-time ship offers, including Anvil’s F7C-M Heartseeker – a special version of the Super Hornet shooting straight for the heart. During the Be my Valentine greeting card contest, most Citizens got creative with their favorite image editing software, though some went old-school with scissors and crayons to create fantastic crafts to share their love across the galaxy.
Also this month, Argo Astronautics released their latest addition to the ‘verse, the SRV. The ‘Standard Recovery Vehicle’ is built for tugging ships, ground vehicles, and massive cargo containers through the stars using its integrated tractor tech. If you’re looking for more information about this rough and rugged ship, head to the Q&A that answers questions voted-on by the community. As a bonus, Shipmaster General John Crewe stopped by Reverse the Verse LIVE for some in-depth tug-talk.
In the February issue of Jump Point (our subscriber-exclusive magazine), Ben Lesnick took a detailed dive into the ARGO SRV’s design process and went on a worker’s tour of Hurston. The Narrative Team also introduced us to the Human holiday Stella Fortuna and shed light on the history of the revered Rust Society.
A major update to the Star Citizen roadmap gave a look at what’s coming to the Persistent Universe in 2019 and what can be expected in upcoming releases.
Released in January, but worthy of another mention, is the official Star Citizen Fankit, which was put together to help all of you share your enthusiasm and engagement. Star Citizen lives by the support it receives from the community, so take a look at this treasure trove of assets and get creating!
The team is also excited to announce that our physical merchandise will soon be receiving a well-deserved face-lift. Having received a lot of feedback over the years, it’s clear that Citizens are passionate about merch and to make the store experience the best it can be, your input was needed. Thanks to everyone who contributed feedback to our thread on Spectrum!
Content – Characters
The Character Team revisited the hair development pipeline in February. With the help of the Graphics Team, they developed new tools and shader tech to improve the realism of hair while maintaining quality and performance. More work went into mission-giver Pacheco, including textures and rigging, with her hairstyle being used to trial the new hair pipeline. Work continues on the assets required for DNA implementation and the female player character, while refinement of the Xi’an concept is making great progress.
Throughout February, Design focused on implementing Area 18’s shops, NPCs, and usables. Last month marked the end of implementation, with March being used for polish to ensure a believable and immersive experience upon release. The team also gained a new member to help with mission implementation and improvement, who is currently setting their sights on the Emergency Communication Network (ECN) mission set.
Regarding the economy, the US Design Team worked with their UK counterparts on the objective criteria and value of objects in-game, laying down the track for acquiring item properties and their values. A system was built to help create an abstract representation, which is both robust and modular enough to allow easy adjustment in the future when the details are finalized.
DevOps had a busy month working on the build system and pipeline that supports feature stream development. After several long nights, they rolled out the upgrades and have been happy with the results so far – internal systems are running smoothly without errors and each evolution improves efficiency and storage consumption.
They’re now attempting to further compress existing data which, when multiplied by hundreds of thousands of individual files, will make a real impact to the dev’s daily development efforts.
February saw the Engine Team spend time on general Alpha 3.5 support, such as profiling, optimization, and bug fixing. They also improved the instance system used in compute skinning and refactored it on the CPU and shader for better maintainability, created a budget-based output-buffer system for skinning results (so they only have to skin once per frame), made more tangent reconstruction optimizations, and worked on wrap-deformation using the color stream.
Basic HDR display support was added to the editor, as was a new hue-preserving display mapping curve suitable for HDR display output. The team provided material layer support for planet tech v4 and continued to improve character hair, which included initial hair mask, support for edge masking, and pixel depth offset. Game physics is progressing with Projectile Manager 2.0, as well as optimizations to wrapped grids and state updates. Support was added for ocean Fast Fourier Transform (FFT) wave generation to physics buoyancy calculations, as well as exposed optimized terrain meshes.
A major system initialization clean-up was completed as part of an initiative to share core engine functionality with PU services, work began on the lockless job manager (a complete overhaul for faster response in high-load scenarios), and a new load time profiler was created. The team are currently wrapping up the ‘ImGUI’ integration and introducing a temporary allocator for more efficiency when containers are used on stack.
They made the switch to the Clang 6 compiler to build Linux targets (including compilation cleanup of the entire code base) and plan to switch to the latest stable release (Clang 8.x) in the near future.
Finally, they finished a ‘create compile time’ analysis tool (utilizing new Visual C++ front and backend profiler flags) to gather, condense, and visualize reasons for slow compile and link times. As a result, various improvements have already been submitted and further action-items defined.
Features – Gameplay
A large portion of Gameplay Feature’s month was dedicated to implementing the new DNA feature into the character customizer. In addition, the team was responsible for creating and setting up the user interface (UI) and accommodating the female playable character, both of which are scheduled for Alpha 3.5.
Another major focus was on video streaming for comms calls, which consisted of a refactor of the comms component to utilize the voice service call mechanism. Research was made into the VP9 streaming format and video streaming improvements were completed that will be rolled out in the upcoming release.
Lastly, support was given to the US-based Vehicle Features Team, with updates to the turret sensitivity HUD, gimbal assist UI, and the shopping service entity registration.
Features – Vehicles
Gimbal Assist and its related HUD improvements were finalized and polished, allowing for better balancing of this new weapon control scheme. Turrets were also improved, as the team added a HUD and keybinds for input sensitivity, implemented adjustable speeds for gimbal target movement based on proximity to center aim, and fixed bugs with snapping and erratic movement.
A lot of work went into scanning improvements, which included adjusting the area for navpoint scanning, enabling use of the navpoint hierarchy, and adding a Boolean to opt into the scanning data. This endeavor also covered adjustments to make scanning more involving by setting up AI turrets to generate signatures and be scannable and adding specific icons for scanned/unscanned targets. Ping and blob were implemented to display on the radar too, including focus angle and ping fire.
To round out the month, they continuing to make item port tech optimizations, developed tech for utilizing geometry component tags in the paint system, and fixed a handful of crash bugs.
Last month, the Graphics Team’s work on the PU was spread between several smaller tasks. There were many shader requests from the artists, such as adding new features to the hard surface shader and ISO support for decals in the forward rendering pipeline.
The team also continued with the CPU optimizations from last month. This included a 3x performance saving on the cost of building per-instance data buffers for the GPU and better support for the depth pre-pass to help occlude hidden parts of the frame with less CPU overheads.
To help the artists optimize their content, the team worked on an improved render-debugging tool that reports how many draw instructions (draw-call) a particular object requires along with a breakdown of why each instruction was needed. Once complete, this will allow the artists to dig into their material and mesh setups to save valuable CPU time.
The Level Design Team soldiered on with ArcCorp’s Area 18, bringing the designer whitebox up to greybox. They began planning the modular space stations that will be built this year too, including looking at the libraries, rooms, and content that goes into them. The procedural tool is also now at a stage where they can slowly start ramping up the modular station production.
The Live Team refactored existing missions to make them scalable to make more content available in the planetary system (other than Crusader). Significant progress was made on a new drug-stealing mission for Twitch Pacheco, as well as a BlackJack Security counter-mission that tasks less morally-corrupt players with destroying the stash.
Another focus was on implementing a variety of encounters with security forces and bounty hunters when the player holds a high crime stat.
As well as practical work, time was taken to define the next tier of many aspects of the law system, such as punishment, paying fines, bounty hunting, and so on.
Last month, the Lighting Team focused on developing the look of Area 18. Lighting Area 18 is a mixture of clean-up work from the previous versions to match new standards and lighting the new exterior layout to a series of targets set by the Art Director. The team is working closely with the Environment Art and VFX teams to ensure that new advertising assets and visual effects ‘pop’ from the environment and provide interesting and varied visuals.
Working closely with the Environment Art and Mission Design teams, February saw the Narrative Team further fleshing out of lore relating to ArcCorp and its moons. From new mission giver contract text to the catchy slogans gracing Area 18’s numerous billboards, a lot of additional lore was created to bring these locations to life.
Additionally, expanded wildline sets for security pilots, bounty hunters, and combat assist pilots were scripted and recorded. The AI and Mission teams will use these sets to begin prototyping and testing out new gameplay for inclusion in future builds.
Also, the Narrative Team made progress on generating the specific text needed for on-screen mission objectives. Currently, this is placeholder text from the designers who worked on levels, but moving forward, the hope is to begin using the proper in-lore objectives.
The Player Relations Team was busy preparing for Alpha 3.5 (including getting ready to test the New Flight Model) as well as boxing off the work created over the holiday period.
“As always, we’d like to point all players to our growing Knowledge Base, which now has 120+ articles and saw almost 450,000 visitors this month! We will continue to grow this by adding more ‘How To’ articles, patch notes, and live service notifications there as well as on Spectrum.”
February saw headway into Area 18’s props: the core street furniture is now in and the team has moved onto the dressing pass, adding in new assets to give life to the streets, alleyways, and landing zone.
As the month closed out, the team jumped into release mode to get a head start squashing bugs and generally tightening up the upcoming release.
Things ramped up on the publishing side in February as the team prepared Alpha 3.5 for the Evocati and PTU. Testing continues on the New Flight Model and other systems as they come online, such as the new weapons, ships, and locations. QA leadership continues to train the newer testers and improve the overall testing process.
The AI Feature Team kept the Frankfurt-based QA testers busy with new features, such as the improved avoidance system and new break-away maneuvers. Testing mainly consists of making sure they’re working as intended, as well as noting visible improvements to what was already in place (in the case of the avoidance system). Combat AI received perception updates which were tested by QA to address issues where the FPS AI would not recognize the player being present in their vicinity.
On the backend, changes to the subsumption visualizer are being tested to ensure no new issues have been introduced in preparation for their full integration into the editor. Testing for ArcCorp and Area 18 is currently underway too.
The Universe Team discovered that mining entities were not appearing in the client due to discrepancies in how they were spawned in the server. This was tracked down and fixed, though testing will continue to make sure it’s working as intended.
The Vehicle Content Team wrapped up the MISC Reliant Mako, Tana, and Sen variants for Alpha 3.5. They’re now in testing with QA who are addressing bugs before the vehicles go live. The designers and tech artists have been busy with the Origin 300i, which will reach QA for testing in the near future.
Back in the UK, the team continued production on the 890 Jump, bringing more rooms into the final art stage from greybox (including the hangar area). The Carrack is heading towards a greybox-complete state and select areas are being polished for review.
Development continues on the Banu Defender which is utilizing a new style of production that caters to its organic art style. ZBrush is being used to sculpt the interior before transferring the high-density model to 3ds Max, where it is then rebuilt (low-poly) for the game engine. A large portion of the exterior greybox is complete and looking fantastic.
Last but by no means least, the interior updates to the Vanguard wrapped up with essentially the entire area from the cockpit seat backwards being completely redone. This is more than was initially anticipated, but the team feels that it’s worth it. Now that the interior rework has been finalized and the framework for the variants agreed upon, the Ship Team can start on the exterior changes to accommodate them and continue with the variant-specific items.
The System Design Team is working on improving and upgrading the no-fly zones used across ArcCorp. Since the existing system now needs to support an entire planet, it has proven quite a challenge.
For social AI, the team’s working on unifying vendor behaviors and making sure they’re built in a modular fashion. For example, the team can easily graft new actions onto the base behavior of a shop keeper to allow them to pick up objects, give them to the player, and interact with things on the counter without having to build new ones from scratch.
As with social AI, the team focused on restructuring FPS AI behaviors to make them more modular, with the goal to make it easier to implement specific chunks of logic. For mining, they added new mineable rocks on ArcCorp’s moons. Wala in particular will have a new type of rock that fits better with the crystalline formations available on the moon.
Finally for System Design, AI traffic over Area 18 is currently being developed. The team’s starting small, with a few ships landing and taking off around the spaceport, but they’re also investigating ways to expand it while being mindful of performance.
RSI Platform: On February 14th, Turbulent supported the announcement of a new flyable variant of the Super Hornet, the F7C-M Heartseeker. They also made major updates to the CMS backend which required all hands on deck.
Services: This month’s game service work was focused around developing support for transporting video streams over the comms channels. This will allow the streaming of a user’s face/in-game texture to another player outside of the bind culling bubble, enabling in-game video calls over wider distances. This method also enables the transmission of in-game video streams to web clients.
Turbulent spent considerable time standardizing services to enable them to run within a new local development environment. This will allow the entire Star Citizen universe’s services to run locally on dev systems to develop and iterate with the entire stack.
The Turbulent Services Team also began work on an administration interface for game designers and game operators to display real-time information about the state of the universe. This application can display information about groups, lobbies, and voice channels along with details of online players, quantum routes, and probability volumes.
As in January, UI supported the Environment Team with in-fiction advertising and branding for Area 18, including animation and hologram textures. They also made headway on the 3D area map using the concepts shown last month as visual targets. Finally, they began working out how to bring the rental functionality from the Arena Commander frontend to in-game consoles in Area 18.
The VFX Team updated the existing particle lighting system to a more modern system. The previous version was based on tessellation, which increased the rendering cost and had limitations on shadow resolution. The new one is a global change that will remove the need for tessellation and improve shadow receiving for crisper, smoother shadows. ArcCorp’s Lyria and Wala will be the first moons to use this new particle lighting system when it’s ready for deployment. It will help the particles integrate into the moons more realistically and address issues when the particles have long shadows going through them, such as during sunrise and sunset.
They also continued to iterate on thruster damage effects and began rolling it out to all ships.
Several new weapon effects were worked on, including a new ballistic hand cannon and ballistic assault rifle. They also carried out extensive visual exploration for the new Tachyon energy weapon class.
Finally, significant time was invested in improving the VFX editor’s UI layout and functionality. Although not as glamorous as planet dressing and effects, improving the quality-of-life for artists is important and helps them to work faster too.
The Weapon Art Team completed the Gemini S71, Kastak Arms Coda, Banu Singe Tachyon cannons, Gallenson Tactical ballistic cannon reworks, and five variants of the Aegis Vanguard nose guns.
The Public Test Universe, or PTU, is a replica environment of all servers needed to operate the game and the platform. This environment exists to allow public testing phases of unreleased patches of the game and platform. This environment will be publicly available to players, but under tight access control.
Access to the PTU requires an invitation, handled in waves, to control the amount of players in the environment based on testing needs. The PTU also includes the Evocati Test Flight group, an advance team of player testers.
HOW DOES THE PTU WORK?
The PTU will be started up when a patch is nearing task implementation lock. Development Operations (Opds) will select the best working build and deploy it to the PTU servers. Then players and internal staff (QA, Development, Ops) will access the environment for testing.
The PTU is managed by testing “phases”. A testing phase includes a date range for testing, set features per release and build, and wave invites for required account badges. The PTU is not always available. We only open the PTU servers when we have release candidate builds to test for an upcoming release.
PTU INVITES AND WAVES
The PTU is designed to be a staging environment where we can deploy builds for external players to test before it goes to the Live servers and general availability to all alpha players.
These early release candidates are builds with new features, new ships, bug fixes, and in-progress updates to existing features. Be advised of the following:
These early builds are not complete and require extensive testing. To help with player feedback and aid in stress-testing performance, features, and fixes, we push the builds to the Public Test Universe servers and open invite waves as needed for that testing.
These builds are not ready for prime time, Live access. They require multiple rounds of code revisions, internal tests, and bench marking to find the right mix of difficulty, performance, stability, and play-ability.
We may push builds to the PTU daily to weekly. Depending on updates from design, development, and QA verification, we may update the PTU servers and game code as needed. When you run the Launcher, it will check for updates.
Updates may require wipes of PTU accounts. If you push your account to the PTU, you will not lose credit for your reports to Issue Council. These may not be in your report links. Don't worry, we still see them linked to you internally.
As part of this process, we learned that the signal-to-noise ratio for the early iterations of a build was far too low. Sifting through the mountains of data on our forums that thousands of players would provide in order to find information that would help us make the build better was a logistical nightmare.
This led us to create the Evocati Test Flight organization and test group. We then schedule waves of invites to the PTU for Evocati and players-at-large, increasing access as needed by development, designers, QA, and operations to test all aspects of the release candidate builds.
Example PTU post
EVOCATI TEST FLIGHT
We determined having a small group of technically-minded players hammering away on the early builds would provide far more accurate data to focus development and testing efforts. This group became Evocati Test Flight, lovingly called Avocados.
The Evocati are a small group of testers we’ve selected from the top players participating in Star Citizen: contributing to Issue Council, racing, running missions, and more. When joining the Evocati, we require a signed NDA (Non-Disclosure Agreement) and work through the process to add members to the Evocati Organization.
They can access the in-progress builds deemed “not quite ready for normal PTU” either due to issues in-progress, features being considered for release, and verifying updates before general release that might be removed depending on how the testing goes.
PTU INVITE WAVES
Once a build is stabilized and features are completed, we then roll that build out to a wider audience. The current PTU release format is as follows (numbers will change per PTU):
Evocati (800-2,000 invites): Our smallest group of testers who help us get our releases ready for a proper public viewing more quickly! Picked from Issue Council posters with multiple submissions or contributions and from our most active PTU testers.
Wave One (6,000 invites): Approximately 1,000 accounts from participating on Issue Council with one New Report and one Contribution, plus 5,000 accounts who have played more than five PTU builds in the last three months.
Wave Two (12,000 additional invites, 18,000 total): 12,000 accounts who have played three to five PTU builds in the last three months.
Wave Three (16,000 additional invites, 34,000 total): 16,000 accounts who have played two PTU builds.
Wave Four (80,000 additional invites, 114,000 total): 80,000 accounts who have played one PTU build in the last three months.
Wave Five: Open to all.
THE PTU IS LIVE AND I GOT AN INVITE! WHAT DO I DO?
When a PTU is live, we post to a new forum in Spectrum. This post will provide information on the play test, links and instructions for any special Launcher and game installation, and any special information you need on the play test.
Copy your account to the PTU environment.
Visit our site and login to Account.
In your account page, click Public Test Universe.
Click Copy account to PTU to copy your current account information.
If you add ships or make changes to your Live account, or you have issues in PTU, you may need to erase and recopy your account to the PTU. When you do, any Issue Council entries on the PTU Issue Council won't show up on your account. Don't worry, we still see them associated to your account.
We provide a PTU RSI site for:
PTU account access if you need to change your password through Account Recovery
PTU Issue Council
PTU Spectrum for chat
When you copy over your account to the PTU, your ships, equipment, and account information transfers from your Live account. The following items do not carry over to PTU: Authenticator settings, rentals, REC, UEC, and flair items. Anything you earn on the PTU does not carry back over to Live.
RECOPYING YOUR ACCOUNT!
During the course of PTU testing, you may need to recopy over your account from Live. You can do this anytime through the Live RSI site. This will send a different password. Your entered Issue Council reports may not be linked to your account anymore, but don't worry! We still see you as the reporter in our systems.
I WANT TO TEST, HOW DO I GET INVOLVED?
These are the best ways to get involved to receive invites:
We accept testing reports on Live and PTU. As you find bugs, issues, and crashes with the RSI Launcher and game, you can use the Issue Council to report them!
Watch for Spectrum posts requesting help and information on specific issues from CIG.
Play the game, extensively, deeply, for enjoyment but also to provide insight back to CIG on gameplay.
We track all involvement to determine our invitation lists for Evocati and PTU waves!
HOW DO I GET A PTU INVITE?
When the PTU is up, we will create a forum and post information in Spectrum. We keep a forum post updated on PTU invites and waves. Please check that post for updates on the PTU! We also post known issues, test requests for the community, and Issue Council links we may need for specific player involvement.
The ARGO SRV depicted in the image is carrying an unknown-sized cargo container. Please elaborate more on this cargo-carrying function. Is the SRV envisioned as one of the tools used to load/unload the larger HULL series ships?
One of the key design goals for this ship was to enable it to carry cargo around. Unloading larger cargo ships, such as the Hull series, is a perfect use of the SRV.
This is not explicitly stated in the documentation, but the ARGO SRV has a Quantum Drive and a Jump Drive. Can the SRV tow a ship in Quantum Travel? Can the SRV use a Jump Point when towing another ship?
The ARGO SRV can Quantum Travel while towing.
Whilst the details of Jump Travel are being ironed out, the original design never accounted for this scenario and requires revisiting. However, our current stance is that it will not be able to tow ships through a Jump Point. If such travel is needed, we recommend towing the vehicle to a nearby repair station first or putting it inside another jump-capable vehicle.
Can the SRV move ground vehicles like a Nova Tank?
There is nothing to stop you moving damaged or stuck ground vehicles, such as the Nova Tank. It will work the same way as moving and transporting damaged spaceships.
Can the SRV move outpost modules?
No, outpost modules are physically drilled into the ground surface. The moving of player-made outposts is restricted to the Pioneer and other dedicated ships as the SRV’s tractor beam is not strong enough to wrench them from the surface. Outposts that exist already on moons/planets cannot be moved.
Can the SRV tow asteroids?
Physicalized items in the world can be manipulated if they’re within the mass range of the tractor beam. Currently, the only dynamic asteroids in the game are the mineable variety, though it will be possible to tow these asteroids around if desired.
Can a person in a space suit be towed?
Capturing an item requires it to be relatively immobile and of a certain size so that the beam can focus on it. While we don’t have the exact details of these limits yet, we foresee that active players will not be easily trapped by tractor beams to prevent griefing.
Is the number of SRVs needed to tow something based on total mass or size/architecture?
It is primarily mass based, though there are some size and volume requirements. There are no arbitrary design restrictions in terms of ‘ship X can specifically not tractor ship Y’.
How will theft using tractor beams be guarded against? Can anyone just fly up to you and start abducting ships?
The current means to limit theft and griefing is that shields will actively block or severely dampen the tractor beam strength. If you wish to have your vehicle moved, you will be required to power down your shields (which also puts you in a vulnerable position). If you wish to guard against theft, just leave your shields up when outside your ship for reassurance that it will still be there when you get back.
Does the tractor beam only pull or can it push as well?
The tractors beam is primarily designed to pull, though it can push to an extent. Moving from side to side, rolling, and pitching are accomplished by the range of motion available to the tractor beam’s mount.
Does towing affect the SRV’s top speed and fuel economy?
Tractor beams consume massive amounts of power, so while the ship’s top speed is still attainable, acceleration and fuel economy are negatively impacted.
Will vehicles being towed have to turn off components for it to be towable, such as shields and power plants?
Yes, the target needs to be relatively immobile with shields powered down for the tractor beam to ‘capture’ it. If the target is actively jinking or maneuvering to avoid it, the SRV pilot will require significant skill and time to capture it.
If an SRV is immobile but still has a working tractor beam, can it use its tractor beam to lock onto another ship and then be towed by that ship?
Theoretically, it is possible for this to work. However, the non-tractor ship would have to maneuver very cautiously and gently to prevent it from breaking away.
Does the tractor beam only work in space? Or, is it possible to tow a ship from a landing pad, take off, go into space, Quantum Travel, enter a planet’s atmosphere, and finally land while towing another ship?
The Tractor Beam can be used in any location, however the environment will affect the difficulty of maintaining a capture of the target item. Another one of the original design aims was for the SRV to act as a tug ship to help larger ships get from a planet’s surface back out into space.
Will it be possible to extend the Argo SRV’s shields around the ship that’s being towed to offer extra protection when extracting disabled ships from the battlefield?
No, the shields from the ARGO SRV and all other ships in the game are currently just for the ship itself and do not cover nearby objects. Towing a ship or vehicle puts it at risk, so the environment and flightpath should be considered carefully by the SRV pilot.
There is mention of it being heavily shielded and armored. How can we expect it to hold up under combat zone conditions?
The SRV carries no offensive weaponry so relies on its shields and armor to survive in combat, so if it’s being directly attacked, the best course of action is to break away and come back later. If you’re entering a known hot zone, I’d recommend bringing an escort along for support.
Does the roof dish provide scanning abilities for search and rescue?
The dish on the roof is simply a visual styling cue and has no specific gameplay attached to it. As mentioned on RTV, we went back and forth over the name during development. At the time ATV was recorded, it was known as the ‘Search and Recovery Vehicle’. However, we have now settled on ‘Standard Recovery Vehicle’.
So i've had my Hammerhead out of the barn for more than a few test flights now and I've encountered a MAJOR problem. I like flying it more than my Connie's. I can't get over how comfortable I am with the design, especially the bridge layout. I thought for certain that being slung on the underside of the ship with no visibility above was going to be a huge disadvantage The more I fly it though, the more practical it seems and the more I feel like it's the best design out there. When I would fly the Connie I loved the feeling of being strapped to the front of a cruise missile. In the Hammerhead, it feels like being strapped to the front of a nuclear warhead.
I have located multiple engineer stations, which is amazing foresight on the designers part. And I've parked it in orbit of a planet and run around to all the turrets checking sectors of fire and looking for blind spots. There aren't many. She also carries a fair bit of cargo so this almost seems to be the ideal ship for hauling that high dollar cargo, or definitely choice for resupply to the capital ships.
If anyone wants a ride, please let me know. We will link up and I'll happily take you out for a spin. We can set course for Arc Corp and run around while in transit.
A few of the S&E leads and team are meeting up on the 24th of this month starting between 7-8 GMT for a few hours looking at ships, general chat, mess around in the verse etc all welcome come and join us.
It up to you. If you have the money, do you plan on melting the other ship to help pay for the new ship. Do you want LTI, do that matter to you.
Upgrading, you keep everything in the base package you are just changing the ship. So that all flair and insurance. If you melt it down the road you get all the money, but you can only buy back the base ship. So no good if you ever think you might melt it later and us that money to try a different ship. As you cant get it back, you have to wait until it on sale again.
If you buy a new ship, well it a new ship.
Warbond is new money only. So if you are planning on melting the ship and putting it to the new ship, you will have it without LTI (if that matters to you). You can always buy back the ship if melted down the road and you change your mind.
But it more down to where you are and what you are trying to do. It is no right answer, it more down to you and what you want out of it.
Thanks all. Well, I feel bad without my Carrack so I now wait for my buy back token in march to re-buy it. I used the January one for my Hoplite. Will use a 300i for luxury personal touring, but that Carrack just still catches my eye as a one stop shop ship for that Enterprise feeling. The 600i is pretty, but the more I fly around in it the more I find it limited to a single purpose.
I expect to wrangle up some org members for crew though Since AI aren't the best for conversation. Not a good Enterprise style adventure with only a bunch of Datas.
Later I realized my 9900k heat issues were strictly voltage regular module (VRM) related, and the blowup I had was actually caused by a faulty component (although I blamed myself for walking away while on Prime95, it would have happened regardless). I purchased an Aorus Gaming Master with a more robust VRM for the 9900k, and that resolved my problem. I still kept the Aorus Gaming 7 with the 8700k and am now using it as my streaming rig over the network via OBS/NDI.
The 9900k is running a custom loop at 5.2 Ghz on all eight cores, the 8700k is running at 5.0 Ghz on six both with low thermals. I could push them further, I just do not see any real difference on benchmarking/gaming on either rig. I'm running two extreme overclocked 1080tis on the 9900k so the only thing that could pass these benchmarks on the GPU side are two 2080tis and I just do not feel that is reasonable considering pricing.
Summarized: In having both, I really do not see a difference in gaming between the 9900k and 8700k. If I set them to the same frequency, they are pretty much identical in performance in most gaming titles. Productivity-wise the 9900k takes the cake with those two extra cores and runs a little cooler with solder. The 9900k also seems to be more stable at high frequencies as well, acting more like a bin product (8086k). I almost get the feeling intel's design brief for the 9900k was taking the 8086k material and production process and squeezing in two extra cores with solder.
In BFV multiplayer, I'm at the limit of my 165 refresh 99% of the time with medium settings (droops when V-1s land near me).
I kinda envy people who have the creativity, resources and dedication to put this kind of thing through. Sadly I consider myself to play too big of a variance in games to pull stuff like this off. looks great though.
Freelancer Dur - stated scu 28 - actual 36! Just added a very capable explorer that can double up for light cargo runs.
Freelancer Max - stated scu 122 - actual 120 An excellent cargo hauler that can cope in a more hostile environment.
Having now flown the Max, I think it needs the following comments:-
1) The top speed is 210 - not the 205 of the other models.
2) Rear Door still has no lock on it.
3) Controls are a pain to use in the cockpit - Using the F key it's stupidly hard to click anything. I have to use shortcuts on the keyboard mostly.