«

"Master Tech ©" <> wrote in message
news:...
>
>
>
> Have a read
>
>
> NVIDIA-based Graphics Cards Will Have a Bug in Half-Life 2?
>
> FSAA Cannot Be Enabled
>
>
> http://www.xbitlabs.com/news/video/d...718155730.html
>

Not really a bug, more of an unanticipated situation when they were coding
their FSAA.

Cheers,
Nicholas Sherlock

"Nicholas Sherlock" <> wrote in message
news:bfb1hj$d9h$...
> "Master Tech ©" <> wrote in message
> news:...
> >
> >
> >
> > Have a read
> >
> >
> > NVIDIA-based Graphics Cards Will Have a Bug in Half-Life 2?
> >
> > FSAA Cannot Be Enabled
> >
> >
> > http://www.xbitlabs.com/news/video/d...718155730.html
> >
>
> Not really a bug, more of an unanticipated situation when they were coding
> their FSAA.
>
What's a bug if it's not an "unnticipated situation"?
Surely it's still a bug....?

"Scott" <****> wrote in
news:8f9Sa.5839$:

> "Nicholas Sherlock" <> wrote in message
> news:bfb1hj$d9h$...

>>
>> Not really a bug, more of an unanticipated situation when they were
>> coding their FSAA.
>>
> What's a bug if it's not an "unnticipated situation"?
> Surely it's still a bug....?

I guess it would depend on who was describing it - an end user for example
might call it a bug while a suposed (probabily self proclaimed) programming
and internet guru might put their own "spin" on it and call it an
"unanticipated situation"



--
Chris Mayhew using Xnews !

Chris Mayhew <> wrote in
news:YGaSa.5851$:
?
>
> I guess it would depend on who was describing it - an end user for
> example might call it a bug while a suposed (probabily self
> proclaimed) programming and internet guru might put their own "spin"
> on it and call it an "unanticipated situation"
>

or a feature

"samg" <> wrote in message
news:Xns93BE622A0725Bsamg@203.97.37.6...
> Chris Mayhew <> wrote in
> news:YGaSa.5851$:
> ?
> >
> > I guess it would depend on who was describing it - an end user for
> > example might call it a bug while a suposed (probabily self
> > proclaimed) programming and internet guru might put their own "spin"
> > on it and call it an "unanticipated situation"
> >
>
> or a feature

Hey.. when you document it, it offically becomes a feature

Cheers,
Nicholas Sherlock

In article <Xns93BE622A0725Bsamg@203.97.37.6>, samg <> wrote:
>Chris Mayhew <> wrote in
>news:YGaSa.5851$:
>?
>>
>> I guess it would depend on who was describing it - an end user for
>> example might call it a bug while a suposed (probabily self
>> proclaimed) programming and internet guru might put their own "spin"
>> on it and call it an "unanticipated situation"
>
>or a feature

Ah ! ... the marketing department is involved

Bruce


--------------------------------------------------------------------
Oook !
NOTE remove the not_ from the address to reply. NO SPAM !