<![CDATA[Forums - Development]]>

<![CDATA[Forums - Development]]> https://www.vdrift.net/Forum/ Tue, 16 Jun 2026 13:36:37 +0000 MyBB <![CDATA[I have a few questions I want to ask]]> https://www.vdrift.net/Forum/showthread.php?tid=2398 Mon, 19 Aug 2019 17:45:59 -0700 Marrish]]> https://www.vdrift.net/Forum/showthread.php?tid=2398
Im trying to market this to my real life drifter friends and they are all computer stupid.]]>
Im trying to market this to my real life drifter friends and they are all computer stupid.]]> <![CDATA[Suspension geometry]]> https://www.vdrift.net/Forum/showthread.php?tid=2372 Thu, 09 Aug 2018 05:25:24 -0700 NaN]]> https://www.vdrift.net/Forum/showthread.php?tid=2372
We have caster, toe and camber values at car rest position (loaded suspension). At the same time we define wheel and suspension at extended position (unloaded suspension). The issue is that with macpherson and double-wishbone suspensions the camber changes with travel. So the camber values would have to be corrected for the extended position, which would be rather hard to do.

A simpler approach is to define suspension and wheel position at rest too (loaded). But should the suspension travel value also be relative to the rest position? Or should we define something like a sag parameter that would tell how much the spring is compressed at rest?

I am currently leaning towards the sag parameter. Although it has the problem that it depends on spring stiffness. Soft springs would require a preload (not enough sag). For very stiff springs the sag would have to be adjusted at loading time (too much sag).]]>
We have caster, toe and camber values at car rest position (loaded suspension). At the same time we define wheel and suspension at extended position (unloaded suspension). The issue is that with macpherson and double-wishbone suspensions the camber changes with travel. So the camber values would have to be corrected for the extended position, which would be rather hard to do.

A simpler approach is to define suspension and wheel position at rest too (loaded). But should the suspension travel value also be relative to the rest position? Or should we define something like a sag parameter that would tell how much the spring is compressed at rest?

I am currently leaning towards the sag parameter. Although it has the problem that it depends on spring stiffness. Soft springs would require a preload (not enough sag). For very stiff springs the sag would have to be adjusted at loading time (too much sag).]]> <![CDATA[Texture rendering in old VDrift version]]> https://www.vdrift.net/Forum/showthread.php?tid=2302 Fri, 11 Aug 2017 02:41:04 -0700 lucifesta]]> https://www.vdrift.net/Forum/showthread.php?tid=2302 First of all I need to thank you all for developing VDrift which I have been using for many years now in a neuroscience project.
For many reasons I can not move on from the code of 2007. I have now access to Nvidia Titan video cards in a Debian 8 system and 4k 3D monitors and have adapted the code here and there.
I need a bit of support on old texture rendering. I need to use the Weekend Drive task in a visual sensitive situation. All is fine except for the water "like" texture. I attached screenshots in the 2007 version and the new one (on purpose I drove down to the lake)
I know this is old story and the simple answer is move to new code, but I can not do that.
Please spend a bit of time and try to provide some support, even if only advice.
Thank you for your time.
.jpg

VdriftOld-New.jpg (Size: 254.35 KB / Downloads: 15) ]]> First of all I need to thank you all for developing VDrift which I have been using for many years now in a neuroscience project.
For many reasons I can not move on from the code of 2007. I have now access to Nvidia Titan video cards in a Debian 8 system and 4k 3D monitors and have adapted the code here and there.
I need a bit of support on old texture rendering. I need to use the Weekend Drive task in a visual sensitive situation. All is fine except for the water "like" texture. I attached screenshots in the 2007 version and the new one (on purpose I drove down to the lake)
I know this is old story and the simple answer is move to new code, but I can not do that.
Please spend a bit of time and try to provide some support, even if only advice.
Thank you for your time.
.jpg

VdriftOld-New.jpg (Size: 254.35 KB / Downloads: 15) ]]> <![CDATA[Announcing releases]]> https://www.vdrift.net/Forum/showthread.php?tid=2269 Mon, 08 May 2017 02:12:42 -0700 GunChleoc]]> https://www.vdrift.net/Forum/showthread.php?tid=2269
The completely outdated information on the homepage also makes it impossible to promote the project in any shape or form.

I think that whoever controls the homepage should give access to someone who cares, e.g. NaN.]]>
The completely outdated information on the homepage also makes it impossible to promote the project in any shape or form.

I think that whoever controls the homepage should give access to someone who cares, e.g. NaN.]]> <![CDATA[Auto-reverse]]> https://www.vdrift.net/Forum/showthread.php?tid=2268 Sun, 07 May 2017 06:25:03 -0700 NaN]]> https://www.vdrift.net/Forum/showthread.php?tid=2268
The option to enabled/disable it is
Options / Controls / Input device / Automatic Reverse]]>
The option to enabled/disable it is
Options / Controls / Input device / Automatic Reverse]]> <![CDATA[Development]]> https://www.vdrift.net/Forum/showthread.php?tid=2266 Tue, 18 Apr 2017 07:55:38 -0700 theaudiomonkey]]> https://www.vdrift.net/Forum/showthread.php?tid=2266
Is this project still in active development? If so I would like to contribute some music / audio fx Smile

