hi again...
my joystick module just leaped many miles in development, as it finally stopped CTD'ing and now successfully supports fully flexible axis-mapping on multiple devices via directinput
but i ran into a wee bit of a bump along my ways...
i had to disable the stock Orbiter joystick feature, because it kept conflicting with my setup... no worries there... i just mapped all the axes to my new module
but it so happens that in doing this, i killed the POV hat...
so, ok, i'll re-program it... how hard can it be...
and indeed, hard it wasn't, but i'm getting trouble now from the re-centering feature that "pulls" the camera into alignment when near the center position in internal mode...
when i get near it, i get a lot of violent jitter, as my code pulls the camera one way, and Martin's code pulls it another :lol:...
this is how it looks:
note how i had to keep track of my own angles for internal mode, since theres no "oapiCameraGetCockpitDir" function :huh:
that's where the conflicts arise... as my angles play tug-of-war with the recentering feature :shrug:
how am i supposed to deal with this? would it be better to convert the directions to keyboard inputs instead? and if so, how do i do this in Orbiter2010?
cheerz!:tiphat:
my joystick module just leaped many miles in development, as it finally stopped CTD'ing and now successfully supports fully flexible axis-mapping on multiple devices via directinput
but i ran into a wee bit of a bump along my ways...
i had to disable the stock Orbiter joystick feature, because it kept conflicting with my setup... no worries there... i just mapped all the axes to my new module
but it so happens that in doing this, i killed the POV hat...
so, ok, i'll re-program it... how hard can it be...
and indeed, hard it wasn't, but i'm getting trouble now from the re-centering feature that "pulls" the camera into alignment when near the center position in internal mode...
when i get near it, i get a lot of violent jitter, as my code pulls the camera one way, and Martin's code pulls it another :lol:...
this is how it looks:
Code:
static double camAZM, camPLR;
//
//
switch(jState.rgdwPOV[0])
{
case 0:
case 4500:
case 31500:
if(oapiCameraMode() == CAM_COCKPIT)
{
camAZM += CAM_MOVE_SPD;
oapiCameraSetCockpitDir(camPLR, camAZM);
} else
oapiCameraRotPolar(-CAM_MOVE_SPD);
break;
case 22500:
case 18000:
case 13500:
if(oapiCameraMode() == CAM_COCKPIT)
{
camAZM -= CAM_MOVE_SPD;
oapiCameraSetCockpitDir(camPLR, camAZM);
} else
oapiCameraRotPolar(+CAM_MOVE_SPD);
default:
break;
}
switch(jState.rgdwPOV[0])
{
case 13500:
case 9000:
case 4500:
if(oapiCameraMode() == CAM_COCKPIT)
{
camPLR -= CAM_MOVE_SPD;
oapiCameraSetCockpitDir(camPLR, camAZM);
} else
oapiCameraRotAzimuth(CAM_MOVE_SPD);
break;
case 22500:
case 27000:
case 31500:
if(oapiCameraMode() == CAM_COCKPIT)
{
camPLR += CAM_MOVE_SPD;
oapiCameraSetCockpitDir(camPLR, camAZM);
} else
oapiCameraRotAzimuth(-CAM_MOVE_SPD);
default:
break;
}
note how i had to keep track of my own angles for internal mode, since theres no "oapiCameraGetCockpitDir" function :huh:
that's where the conflicts arise... as my angles play tug-of-war with the recentering feature :shrug:
how am i supposed to deal with this? would it be better to convert the directions to keyboard inputs instead? and if so, how do i do this in Orbiter2010?
cheerz!:tiphat:
Last edited: