Vsync implementation and exclusive fullscreen mode

[himmatsj]

Since this game is made in Unity, that means the game runs in Borderless Fullscreen mode only. You cannot change the games Vsync settings using external apps.

So usually in Unity engine games, I see a soft Vsync implemented, rather than old school hard Vsync. Sadly, in this game it appears to use hard Vsync. It sucks. It's not smooth as such as a result. I have to disable Vsync to achieve smoother gameplay. But it's bad cause then GPU runs 100%.

And game hangs long time on landing at moon [third loading screen after].

Edit: Basically, long story short, can you allow us to set a limit to framerate? 30, 45 or 60 fps for example.

[himmatsj]

I hope the devs are listening. Would be a shame to play the game if it is marred by this trivial issue.

Either give us Exclusive Fullscreen mode, or allow us to cap our framerate via in-game setting.

[pommak]

The game is built with 5.3.4f1 and according to release notes they have a commandline option to start the game in exclusive mode.

"Windows: Added a new command line argument for standalone builds: -window-mode. Options: borderless, exclusive. It lets users override the default fullscreen window behavior."

Imagining that works as advertised it should help you limit the framerate using external tools, right?

[himmatsj]

Originally posted by pommak:

The game is built with 5.3.4f1 and according to release notes they have a commandline option to start the game in exclusive mode.

"Windows: Added a new command line argument for standalone builds: -window-mode. Options: borderless, exclusive. It lets users override the default fullscreen window behavior."

Imagining that works as advertised it should help you limit the framerate using external tools, right?

Interesting. I'm willing to give this a go. How does it work? What must I do on my end? Can you please kindly briefly describe it to me? TQ

[pommak]

You run the executable like 'pollen64.exe -window-mode exclusive' and the window should be exclusive instead of borderless. According to the thread in Unity forums 5.3.4f1 might have some problems in its exclusive DX11 mode, but those seem to be fixed in later patch releases so they will released in our next patch as well.

I quickly tested the exclusive mode and it works for me, though I couldn't give it a thorough testing nor I couldn't easily confirm if it's truly exclusive.

EDIT: (changed the commandline parameter, it had '=' which was incorrect and didn't trigger the mode properly). Thanks himmatsj for finding the solution!

[himmatsj]

Originally posted by pommak:

You run the executable like 'pollen64.exe -window-mode=exclusive' and the window should be exclusive instead of borderless. According to the thread in Unity forums 5.3.4f1 might have some problems in its exclusive DX11 mode, but those seem to be fixed in later patch releases so they will released in our next patch as well.

I quickly tested the exclusive mode and it works for me, though I couldn't give it a thorough testing nor I couldn't easily confirm if it's truly exclusive.

Simple way to confirm if it is truly exclusive is that when you hit the "Windows" key, it shouldn't smoothly transition back to the desktop or bring up the taskbar or bring up the Start menu. It should either remain in the game, or stutter back after a delay to the desktop.

I'm out currently, will only be home to test it in 6-8 hours time. Hope it works.

[pommak]

Steam launch parameters should work as well.

To be honest the windows start menu comes over the fullscreen when started with the commandline parameter so I think it's not as exclusive as it should be. This is something I need to figure out after the launch rush is after us.

[sturmkoenig2k]

??? So, is there a vsync option or not?

[himmatsj]

Originally posted by sturmkoenig2k:

??? So, is there a vsync option or not?

Yes, basic on/off. It's good enough if you have a very good GPU.

[himmatsj]

Originally posted by pommak:

Steam launch parameters should work as well.

To be honest the windows start menu comes over the fullscreen when started with the commandline parameter so I think it's not as exclusive as it should be. This is something I need to figure out after the launch rush is after us.

Yeah it doesn't work man. Damn :(

[himmatsj]

@pommak I have found the solution, it works now in Exclusive Fullscreen. Thanks!

[pommak]

Originally posted by himmatsj:

@pommak I have found the solution, it works now in Exclusive Fullscreen. Thanks!

That's great to hear! Would you be kind enough to share your solution? I'm curious to hear that as well :)

[himmatsj]

Originally posted by pommak:

Originally posted by himmatsj:

@pommak I have found the solution, it works now in Exclusive Fullscreen. Thanks!

That's great to hear! Would you be kind enough to share your solution? I'm curious to hear that as well :)

No "=". It's just "-window-mode exclusive".

I can't press the Window key and return to the desktop. Now to see if the vsync stuff works or not.

[pommak]

Originally posted by himmatsj:

Originally posted by pommak:

That's great to hear! Would you be kind enough to share your solution? I'm curious to hear that as well :)

No "=". It's just "-window-mode exclusive".

I can't press the Window key and return to the desktop. Now to see if the vsync stuff works or not.

That's it! Thanks for finding the solution (and stupid me giving incorrect instructions).

[himmatsj]

It works with Nvidia control panel vsync settings. Adaptive Half Vsync works.

However, the downside is this feature is unstable from Unity, so once you Alt Tab out, you can't go back in. (This is not your fault at all). Although, you did mention they fixed it in a later Unity build...so maybe it may work fine in the future?

Thank you for teaching me something new today good sir. I can use this in Unity games I play going forward! :)

[Veihis]

Kudos for helping out with the solution himmatsj!!