Original Papy tso problem

[bearlythere12]

I posted this in part of another thread but thought i'd get an actual answer in here. In short, i have a reoccurring problem when trying to use original Papy tsos.

"I had to resave the Rockingham grandstands using 3dsimed b/c simply grabbing them wouldn't work (track won't load in either Sandbox or the game). I have this problem infrequently when using original Papy 3dos. Anyone know what i'm doing wrong? Is there some sort of hidden mip that 3dsimed can't see??

Weird thing is that 3dsimed recognizes the object fine and i assume it "Export(ed) Textures" correctly. But the only way to get them to work is to resave the object. But sometimes 3dsimed doesn't save stuff correctly and i wind up w/ said problem (a streak coming off the front grandstands from time-to-time).

Even now w/ the track complete, you would think i could just grab the original Papy 3do and copy it straight to the track folder. But nope, track won't load."

 

[middlewaymuzak]

I posted this in part of another thread but thought i'd get an actual answer in here. In short, i have a reoccurring problem when trying to use original Papy tsos.

"I had to resave the Rockingham grandstands using 3dsimed b/c simply grabbing them wouldn't work (track won't load in either Sandbox or the game). I have this problem infrequently when using original Papy 3dos. Anyone know what i'm doing wrong? Is there some sort of hidden mip that 3dsimed can't see??

Weird thing is that 3dsimed recognizes the object fine and i assume it "Export(ed) Textures" correctly. But the only way to get them to work is to resave the object. But sometimes 3dsimed doesn't save stuff correctly and i wind up w/ said problem (a streak coming off the front grandstands from time-to-time).

Even now w/ the track complete, you would think i could just grab the original Papy 3do and copy it straight to the track folder. But nope, track won't load."

It's been a while since I edited any Papy TSOs... but I would open the TSO using notepad. Among the code, all mips needed will be listed.
Like I said, it's been a while

 

[Riviera71]

Using what Bowtie said (searching for mip in the 3do) the selected mips in the pic are the mips the main_build.3do uses. When I placed the 3do with those mips on an empty track (one segment, no f-sections or anything) it loaded (and showed up after the old save and reopen) in sandbox. Harder to try ingame with no track to go with it though

As for the streak coming from the grandstand, the only time I've seen anything like that was when I had one segment all on it's own, not attached to any other segment. If it's not the grandstand it might be a segment that's not properly attached in both ends? Unlock geometry and then rightclick somewhere in each segment and make sure that Attach Segment is greyed out for all of them.

Troubleshooting something that you yourself don't experience is never easy or fun.

Edit: unpacked your track and there is no pressb_01_mask.mip in there but maybe that was eliminated with the 3dsimed work?

 

[bearlythere12]

pressb_01_mask.mip sure sounds new to me.........checking........yep, you got it. Holy <>rap dude, thank you. Saved me big time. For whatever reason 3dsimed never exported that texture. Gonna do as Bowtie suggested and use notepad from now on as i've had this sort of problem for years. Guess my 3dsimed is flaky or something.

As for the streaks, get them all the time from faulty 3dos i've tried re-saving in 3dsimed after i remove/add something. Main reason why i've never released any of my tracks before, there's almost always a streak flash in my works.

Thanks to both of ya, load off my shoulders. You might have caused me to release more of my stuff in the future.

 

[Mystical]

As for the streaks, get them all the time from faulty 3dos i've tried re-saving in 3dsimed after i remove/add something. Main reason why i've never released any of my tracks before, there's almost always a streak flash in my works.

The reason for this is texture z-fighting. 3dos should never be re-saved using 3dsimed3. Especially the original papy 3dos. The reason being these 3dos have state switches and multiple 3d objects that appear or disappear depending on the race weekend state. For example a grandstand is actually 2-3 of the same grandstand model in a 3do, One for test session (no crowd) one for qualify/practice (few people in stands), then race day (full crowd). When you save the 3do in 3dsimed what you are doing is having all these models overlay eachother at once.

Not only does 3dsimed3 strip the scripting from a model and it also triple the vert count causing worse performance. Its recommended when making new 3dos or re-saving one to use make3do with a psg script for best efficiency and all scripting feature available.

 

[bearlythere12]

The reason for this is texture z-fighting. 3dos should never be re-saved using 3dsimed3. Especially the original papy 3dos. The reason being these 3dos have state switches and multiple 3d objects that appear or disappear depending on the race weekend state. For example a grandstand is actually 2-3 of the same grandstand model in a 3do, One for test session (no crowd) one for qualify/practice (few people in stands), then race day (full crowd). When you save the 3do in 3dsimed what you are doing is having all these models overlay eachother at once.

Not only does 3dsimed3 strip the scripting from a model and it also triple the vert count causing worse performance. Its recommended when making new 3dos or re-saving one to use make3do with a psg script for best efficiency and all scripting feature available.

Ha! I kinda figured it had something to do w/ the race weekend stuff. Thanks for setting me straight, but now i gotta learn make3do which i've tried using before w/ zero success.