1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Where can I get BTB 0.6?

Discussion in 'Bob's Track Builder' started by Rubinhofan, Jan 22, 2011.

  1. Maybe someone has a link to the 0.6 version of btb. I need it.
  2. If you only need it for the method there is no need from BTB06 since months ago.

    Updated scripts can be downloaded using subversion software. More details here:
    (updated documentation can be found inside the downloaded files)

    And there is a french language web with more info and a few videos
    Parlesportes' site: http://www.plpcreation.tonsite.biz/

    And if you have doubts this forum is a good place to ask: http://forum.rallyesim.fr/viewtopic.php?f=51&t=3025
  3. Yes, I´ve seen the updated scripts and documentation. That´s the reason I want to start again with creating tracks. (IRC Monte-Carlo 2011).

    But at the end I get a venue.xml. (s9_join)
    For BTB 0.8 I need a BIN-file.

    Hopefully you can help me again.
  4. BTB 0.8 can read the Venue.xml (and of course also .bin)
    Otherwise the method would be useless, as BTB 0.6 can read .xml files, but can't write .bin files
  5. Thanks, works fine.
  6. I´ve created a 37 km long stage, but I can´t use it with Octave:

    > importakml('SS1.kml')
    Leyendo el fichero SS1.kml
    ECHO ist eingeschaltet (ON).
    ECHO ist eingeschaltet (ON).
    ECHO ist eingeschaltet (ON).
    ECHO ist eingeschaltet (ON).
    Cerrando el fichero
    3190 valores
    Escribiendo el fichero ..\mapeo.txt
    Cerrando el fichero
    Escribiendo el fichero salida\trazado.kml
    Grabando ficheros
    Cerrando el fichero
    error: memory exhausted or requested size too large for range of Octave's index type -- trying to return to prompt

    Is there a maximum of waypoints ?
  7. Let me see the kml.
    The problem could be a huge number of points but also an ill-conditioned route.
  8. I suppose you were right and it is just a problem with the number of nodes.
    I saw nothing wrong on your kml.

    Options I see:
    1) reduce the number of points (for example http://www.mediafire.com/?2qcuae1h33x8r2b).
    2) use importakml_old('nodes.kml',0.6) instead of importakml. It is the old version and it works ok with your file.

    You can also split the track into several segments, but that would force you to work with multiple tracks.
  9. Thank you, I´ll try it later. Meanwhile I´ve created a 19km long stage but I can´t load it with btb. (error message during loading)


    There are pacenotes and background image paths inside the file. Maybe there is an error.

    Is it possible to get satellite images with SASPlanet in a higher resolution ? For this stage I have 16*26 images but only a resolution of 232*232.
  10. I need to see the error message (click on details) to be able to help you.
    Typically you don't put the images inside XPacks folder (XPacks\Common\Textures\sat_1-1.dds, etc.) and BTB complains because it doesn't find them.
  11. System.ArgumentNullException: Der Wert darf nicht NULL sein.
    Parametername: stream
    bei BobsBits.BobsTextures.FindOrAdd(String lsPath)
    bei BobsBits.BackgroundImages.LoadFromXML(XmlNode Node, BobsTextures Textures)
    bei BobsBits.Venue.LoadFromXML(String ProjectFolder, String Filename, Boolean ForAnUndo)
    bei BobsTrackBuilder.frmMain.OpenVenueFile(String ProjectFolder, String Filename, Boolean ForAnUndo)
    bei BobsTrackBuilder.frmMain.mnuFileOpen_Click(Object sender, EventArgs e)
    bei System.Windows.Forms.MenuItem.OnClick(EventArgs e)
    bei System.Windows.Forms.MenuItem.MenuItemData.Execute()
    bei System.Windows.Forms.Command.Invoke()
    bei System.Windows.Forms.Command.DispatchID(Int32 id)
    bei System.Windows.Forms.Control.WmCommand(Message& m)
    bei System.Windows.Forms.Control.WndProc(Message& m)
    bei System.Windows.Forms.ScrollableControl.WndProc(Message& m)
    bei System.Windows.Forms.ContainerControl.WndProc(Message& m)
    bei System.Windows.Forms.Form.WndProc(Message& m)
    bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
    bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
    bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
  12. It seems to be the typical problem: "BackgroundImages" are not where they are supposed to be. You have to put the .dds in the correct folder and hopefully then BTB will open the project.
  13. ok, a I will start again.
    Any Suggestions about the resolution of satellite images ?
  14. No need to start again. If the .dds files are where BTB looks for them you will be able to open the project.

    When you use SASPlanet there is a zoom factor parameter. I am not an expert, but I suppose that using higher values you will get better resolution. But there must be a limit for that. Sorry I can't help you better.

    (May be ehrlec reads this and can help you)
  15. Sorry a new problem:

    > simplificar
    Leyendo datos entrada (nac.mat y salida\anchors_originales.mat)
    Leyendo elements
    Separando triángulos
    1 de 3
    0 triángulos conducibles
    2 de 3
    15130 triángulos intocables
    3 de 3
    23100 triángulos NO conducibles
    Escribiendo ficheros
    Now you can open intocables.ply to remove unreferenced vertex
    error: structure has no member `vertex_indices'
    error: evaluating argument list element number 1
    error: evaluating argument list element number 1
    error: called from:
    error: c:\project\scripts\simplificar.m at line 144, column 5
    error: c:\project\scripts\simplificar.m at line 129, column 2

    ?? all other previous things worked fine
  16. MeshLab step is deprecated. If you use gmsh thresholds there is no need to simplify further the mesh.

    Nevertheless I answer your question: "0 triángulos conducibles" means "0 driveable triangles" and that means you didn't include the driveable surfaces in the Physical Surface (111) definition. You should always check anchors_carretera.msh. If you haven't included the driveable surfaces in the physical surface you wouldn't be able to see the driveable surfaces in the .msh file.

    So, don't go on. Your problem is in your .geo file. You have to fix it and don't go on with the steps until your anchors_carretera.msh is ok,
    And then if you use gmsh_thresholds, you don't need the MeshLab step.
  17. @zaxxon: [​IMG]

    I used mallado_regular(2,1). So you can´t simplify the drivable zone, right ? Would it be better to use malladao_regular(2,2) and then simplify, because you can remove unreferenced vertex too within the non-drivable zone.

    @ehlec: ok, thanks for the information. I´ll try it later.
  18. The problem with using mallado_regular(2,1) is that you only have 2m of driveable zone on both sides of the road. That's not enough in my opinion.

    We usually don't reduce the amount of driveable triangles, only of non driveable. But since we know about gmsh thresholds it is not a required step to simplify the mesh. So once you have a good.msh I would use trocea_malla and then accept_mesh, skipping MeshLab step. You don't need to reduce the amount of triangles.