StarRuler2-Source
StarRuler2-Source copied to clipboard
BlindMindStudios
Debug build has visual artifacts when using vs 140 tools (Visual Studio 2015)
Didn't feel like downloading VS 2017 so I decided to retool the project to see if things would break (haven't gone through all the code yet myself) and noticed that while a non-steam release build appears to work correctly, that the debug build has major artifacts as if none of the frame buffers are being cleared.
Curious as to whether this is an issue with the toolchain I used or if it may be a hardware issue I am having with the debug build. More or less I was hoping someone may already have an answer before I go digging into that side of the code since there were other parts of the code I was hoping to refactor first, and don't want to mess with code that would otherwise work if I used the recommended toolchain.
Could you please attach a screenshot of the issue? And also please join the RS discord so we can have a chat/figure it out there. Currently that's the OS dev hub :)
I think I may have to do a few more tests because the first 3 or 4 times I launched what would essentially happen is I'd go and run the tutorial and after taking 180 seconds to load the scripts (I assume the debug build does some extreme stress testing, although it is lacking in verbosity or doesn't do a good job of telling you were the debug logs are going) it would load in and on moving the camera the previous frame would be blended with the next ad nauseum with the previous frame retaining only part of its alpha values making for quite a surreal looking blob of colors.
But now that I went to launch the debug build to take a screenshot, it isn't doing it, possibly because the last full build I did was a release. I still launched the debug exe, but this time although it still was eating all my CPU cycles it didn't have weird artifacts...literally the only thing different is that the release version was the last full build. So on a whim I went back and built the debug version just to see if one of the libs or dlls included with the debug version were possibly the culprit and it is occurring again and looks as such
To clarify, I didn't specify different build paths for my debug and release versions, which is why I think specifically building the debug version compared to the release would have an effect at all.