Thanks

- TheAudioMonkey]]>
Is this project still in active development? If so I would like to contribute some music / audio fx Smile

Thanks

- TheAudioMonkey]]> <![CDATA[Vdrift crashing on msvc 2013 community edition]]> https://www.vdrift.net/Forum/showthread.php?tid=2248 Mon, 06 Feb 2017 22:36:37 -0800 suresh mani]]> https://www.vdrift.net/Forum/showthread.php?tid=2248 VDrift Crashing in msvc 2013 community edition debug mode

Application crashing in InitCoreSubsystems function. VDrift window initialized sucessfully but its crashing on GraphicsGL2() initialization.

I dont know why its using GraphicsGL2() instead of GraphicsGL3(). I have installed VDrift latest version in my pc its working fine . But the build-ed one is crashing and used installed VDrift data copy for my development.

help me....]]> VDrift Crashing in msvc 2013 community edition debug mode

Application crashing in InitCoreSubsystems function. VDrift window initialized sucessfully but its crashing on GraphicsGL2() initialization.

I dont know why its using GraphicsGL2() instead of GraphicsGL3(). I have installed VDrift latest version in my pc its working fine . But the build-ed one is crashing and used installed VDrift data copy for my development.

help me....]]> <![CDATA[msys2 bullet perf regression]]> https://www.vdrift.net/Forum/showthread.php?tid=2239 Wed, 07 Dec 2016 02:53:57 -0800 NaN]]> https://www.vdrift.net/Forum/showthread.php?tid=2239 <![CDATA[Tire force combining review]]> https://www.vdrift.net/Forum/showthread.php?tid=2207 Fri, 08 Jan 2016 06:01:24 -0800 NaN]]> https://www.vdrift.net/Forum/showthread.php?tid=2207
Caveat: I am using touring.tire data with Pacejka/Hankook combining parameters. Beckman pre-combining depends on max force slip value (Fx, Fy curve shape). So to have a more fair comparison I have to feed Beckman with the Hankook curves, as they differ somewhat from the touring.tire. This will be addressed in a followup post.

Pacejka curve fit ±0°-32° slip angle, 4° steps:

[Image: HJnGgyd.png]

Beckman pre-combining ±0°-32° slip angle, 4° steps:

[Image: yXYS8aF.png]

According to this preliminary comparison (see caveat) Beckman seems to overestimate the longitudinal force component (Fx) with increasing slip, while Pacejka is keeping Fy closer to maximum at lower slip angle values. This means with Pacejka we would have more side grip but less longitudinal grip at small slip angles but overall less grip (particularly in longitudinal direction) at high slip angles (which is probably what we want for aggressive steering, drifting).]]>
Caveat: I am using touring.tire data with Pacejka/Hankook combining parameters. Beckman pre-combining depends on max force slip value (Fx, Fy curve shape). So to have a more fair comparison I have to feed Beckman with the Hankook curves, as they differ somewhat from the touring.tire. This will be addressed in a followup post.

Pacejka curve fit ±0°-32° slip angle, 4° steps:

[Image: HJnGgyd.png]

Beckman pre-combining ±0°-32° slip angle, 4° steps:

[Image: yXYS8aF.png]

According to this preliminary comparison (see caveat) Beckman seems to overestimate the longitudinal force component (Fx) with increasing slip, while Pacejka is keeping Fy closer to maximum at lower slip angle values. This means with Pacejka we would have more side grip but less longitudinal grip at small slip angles but overall less grip (particularly in longitudinal direction) at high slip angles (which is probably what we want for aggressive steering, drifting).]]> <![CDATA[VDrift 2015-11-28 test build]]> https://www.vdrift.net/Forum/showthread.php?tid=2202 Sat, 28 Nov 2015 05:49:29 -0800 NaN]]> https://www.vdrift.net/Forum/showthread.php?tid=2202

The only change to the previous build is the car spec preview in the garage I think.

Code:
http://sourceforge.net/projects/vdrift/files/vdrift/nightly%20builds/vdrift-2015-11-28.7z/download

Code:
http://sourceforge.net/projects/vdrift/files/vdrift/nightly%20builds/vdrift-2015-11-28.7z/download

The archive contains source code, data (a few cars and tracks) and win7 64bit binaries.

