Laucher causing high cpu and gpu usage 80-100%

[Karamasha]

Is there any way to solve this or do we need to wait for a new launcher?

[Crissa]

I don't know. It has done that to me once. And then it went away.

Don't sit in the launcher is my advice, but it's sorta empty.

[Karamasha]

I don't know. It has done that to me once. And then it went away.

Don't sit in the launcher is my advice, but it's sorta empty.

Yeah, i was just hoping people knew a quick fix for this right now. hopefully it gets patched in later launchers.
It's no big deal, i was just surprised by the usage spike when i forgot the launcher in the background.
Glad to hear i'm not the only one who had this issue at least.

[Silvonis]

It's not a common issue, at least not based on what we've seen or heard. I've left open the launcher open on Windows 10 and the CPU usage never goes above 2.5%. It's already been mentioned, but if it is an issue on your machine - I'd recommend not leaving it open. There is no new launcher planned for the immediate future and it probably won't change until we transition to Steam Early Access.

[Citan]

As Silvonis mentioned we're unlikely to do another launcher update unless there are bugs that keep people from being able to patch or log in. When we switch to Steam soon, the launcher be obsolete and Steam will be the launcher/patcher.

That said, one potential cause comes to mind. Did you adjust global settings for your video driver that may have affected framerate limits? The launcher is capped by the vsync, at least least by default, but uncapping it via driver settings would "work" -- just not in a useful way. The launcher would be able to render many hundreds of FPS and cause the performance problems you mention.

If it's not that, then it may be a bug that can be tracked down with the logs. If you look in the directory where the launcher lives, there'll be a directory named something like ProjectGorgonLauncherWin_Data, and in that directory is a file output_log.txt. This is NOT the same as the file that the game itself generates -- it has the same filename (all Unity apps do) but it's not in the same directory. Anyway, if that is growing dramatically in size while the patcher is sitting idle, that would be useful debugging info, and I'd love to see it! (You can email it to me at eric@projectgorgon.com -- compressed if it's really large!) We may not be planning to release another launcher before Steam early-access, but you never know how things will shake out.

Thanks!

[Karamasha]

The launcher file won't get any bigger, and forcing lower fps doesn't help.

Edit: it seems like locking FPS to 60 in global settings seems to eliminate the problem.