I can't even get to Mission 2. I crash in the tutorial. I finally managed to get past the fleet flyby by turning volumetric settings to low, but it hard crashes with no error message after only a few minutes; changing volumetric simply delays the inevitable. In practice mode it crashes after my first kill. Sometimes it crashes to desktop, sometimes it crashes the whole computer, and I can't tell what triggers the difference. The last full computer crash it did set my resolution down to 1280x720 and produced graphical glitches when I set it back to 1920x1080; I had to restart the computer again to fix it.
Processor: Ryzen 3600
GPU: RTX 2080
RAM: 16GB DDR4
OS: Windows 10 64 bit
Edit: I would attach the crash dump files that I just discovered the game has been putting in my documents folder, but apparently the files are not a supported type for attachment. Which makes no sense, but whatever. Hope this gets patched.
I am also crashing on Yavin right after we take control of the star destroyer. None of the fixes here helped. I literally cannot continue the game.... this is ridiculous.
Also, why is the game locked at 60fps IN VR??? 50% reprojection at 120hz is crazy, even lowering all setting to low doesn't change anything.
Specs:
Valve Index
Ryzen 5 3600 4.25ghz (only about 15%usage)
RTX 2070 Super 1995mhz in game (wont go over 80% usage)
16gb ddr4 3600
Windows 10 Pro
This pc can play Half Life Alyx on Ultra at 120hz without reprojection, so it should be able to play this broken game flawlessly. It's the game not the PC.
This has been happening to me since day 1. I've tried reducing volumetric effects to low. (This is why you need to offer "OFF" options for things. Who cares about game experience if we're doing diagnostics and can't play anyway?) I have also tried verifying game files, reinstalling, etc. etc. etc.
Product:
Star Wars: Squadrons
Platform:
PC
Please specify your platform model.
3900x, 32GB RAM, RTX 2080, game on NVMe SSD, Oculus Quest via Virtual Desktop (also tried non-VR and via Oculus Link with same results). VKB Gladiator K and CH Pro Throttle.
What is your gamertag/PSN ID/EA Account name?
QofDOOM (EA)/MinisterofDOOM (Steam)
Are you playing in VR?
Yes and no
Which part of the game is the issue happening in?
End of Mission 4 (I think?) after the captured Star Destroyer takes out the 3 carriers.
What were you doing when the bug occurred? Step by Step detail is helpful.
Launch game in VR, Continue campaign, load into the Yavin mission at the checkpoint right before Wedge orders the squadron to regroup at the Star Destroyer. Follow, watch Star Destroyer take out the 3 carriers that just jumped in. Game goes to loading screen, hangs, crashes to desktop.
Where did this issue occur?
End of Mission 4, see above
When did this happen? (dd.mm.yy hh:mm)
Repeatedly, including 20201111 at about 1720-1730
How often does the bug occur?
Every single time.
How severe is your issue?
Game is unplayable after this point.
What happens when the bug occurs?
I see the loading indicator in the bottom right, then crash to desktop.
What do you expect to see?
Anything except a crash to desktop.
Which ship were you playing?
X-wing (not applicable as it's not selectable)
What components were you using?
Whatever the mission equpped; singleplayer.
Which customizations (if any) were you using?
Whatever the mission equipped; singleplayer.
Playing on Valve Index with Geforce RTX 2080. Automatic Settings were ultra mode. Consistent crash after captured Star destroyer destroys friendly ships in mission: skies of Yavin. Reducing the Volumetric Quality (not VR) did nothing (put it down until low). Reducing Volumetric Quality VR from "Ultra" to "High" after that fixed the issue. (probably both must be lowered)
--> I believe crash can be consistently reproduced with utra settings in VR - probably the Ultra version of some effect file is missing.