On Linux unpack and run scons to build the binary (make sure you've got the dependencies installed, see docs)]]> <![CDATA[Fixed car parts naming and customization]]> https://www.vdrift.net/Forum/showthread.php?tid=2201 Sat, 28 Nov 2015 03:49:16 -0800 NaN]]> https://www.vdrift.net/Forum/showthread.php?tid=2201
I've been wondering if it would be better to have a fixed set of parts. It would make car files easier to read/modify and eventually allow to add tuning functionality, by adding car part lists.

Something like:

Code:
glass

interior

seat f/r fl/fr/rl/rr

steering

body

hood

trunk

fender fl/fr/rl/rr

door fl/fr/rl/rr -> do we need this?

bumper f/r

spoiler f/r

light f/r

transmission

engine

differential f/c/r

wheel f/r fl/fr/rl/rr

tire ...

suspension ...

Other parts I am missing?]]>
I've been wondering if it would be better to have a fixed set of parts. It would make car files easier to read/modify and eventually allow to add tuning functionality, by adding car part lists.

Something like:

Code:
glass

interior

seat f/r fl/fr/rl/rr

steering

body

hood

trunk

fender fl/fr/rl/rr

door fl/fr/rl/rr -> do we need this?

bumper f/r

spoiler f/r

light f/r

transmission

engine

differential f/c/r

wheel f/r fl/fr/rl/rr

tire ...

suspension ...

Other parts I am missing?]]> <![CDATA[Displaying car specs]]> https://www.vdrift.net/Forum/showthread.php?tid=2189 Sat, 29 Aug 2015 06:30:55 -0700 NaN]]> https://www.vdrift.net/Forum/showthread.php?tid=2189

[Image: UgfXYNU.jpg]

Whatya think? Yay or Nay?

Are the imperial units correct? Do they use cubic inches?

Would you want to see more/less info?]]>

[Image: UgfXYNU.jpg]

Whatya think? Yay or Nay?

Are the imperial units correct? Do they use cubic inches?

Would you want to see more/less info?]]> <![CDATA[Macros Are Evil]]> https://www.vdrift.net/Forum/showthread.php?tid=2188 Fri, 28 Aug 2015 07:21:47 -0700 NaN]]> https://www.vdrift.net/Forum/showthread.php?tid=2188
It turns out it is a bug in Bullet, to be more specific in the SIMD_DEGS_PER_RAD macro.

Code:
#define SIMD_PI           btScalar(3.1415926535897932384626433832795029)

#define SIMD_2_PI         btScalar(2.0) * SIMD_PI

#define SIMD_HALF_PI      (SIMD_PI * btScalar(0.5))

#define SIMD_RADS_PER_DEG (SIMD_2_PI / btScalar(360.0))

#define SIMD_DEGS_PER_RAD  (btScalar(360.0) / SIMD_2_PI)

The first one to spot it gets a virtual cookie. Big Grin

PS:
What is affected by this bug? Tire forces (cars flying off randomly and stuff) and AI steering calculations.]]>
It turns out it is a bug in Bullet, to be more specific in the SIMD_DEGS_PER_RAD macro.

Code:
#define SIMD_PI           btScalar(3.1415926535897932384626433832795029)

#define SIMD_2_PI         btScalar(2.0) * SIMD_PI

#define SIMD_HALF_PI      (SIMD_PI * btScalar(0.5))

#define SIMD_RADS_PER_DEG (SIMD_2_PI / btScalar(360.0))

#define SIMD_DEGS_PER_RAD  (btScalar(360.0) / SIMD_2_PI)

The first one to spot it gets a virtual cookie. Big Grin

PS:
What is affected by this bug? Tire forces (cars flying off randomly and stuff) and AI steering calculations.]]> <![CDATA[VDrift 2015-08-25 test build]]> https://www.vdrift.net/Forum/showthread.php?tid=2185 Tue, 25 Aug 2015 08:58:33 -0700 NaN]]> https://www.vdrift.net/Forum/showthread.php?tid=2185 http://sourceforge.net/projects/vdrift/f...z/download

Code:
http://sourceforge.net/projects/vdrift/files/vdrift/nightly%20builds/vdrift-2015-08-25.7z/download

Code:
http://sourceforge.net/projects/vdrift/files/vdrift/nightly%20builds/vdrift-2015-08-25.7z/download

The archive contains source code, data (3 cars + 3 tracks) and win7 64bit binaries.

On Linux unpack and run scons to build the binary (make sure you've got the dependencies installed, see docs)]]> <![CDATA[VDrift 2015-07-29 test build]]> https://www.vdrift.net/Forum/showthread.php?tid=2183 Wed, 29 Jul 2015 08:02:17 -0700 NaN]]> https://www.vdrift.net/Forum/showthread.php?tid=2183 http://sourceforge.net/projects/vdrift/f...z/download

Code:
http://sourceforge.net/projects/vdrift/files/vdrift/nightly%20builds/vdrift-2015-07-29.7z/download

The archive contains source code, data and Windows 7 64bit binaries.

On Linux unpack and run scons to build the binary (make sure you've got the dependencies installed, see docs/wiki)]]> http://sourceforge.net/projects/vdrift/f...z/download

Code:
http://sourceforge.net/projects/vdrift/files/vdrift/nightly%20builds/vdrift-2015-07-29.7z/download

The archive contains source code, data and Windows 7 64bit binaries.

On Linux unpack and run scons to build the binary (make sure you've got the dependencies installed, see docs/wiki)]]>