GP Bikes beta15b available!
Started by afarre, February 20, 2017, 10:29:06 am
Quote from: PiBoSo on February 20, 2017, 11:14:17 amThe m_fPos values represent the center of the chassis ( 0,0,0 in the Bike Editor ), not the center of mass.Would it make sense to use the chassis CG instead? Or maybe the CG of the whole bike?
Quote from: afarre on February 20, 2017, 11:53:46 amActually, what I need is to transform m_fPos to ground reference. Is there any public bike reference for a transform such that?Example: with current m_fPos, if cornering on flat horizontal surface m_fPosY is going to vary because Chassis Center moves down & up with bike lean angle. Same thing happens with m_fAcclerationY, it moves because Chasis Center dispalcement, when acceleration Y at ground point would be always =0 unless climbing a slope or bike wheeling.
Quote from: afarre on February 20, 2017, 01:46:06 pmIf using GPB as a simulator sub-system, there are many reasons to know where the ground is, here you have an easy example: To drive an external Visual System.Actually, I already developed my own Visual System (based on OpenSceneGraph), which is fed with plugin position & attitude data. But to work it properly, ground reference is mandatory so that I can put the 'world' at its place and tires patches appear all the time on the ground.As I said, once knowing m_fPos is referenced to Bike Editor (0,0,0) I think I have information enough to sort this problem out Just give some time...
Quote from: HornetMaX on February 22, 2017, 09:42:24 amVel and Acc are of the CoG, but the CoG itself is not currently passed to the plugin.
Quote from: afarre on February 22, 2017, 11:06:51 amQuote from: HornetMaX on February 22, 2017, 09:42:24 amVel and Acc are of the CoG, but the CoG itself is not currently passed to the plugin.Right, I can see it at plugin interface, but going beyond, the question also means if it is a fixed point that can be taken from bike data files, or it is a moving point because bike changing conditions (suspensión lenghts, fuel, etc).