Im using windows 7. I always use warning lvl 4 for my projects, Im quite used to it, and Id like to keep it this way.
I migrated a project from VS 2010 to comunity, and now I have a bunch of warnings, theyr all from windows gdi files.
Using Warning version 18 "fixes" it.
Those are from the folder windows kit/8.0/include/.. Theyr mundane things like using parameters names that are the same as the class member, etc.
Which got me thinking...from where should I be including windows includes from..Im under windows 7, and I have in the windows kit folder folders: 8.0, 8.1 and 10...I was assuming newer versions (8.1 and 10) wont produce warnings ( they just got installed with vs community)
But then I tried 8.1, and its the same thing.
From msdn Im under the impression I shouldnt use windows sdk 10 if targeting windows 7 (it doesnt even show windows 10 under the retarget sdk version option, it actually just shows 8.1..)..so I guess Im stuck with it.
Other than that all went incredibly suspiciously fine...Then I pushed play on debug mode, and frame rate is about 2 fps..e_e"
Cant really debug under vs community like that. The release version is fine...theres anything I can do to make the debug version lighter? on vs2010 the debug version took long to initialize due reading ginormous txt files only, but kept decent fps (>60 fps).. On community its not taking even half the time it takes to initialize, but ~2 fps..gotta be kidding me..Using the super "pause lots of times" profiling technique looks like its my collision system, which was also the slower thing on vs2010, but still dont see any reason to that slow down.