[quote][b][u]
FOR ME, THE PROBLEM IS FIXED!
YOU CAN FIND THE SOLUTION IN MY COMMENT BELOW
[/u][/b][/quote]
[b]BattleTag:[/b] lol#23482
[b][u]Configuration Info[/u][/b]
[b]CPU[/b]: Intel Core i7-5500U
• Instructions: MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.1, EM64T, VT-x, AES, AVX, AVX2, FMA3
[b]GPU[/b]: Nvidia GeForce GTX 930M (2GB DDR3) Rev. A2
[b]RAM[/b]: 8GB DDR3 - Single Chanel - PC3-12800 (800MHz) CAS Lat. 8-9-10-11
[b]GPU Driver Version[/b]: Nvidia 388.00
• CUDA Driver: 9.1.56
• Video BIOS version: 82.08.46.00.1E
[b]Operating System[/b]: Window 10 Home x64 (10,0 build 16299)
[b]DxDiag[/b] :[url=https://wetransfer.com/downloads/4628820161c87f0bae0a9aa344e44b9420171028085542/284ffdfb6bc256518618c19fe91b4d6e20171028085542/88a967]WeTransfer - Download[/url] (link will be available for 7 days)
• I have included a CPU-Z validation file alongside that DxDiag.txt
[b][u]Issue Information[/u][/b]
[b]Destination/Activity[/b]: Starting Destiny 2 > Waiting at loading screen
[b]Description[/b]: There are 2 main conditional errors I encounter:
[b]1[/b]. [spoiler]When I delete the generated XML file and let the game create a new one at launch, the game tries to rapidly adjust its window resolution to match my screen resolution. Resulting in a flashing screen that shows a black background and then a scaled down black window with my desktop in the background, only to show a full-screen black screen again (in all variants, my mouse is visible as a stroboscope loading-pointer (white arrow with blue circle next to it).[/spoiler]
[b]2[/b]. [spoiler]When I manually change the settings in the XML file, to change from full-screen to windowed mode (by setting windowed_mode to "0"), the game is stuck in the white loading screen with the pattern animation in the middle. I left it running overnight, so I know for a fact it's not just loading slowly.[/spoiler]
-
After reading about all the automated bans that are happening, I wonder if I even want the game to be working. I'm afraid that running Windows 10 in the background might get me banned at this point...