Ace. Also tried with veteran, and similar results. my thinking is an ace ai should be able to shoot down a non-maneuvering aircraft within a few seconds of intercept. the ace ai should also have a reasonable pk for high aspect snap shots as well.
Latest posts made by sudoku
-
RE: 4.33 AI Bug: unable to hit with guns
-
4.33 AI Bug: unable to hit with guns
First off, hats off for an incredible update 4.33 is generally fabulous! That said, I think something is broken with the AI. I’ve tried with multiple plane types including mig 29, 23, and ef 2000. An Ace AI is nearly unable to score a hit with guns while flying straight and level at around 400kts. It takes over 1 minute from intercept with the AI plane twisting and turning, firing off bursts before it gets lucky enough to hit with a few rounds. ACMI in tacview said the mig fired off 1028 rounds (i had unlimited ammo turned on). I thought maybe if I did some maneuvering it might help, but even while performing a nice gentle 3g turn it took an incredible amount of bursts to score a hit. I checked in 4.32, and while it took more bursts than it ought to, a mig 29 was able to shoot me down while flying straight and level considerably quicker. Anyone else notice this behavior?
I’ve uploaded a youtube video illustrating the issue
-
RE: Gibfender's X55 Profile
No. I haven’t had any ghosting issues since I stopped using the software/figured out how to properly program it.
-
RE: Gibfender's X55 Profile
yea, I did swap from usb3 to usb2 plugs on the mobo. It’s possible that had something to do with it, but I’ve seen people online say to swap to usb3 from usb2 as well. But as I said, after seeing how easy it is to mess up the programming of the software, I had multiple software crashes due to continuous key presses from the stick/throttle. plus, if i remember correctly, i never saw ghosting when leaving the software off and using only dx mapping in the bms keyfile. My suspicion is it has as much to do with faulty button mapping/software bugs than anything else. At the very least that issue only compounds the problems of any usb ghosting.
-
RE: Gibfender's X55 Profile
Thanks again chaos for sending that profile. Couple observations about the x55.
-
when working with the saitek/madcatz software I have experienced the “throttle ghosting.” I think this is more a problem with the software than the stick itself as I haven’t seen any ghosting since setting up the stick with pure dx controls in the bms keyfile. My guess is that the ghosting problem is twofold. First, the software turns the buttons into key-presses which are generally active in any window and windows doesn’t seem to like a lot of errant key-presses. Second, it is really easy to inadvertently leave a button set to hold a key without letting it go. Try holding a couple keyboard keys down and see how well windows behaves
-
I don’t have mfds or rudder pedals. Both Chaos’ and Gibfender’s profiles didn’t work for me out of the box. I’m pretty sure this is because BMS mapped my x55 to the same DX buttons as your rudder pedals and mfds. This showed some interesting behavior as I found my throttle and stick sending the same bms commands using different buttons compounded by further conflicts with the software mappings. What did seem to work in the end was to delete all the joystick entries in the keyfile and then use Chaos’ profile. I never did get Gibfender’s to work since it was more a DX keyfile map than a saitek software one.
In the end I took both maps and modified to fit my own needs with almost exclusive keyfile dx bindings/shifting. Only exception is the stupid slider on the throttle. What a retarded idea they had. It looks and feels like a slider but behaves like a button with no option to change. BMS doesn’t even see it as a dx button, so you are forced to map it using the buggy software. I currently have it set to turn the jammer on and off.
-
-
RE: Gibfender's X55 Profile
Just got my x55 the other day. Tried using the profile (yes i loaded the profile in mad catz config) with the matching keyfile. I’m having issues with the throttle and stick sharing commands. For example in bms stick shows buttons 0-17, throttle shows buttons 33-63 (all hats save pov are registering as button presses) and i get a lot of commands being shared across multiple buttons (1 example is dms is assigned to a hat on both the stick and the throttle).
My current plan is to just enter all the commands in the keyfile manually assigning dxshifting/buttons. Unless you guys have a better solution.