Point-to-point timing help

Discussion in 'Track Modding' started by myself9, Jun 4, 2014.

  1. freew67

    freew67 Registered

    Joined:
    Oct 5, 2010
    Messages:
    303
    Likes Received:
    5
    Single
     
  2. INTEL48

    INTEL48 Registered

    Joined:
    Apr 10, 2013
    Messages:
    229
    Likes Received:
    1
    I can get it to trigger, but not with timer count down in practice or qually
     
  3. INTEL48

    INTEL48 Registered

    Joined:
    Apr 10, 2013
    Messages:
    229
    Likes Received:
    1
    think I will upload a test track, very basic, no real road or anything, maybe 1km long, so we can all use and try different things..........is this a good idea
     
  4. freew67

    freew67 Registered

    Joined:
    Oct 5, 2010
    Messages:
    303
    Likes Received:
    5
    I think that is a good idea. Worth a shot to figure out whats up.
     
  5. freew67

    freew67 Registered

    Joined:
    Oct 5, 2010
    Messages:
    303
    Likes Received:
    5
    Nice talking with you myself9. Here is the pic of this setup in Max.

    https://www.dropbox.com/s/xva7jwhtstktcl6/P2Psectors.jpg

    Instance=xfinish
    {
    Render=False
    MeshFile=xfinish.gmt CollTarget=True HATTarget=False
    MeshFile=xfinish001.gmt CollTarget=True HATTarget=False
    MeshFile=xfinish002.gmt CollTarget=True HATTarget=False
    MeshFile=xfinish003.gmt CollTarget=True HATTarget=False
    Response=VEHICLE,TIMING
    }
    Instance=xsector1
    {
    Render=False Change=False
    MeshFile=xsector1.gmt CollTarget=True HATTarget=False
    MeshFile=xsector3.gmt CollTarget=True HATTarget=False
    MeshFile=xsector5.gmt CollTarget=True HATTarget=False
    Response=VEHICLE,TIMING
    }
    Instance=xsector2
    {
    Render=False Change=False
    MeshFile=xsector2.gmt CollTarget=True HATTarget=False
    MeshFile=xsector4.gmt CollTarget=True HATTarget=False
    MeshFile=xsector6.gmt CollTarget=True HATTarget=False
    Response=VEHICLE,TIMING
    }
    Instance=xpitin
    {
    Render=False Change=False
    MeshFile=xpitin.gmt CollTarget=True HATTarget=False
    MeshFile=xpitin01.gmt CollTarget=True HATTarget=False
    MeshFile=xpitin02.gmt CollTarget=True HATTarget=False
    Response=VEHICLE,PITSTOP
    }
    Instance=xpitout
    {
    Render=False Change=False
    MeshFile=xpitout.gmt CollTarget=True HATTarget=False
    Response=VEHICLE,PITSTOP
    }
     
  6. myself9

    myself9 Registered

    Joined:
    Jan 7, 2013
    Messages:
    348
    Likes Received:
    43
    BIG thanks for talking me through the finer points, freew67!

    I gave it a shot before work this morning. No luck yet. By comparing your code and the drag strip pic, I think I see what I need to fix.
    Can't wait to get home and test it out. I should have called in sick today!
     
  7. myself9

    myself9 Registered

    Joined:
    Jan 7, 2013
    Messages:
    348
    Likes Received:
    43
    I've set everything up perfectly and copied the scn code, but still no timing being triggered. Aaargh!

    Could it have something to do with recycling the rf1 aiw file?
     
  8. freew67

    freew67 Registered

    Joined:
    Oct 5, 2010
    Messages:
    303
    Likes Received:
    5
    Im using the rF1 AIW file. In simed turn on backface cull (I think that's what its called) and see which direction the sectors are facing. In my pic above you can the textured side is facing the car. If its the opposite, that could be the issue.
     
  9. myself9

    myself9 Registered

    Joined:
    Jan 7, 2013
    Messages:
    348
    Likes Received:
    43
    That was going to be my next question.

    I do believe you nailed it, sir! Thank you!
     
  10. INTEL48

    INTEL48 Registered

    Joined:
    Apr 10, 2013
    Messages:
    229
    Likes Received:
    1
    where is backface cull...cant seem to find it
     
  11. myself9

    myself9 Registered

    Joined:
    Jan 7, 2013
    Messages:
    348
    Likes Received:
    43
    If you're in 3dsimed, go to the Display menu at the top of the screen.
     
  12. myself9

    myself9 Registered

    Joined:
    Jan 7, 2013
    Messages:
    348
    Likes Received:
    43
    Got another question for you freew67, or anyone that knows the cause of this:

    Strange problem with the timing in practice mode.

    SOMETIMES, after running part of the track and esc to the pits, then starting again and crossing the first xfinish, "starting" xsectors and "starting" xfinish, it sets about a 3 second lap time.

    It seems that this occurs if the driver finished enough of a lap to pass xfinish002, but not complete a lap, before esc to the pits.
    In the dragstrip and scn code provided by freew67, xfinish002 is not called out

    Should xfinish002 be deleted, or the pre-starting line xfinsh/xsectors be modified in some way?
     
  13. freew67

    freew67 Registered

    Joined:
    Oct 5, 2010
    Messages:
    303
    Likes Received:
    5
    Is it only xfin002? Does it happen if you run a short first lap?

    What do you mean not called out?
     
  14. myself9

    myself9 Registered

    Joined:
    Jan 7, 2013
    Messages:
    348
    Likes Received:
    43
    I was just able to duplicate the error at will. THAT'S a good thing :)

    It happens when you leave the pits, cross all of the "starting line" xfinish/xsectors, then the next 2 xsectors and xfinish002, then esc to pits.

    Upon exiting the pits again for another lap, the timer is triggered on the pre-starting line xfinish, and the lap finishes at the starting line xfinish.

    When I said "called out", I meant in the scn file. Sometimes I have a problem being concise ;)

    The race mode drag strip scn calls out xfinish002

    Instance=xfinish
    {
    Render=False
    MeshFile=xfinish.gmt CollTarget=True HATTarget=False
    MeshFile=xfinish001.gmt CollTarget=True HATTarget=False
    MeshFile=xfinish002.gmt CollTarget=True HATTarget=False
    MeshFile=xfinish003.gmt CollTarget=True HATTarget=False
    Response=VEHICLE,TIMING


    The practice version doesn't
    Instance=xfinish
    {
    Render=False
    MeshFile=xfinish.gmt CollTarget=True HATTarget=False
    MeshFile=xfinish001.gmt CollTarget=True HATTarget=False
    MeshFile=xfinish003.gmt CollTarget=True HATTarget=False
    Response=VEHICLE,TIMING
    }


    BIG TIME EDIT:

    I just opened up the scn file in simed, and xfinish002 seems to have disappeared! WTH?
    I'll put it back in and repackage everything and see if that's where the problem lies.
     
    Last edited by a moderator: Jun 8, 2014
  15. myself9

    myself9 Registered

    Joined:
    Jan 7, 2013
    Messages:
    348
    Likes Received:
    43
    Issue solved, I believe!

    I'll post the details after I do a little more testing....
     
  16. myself9

    myself9 Registered

    Joined:
    Jan 7, 2013
    Messages:
    348
    Likes Received:
    43
    SO

    Based off of freew67's Practice Mode drag strip, here's the simple solution to stopping the freaky timers.

    In SimEd or whatever app you're using, delete the xfinish.gmt

    Then delete the callout to the instance in the output and scn file

    Instance=xfinish
    {
    Render=False
    MeshFile=xfinish.gmt CollTarget=True HATTarget=False <------------------------------Kill This
    MeshFile=xfinish001.gmt CollTarget=True HATTarget=False
    MeshFile=xfinish003.gmt CollTarget=True HATTarget=False
    Response=VEHICLE,TIMING
    }

    Package everything up and go racing!

    Seems like if you exit the course after passing the last xsector, but before the finish line, the game is expecting an xfinish to be the next object.
    So when you enter the course again from the pits and pass the pre-starting line xfinish, rfactor thinks that's a lap.
    Then the quick shot through the two pre-starting line xsectors and starting line xfinish count as another lap.
    No way to get out of the loop once it's begun!
     
    Last edited by a moderator: Jun 8, 2014
  17. A13

    A13 Registered

    Joined:
    Jul 31, 2012
    Messages:
    123
    Likes Received:
    29
    well done :)
     

Share This Page