Sorry for the slightly oversimplified thread title, but titles here have a length limit, that's why I had to keep it (too) simple
So... I'm testing both versions of BTB. So far I like what it offers (saves a huge amount of time, especially compared to using the Blender + TrackEd combo I've been using to create my tracks...), but there seems to be something wrong and I don't know if it's me doing something wrong, a bug, some problem with my hardware or some kind of limitation I'm not aware of.
Here's the thing: I make a track. In the early stage of completition, when there's only the track, some minimal terrain and maybe some roadside objects are in the track, I export it to rFactor (for Pro) or GTR2 (for Evo). Export is sucessful. I run rFactor/GTR2, load the track - works like charm. I go on with BTB, add more objects and elements, the track is getting more complicated. I'm still far from being halfway, say I added some walls, some more terrain, a couple of stands and crowd, a minimal pitlane. Time for a quick check how they look in the game, so another export (deleted the previous export from the game's Location folders beforehand). Seems to work again - though I notice exporting now takes a suspiciously long time (about 15-20 minutes). I run the game, I find the track in the track listing - but it no longer opens, but the game aborts instead. Both rFactor and GTR2 does this, tried with 2 different tracks.
I use XP, my PC is fairly new and, though not a top-notch config, still runs Crysys warhead rather smoothly (just to give you and idea about how much it can handle graphics performance-wise ). Still, the games aborting without any kind of notice seems to yell performance problems...
One thing I noticed is how huge folders BTB creates for the tracks. In GTR2, for example, the built-in tracks - that are much more elaborate and must contain many, many more objects, textures and staff - are all about 50-60 Mb in size - my tracks, even in their less-than-quarter-ready states, wer at least 75 Mb, some as huge as 150Mb... Can that be a problem?
I also found that by deleting stuff from the track I can get it back to a reduced state where it gets playable again. This, again, seems to indicate size problems.
The last thing I should mention is that Racer was still able to open the track rFactor wasn't...
So, anyone with an idea what I should/can do to be able to open my tracks in GTR2 or rFactor even after they grow a bit?
Thx for any advice.
bio
PS: Sorry if this problem has already been dealt with here. I leafed through the recent threads but found no sign of this happening to anyone else...
So... I'm testing both versions of BTB. So far I like what it offers (saves a huge amount of time, especially compared to using the Blender + TrackEd combo I've been using to create my tracks...), but there seems to be something wrong and I don't know if it's me doing something wrong, a bug, some problem with my hardware or some kind of limitation I'm not aware of.
Here's the thing: I make a track. In the early stage of completition, when there's only the track, some minimal terrain and maybe some roadside objects are in the track, I export it to rFactor (for Pro) or GTR2 (for Evo). Export is sucessful. I run rFactor/GTR2, load the track - works like charm. I go on with BTB, add more objects and elements, the track is getting more complicated. I'm still far from being halfway, say I added some walls, some more terrain, a couple of stands and crowd, a minimal pitlane. Time for a quick check how they look in the game, so another export (deleted the previous export from the game's Location folders beforehand). Seems to work again - though I notice exporting now takes a suspiciously long time (about 15-20 minutes). I run the game, I find the track in the track listing - but it no longer opens, but the game aborts instead. Both rFactor and GTR2 does this, tried with 2 different tracks.
I use XP, my PC is fairly new and, though not a top-notch config, still runs Crysys warhead rather smoothly (just to give you and idea about how much it can handle graphics performance-wise ). Still, the games aborting without any kind of notice seems to yell performance problems...
One thing I noticed is how huge folders BTB creates for the tracks. In GTR2, for example, the built-in tracks - that are much more elaborate and must contain many, many more objects, textures and staff - are all about 50-60 Mb in size - my tracks, even in their less-than-quarter-ready states, wer at least 75 Mb, some as huge as 150Mb... Can that be a problem?
I also found that by deleting stuff from the track I can get it back to a reduced state where it gets playable again. This, again, seems to indicate size problems.
The last thing I should mention is that Racer was still able to open the track rFactor wasn't...
So, anyone with an idea what I should/can do to be able to open my tracks in GTR2 or rFactor even after they grow a bit?
Thx for any advice.
bio
PS: Sorry if this problem has already been dealt with here. I leafed through the recent threads but found no sign of this happening to anyone else...