Unfortunately, you'd find it tricky to get within range, as all relevant conventions are fully booked until December. European furry convention organizers are being hard-pressed to keep up with increasing demand, despite significant expansion in the last few years.
At last the species-dysmorphic among us will have some way of making things right. Plus it would be neat for those of us who like the idea of anthropomorphic animals.
This CNET article has more information. There is a vulnerability report at Sun. It is fixed in JDK and JRE 5.0 Update 10 or later, SDK and JRE 1.4.2_13 or later and SDK and JRE 1.3.1_19 or later.
Creatures was a masterpiece for its time, and is still a good game for children today - the author did some technically challenging work, without a background in AI. Perhaps that's what we need - more general developers thinking about how to do AI rather than people who have been trained in current techniques.
ATI got it right, it seems. It's unfortunate that my X1400 runs silky smooth while a 6800 stutters along, and yet both work just fine with the same code under XP. I'm not saying NVIDIA hasn't worked with us - they've been responding to our issues and sending us drivers, they just haven't improved things yet. It is somewhat frustrating to say to customers "there's not a lot we can do until they fix it."
This issue applies similarly to the original; I'm guessing it just wasn't in their testing, or got pushed back because it doesn't actually crash. Which is fair enough, except that it's been out for a while.
In case you were wondering, the other game I was referring to was Second Life, which crashes rather nastily with the same laptop.
If it doesn't matter who you blame, why are you calling me a Microsoft apologist?;-)
For what it's worth, I work for a company which has just released a game that, as of this date, does not work at all optimally under one major graphics card manufacturer's Vista drivers. Are we angry at Microsoft for that? Not particularly. Given that one manufacturer showed that they could get drivers that supported our game out, we are more concerned with the company which dropped the ball. (Of course, the other company's drivers crash one game which I like playing, so it's somewhat swings and roundabouts.:-)
There are serious problems with many games because . . . well, good code takes time, and Microsoft has (quite reasonably) changed the architecture of the drivers significantly, and so we are seeing that some things are now very slow and others just plain don't work right. It is not DirectX's fault, just that code is new and yet is expected to work just as well as it used to in every possible situation - which isn't going to happen.
The blame, if any, goes to Microsoft for not releasing the spec earlier, and to the driver writers for not doing a perfect job. Perfection is pretty hard to achieve the first time around, though, so I don't honestly blame anyone that much. It's just the way things are when you make big transitions. Frankly, I'm surprised things work as well as they do now.
Slashdot Mirror
A Mediation On Value
The system gets paid for dealing with applications, not for approving them. If they aren't approved, they still keep the money. Same with trademarks.
Anonymous Coward is the most respected poster on this site!
Well, they'd better join up quick, or they'll be first against the wall when the revolution comes. Nuts and berries for all!
Unfortunately, you'd find it tricky to get within range, as all relevant conventions are fully booked until December. European furry convention organizers are being hard-pressed to keep up with increasing demand, despite significant expansion in the last few years.
There already are two furry conventions in the UK - RBW and ConFuzzled. See the furry convention map for more worldwide.
. . . they are signed, consecutively numbered, and they only sell 200 of them. Which, considering we're talking about Ford, may well be the case.
How did you write all that and not link WikiFur once? Admittedly, we don't tend to store the fan fiction, just reference it.
I was wondering when we'd come up. Of course, we give all our money to charity.
Jimbo is a party animal, that's for sure. The reputation of Wikipedians as boring people is undeserved.
Here we go.
Since the site is down, here's a mirrored copy
At last the species-dysmorphic among us will have some way of making things right. Plus it would be neat for those of us who like the idea of anthropomorphic animals.
Klingons vs. Furries. They have a bigger wiki than ours, but we're working on it.
Sure, if you assume that. But you shouldn't, because he didn't.
They've got a fair selection of stories - you can even write your own (which people may see as an advantage or a disadvantage), and it's free content. They even make a printable PDF edition.
That's what makes it a joke, for all those who've actually read the license agreement. :-)
That was yet another serious Java bug. Unless they've decided to review a story from January, which I guess is always possible.
This CNET article has more information. There is a vulnerability report at Sun. It is fixed in JDK and JRE 5.0 Update 10 or later, SDK and JRE 1.4.2_13 or later and SDK and JRE 1.3.1_19 or later.
What about the people using it to run nuclear reactors?
Creatures was a masterpiece for its time, and is still a good game for children today - the author did some technically challenging work, without a background in AI. Perhaps that's what we need - more general developers thinking about how to do AI rather than people who have been trained in current techniques.
ATI got it right, it seems. It's unfortunate that my X1400 runs silky smooth while a 6800 stutters along, and yet both work just fine with the same code under XP. I'm not saying NVIDIA hasn't worked with us - they've been responding to our issues and sending us drivers, they just haven't improved things yet. It is somewhat frustrating to say to customers "there's not a lot we can do until they fix it." This issue applies similarly to the original; I'm guessing it just wasn't in their testing, or got pushed back because it doesn't actually crash. Which is fair enough, except that it's been out for a while. In case you were wondering, the other game I was referring to was Second Life, which crashes rather nastily with the same laptop.
If it doesn't matter who you blame, why are you calling me a Microsoft apologist? ;-)
For what it's worth, I work for a company which has just released a game that, as of this date, does not work at all optimally under one major graphics card manufacturer's Vista drivers. Are we angry at Microsoft for that? Not particularly. Given that one manufacturer showed that they could get drivers that supported our game out, we are more concerned with the company which dropped the ball. (Of course, the other company's drivers crash one game which I like playing, so it's somewhat swings and roundabouts. :-)
There are serious problems with many games because . . . well, good code takes time, and Microsoft has (quite reasonably) changed the architecture of the drivers significantly, and so we are seeing that some things are now very slow and others just plain don't work right. It is not DirectX's fault, just that code is new and yet is expected to work just as well as it used to in every possible situation - which isn't going to happen. The blame, if any, goes to Microsoft for not releasing the spec earlier, and to the driver writers for not doing a perfect job. Perfection is pretty hard to achieve the first time around, though, so I don't honestly blame anyone that much. It's just the way things are when you make big transitions. Frankly, I'm surprised things work as well as they do now.
Maybe if you didn't hang out with drug dealers, you wouldn't get busted all the time. Just an idea. :-)