Let us know if you run into any further issues and thank you again for your continued support.
(PC only) Improving some hitching which can be attributed to streaming raytracing data, assets, and a gap in our prebuilt shaders.īe on the lookout for future patches across all platforms. (PC only) General performance improvements to improve both CPU and GPU utilization while reducing idle time, both with and without raytracing. (PC only) Improving performance on newer i7 and i9 CPUs that have efficiency cores. Added a note explaining that some of BD-1’s abilities are not available while in combat.Īdditionally, here are a few known issues we’re currently investigating and working on for future patches. Fixed a collision bug where players can get stuck inside a Meditation Chamber. Fixed a severe animation issue that would break a late game narrative sequence. Fixed a bug where Rayvis would become unbeatable. Fixed an elevator to prevent the player from falling through it and entering a progression blocked state. Fixed a scenario where the player could enter a progression blocked state in the Lucrehulk. Fixed lightsaber marks not displaying correctly in some scenarios. Audio fix for a narrative moment where music was behaving incorrectly. Fixed an issue where one of the vents did not properly activate in Stone Spires. Fixed a streaming issue that causes some streaming scenarios to end on a black screen. ( PS5 only) Fixed an HDR value mismatch that would cause HDR setups to display incorrectly for PS5 users. (PC only) Updated data handling when toggling raytracing, improving non-raytraced performance. (PC only) Performance improvements for some VFX. 
(PC only) Updated streaming budgets that will help alleviate traversal hitching. (PC only) Updated occlusion behavior for raytracing, reducing idle time stalls. Here are the fixes you can expect with this patch: 
Keep an eye for the latest updates via the Twitter account. PC: Patch expected to deploy as soon as possible this week.PlayStation 5 and Xbox Series X | S: Patch expected to deploy Tuesday, May 9.
0 kommentar(er)
