necessarily the most 'l33t' code bandits on the planet. There's bound
to be bugs, unless someone decides to write the entire thing in
assembler with innumerable debug runs throughout the process. ::)
> It would certainly go a long way to explain why the NH patch is
taking so
> long. But it is worrisome if this is best AI all those great and
> experienced brains at Papy and MGI can come up with.
> I fiddled with the AI a bit in NL (to improve the Daytona port). I
know it
> is very complicated.
> Marc.
> > I doubt it slipped through the cracks...
> > I think the real issue is that developers are having a hard time
> developing
> > AI for a detailed 3D simulation. GPL was good, but couldn't even
drive
> > ovals.
> > SCGT certainly had it's problems, and NH did as well.
> > I think there are some AI issues that need to be worked out, and we
will
> > continue to see this since it is proving difficult for the
programmers.
> You
> > guys act as if this is all really easy stuff, but AI can be very
> > complicated, so it's not a BUG I don't think, it's incomplete,
because it
> > had to ship someday.
> > > Any ideas how it (and problems at many other tracks) slipped
through the
> > > testing cracks?
> > > Marc.
> > > > It is a problem that is definately known about by Papy.
> > > > > The problems running a full field race at this track are so
> plentiful
> > > and
> > > > > absurd it's not even worth listing them here.
> > > > > My apologies to the NH crew. I said Papy would never release
a
> NASCAR
> > > > title
> > > > > with ludicrous, obviously untested or far from ready to
release AI.
> I
> > > was
> > > > > wrong.
> > > > > And Martinsville may be the worst example (I don't know as I
have
> only
> > > > tried
> > > > > a few tracks), but I haven't seen any track yet that has
> > release-quality
> > > > AI.
> > > > > Marc.
> > > > > --
****
> > > > > Your mouse has moved. Windows must be restarted for the change
> > > > > to take effect. Reboot now?
****
Sent via Deja.com
http://www.racesimcentral.net/