argh... i killed my track

Use this forum to report bugs or ask for help

Moderator: kilo

argh... i killed my track

Postby simon-2 » Wed Feb 10, 2016 12:45 am

hi all,

i'm currently working on macau track, but i killed it and i don't know why.

last things i changed where all pit-related:
-added graphic files barrier_wall_arbor_n.png and name_wall.png
-added according surface definitions in xml file
-changed border style, side widths, border surface and so on in pit area
-added pit definitions in xml file

prior to these changes, everything worked fine.
Now, trackgen still runs w/o errors (--> xml is still ok, i think..?), but when starting a race, speed dreams crashes with the following message:

Code: Select all
00:00:12.639 Default  Info    Loading Viela.ac
00:00:12.707 Default  Error   GfTexReadImageFromPNG(data/textures/pylon1.png) : Bad byte count (96 instead of 128)
Speicherzugriffsfehler (Speicherabzug geschrieben)


("Speicherzugriffsfehler" means "seg fault")

any ideas..?

edit: removed old archive, see below for newer version
Last edited by simon-2 on Wed Feb 17, 2016 1:57 pm, edited 1 time in total.
simon-2
 
Posts: 83
Joined: Thu Jan 29, 2015 3:01 pm

Re: argh... i killed my track

Postby MiniJoe » Wed Feb 10, 2016 3:59 am

Hi Simon,
What version of Sd/Trackgen are you using?
This sounds like Ticket 905 on SourceForge. Fixed after 2.1 (should be OK in 2.2 beta).
http://sourceforge.net/p/speed-dreams/tickets/905/
I have attached pylon1.png
You should be able to replace just that file.
You do not have the required permissions to view the files attached to this post.
MiniJoe
 
Posts: 95
Joined: Fri Mar 16, 2012 1:32 am

Re: argh... i killed my track

Postby simon-2 » Wed Feb 10, 2016 3:45 pm

thanks again, joe for your immediate reply...

you're right, i've been to lazy to install the newest version yet; so still running 2.1..

the new pylon file fixed the error message, but it seems this was not the reason why SD crashes; i.e. now the last lines before crash are

Code: Select all
00:00:13.841 Default  Info    Loading Viela.ac
Speicherzugriffsfehler (Speicherabzug geschrieben)


anyway, i'm not able to restore a working condition, so i'm really perplexed...

ps: i imported the ac to blender and it seems ok... just with pits defined, it is really insane, but SD crashed both with and without pits...
simon-2
 
Posts: 83
Joined: Thu Jan 29, 2015 3:01 pm

Re: argh... i killed my track

Postby MiniJoe » Wed Feb 10, 2016 10:08 pm

Hi Simon,
I took a look at your Viela.xml file. The problem is (on line 5155 (section R_a2)). The pitwall height must be the same for the whole pit wall. Change this from 1.4 to 1.2 to match all the others segments containg pit walls. There are some bugs with pitwalls.
More info here:
viewtopic.php?f=5&t=626&start=20
MiniJoe
 
Posts: 95
Joined: Fri Mar 16, 2012 1:32 am

Re: argh... i killed my track

Postby simon-2 » Thu Feb 11, 2016 1:14 am

once again, you made my day :-) i can always rely on you...

and once again, this shows how much knowledge is already in this board, but it is so spread that it's hard to find info on a specific subject..
simon-2
 
Posts: 83
Joined: Thu Jan 29, 2015 3:01 pm

Re: argh... i killed my track

Postby simon-2 » Mon Feb 15, 2016 3:30 pm

i'm still encountering some problems with this track's pits.. but i will upgrade und check against 2.2.0 first, as some of them might be bugs and it's bad manners to complain about an outdated version :mrgreen:..
simon-2
 
Posts: 83
Joined: Thu Jan 29, 2015 3:01 pm

Re: argh... i killed my track

Postby simon-2 » Mon Feb 15, 2016 5:58 pm

tested it with 2.2 now; same problems..:


1. no barrier is drawn behind the pit wall border- i.e. left barrier is drawn correctly for segments up to pit entry and from pit exit, but not in the segments having a wall-style border. i tried all the styles (fence, wall and curb) and all barriers within this part have uniform height, width, style and surfaces. What else could be wrong..?

2. pit building continues after the end of pits. It seems as if trackgen would not understand where pit buildings should end...

this is how the pits are defined:
Code: Select all
<section name="Pits">
      <attnum name="pit style" val="1" />
      <attstr name="side" val="left" />
      <attstr name="entry" val="R_a1" />
      <attstr name="start" val="R_a2" />
      <attstr name="start buildings" val="pitstart" />
      <attstr name="end" val="reservoir-bend" />
      <attstr name="exit" val="pitout" />   
      <attnum name="max pits" val="9" />
      <attnum name="length" unit="m" val="15.0" />
      <attnum name="width" unit="m" val="5.0" />
    </section>

