+- Forums (https://www.vdrift.net/Forum)
+-- Forum: Project (https://www.vdrift.net/Forum/forumdisplay.php?fid=4)
+--- Forum: Development (https://www.vdrift.net/Forum/forumdisplay.php?fid=9)
+--- Thread: surfaces.txt (/showthread.php?tid=1316)
- thelusiv - 08-25-2010
NaN Wrote:Only if you want to stay compatible to the pre-surfaces.txt releases.Which I'm not worried about. So what I have gathered is that surfaces.txt replaces the following:
- list.txt object parameters
- bump wavelength
- bump amplitude
- friction coefficient for non-treaded tires
- friction coefficient for treaded tires
- rolling resistance coefficient
- rolling drag
- bump wavelength
- track.txt parameters
- non-treaded friction coefficient
- treaded friction coefficient
- non-treaded friction coefficient
And that it adds the last parameter in the objects in list.txt which specifies the surface id?
- NaN - 08-26-2010
List parameters: http://svn.vdrift.net/viewvc.cgi/trunk/listedit/format.txt?root=VDrift+Track+Editor&view=co
The surface id(surface-id) in surfaces.txt is parameter 16. Type determines the surface sound. There are 6 sounds: none, asphalt, grass, gravel, concrete, sand, cobbles. The sounds will be customisable in the future.
Code:
[surface-01]
Type = asphalt
BumpWaveLength = 2.0
BumpAmplitude = 0.01
FrictionNonTread = 0.8
FrictionTread = 0.9
RollResistanceCoefficient = 2.5
RollingDrag = 5.0- thelusiv - 08-26-2010
Thanks for the info...I am too lazy to read the source.
I have implemented a few things in the Blender gui script to add/edit/delete surfaces.
- thelusiv - 08-27-2010
From what I can see, there is no functionality to import/export surfaces.txt in vdrift.py yet, correct?
- NaN - 08-27-2010
Create an empty object per surface and set the properties. I think I had the code somewhere. But it looked much simpler to me to edit the surfaces file outside of blender.
- thelusiv - 08-29-2010
I think I'll just code up something myself to write surfaces.txt - it is pretty simple, after all. I will need to do some heavy refactoring on this code anyway, and will, at that point, merge any such duplicate functionality with vdrift.py.
What are reasonable limits on each of the surface parameters?
bump_wavelength
bump_amplitude
friction_treaded
friction_non_treaded
rolling_resistance
rolling_drag
- NaN - 08-29-2010
My best guess:
bump_wavelength: 0.001 - 1 // needs experimental verification, lol
bump_amplitude: 0 - 0.1 // should be enough I guess, needs verification too
friction_treaded: 0 - 1 // wet/loose surface traction factor, scales tire grip
friction_non_treaded: 0 - 1 // slicks traction factor, scales tire grip
rolling_resistance: 0 - 10 // rolling resistance factor(track deformation), scales tire rolling resistance
rolling_drag: 0 - 20 // viscous drag(sand, mud, ...), sand is actually not viscous but who cares
rolling_drag and bump_amplitude are scaled by 1/4 internally.
Maybe someone more experienced with the tracks (I haven't even tested all of them I think), can provide some limits that look/feel realistic. Looking at existing surfaces might be helpfull too.