Quote:
Originally Posted by JSWolf
So what I am gathering is that this is a 1.0 bug fixed in 1.0.4.
|
If anyone can get me 1.0.4 file, I can try to confirm/deny... I have been trying since the 15th to get the update to see if it resolved this, but it hasn't come to me yet.