Listen up, Squaddies!
Unreal Engine 5 Public Playtest #5 is coming this Friday, July 11th 11:00am PDT!
THIS WILL BE OUR FINAL PUBLIC TEST FOR UNREAL ENGINE 5.
Here’s what to expect:
You will need to download a special Playtesting Branch of Squad, that has already been released, with access to Servers on Friday around 11am PDT. There will be multiple servers being hosted by Community names that you will know and recognize! Feel free to play wherever you like, but servers will open and close to accommodate the population needs! The general public will not be given access to the Server hosting branch for testing. There is a special Squad Testing Discord that is open to the public. Please be aware that all the normal Squad Community server rules apply in this server as well. Please refer to the onboarding channels for help if you need it!
We have included some known issues in this post, but anything that you come up against can be reported in the previously mentioned Discord Server for testing. Testing will run over the weekend and end on Monday July 14th 11:00AM PDT, and then the UE5 Servers will be taken down. We are also hoping you can take the time to fill out a survey for us, answering some questions about your experience during testing. This will be available IN GAME, in the News Box on the main menu. We will send out a reminder of this later on as well, as it will be accessible through Discord too.
The Important Stuff
In place of a change log this week, we have some information to update you on regarding PiP (Picture in Picture) scopes, from [O] Norby!
"We have a new implementation for the pip scopes. Why is the pip rendering such a big challenge? For high magnification optics like in Squad we need to render two scenes for the different magnification levels. Rendering creates load on the CPU, which is issuing the render commands and on the GPU. In the worst case it cuts the frame rate in half.
Our goal is to have the same frame rate in pip mode as outside of pip. For that we need to address both bottlenecks. For the GPU the most efficient way to gain performance is rendering less pixels. We can do that for the outside scene, since there is a blur effect applied anyway.
For the render thread we have the benefit that we're always looking in the same direction with both views. This allows us to do optimizations similar to VR to reuse resources for both views.
The biggest challenge with this is handling the transition of render states smoothly. We pre-allocate resources when kits are switched and are spreading some of the transitions over multiple frames to reduce hitching."
-Norby
We did add a bunch of fixes that came in since the last playtest, but we will be saving those for the Patch Notes of the 9.0 release, once it arrives. We are aware of a few persisting bugs, including some hitching during ADS animations, some black frames inside PiP scopes, and an issue where a portion of the PiP screen can get duplicated.
Join the discussion in Discord, and we hope to see you over the weekend!