Ubit,
I appreciate the information. It certainly helps me understand what some of
these functions do.
I have been thinking about changing over to using ubOde now for awhile.
Many months ago when I tried doing that my residents went nuts because so
many things stopped working or worked
Hi just a few more notes about ubOde:
VEHICLE_FLAG_HOVER_GLOBAL_HEIGHT is dominant, if present
VEHICLE_HOVER_HEIGHT is a region height
Else it is a height relative to water and or terrain according to:
If VEHICLE_FLAG_HOVER_WATER_ONLY is present, water is the reference,
Hi,
Sorry Fred, this is not correct
VEHICLE_HOVER_HEIGHT can work with terrain, water, higher of both,
or fixed value.
This is controlled by flags:
VEHICLE_FLAG_HOVER_GLOBAL_HEIGHT
VEHICLE_FLAG_HOVER_WATER_ONLY
VEHICLE_FLAG_HOVER_TERRAIN_ONLY
Tom, I think this is a difference in implementation details. To me,
Bullet actually gets it correct.
Your script is setting Hover height to go up and down. It is
effectively llSetVehicleFloatParam( VEHICLE_HOVER_HEIGHT, HovHeightBase
+= .02 ); each click Up and -= 0.02 on Down, while
Hi,
ubOde and bullet where created in parallel so naturally had
different interpretations of details and implementation.
Making them more identical is a slow and hard going on process.
To check if ubode or bullet are more corret on a feature, one
