Posted: 08 Dec 2008, 10:57
I tried creating a track using double-wide track pieces. The track I was aiming to create is a large double-oval, which seemed like a simple idea. It might be a bit big, but technically its not too much larger than any of the other tracks I was hoping to create.
Its basically just four 38 long straights with four U-turns connecting them. The end result is a load time that's, um, long. Really long. How do you avoid load times like that? I mean, I figure you could trim it down by re-using the same few prms over and over - short straight, small turn, big turn, etc... But it might make for redundant tracks, and piecing all the little pieces together one at a time sounds like a real pain.
Another thing, looking at the UltraGlide track, the main NCP file is 836k, and it loads in a reasonable amount of time. The combined size for all the NCPs in my track is 1.4megs, yet mine seems to take considerably longer to load than the one in UltraGlide. What's up with that? Do NCPs load faster when they're for the .w file or something? Or when they're merged?
Its basically just four 38 long straights with four U-turns connecting them. The end result is a load time that's, um, long. Really long. How do you avoid load times like that? I mean, I figure you could trim it down by re-using the same few prms over and over - short straight, small turn, big turn, etc... But it might make for redundant tracks, and piecing all the little pieces together one at a time sounds like a real pain.
Another thing, looking at the UltraGlide track, the main NCP file is 836k, and it loads in a reasonable amount of time. The combined size for all the NCPs in my track is 1.4megs, yet mine seems to take considerably longer to load than the one in UltraGlide. What's up with that? Do NCPs load faster when they're for the .w file or something? Or when they're merged?