When I installed it last night on Win 7 64 bit, that whole UAC and driver signing bit threw me for a bit of a loop - wasn't expecting to have to mess around like that.  It's definitely not for the casual.

 

What unsigned driver is it installing???   Be careful!!  I can't think of any reason why a scenery process for FSX would want to install an unsigned driver?

 

 

The color however is still pretty off

 

Agree, for example golf course around Las Vegas is dark brown (real world it's always green) and there is an overall darkish tint and many greens got turned into dark browns.  Also agree the Reno/Taheo area has acknowledged problems which are hopefully going to be correctly (at least that's what the developer indicated).

 

But some of your images are also differences in season from MSE.

 

 

What unsigned driver is it installing???   Be careful!!  I can't think of any reason why a scenery process for FSX would want to install an unsigned driver?

That's normal with Tile Proxy, I remember having to search for some info before I found a way to install it on Win 7 64 bit. 

Like tile proxy idea but I am lazy and dont have patience to play with it. Photoscenery will improve over time with ethier method. Convienance factor mega scenery earth is factor. Sbuilder is another option, but all pay for someone to do a job too lazy to do myself. Colorado needs more work than Nevada, but not too worried product will improve with time.

 

 

What unsigned driver is it installing??? Be careful!! I can't think of any reason why a scenery process for FSX would want to install an unsigned driver?

 

Unsigned drivers aren't an uncommon thing, although you're right to advise caution; it's not something you normally see in a scenery add-on.  That said, Tile Proxy does significantly more work than a normal static add-on.   I researched it enough to satisfy me before taking the steps to allow it to run.  To be honest, for all the work that you have to do to get it to utilize that unsigned driver, if it was malicious, there are much more 'silent' and hence more efficient and likely to work methods of being malicious.

It has to use the unsigned driver to always automatically overlay the scenery top most in real-time and to process the hooks and files. There might have been a way to do this without an unsigned driver, but he likely didn't get the same warning in XP when he was originally developing it so that he didn't want to rewrite it for Windows 7.

 

I've written programs for XP in the old days where they did weird things in 7 (different warnings), as it is a totally different security model.