I should have called the spins I’m seeing in Dogfight on AI aircraft prior to them crashing instead spiral dives. Perhaps a result of the AI blacking out?
Latest posts made by Reticuli
-
RE: Some stuff I've noticed in 4.33 U4 … not sure if bugs
-
Some stuff I've noticed in 4.33 U4 … not sure if bugs
Saved custom dogfights don’t seem to save anything except my aircraft.
I don’t know if it’s too much ground effect lift or what, but enemy AI aircraft sometimes go into a weird low speed, high AoA hover very close to the ground. Is ground effect modeled in BMS 4.33? Sometimes it does seem oddly easy not to crash into the ground in it, but I’m not sure if that’s my imagination or not. It doesn’t bother me in my own aircraft, just seems to be more an issue for that hover thing happening to the AI.
AI enemy aircraft also seem to depart and spin frequently out of control.
Not sure if it’s intentional or not, but sometimes the new roll + AoA limiting seems to be preventing mixed inputs in both roll and pitch, wanting an oddly-pure control input and ignoring something that’s in between. Might be intentional and/or realistic, as I’ve never flown a real F-16.
Sometimes grass doesn’t seem to render in both eyes in stereoscopic.
This is more a request than a bug and I don’t actually expect it ever to be implemented: if labels could render at the stereo depth that their object they’re labeling is at, that’d be great. I know that’s asking for a lot.
Anyway, thanks to the mods/coders for all their hard work.
-
RE: Saitek X-65f control panel deadzones ignored by Falcon BMS for ministick radar
Both are off by -0.125007629860221, so I’ve just created a GlovePIE script for PPJoy with the following lines:
PPJoy1.Analog0 = ensurerange(Joystick2.xrot+0.125007629860221,-1,1) // x ministick
PPJoy1.Analog1 = ensurerange(Joystick2.yaw+0.125007629860221,-1,1) // y ministickvar.1 = PPJoy1.Analog0
var.2 = PPJoy1.Analog1Edit, this issue is not present in 4.33, just in the last version of 4.32, and I’m not sure how I resolved it before.
-
RE: Saitek X-65f control panel deadzones ignored by Falcon BMS for ministick radar
with the ministick, how are you mapping it in BMS? Have you made it a pair of directx axes? Or is it mapped via keyboard emulation in the Saitek SST software?
They’re axis through the reghack widely available. I’ve had this issue before with a deadzone, but could always resolve it before. It’s been a year since I’ve used flight sims much, and I can’t remember how I resolved it before. It’s as if BMS’s own deadzone and the Saitek deadzone are both being ignored. All the sim sees is the raw axis.
-
Saitek X-65f control panel deadzones ignored by Falcon BMS for ministick radar
Saitek X-65f control panel deadzones ignored by Falcon BMS for ministick radar
No size deadzone makes any difference in the sim’s own settings. The sim doesn’t seem to care what I do with the Saitek software deadzone for the hacked ministick, either, which I use for the radar cursor. This is a strange recent issue that I’m certain I’ve fixed previously, but can’t remember how. Anyone?