AmpedRobot I googled for that error and got these, do they help?
I ended up installing the latest Windows 10 SDK, as recommended from Quora, but that did nothing, probably because it did not install in the right directory or it may not be compatible with this version of VS?
What worked was adding 0.0.0 to the version (after right clicking and opening the manifest file in VS 2015) and then installing Windows Tools and Windows 10 SDK (an older one).
So the project now opens and plays on local machine.
That being said, I do have some questions/concerns to make sure I don't have to do this a zillion times because it is very time consuming.
1) Why won't UWP exports open in Microsoft Visual Studio Community 2017?
This post dated June 27, 2017 by Scirra states they should:
“Currently Visual Studio 2015 and 2017 are supported - older versions of Visual Studio won't work.”
Initially, I installed VS Studio 2017 Community (I believe with Window Tools and the Windows 10 SDK) and when you open up the project in VS, it does not open up as a full solution, just states “incompatible” right next to the name.
Ashley, could you test this to make sure it works now as intended?
I ended up installing and reinstalling VS 2017 three times just to confirm. Same result.
(Some people claim reinstalls fix everything).
2) So are we stuck using VS Studio Community 2015 for now?
3) I installed a student version of Vs Studio Community 2015. It comes as an iso image with all the updates supposedly and everything needed (base software). But it comes with Update 3.
This post by Scirra, about a year old (I could not find anything more recent with specs), states you need Update 2 with Vs Studio 2015.
Has Scirra tested C2 for Xbox Live publishing with Update 3 since then?
4) If we are indeed stuck with Vs Studio 2015, the iso I downloaded from a Microsoft web site installed with errors:
The KB3165756 Microsoft C++ Redistributable was apparently newer on my system, so it would not install the old one.
Is this an issue?
Should I install the new redistributable and let it install the old one?
5) This post by Scirra states we should be using Edge to export UWP apps.
I’ve encountered significant issues with Edge. First obvious one is the music, sporadically upon loads and quite often cuts out for the main game. Nothing fancy there. Just standard play code on start of layout. This NEVER happened with Chrome, so I exported using Chrome as preview browser. Is this an issue?
The exported UWP opens in VS Studio 2015 fine and plays on local machine (haven’t been able to get it to play on the simulator yet).
But it plays with issues. **Keyboard controls are slow and sometimes weirdly unresponsive.** Not sure if this is representative of the final product, but things like that were NEVER in the Android build in the XDK Intel simulator. Now, this NEVER happened in the zillion times I played the game via C2 using preview/Chrome, so I’m hoping this won’t end up playing like that in the final product. VS is supposed to do all sorts of code optimizations on the back end before packaging, so I’m hoping this won’t be an issue, but if anyone can chime in, or if this is a real concern and why, please let me know.
Also, portions of the credit sequence sporadically cut out (just the front portion). This happened in the Intel XDK simulator also, so I ended up cutting the credit sequence for the Android build, but I want it in this time around (because it’s cool and has a cool track and adds to the game experience). Now why would it cut out in both simulators (and the final builds, which I so far only tested for Android), but NEVER a single time in the browser/C2 preview?
My guess is corrupt code, which is a real issue in C2, but it’s a lot of code to rebuild from scratch. I would never recommend copying and pasting code from one capx to another, as recommended by some You Tube videos, because that has almost a 100% chance of creating corrupt code in my experience.
Also, we could really use sequential saves in C2/C3 to avoid corruptions. I had one layout go corrupt when combining via another method (not copy and paste), but it was fixable as I had many backup copies and many different versions.
Corruptions are nothing new. Both Autodesk Maya and 3ds Max have sequential saves to avoid these very issues.
I got criticized once for using many subfolders by some crazy/angry devs here, but again they had no idea what they were talking about (so know before you open your mouth).
And the simulators are often right on as far as the final build/product.
6) Windows Tools and the Window 10 SDK for this version of Vs Studio 2015 (Update 3, not 2) installs with this SDK:
This is the most current one:
QFE Build: 10.0.16299.91 - Released November 2017 (which I don’t have the option to retarget, even though I installed it from this site:
I do have the option to set this one as target via Project/Properties in VS:
Which one should I be using and how do I retarget if it’s the latest one, even though I’m using VS Studio 2015?
I don’t have the option to retarget by right clicking on the project in the Solution Explorer as I should per this post:
6) How often is testing done by Scirra with new updates/releases since the posted recommendations to make sure everything plays well together? The posts are often dated and they make one recommendation, but they never state this version or this update *and above*.