+- Forums (https://www.icr2.net/forum)
+-- Forum: CART Racing Headquarters (https://www.icr2.net/forum/forumdisplay.php?fid=1)
+--- Forum: Indycar Racing 2 - CART Racing (ICR2) (https://www.icr2.net/forum/forumdisplay.php?fid=2)
+--- Thread: Dennis tracks (/showthread.php?tid=1105)
RE: Dennis tracks - Dennis - 12-22-2020
Yes, and the TSOs are together at the begin of the .3D file, so I can make corrections faster and I have a better overview. That's useful, because I want to extend visibility, so that I can see almost everything from everywhere.
As I already told, I'm a perfectionist, and I'm not really happy with some unsolved drawing problems. But now I looked at the original Laguna Seca track with different eyes, and I have a smile on my face. What a difference. I think, the guys of Papyrus didn't invest too much time to make good drawing.
RE: Dennis tracks - Dennis - 12-24-2020
I think, I've solved one part of the drawing "disorder".
An example:
segment 1 - TSO A,B
segment 2 - TSO A,B
segment 3 - TSO A,B
segment 4 - TSO A,B
segment 5 - TSO A,B
As you can see, at every track segment TSOs A and B are visible and A is everywhere behind B. In theory. But sometimes strange things happened, and from segment 3 onward A appeared in font of B. How could this happen, when A should be only visible in the segments 1-5 and always behind B?
My theory is, that the game draws an object just once at a frame, maybe to spare memory.
At segment 3, segment 6 comes visible, which has B as the only TSO. The human logic says, that A never can be in front of B, because it is behind B or invisible. But the game seems to draw the track segments from front to back and every TSO only once (I'm still not sure what happens, when an object is also left and right side TSO, in this case I'm still at trial and error).
So, when the car is arriving to segment 3, segment 6 is drawing and B. Then segment 5 is drawing and A. A should be behind B, but it can't, because B is already there, so it comes in front of it.
Now I can redo my drawing order again. It seems, that it still won't be the last time.
RE: Dennis tracks - checkpoint10 - 12-24-2020
Would the solution be to include TSO A in Segment 6 so that it forces the game to draw TSO A first when it first encounters Segment 6? Maybe you would need to include both TSO A and B for all the segments on the track that could be visible at the same time as both of those objects.
RE: Dennis tracks - Dennis - 12-24-2020
(12-24-2020, 05:40 AM)checkpoint10 Wrote: Would the solution be to include TSO A in Segment 6 so that it forces the game to draw TSO A first when it first encounters Segment 6? Maybe you would need to include both TSO A and B for all the segments on the track that could be visible at the same time as both of those objects.Yes, I made it so. After I spent days with trial and error, today I corrected almost all drawing errors within 3 hours.
RE: Dennis tracks - samsepi0l - 12-24-2020
Guys- I am commenting from a perspective of a newbie who is pretty ignorant, but even with Dosbox running on a newer computer can't we get away with murder compared to the original papyrus tracks? What I mean is, our machines these days are so much faster running dosbox ece 32 bit it should perform perfect with all of the objects loaded early so you can see them right? I remember reading that Pavel added more trees and other things to his versions of the tracks because they were lacking in the original game- I think that is due to hardware performance capabilities these days compared to 1995 right?
I would think the only limits would be what the game can handle- not the speed of our PCs
RE: Dennis tracks - Pavel 69 - 12-25-2020
(12-24-2020, 01:51 AM)Dennis Wrote: I think, I've solved one part of the drawing "disorder".In such case with two objects is better to combine them using BSPN function into one TSO in track.3d and call this one object in TSO list.
An example:
segment 1 - TSO A,B
segment 2 - TSO A,B
segment 3 - TSO A,B
segment 4 - TSO A,B
segment 5 - TSO A,B
As you can see, at every track segment TSOs A and B are visible and A is everywhere behind B. In theory. But sometimes strange things happened, and from segment 3 onward A appeared in font of B. How could this happen, when A should be only visible in the segments 1-5 and always behind B?
My theory is, that the game draws an object just once at a frame, maybe to spare memory.
At segment 3, segment 6 comes visible, which has B as the only TSO. The human logic says, that A never can be in front of B, because it is behind B or invisible. But the game seems to draw the track segments from front to back and every TSO only once (I'm still not sure what happens, when an object is also left and right side TSO, in this case I'm still at trial and error).
So, when the car is arriving to segment 3, segment 6 is drawing and B. Then segment 5 is drawing and A. A should be behind B, but it can't, because B is already there, so it comes in front of it.
Now I can redo my drawing order again. It seems, that it still won't be the last time.
See example attached. TSO8c, TSO14c, TSO25c, TSO29c there are combinations of several objects.
RE: Dennis tracks - Dennis - 12-25-2020
I had that idea also, but I will do it only at the end, if needed. As long as I'm making new objects, it needs probably more time to combine them this way again and again.
RE: Dennis tracks - Pavel 69 - 12-26-2020
No, it's pretty easy. And you'll save much time compare to just trying to figure out right drawing order.
RE: Dennis tracks - Dennis - 12-26-2020
Today I tried to add the track segments of the road course as TSO to extend visibility. I had to change the drawing order as described in post #71. I putted the DYNO line behind the track surfaces into the LIST statement, and the cars appeared also in the TSO segments.
Unfortunately, I need an other solution. As the TSO track segment is drawing after the regular track segment, there is bad drawing at the edge of the two segments.
Checkpoint10, did you make further experiments with the DATA lines?
If we don't find a solution, I will place simple polygons below the track surface in asphalt color (or I have to place some bushes to hide the problems
). I hope, we will find something better, because the track would look much better with walls.
RE: Dennis tracks - checkpoint10 - 12-26-2020
I haven't done any more work with DATA except my current belief that it tells the game which segment is associated with each DLONG, because the DLONGs don't appear elsewhere in the .3D file except in the comments and DYNO (which I believe relate to AI cars).