Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Strange.  With version 176, I doubled the frame rate at sea on mine.  The only difference with 177, is that I compiled that same code with Visual Studio 2019 and I get slightly better FPS at sea than #176.  I wonder if I should switch it back to VS 2017?

I do not know if this is a coincidence or not, but in corsairs to each his own, the same drop in performance on the last beta release. And the engine there is also compiled for 2019 studio.

I just uploaded another variation today.  Try it and see if that helps.  It is still 2019, but I altered some of the sea performance code.  If that does not change things for you, I will change to VS2017 compilation instead.

Checked the latest revision. Yes, now the FPS is the same as at the 2017 studio.

Everything is super!

(+1)

Good to hear.  I already had the 2017 ready to upload at a moment's notice if it was still a problem, but it sounds like I can continue moving forward with 2019 for the x64 bit.  The 32 bit still uses 2017 because Microsoft has deprecated XP support in the newer VS2019 toolkit (I think you can configure to continue using it, but it is more work than I deem worth the effort) and it is simply easier to keep using 2017 for those 32 bit versions because I want them to remain compatible for WinXP.