vielapits.png


following screenshot shows most of the dilemma:
sd-20160215181443.png

(barriers are missing on complete pit lane, i.e. also in front of building)
has anyone had such behaviour before? is it a bug, or a known issue, caused by errors, naming conventions etc within my xml file?

one more info- this is trackgen's output regarding pits:
Code: Select all
00:00:00.040 Default  Info    PitEntry: R_a1
00:00:00.040 Default  Info    PitExit: pitout
00:00:00.040 Default  Info    PitStart: R_a2
00:00:00.040 Default  Info    PitBuildingStart: lastStraight_b
00:00:00.040 Default  Info    PitEnd: reservoir-bend
00:00:00.040 Default  Info    track4:: Pit style: 1
00:00:00.040 Default  Debug   toStart: lastStraight_b 7.50 toStart: pitstart 7.93 toStart: pitstart 11.19 toStart: pitstart 10.54 toStart: pitstart 9.88 toStart: pitstart 9.23 toStart: pitstart 8.58 toStart: pitstart 7.93 toStart: pitstart 11.19 toStart: pitstart 10.54 toStart: pitstart 9.88 toStart: pitstart 9.23 toStart: pitstart 8.58 toStart: reservoir-bend 10.07 toStart: reservoir-bend 9.87 toStart: reservoir-bend 9.68 toStart: reservoir-bend 9.49 toStart: pitout 9.34 toStart: pitout 9.34 toStart: MainStraight2b0 9.24 toStart: MainStraight2b0 8.86 toStart: MainStraight2b0 8.47 toStart: MainStraight2b 8.09 toStart: MainStraight2b 7.85 toStart: MainStraight2b 7.61 toStart: MainStraight2b 11.18 toStart: MainStraight2b 10.95 toStart: MainStraight2b 10.71 toStart: MainStraight2c 10.59 toStart: MainStraight2c 10.59 toStart: MainStraight2c 10.59 toStart: MainStraight2c 10.59 toStart: MainStraight2d 10.25 toStart: MainStraight2d 9.56 toStart: MainStraight2d 8.87 toStart: MainStraight2d 8.19 toStart: MainStraight2d 7.50 toStart: MainStraight2d 10.74


notice, that:
-PitBuildingStart is lastStraight_b instead of "pitstart" as defined in xml
-debug output shows positions up to MainStraight2d, which is far behind pit end/exit; but this is approximately up to where trackgen creates buildings:
sd-20160215182817.png
You do not have the required permissions to view the files attached to this post.
simon-2
 
Posts: 83
Joined: Thu Jan 29, 2015 3:01 pm

Re: argh... i killed my track

Postby MiniJoe » Wed Feb 17, 2016 6:03 am

It looks like the track segment "pitstart' does not exist.
Can you post your changed xml file?
MiniJoe
 
Posts: 95
Joined: Fri Mar 16, 2012 1:32 am

Re: argh... i killed my track

Postby simon-2 » Wed Feb 17, 2016 1:57 pm

sorry, i made some changes in the xml (basically changed names and added segments)- attached is the newest version.
"pitstart" is now the first segment of the track and in the final version i would like to use its length completely (maybe 15 pits à 12m); i just reduced this for testing purpose.

but you should be able to observe the issues with the old xml (along with the old pit definition) as well..?
You do not have the required permissions to view the files attached to this post.
simon-2
 
Posts: 83
Joined: Thu Jan 29, 2015 3:01 pm

Re: argh... i killed my track

Postby MiniJoe » Sat Feb 20, 2016 2:46 am

The easiest way to partially fix this is to use the old-style pit definition.
Code: Select all
     <section name="Pits">
      <attnum name="pit style" val="1" />
      <attstr name="side" val="left" />
      <attstr name="entry" val="R_a1" />
      <attstr name="start" val="pitstart" />
      <attstr name="end" val="pitstart" />
      <attstr name="exit" val="pitout" />
      <attnum name="max pits" val="12" />
      <attnum name="length" unit="m" val="15.0" />
      <attnum name="width" unit="m" val="5.0" />
    </section>

The Viela.xml exposes several bugs in the SD2-trackgen program:
    The first segment in the xml file can not be found for "start buildings"
    The length of the pit buildings is computed incorrectly
    The visual barriers are not generated for for the pitlane.
MiniJoe
 
Posts: 95
Joined: Fri Mar 16, 2012 1:32 am

Next

Return to Problems, Fixes & Help

Who is online

Users browsing this forum: No registered users and 3 guests