Marc...
As I stated, I wasn't trying to be a smart ass......but your post doesn't
contain anything of merit, IMHO.....and that statement was made for the
newbies only. I'm pretty confident all of the experienced sim drivers would
realize your post was of no merit.
By "no merit"....I'm again, not trying to be a smart ass....honest. What I
mean by that is it contains false premises. IMHO, you are trying to compare
targets that have "moving bullseyes"....and that is just a waste of
time...usually. And, requiring that the Papy production team develop an AI
code that has the AI running at all 26 WC tracks....at (or near) their
real-life race speeds....when the game option AI Strength slider is set to a
global value of 100%.....is just ridiculous. It shows you don't really
understand the AI coding.....or how the sim actually operates. Again, this
adds a "no merit" value to your post. You are also assuming the AI performs
equally at all sessions of a race....and it doesn't. It never has...even
from the N3 days.
If you want to obtain a "realistic experience" racing against the AI
cars......then you must do some work on your own. Its easy to do....it just
takes time to do it. Most of us, who regularly race against the AI (I do
this regularly...by adding AI cars to fill out online races with just a few
friends in the race)....have been doing this since the N3 days. The process
is something like this:
1. Go to NASCAR.com or a varying number of other resources and find out
what the real-world qual or race times/speeds were at a given track....in
2002 (for the entire field....front to back). As WC races are run this
year.....you should log that same data and this will allow you to update
your data to real-world WC, 2003 speeds/times at each track. Also, record
the weather conditions as best you can (ambient temp.....range too.....if it
varied for the entire event/qual period).
2. Once you have this data for a track....let's say, Daytona (spring
race...and a different set for the fall race would then be required).....you
can go to the Daytona NR2003 track and create a race session with the same
or equivalent weather conditions....and the AI slider set at 100%. Let the
field qualify (ignore practice sessions speeds/lap times). Now...compare
those results to the real-life data from the same track.
3. Make adjustments to the AI slider (up or down as needed) until the field
is qualifying at or near the same lap times/speeds "spread" as the real-life
data. Once you get this set...then check the race speeds/lap times
too...make sure those are also in line with the real-life data. If that is
okay, record your AI slider setting for that track. What ever it
is....that's what it needs to be (at a given weather setting) for the AI to
be performing at or near "realistic experience" levels. You will find this
will almost never be exactly 100% at any track....at least it wasn't for
NR2002.
Now...you have a "baseline" bullseye.....by which you can compare your own
driving skills/setup.......depending on your goals. If you want to finish
in the top 10 consistently....then adjust the AI slider from your baseline
value....until you can....if that's what you want to do! There's many other
things you can do......but nothing is of merit until you establish a
baseline for the AI that has a fixed bullseye. This is the only way I know
to do it.......compare everything to real-world WC driver performance.
In recalling these AI slider values for NR2002.....I know that it was about
only 95% for Sears Point (though the track config was slightly different
from the Papy track to the real track).....and it was around 112% for
Talladega. Those two tracks had the biggest variation....if I recall
correctly....from the 100% settings. I would expect NR2003 to have less of
a "spread" from 100%...for many reasons too numerous to mention here.
Once again, I'm sorry you took offense to my terminology.....it wasn't meant
to be a personal attack or anything like that. I apologize to you....and
will try to choose my words more carefully in these posts.
Regards,
Tom
"Marc Collins" <marc_coll...@sympatico.ca> wrote in message
news:zZv1a.191$606.51561@news20.bellglobal.com...
> Once again Tom, you are an ass. Your message was quite reasonable and
> respectful until you couldn't stop yourself from saying my message
contained
> nothing of merit.
> If you are not annoyed by bugs and oversights that were pointed out 3
> versions ago, so be it. Shut the *&%# up about Sears Point/Infineon
> accuracy, then, too, to be consistent, since the vast majority wouldn't
> notice and could care less.
> The point is that 100% AI *DOES NOT* represent true WC speeds. And how
> closely it represents them varies dramatically from one track to the next.
> So great orb of wisdom, tell us what someone--a newbie or old timers like
> us--should set their AI to if they want the "realistic" experience that
this
> title is striving to provide. Looking forward to your reply.
> Marc
> "Tom Pabst" <tmpa...@attbi.com> wrote in message
> news:IMn1a.46058$Ec4.38294@rwcrnsc52.ops.asp.att.net...
> > Marc....
> > I don't know if the AI slider was ever supposed to be set a one
> > setting....and have that be universally correct (compared to something,
> I'm
> > not sure what) for all tracks. To me, if its a "slider"....its meant to
> be
> > "moved." Seems like sort of a common sense thingy.....LOL. Since I
> don't
> > run in "season mode" I guess it would be frustrating if you are not
> allowed
> > to alter the AI settings for each track/race. Is that true?
> > Alternately, when I want to race against the AI at a track that I am
> fairly
> > competent at.....I try to find a "slider" setting that has the top of
the
> > field running at or near what the real WC cars run (top of their field)
at
> > the same track (taking into consideration any variables in
> > weather....depending on what data you are using for the real WC
speeds/lap
> > times). Of course, this requires keeping a log of these settings for
each
> > track....if you want to repeat a race at any time in the future. Not
too
> > difficult.
> > I don't think the adaptive AI was meant for us hardcore simmers. Do
you?
> > I can't comment on the AI "ignoring incidents on track" in practice
> > sessions....haven't run any yet. However, if that is universal to all
> > tracks, my guess is there's a setting out of whack in the "papy_ai.ini"
> > file....someone is sure to find it and post a correction (like JJ
> > Johnston....or someone with similar skills in hacking/improving Papy's
AI
> > performance).
> > I don't think using Bob Stanley's setups as a "benchmark" of what the AI
> > "should" be running....is a reasonable proposition. While Bob's setups
> are
> > excellent, indeed.....they are not meant to be AI benchmarking
> > devices....are they? If you use one of Bob's setups and you are running
> at
> > lap speeds equivalent to the real WC drivers....then find a suitable AI
> > slider setting that matches up....and bingo....problem over! And by the
> > way, if you only took 10 minutes to be as fast as Bob's notes say he
> > is....then I would guess there's a lot more speed left in that
> > setup.....with further adjustments. You shouldn't have even warmed your
> > tires practically....in 10 minutes. Perhaps you were "fudging" a little
> bit
> > in your time statement? Or, maybe trying to impress us a little bit?
> > To explain the "inexplicably"....some WC tracks don't have enough pit
> stalls
> > for 42 cars.....so the field gets reduced to the number of pit stalls it
> > does have. That used to be a lot of WC tracks....now its just a few.
> > Having to manually reset to "full field, 42 cars" doesn't seem like such
a
> > bummer.......to me at least.
> > Calling NR2003 "another update" is being a little unrealistic....IMHO.
> And,
> > I think its unfair to those people at Papyrus (who were not around when
> N3,
> > or N4 were produced) who worked very hard (again, IMHO) on getting as
much
> > of the "goodies" packed into NR2003 as they did (and some cools stuff
we'd
> > not even been asking for) because it was the "last" of the Papy NASCAR
> sims!
> > Fortunately, I think most of them will view your post, as I did.......as
> > being from a little too anal of a "POV"......I don't think they'll lose
> any
> > sleep over your being aggravated at their work.
> > I'm not trying to be a smart-ass here.....just trying to balance the
> scales
> > a little bit.....for the newbies to this sim racing community who might
> have
> > mistakenly read your post and thought it contained anything of merit.
It
> > doesn't.
> > Regards,
> > Tom
> > "Marc Collins" <marc_coll...@sympatico.ca> wrote in message
> > news:Fem1a.6759$Pg6.1380808@news20.bellglobal.com...
> > > No one has replied to my earlier message about the AI ignoring
incidents
> > in
> > > practice mode...it's like they only slow down based on a yellow flag,
> not
> > on
> > > what they are "seeing." Sorry, but after having this same issue since
> N3,
> > > it sucks.
> > > The next issue has also been around since N3...that is, the AI aren't
> > based
> > > on some realistically driveable model for each track. If you set them
> to
> > > 100%, at some tracks they are unbeatable (uncatchable) and at others
> > > relatively easy to beat.
> > > I downloaded Bob Stanley's set-ups. I have no end of respect for Bob
> and
> > > his generous contributions to our community. I have used his set-ups
> for
> > N4
> > > and NR2002 extensively. Of course, he was also involved in testing
and
> > > developing NR2003. Fire up Michigan and after quite a while manage a
> > > 37.661, which puts me 37th in the field. I am not an alien, but I
have
> > been
> > > around the block a few times and with a great set-up I should be able
to
> > at
> > > least make the bottom of the top third of
...
read more »