03-30-2020, 04:15 AM
(This post was last modified: 04-01-2020, 05:43 AM by checkpoint10.)
Note from the latest version of Caesars.
- The pits tutorial & Excel file are easy to follow. However part of my pit lane is in a slightly different angle to the racing track and this caused some of the AI to be parked in the wrong position. I believe this means I need to make the pit lane parallel to the racing track and this may be a limitation of ICR2 and N2.
- Drawing the TSDs within OPE was hard to be exact, maybe due to the sensitive fake joystick controls I am using. But I ended up manually coding the pit lane lines in the .TSD file and then importing it into OPE. This actually might be the best way to draw pit lines, because the coordinates are largely the same coordinates you figure out for the track.txt file.
- I also realized that saving TSDs in OPE is a non-reversible process (unless you generate the .3D file again). In other words, once you save a .3D file in OPE with all your TSDs, you can't go back and unpaint them. Actually, I don't even think you can unpaint TSDs within the same OPE session. I tried to remove the TSD section of the .3D file by hand, but you also have to empty out the visibility lists which is tedious. I also apparently didn't do this right, because 3D23DO now gives me an warning when I compile (although it doesn't impact ultimately being able to convert to ICR2). I will probably do another fresh TRK23D at some point, which will require me to manually bring over TSOs from a back-up, as per Dennis's suggestion.
Edit: Another way is to copy all the TSOs (the first rows of a .3D file) into its own file. Then, every time you have to recompile the track, go into OPE, option F1, 3 to open the text file. This is now my preferred way to bring TSOs back into a track whenever I have to fix something in SFE or SGE.
- The pits tutorial & Excel file are easy to follow. However part of my pit lane is in a slightly different angle to the racing track and this caused some of the AI to be parked in the wrong position. I believe this means I need to make the pit lane parallel to the racing track and this may be a limitation of ICR2 and N2.
- Drawing the TSDs within OPE was hard to be exact, maybe due to the sensitive fake joystick controls I am using. But I ended up manually coding the pit lane lines in the .TSD file and then importing it into OPE. This actually might be the best way to draw pit lines, because the coordinates are largely the same coordinates you figure out for the track.txt file.
- I also realized that saving TSDs in OPE is a non-reversible process (unless you generate the .3D file again). In other words, once you save a .3D file in OPE with all your TSDs, you can't go back and unpaint them. Actually, I don't even think you can unpaint TSDs within the same OPE session. I tried to remove the TSD section of the .3D file by hand, but you also have to empty out the visibility lists which is tedious. I also apparently didn't do this right, because 3D23DO now gives me an warning when I compile (although it doesn't impact ultimately being able to convert to ICR2). I will probably do another fresh TRK23D at some point, which will require me to manually bring over TSOs from a back-up, as per Dennis's suggestion.
Edit: Another way is to copy all the TSOs (the first rows of a .3D file) into its own file. Then, every time you have to recompile the track, go into OPE, option F1, 3 to open the text file. This is now my preferred way to bring TSOs back into a track whenever I have to fix something in SFE or SGE.