Fiya
November 19th, 2020, 13:32
Hi, my Fantasy Grounds Classic stalls on a white screen on trying to initialize the program. I've spent a few days poking around the forums at similar issues that have been resolved in the past. I became aware of the issue after a windows features update, that I haven't been able to revert from. I also updated my graphics driver during this time, but I've rolled back several iterations of graphics drivers with no observable change.
• I don't have Duet installed
• I've run through several iterations of graphical drivers
• I've reinstalled windows
• I've deleted my installations of Fantasy Grounds and completely reacquired files.
• I've verified my installations of DirectX and .Net Frameworks.
My console.log looks like this,
[19.11.2020 13:23:14] Runtime Notice: Initializing DirectX
[19.11.2020 13:23:14] Runtime Notice: Initializing COM
[19.11.2020 13:23:14] Runtime Notice: Fantasy Grounds starting
and does not progress unless the program is terminated. The console.log updates with an exit line upon program termination.
[19.11.2020 13:26:31] Runtime Notice: Fantasy Grounds exiting
I'm trying to roll my windows installation back from the features update, but if I'm overlooking something please inform me of that.
I've attached a DxDiag.txt output
Thanks
Edit 1: Reverting to previous version of Windows did not resolve the issue.
• I don't have Duet installed
• I've run through several iterations of graphical drivers
• I've reinstalled windows
• I've deleted my installations of Fantasy Grounds and completely reacquired files.
• I've verified my installations of DirectX and .Net Frameworks.
My console.log looks like this,
[19.11.2020 13:23:14] Runtime Notice: Initializing DirectX
[19.11.2020 13:23:14] Runtime Notice: Initializing COM
[19.11.2020 13:23:14] Runtime Notice: Fantasy Grounds starting
and does not progress unless the program is terminated. The console.log updates with an exit line upon program termination.
[19.11.2020 13:26:31] Runtime Notice: Fantasy Grounds exiting
I'm trying to roll my windows installation back from the features update, but if I'm overlooking something please inform me of that.
I've attached a DxDiag.txt output
Thanks
Edit 1: Reverting to previous version of Windows did not resolve the issue.