1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
Dismiss Notice
Like RaceDepartment on Facebook.

TrackEd : Splitter

Discussion in 'Racer Problems & Fixes' started by berzingue, May 24, 2015.

  1. Hi all, that's me, and I'm coming back with my problems...

    Actually, I use TrackEd 7.7.0 and Racer 0.90 RC 10.

    Carlswood have a good FPS (around 72 FPS.)
    But when I test my track (385.000 polys and .dds textures... ) , framerate is very low. (Under 10 FPS).

    I'm not sure, but probably I must use "splitter" button in TrackEd. Then it should go better.

    But when I push this button, it's like TrackEd do nothing and stops to work.

    Here are my questions :

    - Is it normal Splitter works so long ? how many hours must we wait before a result ?
    - Must I create a c:/sims/racer/output directory, as said in old racer doc ? or is it different with racer 090RC10 ?

    Thanks for answer....
     
  2. Alexander Knoll

    Alexander Knoll
    NEVER GIVE UP!!

    Hi,
    yes you have to create the output folder, like racer doc's say...
    hmm...i'm not sure, but it need some minutes....

    Alex
     
  3. Thanks Alex, finally Splitter finished to load, but there is a message error at the end :

    QLOG last said :

    Mon May 25 12:23:58 (WARN): RTrackSplitter:SplitGeob(); out of vertices (max=250000) [split.cpp:370 / RTrackSplitter::SplitGeob]
    Mon May 25 15:03:19 (WARN): [3236707x repeat] RTrackSplitter:SplitGeob(); out of vertices (max=250000) [split.cpp:370 / RTrackSplitter::SplitGeob]
    Mon May 25 15:03:19 (WARN): QInfo:Write(); file (data/tracks/sotchi_split/geometry.ini) can't be written [qinfo.cpp:780 / QInfo::Write]

    QLOG said :

    Mon May 25 12:23:58 (WARN ): [tracked] RTrackSplitter:SplitGeob(); out of vertices (max=250000) [split.cpp:370 / RTrackSplitter::SplitGeob]
    Mon May 25 15:03:19 (WARN ): [tracked] [3236707x repeat] RTrackSplitter:SplitGeob(); out of vertices (max=250000) [split.cpp:370 / RTrackSplitter::SplitGeob]
    Mon May 25 15:03:19 (WARN ): [tracked] QInfo:Write(); file (data/tracks/sotchi_split/geometry.ini) can't be written [qinfo.cpp:780 / QInfo::Write]
    Mon May 25 15:06:54 (INFO ): [tracked] Loading track 'sotchi' [rtrack.cpp:1348 / RTrack::Load]
    Mon May 25 15:07:29 (WARN ): [tracked] No surfaces found that match pattern 'gras*' [rtrack.cpp:1153 / ApplySurfaceTypeToMaterials]
    Mon May 25 15:07:29 (WARN ): [tracked] No surfaces found that match pattern 'ker*' [rtrack.cpp:1153 / ApplySurfaceTypeToMaterials]
     
  4. Alexander Knoll

    Alexander Knoll
    NEVER GIVE UP!!

    hmm...
    the Qlog Last sounds like you hit the boundarys of tracked...maybe...but i'm not sure...never had this...
    the write problem sounds like a user rights problem?
    the pattern error can be ignored for the mom...

    Bob you are the QLog specialist, can you help me out?

    Alex
     
  5. Sorry Alex, I never used the track splitter. I made smaller .dofs and never had problems even with huge tracks.

    Perhaps if the track in question was posted it could be looked at for a better solution than trying to us the track splitter.
     
  6. How many render calls are you making?

    Use CTRL 6 screen in Racer and you'll get a few readouts.

    Renderer triangles drawn:
    Tris visible %:
    OpenGL draw calls:

    Since Racer is not perfectly multi-threaded, the CPU core that the graphics runs on can also be shared with other processes too, so basically it gets bogged down with lots of draw calls.

    That is the single biggest cause of low FPS really.

    I've run gigabytes of textures on tracks before, all visible at once, and get 60fps+, or run millions of polygons of geometry, and get perfectly fine FPS.

    Yet run 1mb of textures and 5000 triangles and I can make it run 15fps.


    Splitter made sense more with the old rendering engine, but the new one is more bottlenecked with draw calls, so splitting can actually slow you down.


    It sounds mostly like you just need to optimise your track manually first, and make there be less textures and geometry entities, than make more!

    Dave
     
  7. finally, framerate is good when I use "Cut Multisub Ase".
    Actually framerate = 72fps. So it's perfect.

    Thanks all for answers and help. ;)