I guess they're just not gonna close my account! But I'm glad I have the opportunity to respond here before they get around to it... if they ever do...
As I said before, you already have everything you need. No one is being left stuck. I will clarify...
If something stopped working since the 2010 release, it was most likely not my doing. To clarify, I only authored r102 - r113. There were about 100 revisions before that, which I had nothing to do with. Most of the real changes from the 2010 release were done by others. I just showed up on the scene recently, and dove in and tracked things down, like you're doing.
Basically what I did was to roll back a few faulty revisions and corrected some errors that I found. In the repository, you can look at the revision logs and see exactly what was done for each revision, as well as who authored that revision (each author will have their own style). Stencil shadows is a feature that I'm not familiar with and have never used. So I never tested it. See, I made the fixes to the source code for my own use, and then figured why not share those changes with everyone since anyone wishing to use the source code would be in the same boat.
The earliest revision I rolled back from was r55. So try checking out r54 (which does build and function for DarkGDK) and see if the stencil shadows work there. If they do, then I probably missed something - another later revision that should have been fixed or rolled back.
In any case, to find the revision that "broke" the stencil shadows... well here is what I did to track down a revision that broke something:
1. I determined which module the fault was in (camera, Basic3D, music, etc).
2. I looked in the revision logs to find which revisions made changes to the relevant files.
3. I checked out and built the revision just before to see if it was functional in that area. And if it was, then I checked out and built the one that updated those files to see if that was the one that broke it.
And that's all a lot easier to do from the SVN on your computer, rather than the repository website (browsing the logs, seeing what files were effected, etc). If you wish to track down where in the effected files the bugs were created, you can view differences, which gives you a side-by-side comparison with changes highlighted. The SVN documentation can help further with that.
When you figure out how to fix it or where the problem is, you can add an Issue to the repository with the specifics of that information, like you did in the other tread in this forum. Adding an Issue in the repository is what I did before Lee gave me account access there (which I have since removed myself from). Anyone who can sign in to Google can add an Issue there. But without Lee adding you specifically as a "Person" on the project, you can't delete or modify an Issue, not even one that you created. So keep that in mind. But you can add and delete your own comments within an Issue.
Take care, and good luck!!!