Wed Mar 22 05:33:41 2023 UTC - Modules at GameOverlayRenderer.dll attach Wed Mar 22 05:33:41 2023 UTC - Hooking SetCursorPos, GetCursorPos, ShowCursor, SetCursor, and GetCursor Wed Mar 22 05:33:41 2023 UTC - Failed loading shell32.dll, not hooking ShellExecute calls Wed Mar 22 05:33:41 2023 UTC - Module file name: C:\Program Files (x86)\Steam\gameoverlayrenderer.dll When Terraria is launched for the first time, this log file looks like this: The most significant, is the “C:\Program Files (x86)\Steam\GameOverlayRenderer.log” file. If I happen upon a solution there, I will come back and update this thread.Īnyway, I thought it would be valuable to call out some items I’ve seen after going through this process. As for the reverse…applying those changes to the computer prior to the first launch (after restoring the checkpoint)…that is still on the to-do list. I believe I’ve chased them all down, but undoing those changes individually does not result in the Steam overlay being broken again. I have tried using a “whatchanged” utility, to capture changes to files/registry in the VM after Terraria has been launched once. Since the Steam overlay DOES work on the subsequent launches of the game, we know that “something” is being changed after the first launch…but that “something” has been elusive to me. The Steam overlay does not work on the first launch of the game, ever. When I revert to the checkpoint, the same thing happens. Now, I can run Terraria in the virtual machine, and the Steam overlay does not work during the first launch of the game, but does work on subsequent launches. Then, I took a checkpoint of the VM (Hyper-V’s term for a snapshot), so that I could keep going back to this state. The latter is included with the game, and I installed it manually so that Steam wouldn’t prompt to install it when running Terraria for the first time. I installed Steam, Terraria, and the Microsoft XNA Framework Redistributable 4.0. I reproduced this on three different Windows computers.Īfter seeing this pattern, I provisioned a new Windows 11 22H2 virtual machine inside of Hyper-V on my laptop. But on subsequent launches, the Steam overlay worked fine. After installing the game through Steam, on a local computer which has never had the game installed previously…the Steam overlay did not work during the first launch of the game. While troubleshooting the Steam overlay issue with this game, I noticed a pattern. As such, I think the information I’m writing here can be helpful in chasing it down on those systems as well. While I’m trying to find a way the issue can be prevented on the GFN service, there is some overlap with the issue on local systems. There have been many posts (and various “solutions”) over the years, about the Steam overlay not working in Terraria for people using local computers. The information below details how I came to this conclusion. What I don’t know, is how to stop it from happening on the “first” launch. Every gaming session is essentially being run on a new computer. I believe this to be the reason the issue persists on the GFN service, because gaming sessions there use ephemeral virtual machines. The TL DR is that one “root cause” of this issue, is related to the Windows “application compatibility” functionality in the OS…when the game is launched for the first time. The specific details are in this community forum post, Terraria Is Extremely Broken [I would really like to get to the bottom of the “why” this is happening, so that it can potentially be fixed. As of this writing, the Steam overlay is not functional when playing Terraria on NVIDIA’s GeForce NOW (GFN) cloud gaming service.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |