when you put out a new build, do you test it on windows 7 and windows 10. Myself and 3 others I know on a w7/p3dv4 build all had this issue today.
I must admit I don't have any PC left with Windows 7, nor anybody else at FSDT still has one. I usually check before adding a new function, if it's supported on at least Windows 7 ( we really don't support XP or Vista anymore ), but didn't this time.
It wasn't anything fancy: just a simple function that removes trailing backslashes (if they exists) from a pathname, because some 3rd party scenery installers add them, some don't, and this caused GSX missing those sceneries. I assumed using the official MS function was the safest way but, unfortunately, I didn't noticed they added it in Windows 8...
I'll probably rewrite the function from scratch, so at least I'll know how it works...
The current martket share / distribution is 42% windows 7 and 37% windows 10 so they are both as important.
Yes, even if the global market share doesn't tell much about the market share that concerns us (high-performance PCs used for gaming), we don't plan to drop support for Windows 7 NOW.
Just keep in mind the official "Mainstream" support for Windows 7 ended in January 2015, and the Extended support will end in January 2020 so, I guess that by that date, we'll have to drop support for Windows 7 officially. Or, if P3D will eventually move to DirectX 12, whichever comes first.