Guys...
I'm getting lost of email a questions about this issue. I have no clue why
it works on most systems and not on a few (it seems).
I can't troubleshoot a problem I don't have. So, I've started this string
so those of you who can't seem to get the alternate cockpit cam to work can
post your system specs and what you have in your N2K2/Series/Cup folders and
see if you can find a common denominator that's causing the problem just for
you.
I'm turning this over to you guys with the problem.
Tom
Troubleshooting Tom Pabst's alternate cockpit cam file
Tom Pabst asked for help with his alternate NASCAR Racing 2002 cockpit camera, which worked for some users only. Users discovered the make_a.cam file applies only to Chevrolets, so it must be copied as make_b and make_c for other makes. Others pointed to GPL camera and FOV editors that also work for NASCAR 2002, though a modified executable blocks Sierra online play.
Automated summary.
Hmmm...
Here's a try; no workee here with only 4 Files, 2002season.ini, all.ini,
cup.dat and series.def in the series/cup folder, along with the /cars
subfolder.
Tried the file named as make_a.cam through make_d.cam in case it was due to
choosing a different make of car. (I use Elliot's #9 Dodge; too lazy to
paint my own) No difference on any from oem view. I'm assuming this IS the
cockpit view, correct? Not a tweaked other view? I cycled through them all
for make_a.cam but not for the rest.
Running on an AMD XP1800/GF4-4400 on 98SE, using the current patched
version, N2002 1.1.0.2. I do note the size of my cup.dat file is 5233K vs
the 5221 on the CD. (I assume that's from the patch, as I've made no other
tweaks or changes to the program.)
Be interested to get this one sorted; but anyway, thanks for making the cam
available, Tom and for the updated track graphics. Nice work!
SB
Tom Pabst" <[email hidden]> wrote in message
news:RLX69.47825$me6.6536@sccrnsc01...
> Guys...
>
> I'm getting lost of email a questions about this issue. I have no cluewhy
> it works on most systems and not on a few (it seems).
>
> I can't troubleshoot a problem I don't have. So, I've started this string
> so those of you who can't seem to get the alternate cockpit cam to workcan
> post your system specs and what you have in your N2K2/Series/Cup foldersand
> see if you can find a common denominator that's causing the problem justfor
Quoted text (8 lines)
> you. > > I'm turning this over to you guys with the problem. > > Tom > > >Well, heres what I tried Tom, with no success.
Unpacked cup.dat and moved the file out. No cup.dat file left just the files
(lots).
Unpacking also created a Art sub folder.
Copied your make_a.cam and bottom.mip files to the cup folder and replaced
what had been extracted.
PIII 1Ghz 512Ram GF2 GTS Vid Win 98SE OpenGL Updated N2002 Patch
No change to InCar but I did notice if I delete the make_b.cam and
make_c.cam in one view (not InCar) I get a view from underneath the car and
a good look at the inside of the front tires :) Not sure if your files had
anything to do with that but kinda cool I suppose that Papy took the time to
draw all that lol
--
Tim White
www.intracmotorsports.com
"Steve Blankenship" <[email hidden]> wrote in message
news:DwY69.162631$[email hidden]...
> Hmmm...
>
> Here's a try; no workee here with only 4 Files, 2002season.ini, all.ini,
> cup.dat and series.def in the series/cup folder, along with the /cars
> subfolder.
>
> Tried the file named as make_a.cam through make_d.cam in case it was due
to
> choosing a different make of car. (I use Elliot's #9 Dodge; too lazy to
> paint my own) No difference on any from oem view. I'm assuming this IS
the
> cockpit view, correct? Not a tweaked other view? I cycled through them
all
> for make_a.cam but not for the rest.
>
> Running on an AMD XP1800/GF4-4400 on 98SE, using the current patched
> version, N2002 1.1.0.2. I do note the size of my cup.dat file is 5233K vs
> the 5221 on the CD. (I assume that's from the patch, as I've made no
other
> tweaks or changes to the program.)
>
> Be interested to get this one sorted; but anyway, thanks for making the
cam
> available, Tom and for the updated track graphics. Nice work!
>
> SB
>
> Tom Pabst" <[email hidden]> wrote in message
> news:RLX69.47825$me6.6536@sccrnsc01...
> > Guys...
> >
> > I'm getting lost of email a questions about this issue. I have no clue
> why
> > it works on most systems and not on a few (it seems).
> >
> > I can't troubleshoot a problem I don't have. So, I've started this
string
> > so those of you who can't seem to get the alternate cockpit cam to work
> can
> > post your system specs and what you have in your N2K2/Series/Cup folders
> and
> > see if you can find a common denominator that's causing the problem just
> for
> > you.
> >
> > I'm turning this over to you guys with the problem.
> >
> > Tom
> >
> >
> >
>
>
i have found that it works fine, but maybe not on a track or two... might
help
--
Donald Wilshe
888 588-9207
Martel Brothers Performance, Worlds Largest On-Line Auto Parts Mfg Catalog
Library
www.martelbros.com
Other Interest:
www.ivga.com
www.games-advertising.com
www.whra.com
"Tom Pabst" <[email hidden]> wrote in message
news:RLX69.47825$me6.6536@sccrnsc01...
> Guys...
>
> I'm getting lost of email a questions about this issue. I have no clue
why
> it works on most systems and not on a few (it seems).
>
> I can't troubleshoot a problem I don't have. So, I've started this string
> so those of you who can't seem to get the alternate cockpit cam to work
can
> post your system specs and what you have in your N2K2/Series/Cup folders
and
> see if you can find a common denominator that's causing the problem just
for
> you.
>
> I'm turning this over to you guys with the problem.
>
> Tom
>
>
>
>
Guys...
This is not an "answer"....but may help you troubleshoot this. The
"make_a.cam" file alters the roof cam. It takes the original one and lowers
it down into the cockpit. So, if you have the standard roof cam still (when
hitting the page down key), then somehow the alternate "make_a.cam" outside
of the dat file is not being read by the game. And, I haven't got a clue
what causes that to happen on some systems and not on others.
TP
"Tom Pabst" <[email hidden]> wrote in message
news:RLX69.47825$me6.6536@sccrnsc01...
> Guys...
>
> I'm getting lost of email a questions about this issue. I have no cluewhy
> it works on most systems and not on a few (it seems).
>
> I can't troubleshoot a problem I don't have. So, I've started this string
> so those of you who can't seem to get the alternate cockpit cam to workcan
> post your system specs and what you have in your N2K2/Series/Cup foldersand
> see if you can find a common denominator that's causing the problem justfor
Quoted text (8 lines)
> you. > > I'm turning this over to you guys with the problem. > > Tom > > >Tim...
Don't know if I would have eliminated the dat file....but apparently its had
no negative impact.
Deleting the two cam files must have kicked in some sort of "default"
cam.....in their absence. Who knows? 3D programs can do some weird default
stuff......in my experience.
And because of this sentence, "No change to InCar but I did notice if
........" The "in-car" cockpit is not what's changed....its the roofcam,
that now is inside the car. Just to make sure, thought I'd better mention
that.
TP
"Tim" <[email hidden]> wrote in message
news:sJY69.14115$[email hidden]...
> Well, heres what I tried Tom, with no success.
> Unpacked cup.dat and moved the file out. No cup.dat file left just thefiles
and
> a good look at the inside of the front tires :) Not sure if your fileshad
> anything to do with that but kinda cool I suppose that Papy took the timeto
vs
clue
> > why
> > > it works on most systems and not on a few (it seems).
> > >
> > > I can't troubleshoot a problem I don't have. So, I've started this
> string
> > > so those of you who can't seem to get the alternate cockpit cam towork
> > can
> > > post your system specs and what you have in your N2K2/Series/Cupfolders
> > and
> > > see if you can find a common denominator that's causing the problemjust
Quoted text (10 lines)
> (lots). > Unpacking also created a Art sub folder. > > Copied your make_a.cam and bottom.mip files to the cup folder and replaced > what had been extracted. > > PIII 1Ghz 512Ram GF2 GTS Vid Win 98SE OpenGL Updated N2002 Patch > > No change to InCar but I did notice if I delete the make_b.cam and > make_c.cam in one view (not InCar) I get a view from underneath the carQuoted text (26 lines)
> draw all that lol > > -- > Tim White > www.intracmotorsports.com > > > "Steve Blankenship" <[email hidden]> wrote in message > news:DwY69.162631$[email hidden]... > > Hmmm... > > > > Here's a try; no workee here with only 4 Files, 2002season.ini, all.ini, > > cup.dat and series.def in the series/cup folder, along with the /cars > > subfolder. > > > > Tried the file named as make_a.cam through make_d.cam in case it was due > to > > choosing a different make of car. (I use Elliot's #9 Dodge; too lazy to > > paint my own) No difference on any from oem view. I'm assuming this IS > the > > cockpit view, correct? Not a tweaked other view? I cycled through them > all > > for make_a.cam but not for the rest. > > > > Running on an AMD XP1800/GF4-4400 on 98SE, using the current patched > > version, N2002 1.1.0.2. I do note the size of my cup.dat file is 5233KQuoted text (15 lines)
> > the 5221 on the CD. (I assume that's from the patch, as I've made no > other > > tweaks or changes to the program.) > > > > Be interested to get this one sorted; but anyway, thanks for making the > cam > > available, Tom and for the updated track graphics. Nice work! > > > > SB > > > > Tom Pabst" <[email hidden]> wrote in message > > news:RLX69.47825$me6.6536@sccrnsc01... > > > Guys... > > > > > > I'm getting lost of email a questions about this issue. I have noQuoted text (13 lines)
> > for > > > you. > > > > > > I'm turning this over to you guys with the problem. > > > > > > Tom > > > > > > > > > > > > > > >It should not matter what track....at least I've not found a track that it
matters. There is a difference (slightly) for each of the cars...it moves
about its original orientation slightly. It was built for the Chevy...which
is what I drive. Keep in mind, I didn't create this cam file for the
net....it was done strictly for my WC cockpit simulator....and a few guys
asked to see it.....that's how it got out and this "problem" surfaced.
TP
"Don Wilshe" <[email hidden]> wrote in message
news:whZ69.300821$[email hidden]...
string
Quoted text (25 lines)
> i have found that it works fine, but maybe not on a track or two... might > help > > > -- > Donald Wilshe > 888 588-9207 > Martel Brothers Performance, Worlds Largest On-Line Auto Parts Mfg Catalog > Library > www.martelbros.com > Other Interest: > www.ivga.com > www.games-advertising.com > www.whra.com > > > "Tom Pabst" <[email hidden]> wrote in message > news:RLX69.47825$me6.6536@sccrnsc01... > > Guys... > > > > I'm getting lost of email a questions about this issue. I have no clue > why > > it works on most systems and not on a few (it seems). > > > > I can't troubleshoot a problem I don't have. So, I've started thisQuoted text (17 lines)
> > so those of you who can't seem to get the alternate cockpit cam to work > can > > post your system specs and what you have in your N2K2/Series/Cup folders > and > > see if you can find a common denominator that's causing the problem just > for > > you. > > > > I'm turning this over to you guys with the problem. > > > > Tom > > > > > > > > > >Tom,
If that were the case, then wouldn't making all three make_x.cams the same,
result in all 3 paging options giving the same view?
just making sure i understand the cam files, thanks
--
Tim White
www.intracmotorsports.com
"Tom Pabst" <[email hidden]> wrote in message
news:LqZ69.49249$me6.5698@sccrnsc01...
> Guys...
>
> This is not an "answer"....but may help you troubleshoot this. The
> "make_a.cam" file alters the roof cam. It takes the original one and
lowers
> it down into the cockpit. So, if you have the standard roof cam still
(when
> hitting the page down key), then somehow the alternate "make_a.cam"
outside
> of the dat file is not being read by the game. And, I haven't got a clue
> what causes that to happen on some systems and not on others.
>
> TP
>
I couldn't get Tom's files to make any difference to the roof cam view.
Then read in his post that he made the files for the Chev. Hmmmm I thought.
I've got a custom paint job on the Grand Prix for my car. So I went and
changed my car to Waltrip's 15 car. Hey presto.....it works. I
like....:o) Haven't tried on the other makes of default cars as yet.
Steve
system specs
win 98
p3 600 @ 738 (doubling size of cpu soon. married, kid, on a budget)
256meg ram
gforce 2 mx 200 (don't laugh. married, kid, on a budget)
opengl
patched N2002
"Steve Whitty" <[email hidden]> wrote in message
news:3d5c96ed$0$29908$[email hidden]...
> I couldn't get Tom's files to make any difference to the roof cam view.
> Then read in his post that he made the files for the Chev. Hmmmm Ithought.
> I've got a custom paint job on the Grand Prix for my car. So I went and
> changed my car to Waltrip's 15 car. Hey presto.....it works. I
> like....:o) Haven't tried on the other makes of default cars as yet.
>
> Steve
This sounds like a good lead. Are we misinterpretting what make_a.cam is?
Remember in N3, the cars were called a, b, c and d. I guess there could be a
camera for each car type called make_a.cam, make_b.cam etc. In N3 "a" was a
Chevy, "b" was a Ford etc. I drive a Ford which could well be why the cam
file doesn't work. I'm going to try renaming the camera to make_b.cam to see
what happens. I'll test this theory out tonight.
Phil
---
Race Sim Central Administrator
http://www.racesimcentral.com
Tim..
I haven't tried it...but I assume they would.
TP
"Tim" <[email hidden]> wrote in message
news:VWZ69.14132$[email hidden]...
> Tom,
>
> If that were the case, then wouldn't making all three make_x.cams thesame,
clue
> > what causes that to happen on some systems and not on others.
> >
> > TP
> >
>
>
Quoted text (20 lines)
> result in all 3 paging options giving the same view? > just making sure i understand the cam files, thanks > > -- > Tim White > www.intracmotorsports.com > > > "Tom Pabst" <[email hidden]> wrote in message > news:LqZ69.49249$me6.5698@sccrnsc01... > > Guys... > > > > This is not an "answer"....but may help you troubleshoot this. The > > "make_a.cam" file alters the roof cam. It takes the original one and > lowers > > it down into the cockpit. So, if you have the standard roof cam still > (when > > hitting the page down key), then somehow the alternate "make_a.cam" > outside > > of the dat file is not being read by the game. And, I haven't got aYou might be on to something there......
TP
"Phil Lee" <[email hidden]> wrote in message
news:aji9d8$1bk04t$[email hidden]...
a
> camera for each car type called make_a.cam, make_b.cam etc. In N3 "a" wasa
> Chevy, "b" was a Ford etc. I drive a Ford which could well be why the cam
> file doesn't work. I'm going to try renaming the camera to make_b.cam tosee
Quoted text (14 lines)
> "Steve Whitty" <[email hidden]> wrote in message > news:3d5c96ed$0$29908$[email hidden]... > > I couldn't get Tom's files to make any difference to the roof cam view. > > Then read in his post that he made the files for the Chev. Hmmmm I > thought. > > I've got a custom paint job on the Grand Prix for my car. So I went and > > changed my car to Waltrip's 15 car. Hey presto.....it works. I > > like....:o) Haven't tried on the other makes of default cars as yet. > > > > Steve > > > This sounds like a good lead. Are we misinterpretting what make_a.cam is? > Remember in N3, the cars were called a, b, c and d. I guess there could beQuoted text (8 lines)
> what happens. I'll test this theory out tonight. > > Phil > --- > Race Sim Central Administrator > http://www.racesimcentral.com > >Bingo - got it working last night as make_b.cam for the Dodge. Depends on
which car you drive whether you use a,b,c, etc... Interesting; reminds me
of a GPL cam I did for someone who wanted an in-car that still allowed you
to see the data readouts you get with the chase view. This one's a bit too
wide angle on the FOV for my tastes, but it does give you a driver's-eye
perspective without the obstructed tank-slot view of the cockpit.
Thanks for sharing it,
SB
"Tom Pabst" <[email hidden]> wrote in message
news:wU179.47733$Zl2.11115@sccrnsc02...
view.
> > > Then read in his post that he made the files for the Chev. Hmmmm I
> > thought.
> > > I've got a custom paint job on the Grand Prix for my car. So I wentand
is?
> > Remember in N3, the cars were called a, b, c and d. I guess there couldbe
> a
> > camera for each car type called make_a.cam, make_b.cam etc. In N3 "a"was
> a
> > Chevy, "b" was a Ford etc. I drive a Ford which could well be why thecam
Quoted text (10 lines)
> You might be on to something there...... > > TP > > > "Phil Lee" <[email hidden]> wrote in message > news:aji9d8$1bk04t$[email hidden]... > > "Steve Whitty" <[email hidden]> wrote in message > > news:3d5c96ed$0$29908$[email hidden]... > > > I couldn't get Tom's files to make any difference to the roof camQuoted text (7 lines)
> > > changed my car to Waltrip's 15 car. Hey presto.....it works. I > > > like....:o) Haven't tried on the other makes of default cars as yet. > > > > > > Steve > > > > > > This sounds like a good lead. Are we misinterpretting what make_a.camQuoted text (12 lines)
> > file doesn't work. I'm going to try renaming the camera to make_b.cam to > see > > what happens. I'll test this theory out tonight. > > > > Phil > > --- > > Race Sim Central Administrator > > http://www.racesimcentral.com > > > > > >
Steve Blankenship <[email hidden]> wrote in message
news:g_579.27063$[email hidden]...
> Bingo - got it working last night as make_b.cam for the Dodge.Depends on
> which car you drive whether you use a,b,c, etc... Interesting;reminds me
> of a GPL cam I did for someone who wanted an in-car that still allowedyou
> to see the data readouts you get with the chase view. This one's abit too
> wide angle on the FOV for my tastes, but it does give you adriver's-eye
> perspective without the obstructed tank-slot view of the cockpit.
>
> Thanks for sharing it,
>
> SB
>
Yep, different car makes use different make_*.cam files (*makes* sense
when you think about it) ;o)
To cover your bases, copy & rename TP's "make_a.cam" to "make_b.cam", &
"make_c.cam" (there is no "make_d.cam", seems the Dodge uses the Ford's
make_b.cam?), so you end up with 3 .cam files (all exactly the same,
just named make_a, make_b, & make_c) in the \cup dir.
Thx for the files, Tom, but the gauges & mirror are too small for my
tastes. Maybe has something to do with the wider FOV? Guess I'll stick
with the in-cockpit view & hope someone figures out how to adjust the it
(tho it seems unlikely, from what I recall reading about something to do
with the 3D movement). Except at the RC's, there I use Sam Dobie's
"sd_cockpit" from N4. Yeahhhhhhhhh, then I'm a roof-rider. ;o(
-Red
cam
> view.
> > > > Then read in his post that he made the files for the Chev.Hmmmm I
> > > thought.
> > > > I've got a custom paint job on the Grand Prix for my car. So Iwent
> and
> > > > changed my car to Waltrip's 15 car. Hey presto.....it works.I
> > > > like....:o) Haven't tried on the other makes of default cars asyet.
> > > >
> > > > Steve
> > >
> > >
> > > This sounds like a good lead. Are we misinterpretting whatmake_a.cam
> is?
> > > Remember in N3, the cars were called a, b, c and d. I guess therecould
> be
> > a
> > > camera for each car type called make_a.cam, make_b.cam etc. In N3"a"
> was
> > a
> > > Chevy, "b" was a Ford etc. I drive a Ford which could well be whythe
> cam
> > > file doesn't work. I'm going to try renaming the camera tomake_b.cam to
Quoted text (13 lines)
> > "Tom Pabst" <[email hidden]> wrote in message > news:wU179.47733$Zl2.11115@sccrnsc02... > > You might be on to something there...... > > > > TP > > > > > > "Phil Lee" <[email hidden]> wrote in message > > news:aji9d8$1bk04t$[email hidden]... > > > "Steve Whitty" <[email hidden]> wrote in message > > > news:3d5c96ed$0$29908$[email hidden]... > > > > I couldn't get Tom's files to make any difference to the roofQuoted text (14 lines)
> > see > > > what happens. I'll test this theory out tonight. > > > > > > Phil > > > --- > > > Race Sim Central Administrator > > > http://www.racesimcentral.com > > > > > > > > > > > > >
"B.Farmer" <[email hidden]> wrote in message
news:6c779.5865$[email hidden]...
maybe the make_d.cam is for Toyota. The old ICR2 guys found a way to put
a 4th engine(the toyota) into that sim. Trouble was, the sound engine
couldn't take 4 different engine notes and the Toyotas sounded like they
were spinning 30krpm while idling. You always KNEW when a Toyo was near.
>dave henrie
Quoted text (27 lines)
> > Steve Blankenship <[email hidden]> wrote in message > news:g_579.27063$[email hidden]... > > Bingo - got it working last night as make_b.cam for the Dodge. > Depends on > > which car you drive whether you use a,b,c, etc... Interesting; > reminds me > > of a GPL cam I did for someone who wanted an in-car that still allowed > you > > to see the data readouts you get with the chase view. This one's a > bit too > > wide angle on the FOV for my tastes, but it does give you a > driver's-eye > > perspective without the obstructed tank-slot view of the cockpit. > > > > Thanks for sharing it, > > > > SB > > > > Yep, different car makes use different make_*.cam files (*makes* sense > when you think about it) ;o) > > To cover your bases, copy & rename TP's "make_a.cam" to "make_b.cam", & > "make_c.cam" (there is no "make_d.cam", seems the Dodge uses the Ford's > make_b.cam?), so you end up with 3 .cam files (all exactly the same, > just named make_a, make_b, & make_c) in the \cup dir.Dave Henrie <[email hidden]> wrote in message
news:Zi779.50923$Zl2.10967@sccrnsc02...
<snip>
> > To cover your bases, copy & rename TP's "make_a.cam" to"make_b.cam", &
> > "make_c.cam" (there is no "make_d.cam", seems the Dodge uses theFord's
> > make_b.cam?), so you end up with 3 .cam files (all exactly the same,
> > just named make_a, make_b, & make_c) in the \cup dir.
>
> maybe the make_d.cam is for Toyota. The old ICR2 guys found a wayto put
> a 4th engine(the toyota) into that sim. Trouble was, the sound engine
> couldn't take 4 different engine notes and the Toyotas sounded likethey
> were spinning 30krpm while idling. You always KNEW when a Toyo wasnear.
>
> dave henrie
>
Wasn't there also a debate 'bout adding a 4th chassis (Swift)? Or was
that just for replacing the Lola? Where's Mark Collins when ya need
him? ;o)
-Red
Hey BF....
Nice detective work. I probably should have figured something like that but
as I said, I made that cam file for my own use and wasn't trying to make
something "universal" for the net download. However, its useful to know.
All you have to do is grab the GPLCam editor and you can change the views
(FOV) on your own. The gauges are the same as the "outside" gauges for all
the cam views. I don't use them, so didn't really care what they looked
like....but being too small would be my assessment as well.
I'm glad you guys figured this out. I figured if we concentrated the effort
into one string....it would get done quickly.
Regards,
Tom
"B.Farmer" <[email hidden]> wrote in message
news:6c779.5865$[email hidden]...
Quoted text (98 lines)
> > Steve Blankenship <[email hidden]> wrote in message > news:g_579.27063$[email hidden]... > > Bingo - got it working last night as make_b.cam for the Dodge. > Depends on > > which car you drive whether you use a,b,c, etc... Interesting; > reminds me > > of a GPL cam I did for someone who wanted an in-car that still allowed > you > > to see the data readouts you get with the chase view. This one's a > bit too > > wide angle on the FOV for my tastes, but it does give you a > driver's-eye > > perspective without the obstructed tank-slot view of the cockpit. > > > > Thanks for sharing it, > > > > SB > > > > Yep, different car makes use different make_*.cam files (*makes* sense > when you think about it) ;o) > > To cover your bases, copy & rename TP's "make_a.cam" to "make_b.cam", & > "make_c.cam" (there is no "make_d.cam", seems the Dodge uses the Ford's > make_b.cam?), so you end up with 3 .cam files (all exactly the same, > just named make_a, make_b, & make_c) in the \cup dir. > > Thx for the files, Tom, but the gauges & mirror are too small for my > tastes. Maybe has something to do with the wider FOV? Guess I'll stick > with the in-cockpit view & hope someone figures out how to adjust the it > (tho it seems unlikely, from what I recall reading about something to do > with the 3D movement). Except at the RC's, there I use Sam Dobie's > "sd_cockpit" from N4. Yeahhhhhhhhh, then I'm a roof-rider. ;o( > > -Red > > > > > "Tom Pabst" <[email hidden]> wrote in message > > news:wU179.47733$Zl2.11115@sccrnsc02... > > > You might be on to something there...... > > > > > > TP > > > > > > > > > "Phil Lee" <[email hidden]> wrote in message > > > news:aji9d8$1bk04t$[email hidden]... > > > > "Steve Whitty" <[email hidden]> wrote in message > > > > news:3d5c96ed$0$29908$[email hidden]... > > > > > I couldn't get Tom's files to make any difference to the roof > cam > > view. > > > > > Then read in his post that he made the files for the Chev. > Hmmmm I > > > > thought. > > > > > I've got a custom paint job on the Grand Prix for my car. So I > went > > and > > > > > changed my car to Waltrip's 15 car. Hey presto.....it works. > I > > > > > like....:o) Haven't tried on the other makes of default cars as > yet. > > > > > > > > > > Steve > > > > > > > > > > > > This sounds like a good lead. Are we misinterpretting what > make_a.cam > > is? > > > > Remember in N3, the cars were called a, b, c and d. I guess there > could > > be > > > a > > > > camera for each car type called make_a.cam, make_b.cam etc. In N3 > "a" > > was > > > a > > > > Chevy, "b" was a Ford etc. I drive a Ford which could well be why > the > > cam > > > > file doesn't work. I'm going to try renaming the camera to > make_b.cam to > > > see > > > > what happens. I'll test this theory out tonight. > > > > > > > > Phil > > > > --- > > > > Race Sim Central Administrator > > > > http://www.racesimcentral.com > > > > > > > > > > > > > > > > > > > > > >Yep, it's the 98 degree FOV that makes the gauges & mirror look small. As
Tom says, you can tweak it with Brian Heiland's great GPL carcam editor;
it's not a dedicated NR2002 program, but it works fine; the roof cam here is
seen as the rollbar cam in the editor. Get it at:
http://www.fortunecity.com/underworld/3d/797/
Cheers, (and thanks again Brian!)
SB
"Tom Pabst" <[email hidden]> wrote in message
news:Ca979.51603$Zl2.11469@sccrnsc02...
> Hey BF....
>
> Nice detective work. I probably should have figured something like thatbut
> as I said, I made that cam file for my own use and wasn't trying to make
> something "universal" for the net download. However, its useful to know.
> All you have to do is grab the GPLCam editor and you can change the views
> (FOV) on your own. The gauges are the same as the "outside" gauges forall
> the cam views. I don't use them, so didn't really care what they looked
> like....but being too small would be my assessment as well.
>
> I'm glad you guys figured this out. I figured if we concentrated theeffort
> into one string....it would get done quickly.
>
> Regards,
>
> Tom
Hey Steve...
Thanks for posting that link to the GPL carcam editor. I couldn't remember
where I got it.....I've actually had it for a long time. In fact....it was
quite by accident that I discovered this would work for the N2K2 cams. I
was doing some track editing and noticed that several of the file extensions
were listed as "GPL..xxx" ....file types. This led me to experiment to see
if the GPL carcam editor worked....and bingo it did, no sweat. There are
several other file formats in N2K2, though they have different file
extension names....they are simply GPL files.
Maybe others will be able to use the carcam editor now....and they can
adjust these alternate cockpits as they have the need. If I raced at a pure
desktop rig, I would stick to the standard 3D cockpit, however. It immerses
you better........but that's just my opinion.
On the same note, I know a lot of guys drive from the roof cam...or chase
cam too. I spend a lot of time driving in those views.......not racing
exactly....but driving around the tracks....when I'm doing track graphics
(you often need to make a change to graphic texture...then go into the track
and check to see if it works they way you wanted...part of the reason that
doing these track re-textured jobs takes so long).....and I haven't got a
clue why they like it. Its fun....I'll give it that, but you don't have any
advantage that I can see. I'm 2x slower in those views....even though I
have a better vantage point of the racing surface and upcoming track. Maybe
my brain doesn't allow me to function at peak....because its been in a lot
of race cars and therefore doesn't get immersed when in a chase view or
something? I don't know.....but I thought I'd mention what my experience is
with this issue.
By the way, the angle of the FOV in that carcam you tried wasn't arbitrarily
chosen. I sat in a GTA race car out at Sears Point (at M&R Racing).....the
GTA race car cockpits are nearly identical to a WC car. I put a helmet
on....and had somebody at the shop use string to identify the edges of my
peripheral vision with the helmet on (taped the string to the sides of my
helmet...then stretched it out to the front windshield....etc., and my head
in the driving position/seat....looking straight forward. What you see in
that carcam is exactly what you'd see, sitting in a cup car. The 3D cockpit
of Papy's has to wide of an FOV.....you can't see all that stuff they show
in that cockpit. But, I suspect they did it on purpose.....because it looks
cool.
Regards,
Tom
"Steve Blankenship" <[email hidden]> wrote in message
news:6O979.175734$[email hidden]...
> Yep, it's the 98 degree FOV that makes the gauges & mirror look small. As
> Tom says, you can tweak it with Brian Heiland's great GPL carcam editor;
> it's not a dedicated NR2002 program, but it works fine; the roof cam hereis
know.
> > All you have to do is grab the GPLCam editor and you can change theviews
Quoted text (16 lines)
> seen as the rollbar cam in the editor. Get it at: > > http://www.fortunecity.com/underworld/3d/797/ > > Cheers, (and thanks again Brian!) > > SB > > "Tom Pabst" <[email hidden]> wrote in message > news:Ca979.51603$Zl2.11469@sccrnsc02... > > Hey BF.... > > > > Nice detective work. I probably should have figured something like that > but > > as I said, I made that cam file for my own use and wasn't trying to make > > something "universal" for the net download. However, its useful toQuoted text (14 lines)
> > (FOV) on your own. The gauges are the same as the "outside" gauges for > all > > the cam views. I don't use them, so didn't really care what they looked > > like....but being too small would be my assessment as well. > > > > I'm glad you guys figured this out. I figured if we concentrated the > effort > > into one string....it would get done quickly. > > > > Regards, > > > > Tom > >I drive a custom chevy, and it doesn't work here .. YET ! lol
--
Tim White
www.intracmotorsports.com
"Steve Whitty" <[email hidden]> wrote in message
news:3d5c96ed$0$29908$[email hidden]...
> I couldn't get Tom's files to make any difference to the roof cam view.
> Then read in his post that he made the files for the Chev. Hmmmm I
thought.
> I've got a custom paint job on the Grand Prix for my car. So I went and
> changed my car to Waltrip's 15 car. Hey presto.....it works. I
> like....:o) Haven't tried on the other makes of default cars as yet.
>
> Steve
>
> system specs
> win 98
> p3 600 @ 738 (doubling size of cpu soon. married, kid, on a budget)
> 256meg ram
> gforce 2 mx 200 (don't laugh. married, kid, on a budget)
> opengl
> patched N2002
>
>
Can I get this view somewhere? Now that it works :o)
>"Tom Pabst"
>alternate cockpit cam to work can
>post your system specs and what you have in your N2K2/Series/Cup foldersand
SNIP
I'm a cockpit guy too, Tom; just can't resist the urge to tweak. Would be
nice though, if some bright soul would figure out how to adjust the POV/FOV
of the 3D cockpit view ala GPLShift or GPLFOV/GPLSA. I'm kinda scrawny and
I'd like to scoot the seat up a bit... ;-)
As for the 98 degree FOV, the only issue I have with it is how it distorts
the track view and changes your sense of motion. Going so wide angle makes
the tracks look loooonnng! Plus, while it does intensify sense of speed, it
reduces the sensation of lateral motion. Just a preference thing for me, as
I've always preferred something close to Papy's 78 degree std. - even in
F1-2002. Never could get happy with the 40-50 degree zoom lens effect a lot
of folks went for with GPL. Made the corners flow oddly, imho. You could
probably get your correct in-car view with a narrower FOV by moving the POV
back a bit.
The Glen's new skies do look nice without the roof in the way, though!
SB
"Tom Pabst" <[email hidden]> wrote in message
news:iGa79.168321$[email hidden]...
> Hey Steve...
>
> Thanks for posting that link to the GPL carcam editor. I couldn'tremember
> where I got it.....I've actually had it for a long time. In fact....itwas
> quite by accident that I discovered this would work for the N2K2 cams. I
> was doing some track editing and noticed that several of the fileextensions
> were listed as "GPL..xxx" ....file types. This led me to experiment tosee
> if the GPL carcam editor worked....and bingo it did, no sweat. There are
> several other file formats in N2K2, though they have different file
> extension names....they are simply GPL files.
>
> Maybe others will be able to use the carcam editor now....and they can
> adjust these alternate cockpits as they have the need. If I raced at apure
> desktop rig, I would stick to the standard 3D cockpit, however. Itimmerses
> you better........but that's just my opinion.
>
> On the same note, I know a lot of guys drive from the roof cam...or chase
> cam too. I spend a lot of time driving in those views.......not racing
> exactly....but driving around the tracks....when I'm doing track graphics
> (you often need to make a change to graphic texture...then go into thetrack
> and check to see if it works they way you wanted...part of the reason that
> doing these track re-textured jobs takes so long).....and I haven't got a
> clue why they like it. Its fun....I'll give it that, but you don't haveany
> advantage that I can see. I'm 2x slower in those views....even though I
> have a better vantage point of the racing surface and upcoming track.Maybe
> my brain doesn't allow me to function at peak....because its been in a lot
> of race cars and therefore doesn't get immersed when in a chase view or
> something? I don't know.....but I thought I'd mention what my experienceis
> with this issue.
>
> By the way, the angle of the FOV in that carcam you tried wasn'tarbitrarily
> chosen. I sat in a GTA race car out at Sears Point (at M&RRacing).....the
> GTA race car cockpits are nearly identical to a WC car. I put a helmet
> on....and had somebody at the shop use string to identify the edges of my
> peripheral vision with the helmet on (taped the string to the sides of my
> helmet...then stretched it out to the front windshield....etc., and myhead
> in the driving position/seat....looking straight forward. What you see in
> that carcam is exactly what you'd see, sitting in a cup car. The 3Dcockpit
> of Papy's has to wide of an FOV.....you can't see all that stuff they show
> in that cockpit. But, I suspect they did it on purpose.....because itlooks
> cool.
>
> Regards,
>
> Tom
Hey Tom where can I get these new cam files?
"Tom Pabst" <[email hidden]> wrote in message
news:RLX69.47825$me6.6536@sccrnsc01...
> Guys...
>
> I'm getting lost of email a questions about this issue. I have no cluewhy
> it works on most systems and not on a few (it seems).
>
> I can't troubleshoot a problem I don't have. So, I've started this string
> so those of you who can't seem to get the alternate cockpit cam to workcan
> post your system specs and what you have in your N2K2/Series/Cup foldersand
> see if you can find a common denominator that's causing the problem justfor
Quoted text (8 lines)
> you. > > I'm turning this over to you guys with the problem. > > Tom > > >I would also like to try it
"Plowboy" <Plowboy'[email hidden]> wrote in message
news:3d5d6a67$[email hidden]...
Quoted text (9 lines)
> Can I get this view somewhere? Now that it works :o) > > >"Tom Pabst" > >alternate cockpit cam to work can > >post your system specs and what you have in your N2K2/Series/Cup folders > and > SNIP > >Sorry if this appears as a double post, but I'm having problems with
my ISP's news server - here's a repost.
One of the GPL FOV editors - FovEd (foved.exe) by Alex Cameron also
works of the N4 and N2002 executables.
Phil Flack's GPL FOV editor (the original) will not work, since it
assume a hard-coded location of the FOV. FovEd searches the
executable for the position of the default FOV value (78 degrees) and
will work with N4/N2002 (with an unmodified FOV).
To use, bring up the File->Settings dialog, select "Search GPL.exe",
and enter the path to your NR2002 executable (with an unmodified FOV -
back it up beforehand, as it will be modified). Press Search and then
Save (this will save the NR2002.exe path and FOV offset in a foved.ini
file). Close the dialog and then set the FOV and Save.
For me, setting the N2002 FOV to 65 degrees looks pretty close to
Tom's (in terms of part of the cockpit is visisble), greatly lessens
the claustrophobic tank slot view, and provides the impression that
the seat has been moved forward.
Brian
"Steve Blankenship" <[email hidden]> wrote in message news:<UVb79.30919$[email hidden]>...
Quoted text (15 lines)
> I'm a cockpit guy too, Tom; just can't resist the urge to tweak. Would be > nice though, if some bright soul would figure out how to adjust the POV/FOV > of the 3D cockpit view ala GPLShift or GPLFOV/GPLSA. I'm kinda scrawny and > I'd like to scoot the seat up a bit... ;-) > > As for the 98 degree FOV, the only issue I have with it is how it distorts > the track view and changes your sense of motion. Going so wide angle makes > the tracks look loooonnng! Plus, while it does intensify sense of speed, it > reduces the sensation of lateral motion. Just a preference thing for me, as > I've always preferred something close to Papy's 78 degree std. - even in > F1-2002. Never could get happy with the 40-50 degree zoom lens effect a lot > of folks went for with GPL. Made the corners flow oddly, imho. You could > probably get your correct in-car view with a narrower FOV by moving the POV > back a bit. >Gracias for the heads-up! Will check it out asap.
SB
"Brian Michael" <[email hidden]> wrote in message
news:[email hidden]...
news:<UVb79.30919$[email hidden]>...
> > I'm a cockpit guy too, Tom; just can't resist the urge to tweak. Wouldbe
> > nice though, if some bright soul would figure out how to adjust thePOV/FOV
> > of the 3D cockpit view ala GPLShift or GPLFOV/GPLSA. I'm kinda scrawnyand
> > I'd like to scoot the seat up a bit... ;-)
> >
> > As for the 98 degree FOV, the only issue I have with it is how itdistorts
> > the track view and changes your sense of motion. Going so wide anglemakes
> > the tracks look loooonnng! Plus, while it does intensify sense ofspeed, it
> > reduces the sensation of lateral motion. Just a preference thing forme, as
> > I've always preferred something close to Papy's 78 degree std. - even in
> > F1-2002. Never could get happy with the 40-50 degree zoom lens effect alot
> > of folks went for with GPL. Made the corners flow oddly, imho. Youcould
> > probably get your correct in-car view with a narrower FOV by moving thePOV
> > back a bit.
> >
Quoted text (25 lines)
> Sorry if this appears as a double post, but I'm having problems with > my ISP's news server - here's a repost. > > One of the GPL FOV editors - FovEd (foved.exe) by Alex Cameron also > works of the N4 and N2002 executables. > > Phil Flack's GPL FOV editor (the original) will not work, since it > assume a hard-coded location of the FOV. FovEd searches the > executable for the position of the default FOV value (78 degrees) and > will work with N4/N2002 (with an unmodified FOV). > > To use, bring up the File->Settings dialog, select "Search GPL.exe", > and enter the path to your NR2002 executable (with an unmodified FOV - > back it up beforehand, as it will be modified). Press Search and then > Save (this will save the NR2002.exe path and FOV offset in a foved.ini > file). Close the dialog and then set the FOV and Save. > > For me, setting the N2002 FOV to 65 degrees looks pretty close to > Tom's (in terms of part of the cockpit is visisble), greatly lessens > the claustrophobic tank slot view, and provides the impression that > the seat has been moved forward. > > Brian > > "Steve Blankenship" <[email hidden]> wrote in messageIt works great and 65 degrees is about perfect,however you cant race on
sierra, you get the message your exe is not up to date or modified,any
workarounds as I really like the new view??
"Steve Blankenship" <[email hidden]> wrote in message
news:IFT79.208334$[email hidden]...
message
> news:<UVb79.30919$[email hidden]>...
> > > I'm a cockpit guy too, Tom; just can't resist the urge to tweak.Would
> be
> > > nice though, if some bright soul would figure out how to adjust the
> POV/FOV
> > > of the 3D cockpit view ala GPLShift or GPLFOV/GPLSA. I'm kindascrawny
in
> > > F1-2002. Never could get happy with the 40-50 degree zoom lens effecta
> lot
> > > of folks went for with GPL. Made the corners flow oddly, imho. You
> could
> > > probably get your correct in-car view with a narrower FOV by movingthe
> POV
> > > back a bit.
> > >
>
>


































