1
Pebble Beach Problem
Started by David Fahrner , Jun 05 2010 - 10:24 AM
26 replies to this topic
#1
Posted Jun 05 2010 - 10:24 AM
I've downloaded Jim Turley's Pebble Beach GPL track and it installs correctly on my machine, but when I try to use the track I get a "could not load the track" error. An online search found a reference to a fix for this problem, another download called peb_resized.zip (or "peb resized.zip") but the link to racesimcentral.com is long gone. Does anybody know were I can find this fix, or if changes can be made to .ini or setup files to get the track to load? Thanks...
df
df
#2
Posted Jun 05 2010 - 12:16 PM
no problem when i tried it using "old" direct3d , it seems opengl problem.Its not load at all with "old" opengl.
perhaps one (or more) of *.mip's are unsuitable for opengl use.
i try it soon with Nigel rasterizers
perhaps one (or more) of *.mip's are unsuitable for opengl use.
i try it soon with Nigel rasterizers
Edited by Jhalli, Jun 05 2010 - 12:18 PM.
#3
Posted Jun 05 2010 - 02:32 PM
Try Kenny's update, it may fix your problem. https://srmz.racesimcentral.net/inde...indpost&p=42542
#4
Posted Jun 05 2010 - 02:40 PM
didnt know that update, thanks Craig.
trackdatabase not have a link to Kenny's update ,hmmm.....
trackdatabase not have a link to Kenny's update ,hmmm.....
#5
Posted Jun 06 2010 - 02:17 AM
OK, I've downloaded the Pebble Beach update, so how do I install it? Or can somebody refer me to some online site that explains how to do track updates? I should admit here that I'm brand-new to GPL - although I have installed it sucessfully and downloaded a few tracks, including Riverside (used to go out there to watch the Times-Mirror GP in the early 1960s) and Laguna Seca (did a few bicycle races there), and I used to cycle out to the old Pebble Beach course and ride around it all the time (that's why I need this track)...
df
df
#6
Posted Jun 06 2010 - 04:22 AM
i haven't had a look at either the update or the original track, but usually the way updates work is you unzip the archive the update is in into a temporary folder. if you are lucky, there is a .txt (readme of sorts) to go with it. if there is reading it might give you a clue, it might also include information of how to use different versions - although this is usually for car updates for the most part.
anyway, in your gpl directory should be a subfolder called "tracks" - in there are all the folders for the tracks you have installed. locate the track folder this update is for.
now here's two ways of going about it. the "gung-ho" (aka mine) or the "safety first" approach. the latter being the better. what you do is, you copy the entire track folder to something like <trackname_ORG> or similar so that you can go back if something goes wrong. then you copy the content of that temporary folder into the trackfolder, overwriting everything in there. presto.
the gung-ho approach is to copy the temporary folder content straight into the track folder - not recommended.
most of the time the updates will simply be better or corrected versions of the graphics. those files are .mip. if there are .3do's include in the package, that means some of the 3D objects have also been changed or added to the mix.
that should about cover it, i think. oh and welcome to the world of GPL enjoy your spare time, while you still have it
anyway, in your gpl directory should be a subfolder called "tracks" - in there are all the folders for the tracks you have installed. locate the track folder this update is for.
now here's two ways of going about it. the "gung-ho" (aka mine) or the "safety first" approach. the latter being the better. what you do is, you copy the entire track folder to something like <trackname_ORG> or similar so that you can go back if something goes wrong. then you copy the content of that temporary folder into the trackfolder, overwriting everything in there. presto.
the gung-ho approach is to copy the temporary folder content straight into the track folder - not recommended.
most of the time the updates will simply be better or corrected versions of the graphics. those files are .mip. if there are .3do's include in the package, that means some of the 3D objects have also been changed or added to the mix.
that should about cover it, i think. oh and welcome to the world of GPL enjoy your spare time, while you still have it
#7
Posted Jun 06 2010 - 06:26 AM
Just follow Sky's advice, this one just needs to be unzipped into the track directory like he says. Kenny's updates are very good and I doubt you would want to uninstall it.
#8
Posted Jun 06 2010 - 11:12 AM
That was the first thing I did, copy the upgrade files into the Pebble Beach folder in the tracks folder. But there don't seem to be any duplicate files in the original Pebble Beach track download (Pebble_Beach_final_100.zip) and the update (Pebble Beach update.RAR). The original has 13 files, a 9MB data file, some LP and configuration files, and the track install program. The update has 62 files, almost all MIP or SRB files, no install program, and a readme that only describes the changes. I must be missing something...???
I've also upgraded to GPL1.2.0.2, but no difference. Has anyone ever heard of the peb_resized.zip fix? Does "resized" indicate anything to anybody? Thanks, everybody, for your assistance...at some point, hopefully, I'll get Pebble working...
df
I've also upgraded to GPL1.2.0.2, but no difference. Has anyone ever heard of the peb_resized.zip fix? Does "resized" indicate anything to anybody? Thanks, everybody, for your assistance...at some point, hopefully, I'll get Pebble working...
df
#9
Posted Jun 06 2010 - 11:25 AM
actually that is sort of normal. tracks come with a few files, a bunch of .inis and a few others. the big .dat file is where all the other files are stored in.
gpl works in such a way that when it tries loading a file it checks the directory first. if the file isn't in there, it loads the file from the .dat.
so after you've done the initial install of the track you have that .dat, and a few other files. then you just copy the updated .mips, .srbs, .3dos and whatever in there and gpl should load them, instead of the (original) versions from the .dat. all the files that have no pendant in the directory will be loaded from inside the .dat.
if you still don't see any change, i suspect there's something else awry. wrong folder maybe?
gpl works in such a way that when it tries loading a file it checks the directory first. if the file isn't in there, it loads the file from the .dat.
so after you've done the initial install of the track you have that .dat, and a few other files. then you just copy the updated .mips, .srbs, .3dos and whatever in there and gpl should load them, instead of the (original) versions from the .dat. all the files that have no pendant in the directory will be loaded from inside the .dat.
if you still don't see any change, i suspect there's something else awry. wrong folder maybe?
#10
Posted Jun 06 2010 - 02:24 PM
sky, on Jun 06 2010 - 11:25 AM, said:
actually that is sort of normal. tracks come with a few files, a bunch of .inis and a few others. the big .dat file is where all the other files are stored in.
gpl works in such a way that when it tries loading a file it checks the directory first. if the file isn't in there, it loads the file from the .dat.
so after you've done the initial install of the track you have that .dat, and a few other files. then you just copy the updated .mips, .srbs, .3dos and whatever in there and gpl should load them, instead of the (original) versions from the .dat. all the files that have no pendant in the directory will be loaded from inside the .dat.
if you still don't see any change, i suspect there's something else awry. wrong folder maybe?
gpl works in such a way that when it tries loading a file it checks the directory first. if the file isn't in there, it loads the file from the .dat.
so after you've done the initial install of the track you have that .dat, and a few other files. then you just copy the updated .mips, .srbs, .3dos and whatever in there and gpl should load them, instead of the (original) versions from the .dat. all the files that have no pendant in the directory will be loaded from inside the .dat.
if you still don't see any change, i suspect there's something else awry. wrong folder maybe?
Thanks, Sky, that's good info to have - so an install program is not required, I guess...I'm pretty sure it's in the right folder (Sierra\gpl\tracks\pebble)...and the fact that there was a fix (that peb_resized.zip file) would seem indicate that it's something else...??? Maybe there's a later version of Pebble Beach that Pebble_Beach_final_100.zip?
df
#11
Posted Jun 06 2010 - 04:21 PM
Have you tried loading the track with different cars selected? I don't think it may be the cause but I had a corrupted file with one of my cars once and it was causing an issue.
#12
Posted Jun 06 2010 - 07:24 PM
"I've also upgraded to GPL1.2.0.2"
How did you install GPL? Did you use the GPLPS Installer?
How did you install GPL? Did you use the GPLPS Installer?
#13
Posted Jun 06 2010 - 09:46 PM
I installed GPL with the installation program that came on the Sold Out Software distribution CD. Selecting a different car doesn't seem to make any difference.
The 1.2.0.2 update I found online, and it installed without any problems, and everything else seems to work as before.
The 1.2.0.2 update I found online, and it installed without any problems, and everything else seems to work as before.
#14
Posted Jun 07 2010 - 02:40 AM
hm,
I've downloaded the track yesterday. will prolly try installing it later today and see what happens. same as bridgehampton. don't have the updates though.
I've downloaded the track yesterday. will prolly try installing it later today and see what happens. same as bridgehampton. don't have the updates though.
#15
Posted Jun 07 2010 - 06:06 AM
My Pebble Beach folder is 18.0mb exactly and works fine, I have Kenny's update installed. Check yours and see what size it is, maybe something is missing , worst case scenario I will PM you my directory to drop into your tracks folder to see if it works, you have no problems with other tracks I assume
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users