Updated Log Parser

I've updated the development version with the ability to specify where the log directory is located (it's no longer in the same directory as the game). Can someone give the newest version a run for it's money and tell me if it fixes the log issues?

Comments
The log file works well for me, but if I try and jump to the line were the error accrued, I get an error that the file can not be opened. This is due to the compiler using an apparent hard coded path, rather then the actual path it is using.
This is a bug from epic, so either we wait for them to fix it, or create an ugly hack to get around it. (The other option is to have your source in the same path as the one from the compiler, then it would work)


I suggest that with the default install that '-useunpublished' is added to the list of switches.
Also if UT3.com is used as the compiler, it will allow the capture of the output into the wotgreal interface window.
# Posted By Michael Robinson | 6/26/08 12:29 AM
The log problem I'm having is that I'm running on Vista, and UT3 make always exits in a way that makes Vista think it's crashed, instead of closed properly. This results in the output not being sent / captured by WOTgreal for some reason.
# Posted By Pfhoenix | 7/5/08 9:23 PM
Try configuring WOTgreal to use UT3.com instead of UT3.exe. I'm also using Vista and do not have that problem.
# Posted By Immortius | 7/7/08 5:32 AM
I tried using the "Create Subclass" functionality, and it doesn't work. It doesn't find any packages in the dropdown, and when you click okay or create or whatever, it says that the package you are trying to add it to does not exist.
# Posted By Sir_Brizz | 7/22/08 10:10 AM
BlogCFC was created by Raymond Camden. This blog is running version 5.8.001.