I opened GCFScape up in Visual Studio 2005 the other day just to see how it would look in .NET v2.0. Visual Studio prompted me, asking if I wanted it to backup any files it converted to which I replied "yes". It did an excellent job backing up the various project files, however, it also decided it would be a good idea to alter the source code without telling me or backing it up. Needless to say the project would no longer compile in Visual Studio 2003.
So why am I telling you all of this? Well, instead of trying to manually convert the code back, I decided to go with the flow which is why GCFScape v1.4.0 and up now requires the .NET v2.0 Framework. GCFScape v1.3.1 will be the last version offered with .NET v1.1 Framework support.
If GCFScape v1.3.1 works fine for you, then there is no reason to upgrade, unless you are the sort of person who is interested in Source BSP support and updated widgets, in which case GCFScape has a new home here.
how is net 2.0 framework
are you going to update batch compiler with the HDR checkbox and options
I've updated the specifications (Automatic Update should work) but Valve hasn't released the updated source code yet so I don't know if it is 100% right. Let me know if I've missed anything.
can I add the parameters to BC and it will work?
I'm sure you know that they also have an HDR full compile version with the [b]-final[b] command (slow)
-both -final -game $gamedir $path\$file
Anyways, I've updated the specifications again, I've added a Lightmap Type combo box that lets you choose between -ldr, -hdr and -both. I've also added the -final option to the existing RAD Type combo box.
Hopefully that is everything, when Valve releases the updated source code I'll double check. One thing I assumed is that the -ldr option is the default option. And for the record, you could have added -final -both to the Additional Parameters field while you were waiting, that's what it is for.
thanks for the updates.
To bad about 2005's auto-backup-updater funktion... oh weal as long as it didn't just brake the code.
Good to hear that the progress on Object viewer is progressing steadily.
oh and i see you have gotten new emoticons ended.
Object Viewer should be ready for either an alpha or a beta by the end of this month. I just need to do a little work on the VBSP support, memory management and configuration before it is ready. It is currently quite stable and quick, just a little bit of a memory hog.
New users can register here.