rec.autos.simulators

These all seem to be related to some type of install issue which is
causing the files to be read and attempted to save to and from the CD
rather than your hard drive.  Weird.  Did you do a full or minimum
install?

Eric

points.

Sounds like ol' N2 with a minimum install before they patched it - it tried
to read AND write everything to the CD path.

--
Ken's Sig 3.01

"Who is the more foolish?  The fool, or the fool who follows him?" -
Obi-Wan Kenobi

Go #43 and #44!

volksy (at) yahoo (dot) com

Does anyone know whether or not Papyrus plans on putting out a patch for NL?

I've been playing the game for a little over a week (needed a break from
GPL), and
I noted several frustrating items that need to be fixed.   I do not own N3,
but I would
surmise that many of these items were similar to problems present in that
game prior
to it's patch.

Items that I've seen:
1. Can't create custom set ups.  Actually, I can't create a filename for a
set up, and I am
    stuck using the ACE,FIXED,EASY,QUALIFY filenames only.  I've tried
reinstalling,
    as well as copying another setup file and renaming it, but still no joy.
Right now, I can
    only alter and save using the default names, and cannot make comments.
    Is this unique to my copy, or do others have this problem?

2.Since I wanted to drive a Mercury Cyclone, I  took over the default Sean
Edwards car and
   renamed the driver.  All is well on some /most screens,  but I ran into
some instances where
   it displays "Sean Edwards" and not the correct driver name on some
screens (not all) such as
   best lap time.

3. I started a championship season, and after race 3 at Richmond, the game
lost track of my Driver's
    record. All of a sudden, I showed 0 starts and 0 points.  Granted my
poor driver wasn't doing well
    and had 3 DNFs in the first 3 races, but I still wanted my points.

4. Pace Car/accident bug.
    At the Rock, there was an accident on pit road.  As a result,  several
of the cars were trapped on pit
    road, including the pace car, which pulled off on the "going green next
time around".
    This lead to  several wierd things.....
     1. Cars on the track "racing" each other even though we were still
under yellow.
     2. Stuck on yellow flag for about 30 laps until pace car could get back
past the start line in the pit.
     3. Black flag penalty for passing the pace car/other cars that were
stuck in the pit lane.
     4. Your pit chief doing LSD on the pit wall...talk about flipping out.
I was 18 laps down, and he
         would alternately tell me "stay to the outside, you're on the lead
lap", "stay behind the X car"
         and the darn car was stuck in the pit lane.   You would also here "
green flag", followed later
         by other pit calls that must have been stuck in a buffer since they
related to events that had
         occurred earlier...in some cases laps earlier.
     5. The way AI cars will  stop in front of you and stay stopped for a
long time.
    6. The way AI cars, when stopped, can pivot instantaneously 90 degrees.

Are these common items that others have experienced with this game?
The game is fun, especially since I remember the "real thing"....
Any chance these items will get patched, or is NL going to be an orphan?

Regards,
Don

To create custom setup's you just alter the Ace setup and then click on the
"ace" tab and rename it. Click save and viola your new setup.

Al Stiff

All problems at the Rock *seem* to be caused by the incredible high speed of
the pace car. Change the pacea line in yr Rocking.txt to
PACEA 2 31800000 52000 -52000 0 65
and that should sort it out. (slows pace car to 65)

--

Colin Harris
ColinHarris in N3/NL
Proud co-owner - CLONE N.Legends league
http://members.chello.se/clone/index.htm
ICQ 25485061

On Thu, 09 Mar 2000 00:01:48 GMT, "seydlitz"

Unsure of this myself, but I've read over the last few days about an
N3 patch? I assume that they're unlikely to be compatible, but is
there one in conjunction to NL?

I'm pretty happy with my version of NL except for a few niggly things
like the cars being trapped in pit lane as you say...

Having fun with it, except that it's been shelved momentarily for my
new found love, SBK2000 ;)

Cheers,
Rod.

Exactly like the manual says...only it won't allow me to change the setup
name or type in comments.  Very strange indeed.
I even uninstalled and reinstalled but it's still broken.

Don

I did a full install to the default directory both times.     I've also
defragged my HD and tuned my registry.

You might have a point.  Some install packages can cause issues. I might try
reinstalling again with the read-ahead
turned off.

Don

I'm hoping that they will do a patch, but  you know how it is these
days...why waste programmer time on a game that
isn't a big seller.

I really like NL, in fact I chose to buy it instead of N3...after all, why
race with a Taurus when you can
have a Superbird or Torino........

Getting used to the "no speed limit in the pit lane" took some work. Kind of
sucks though when that AI car
decides to pull out of the pit just as you race by in 3rd gear <g>.

Don

I bought NL just to race at Riverside only to find that Papy put the
starters stand on the wrong side of the track, not a huge error but it still
bugs me. Does anyone know of a way to fix this?

--
don

[|]-(_)-[|]

NL?

Update: I reinstalled a third time...this time after turning read-ahead off
on the CD-Rom.  It's working correctly now.

Don

You need to read the book.
Points 1 and 2 are easily accomplished.

Thanks for your input, but if you had read my note, you would have seen that
I had read the manual.  There should have been nothing to saving a set up,
esp since it is pretty much the same as in the other papy games I
own...however it flat wasn't working.  I was merely inquiring as to whether
or not others had this problem with the same title.
I have since fixed it by reinstalling with the read-ahead turned off on my
CD-rom drive and it is working correctly now. Why the game wasn't
functioning correctly on the  first two installs with read-ahead turned on
beats me, but may be related to a combination of  the CD-rom and particular
install package used, and there are several different ones out there.

I did a full install each time.  It wasn't trying to write to the CD, its
just that some of the game functions did not work correctly.  The source of
the problem is occurring during the install process.  It seems peculiar to
my machine and the
way that it reacts with certain vendors' install packages.  I have a US
Drives 24X CD-Rom and a 5 gig Western Digital
Hard drive.  Back when I set the system up, my mobo Bios did not yet have
the ability to read a drive larger than 2.1 gig
as a single partition, so I used Western Digital's Drive program to set
up/translate the FAT so that I can run the entire
drive as one large partition.    When installing a game, it will look like
it installed correctly and will normally work fine.
However, the install will be "blemished" by something that doesn't work like
it should or  doesn't look like it should.
For example: a map graphic that has a section that has a pallette
corruption, or something like the NL setup save function
error.  I have only had this problem on about 3 games in the last two years,
so it's not real serious, but I can assure  you that
when I go to a new HD the western Digital program will not go back on my
computer.  Depending on how the setup/install pkg was written, some of the
install data is lost/garbled between the read-ahead function on the CD rom
and the time it
gets stored on the HD......possibly due to something in the WD FAT
management program.

Don