You sure this has been 'tested'?
It's pretty crap that we'll be releasing builds that don't work for some people.
I'll give the latest RC a couple hours of play tonight, in case it crops up over time. Could run it on my Surface to give it less resources to work with, though nullcascades machines seem to be pretty well specced.psi29a wrote: ↑19 Jun 2018, 15:53According to him, it only happens on release builds including the latest RC build. He can't reproduce it locally when he builds everything from scratch. His builds work, ace's apparently did not. I don't believe his is lying so I think it prudent that more people test the windows build. More testing couldn't hurt right?
I won't be able to get to this for another couple of weeks. I'm out of town.Ace (SWE) wrote: ↑19 Jun 2018, 19:38NullCascade, could you maybe try building up some release binaries using the CI script, with the LTO build flag enabled in the CMake options, see if that still results in the same issue?
If those too show the issue then it might be worth looking over doing some gentler optimization - though it'll lose us performance.
Users browsing this forum: Google [Bot] and 14 guests