• So long as all your wheels are pointing in roughly the same direction, you should be fine.
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. Dear Guest. Follow RaceDepartment on Twitter, Facebook, Instagram, Twitch, Steam and YouTube.

Sobjects Problem

Discussion in 'Bob's Track Builder' started by Stealthy, Sep 1, 2009.

  1. Stealthy

    Stealthy

    Messages:
    118
    Ratings:
    +0
    Everytime i try to use a long Sobject like a wall my track freezes on export , why dose this always happen?
     
  2. Stealthy

    Stealthy

    Messages:
    118
    Ratings:
    +0
    please someone help , when ever i use Sobjects at lenght it freezes my game when i go to export
     
  3. Eric Tozer

    Eric Tozer

    Messages:
    301
    Ratings:
    +1
    Does it happen with sobjects in the default xpack ??
     
  4. Stealthy

    Stealthy

    Messages:
    118
    Ratings:
    +0
    yes , but this error is from a custom xpack
     
  5. MaxAttack

    MaxAttack

    Messages:
    26
    Ratings:
    +0
    I had a problem like that but it went away with later versions.
     
  6. Eric Tozer

    Eric Tozer

    Messages:
    301
    Ratings:
    +1
    how long are your sobjects?
    I can try it here & see if i get the same problem.
     
  7. Stealthy

    Stealthy

    Messages:
    118
    Ratings:
    +0
    multiples a k long first noticed the problem when using the great britten xpack
     
  8. Brendon Pywell

    Brendon Pywell
    Bob's Track Builder

    Messages:
    418
    Ratings:
    +156
    A quick guess at the problem: it's probably overflowing the maximum amount of point/polys that an rFactor GMT can contain.

    Each SObject creates one GMT.

    As a guide you should limit the size of a SObject. This is improtant for two reasons:
    1. It avoids the problem you are having with rFactor export.
    2. 4 x 250m walls will render better than 1 x 1000m wall because the Level Of Detail system will be more effective.

    I'll add a test upon export to at least skip long SObjects rather than export them.

    The reason I don't prevent them in the first place is because RBR isn't affected by this problem.