3dstudio, google earth and BTB [Archive]

rodrigouy

26 October 08, 00:20

hi, i extract the gps file for a track in google earth and i did a circuit in BTB but i have a problem, the track surface is very irregular and with a lot of innecesary bumps.

some time ago i listen the possibility to normalize surface with a function in 3d studio, anybody remember who is and how to use?

thanks

banger

28 October 08, 05:04

if your using btb you could use the btblofty program. which will do the calculations, it not perfected in gps or btblofty. but it will make it a lot easier to sort out the bumps.

btbloft is on the rsc site,under rfactor/modding/bob track builder
http://forum.racesimcentral.com/showthread.php?t=308449
also chub pearson released a large tutorial on that subjected
http://forum.racesimcentral.com/showthread.php?t=324395

also if this is a normal road in ge. you could try VE trackstarter.
http://forum.racesimcentral.com/showthread.php?t=301432&highlight=trackstarter

-Jesse-

10 March 09, 17:20

if your using btb you could use the btblofty program. which will do the calculations, it not perfected in gps or btblofty. but it will make it a lot easier to sort out the bumps.

btbloft is on the rsc site,under rfactor/modding/bob track builder
http://forum.racesimcentral.com/showthread.php?t=308449
also chub pearson released a large tutorial on that subjected
http://forum.racesimcentral.com/showthread.php?t=324395

I'd like to test the BTBLofty as I'm having few altitude problems in BTB I can't solve. Where could I find it since RSC is down? And does anyone have that tutorial in PDF or is it posted elsewhere? Thanks!

banger

10 March 09, 19:45

http://www.fileplanet.com/files/190000/197210.shtml

here you go.

-Jesse-

11 March 09, 14:58

Thanks banger!

S.Moss

12 March 09, 13:20

Another tip for google earth. Download Google sketch up, find the track in google earth and make sure its in window. Load up sketchup and i think its Tools, Google Earth then Get View. After you've got the view go back to Tools, Google Earth and select terrain. Now you'll have a rough area of the track with terrain heights. Then zoom in and repeat process for higher detail images. Export as .3ds

-Jesse-

12 March 09, 17:06

Oh crap. I didn't use any KLM data for the track so I guess the BTBLofty is useless for me...?

-Jesse-

22 March 09, 07:41

Since I can't get the altitudes smooth using only BTB, I decided to go and create the track with Google Earth + BTBLofty. I can import the KML I created in GE into BTB, but with BTBLofty I get this error message:

"unable to find a valid path in the KLM file"

Any clue why?

Emery

22 March 09, 16:07

Jesse - I don't know how many points you've got in your KML, but, if it's under 100, it's pretty feasible to just read the altitudes at each waypoint directly from Google Earth and then manually edit the KML file. 60-90 minutes for the entire 2.8 mile track I was working with.

-Jesse-

22 March 09, 17:36

Does typing the altitudes into KML make it work in BTBLofty? Since the reason I want to try out the program is that I already have the track layout ready in BTB, but I can't make the altitude changes smooth in BTB. If I understood correctly, BTBLofty would be just the right tool to do that...

Emery

25 March 09, 01:02

Sorry, I haven't used BTBLofty, so can't offer that feedback.

Doing the manual entry, I drove the circuit a few times and tweaked accordingly. Wasn't too tough to make smooth.

banger

26 March 09, 21:29

invaild path mean you got close to the start of the path,always leave a gap between and end of path,has it can't do it since it doesn't find a path anymore but a filled path.(polygon).or not enought data points to make a path.
kml seems to strip the height out slighty to make it faster in processing the kml file

easy notes:
on corners , make at least 3 to four points to make a corner. apex in,center,apex out has points,keep it close to the center.4 points for a sharper turn.

-Jesse-

27 March 09, 16:55

invaild path mean you got close to the start of the path,always leave a gap between and end of path,has it can't do it since it doesn't find a path anymore but a filled path.(polygon).or not enought data points to make a path.
kml seems to strip the height out slighty to make it faster in processing the kml file

easy notes:
on corners , make at least 3 to four points to make a corner. apex in,center,apex out has points,keep it close to the center.4 points for a sharper turn.

Thanks again banger. I connected the end point to the start point so that must be it. Did work in BTB though. Off to test it...