Dennis tracks

[Pavel 69]

Can you post problematic 3d file here?

[Dennis]

chmlnrc.3d ist the working file from yesterday.
chmlnrc - Kopie.3d ist the bad file from today.

[Pavel 69]

I've converted both 3d files to 3do without problems. But I saggest to keep "nil : NIL;" string at the top of the 3d file after "3D VERSION 3.0" string.

Also, if you see such message don't worry. It's just information.

3d23do version 3.11:  Converting "Chmlnrc2.3d" -> "Chmlnrc2.3do"

Checking UV
Warning: Poly has stretched texture: __unnamed_object_5273 (8 pts) Ob 5279
Warning: Poly has stretched texture: __unnamed_object_5603 (4 pts) Ob 5605
Warning: Poly has stretched texture: __unnamed_object_5762 (4 pts) Ob 5764
Warning: Poly has stretched texture: __unnamed_object_5921 (4 pts) Ob 5923
Warning: Poly has stretched texture: __unnamed_object_6080 (4 pts) Ob 6082
Warning: Poly has stretched texture: __unnamed_object_6239 (4 pts) Ob 6241
Warning: Poly has stretched texture: __unnamed_object_6314 (4 pts) Ob 6316
Warning: Poly has stretched texture: __unnamed_object_6473 (4 pts) Ob 6475
Warning: Poly has stretched texture: __unnamed_object_6632 (4 pts) Ob 6634
Warning: Poly has stretched texture: __unnamed_object_6791 (4 pts) Ob 6793
Warning: Poly has stretched texture: __unnamed_object_6950 (4 pts) Ob 6952
Warning: Poly has stretched texture: __unnamed_object_7109 (4 pts) Ob 7111
Warning: Poly has stretched texture: __unnamed_object_7268 (4 pts) Ob 7270
Warning: Poly has stretched texture: __unnamed_object_7427 (4 pts) Ob 7429
Warning: Poly has stretched texture: __unnamed_object_7586 (4 pts) Ob 7588
Warning: Poly has stretched texture: __unnamed_object_7661 (4 pts) Ob 7663
Warning: Poly has stretched texture: __unnamed_object_7820 (4 pts) Ob 7822
Warning: Poly has stretched texture: __unnamed_object_7979 (4 pts) Ob 7981
Warning: Poly has stretched texture: __unnamed_object_8138 (4 pts) Ob 8140
Warning: Poly has stretched texture: __unnamed_object_8297 (4 pts) Ob 8299
Too many warnings to print...
Outputting

D:\ICR2_P~1\N3_tool\3DO_CR~1>pause
Press any key to continue . . .

[Dennis]

I know this message, I have it since the beginning.
But the problem is not the 3d->3do conversion.
The problem is the .dat conversion with the N99toICR2Converter.

[checkpoint10]

I know this message, I have it since the beginning.
But the problem is not the 3d->3do conversion.
The problem is the .dat conversion with the N99toICR2Converter.

Which version of the converter are you using? I used to have all kinds of errors with 1.00l and then I found 1.01c which seems to be very reliable. The newer one I have is from http://trackshoppe.com/utilities/utilities.htm under "N2<->ICR2 Converter"

[Pavel 69]

I know this message, I have it since the beginning.
But the problem is not the 3d->3do conversion.
The problem is the .dat conversion with the N99toICR2Converter.

I converted 3do without problems too. I use converter version 1.00l. Are you sure you've correctly removed MRON section from 3do before conversion?

[Dennis]

Are you sure you've correctly removed MRON section from 3do before conversion?

I'm sure, because I did it twice.

I downloaded the newer version of the converter and try it with it.
--------------------------------------------------------------------------------------
Update: With the new version it's fine, I don't get error messages.

If I had it already 6 years ago, I didn't have so much trouble with the objects, and maybe I didn't lose motivation several times.

[Dennis]

I did a lot of experimenting in the last days with object visibility and drawing order, and it seems, that I've found a new mystery.

Can someone explain, what the DYNO line in the .3d file exactly is and what function it has?
Everything else in the .3d file has x,y,z coordinates, but DYNO has dlong,dlat coordinates.

I want to put the track segments of the oval track as TSO to the road course.
As I made simply a .3do from one segment and placed it, it made strange effects. Its dlong,dlat coordinates refer to the oval track, so they aren't compatible with the road course. So I decided to replace the DYNO line simply with NIL. And then I became bad drawing order.
After I spent some hours to study the drawing commands and the BSP tree in the .3d file, it was obvious, that the drawing order is wrong.
But why looks a track normally correct? Does the DYNO line change the drawing order?

Here comes an explanation, how a track segment is built up normally.

FACE (track surface)
    LIST
        BSPA (right wall)
            BSPA (left wall)
                left objects
                left wall
                DYNO
            right wall
            right objects
        track surfaces

If we ignore the DYNO line, this structure results in transparent walls, because the track surfaces are drawing at last. That happens, when I place a track segment from the other track as TSO. But why not on the active track?

I changed the structure for the TSO subsegment as follows.

FACE (track surface)
    BSPN (left wall)
        BSPN (left wall)
            left objects
            left wall
        BSPA (right wall)
            LIST
                track surfaces
            right wall
            right objects

This looks good, but makes a lot of work. Probably I could make it by hand for the about 20 oval subsegments needed for the road course, but the about 100 road course subsegments needed for the oval track, would be definitely too much.

Any explanation or other input is welcome. Meanwhile I go on with the hills.

[Pavel 69]

If you look in track 3d file you can notice that track sections may appear with as HI, MED, LOW format. Low is used for farthest distances, MED on medium distances, HI at close distance. Ususlly four HI segments at farther distance are replaced with one MED segment. And four MED segments in farthest distance are replaced with singe LOW segment. Siwtch distance is determined by DYNO function that specified distance at which each segment is drawn. So when you remove DYNO line HI, LOW and MED segments are drawn simultaneously so you get wierd effect.

If you want to make object from track segment my advice is to use only HI segments (or MEDium). But I think you need to keep DYNO for this HI segments to make them drawn properly. I think I did such thing for Riverside scenery.

[Dennis]

If you look in track 3d file you can notice that track sections may appear with as HI, MED, LOW format. Low is used for farthest distances, MED on medium distances, HI at close distance. Ususlly four HI segments at farther distance are replaced with one MED segment. And four MED segments in farthest distance are replaced with singe LOW segment. Siwtch distance is determined by DYNO function that specified distance at which each segment is drawn. So when you remove DYNO line HI, LOW and MED segments are drawn simultaneously so you get wierd effect.

If you want to make object from track segment my advice is to use only HI segments (or MEDium). But I think you need to keep DYNO for this HI segments to make them drawn properly. I think I did such thing for Riverside scenery.

I know about HI, MED and LO segments, so I use only LO, because I have a lot of them, and I want to keep the graphics as light as possible, because I don't know, how much buildings and textures I will place in the future.
With keeping DYNO, the cars disappeared in the replay at some places.