One for the GTR2 Track Builders

[Caribstu]

I have an issue with two track builds, Chiltern Downs (released) and Lincoln (to be released)

When you enter the track from the GARAGE screen the car drops 'plonks' down into the garage. similarly, when you go to RACE from the garage screen the car drops into the grid position.

this error did not happen when i was first developing the track, it's something which came on quite late in the editing phase. I don't know the root cause or how to fix it.

I wonder if perhaps, during the post production stage, between exporting edited versions of the track from BTB, and importing into 3DsimEd somehow the track model has ended up marginally lower on the Z axis than the AIW waypoint coordinates for the Grid and Garage position Z value. But I'm not certain, and that would be a huge amount of editing to change all the grid and garage Z values, without knowing exactly, trial and error shot in the dark type stuff.

Has anyone else come across this problem, if so .... HELP.... PLEASE.... I'd love to be able to fix it. How did you fix it?

Thanks.

 

[IMC '67]

I would just do the height adjustment testing using ONE car and then adjust the heights for the other slots with the same difference since you mentioned that all cars used to be in level with the track surface. An alternative would be to raise the whole track with the figure you got from testing one car.

 

[sunalp2]

That's what I've done before.

Adjust the height:


[PITS]
TeamIndex=0
PitPos=(-11.664,-0.086,-11.213)
PitOri=(-0.003,1.314,0.000)
GarPos=(0,-11.116,-0.087,-14.608)
GarOri=(0,0.001,2.897,-0.005)
GarPos=(1,-8.050,-0.072,-13.845)
GarOri=(1,0.001,2.897,-0.004)
GarPos=(2,-5.043,-0.061,-13.095)
GarOri=(2,0.001,2.897,-0.003)

A little at a time until it's right.

Same for the grid:

[GRID]
GridIndex=0
Pos=(-34.154,-0.125,-7.205)
Ori=(0.000,1.370,0.000)

 

[Caribstu]

That's what I've done before.

Adjust the height:


[PITS]
TeamIndex=0
PitPos=(-11.664,-0.086,-11.213)
PitOri=(-0.003,1.314,0.000)
GarPos=(0,-11.116,-0.087,-14.608)
GarOri=(0,0.001,2.897,-0.005)
GarPos=(1,-8.050,-0.072,-13.845)
GarOri=(1,0.001,2.897,-0.004)
GarPos=(2,-5.043,-0.061,-13.095)
GarOri=(2,0.001,2.897,-0.003)

A little at a time until it's right.

Same for the grid:

[GRID]
GridIndex=0
Pos=(-34.154,-0.125,-7.205)
Ori=(0.000,1.370,0.000)

IMC67 made a good suggestion. (can't believe I didn't think of that )

I'm thinking to incrementally adjust the Z value of a specific grid or garage position, and keep loading the track in Race Mode without qualifying but with that grid position pre-selected until the car no longer drops into the garage or grid space. Note the difference in Z height. Then return them both to the current Z value so they're all the same.

In 3Dsimed raise the model by the same amount.

That hopefully would correct all the grid slots and garages.

 

[Caribstu]

Update on this issue. The 'dropping' has been fixed and I've uploaded a FIX folder to the GTR2 Tracks mods.

Process: Went back into BTB and exported a new track. Then in 3DsimEd i imported an object from the new track into the existing track model. Noting the difference of Z axis. The object from the new track was -0.27 LOWER than the existing track model.

So, at some point during the post production editing stage, I'd raised the entire track model by 0.27.

Simple solution was to lower the model by -0.27 and export into the original track GTR and trk.

Did a test run and all is good. No more dropping into the garage or grid slots.

Also fixed two curbs and the landscape horizon object issues that were creating blue distortion and morphing of the hills. The FIX folder also has CAM files for a couple of other tracks which correct TV Cams that were below the track surface.

 

[Shovas]

So, at some point during the post production editing stage, I'd raised the entire track model by 0.27.

It seems this is more common on mod tracks than it really should be.

I wonder if it's not you but maybe some glitch or rounding error in the software that has a trigger we're unaware of

 

[Caribstu]

It seems this is more common on mod tracks than it really should be.

I wonder if it's not you but maybe some glitch or rounding error in the software that has a trigger we're unaware of

Possibly, because I can't see me accidentally or intentionally raising the entire model, and it's happened on more than one of my track builds. Specifically those I was doing a LOT of post production on in 3DsimED. In all cases it just seemed to happen out of the blue. But good thing is I know the fix now.