Jump to content

Reticuli

Members
  • Posts

    347
  • Joined

  • Last visited

Everything posted by Reticuli

  1. Ferrite choke cores work on the X-65F to drastically reduce interference, particularly with the twist axis. It should have them built into the cables, especially the end that plugs into the stick, but you can do this yourself. I'm using a bunch of small ones, but a single large cheap ring one would probably work with that cable wrapped around it a few times to get a similar effect.
  2. Ferrite choke cores work on the X-65F to drastically reduce interference, particularly with the twist axis. It should have them built into the cables, especially the end that plugs into the stick, but you can do this yourself. I'm using a bunch of small ones, but a single large cheap ring one would probably work with that cable wrapped around it a few times to get a similar effect.
  3. Or you can just forgo using the sim's own trim. Using an auto-trimming GlovePIE script with PPJoy and do your yaw manually; just keeping the yaw dampening channel on. By the way, I'll have some X65f scripts soon. It works even better for auto trimming/trim update AFCS mimicking than the X52. And looks like a Comanche SAC.
  4. Do the cessna pedals have the detent? And how low can you get the tension on the three different pedal models without removing that spring?
  5. Any tutorials on how to remove the detents, change the lube on the throttle, and/or change out the awful unsheilded/unferrited PS/2 cable? I was thinking about a heating pad/plate under the throttle on low, but they produce so much RFI/EMI, that it would make the rudder axis worthless. The detents definitely need to go.
  6. Wow. Rearranging the axiis would be very beneficial, as well as disabling some axiis. Flanker doesn't seem to recognize the X-65f properly for dual throttles. And Eidos JSF crashes with the X-65f immediately. JSF and Longbow 2 also do not allow PPjoy and GlovePIE for rearranging axiis as they don't recognize Windows preferred joystick setting. They always default to the first axis.
  7. I sometimes have the top rotary set in GlovePie to mix with the twist, for when I want uncontaminated yaw.
  8. The cable between the stick and throttle needs better shielding construction and ferrites along the length, like two or three of them. It picks up all manner of RF/EMI interference as an antenna. This PS/2 cable is unfortunately hardwired on the throttle end. Even your hand and body can change the amount of pickup it's getting and deflect the rudder axis. I suspect this is where the majority of complaints regarding centering are stemming from. If you place that cable around your back, you can usually plug the stick in (only sure calibration method: replugging) to get some level of stability in the RF/EMI pickup so that it stays that way, only wobbling a little. Pretty inexcusable considering even DJing equipment USB cables, Xbox controllers, and my old PS/2 mouse cable all have superior shielding AND at least one ferrite cylinder. A $300 controller botched by a $1 cable choice that could have been prevented with a $3 cable. It doesn't help that their calibration screen does nothing like 75% of the time. People with electronics and modding experience might want to try replacing that cable, assuming Saitek doesn't remedy this situation. It will take some effort, though. If it wasn’t hardwired, there are a few appropriate ones out there for very cheap that could just be plugged right in. Interestingly, while I think for both jets and props this pressure sensing thing is exaggerated horsecrap, it actually does make FBW/AFCS easier to program. This is not just the case in real life (F-16 & F-22 1G AFCS roll & pitch hold are fairly simple in concept, ignoring for a moment their flight laws complexity due to their instability), but is especially true with helos. Its near-zero post-input latency makes it optimal from an Auto-trimming/Trim Update standpoint, like in EECH, Blackshark, and Comanche Gold. The effect is nearly indistinguishable from Janes Longbow Anthology and Gunship!(with proper ini config setting). The need to have a delay, dead period between reaching the desired state and recentering the stick, or reducing the sensitivity of such a feedback system is all moot with it. So that is a positive. Certainly I can understand why engineers might be tempted to use it to compensate for their inability or lack of desire to solve those sorts of problems with AFCS.
  9. Why can't the trims be axiis with the Su-25T? Most combat aircraft do not have axiis you just twirl on a knob, but rather use a hat. Yet many high quality sims, even X-Plane and Lock-On, give you that option. Why not allow that on the Su-25T? Otherwise, you might as well remove the axiis option from the other aircraft, since they don't have them either and it's certainly redundant having both axiis assigned AND a hat dedicated to trim. ED ought to make up its mind: do they want to allow us trim axiis as a convenience, or not. The whole "realism" argument is moot.
  10. That override's the autopilot, not the trim. Why don't the trim axiis work? You have to just use the buttons? I try moving the trim manually with the keyboard and I never get it back to making the lights green again on the su-25T. Huge annoyance. The worst is trying to move the controls with autopilot when you forget to disengage or turn on temporary override and the AP puts full trim in the opposite direction. Then you're pretty much screwed. With all these issues on the su-25T, I'd rather simply not use the AP at all at this point.
  11. If it's working correctly, you should be able to put the profile in "manual trim" (hint: it's that way when it's first activated, or you can cycle through to hear it confirm). Then the pinkie should just act as the trim button and you have it functioning as if you hadn't done anything at all in GlovePIE and PPJoy. You get ordinary response and trimming. No different than without it. No lag. No decrease in resolution or fine response. Zero strange happenings. When you do this, does it still go crazy? If so, that's an indication something's not right with how it's been set up. Don't judge the dynamic trim aspect until you're certain the manual mode is actually behaving properly. ----------- The only serious problem was associated with the issue of getting PPJoy installed on modern systems, which the author of it has since resolved. There are some minor niggles: Clear Trim sometimes doesn't work properly for some reason in Blackshark 2 from the script. This might necessitate hitting Ctrl T on your keyboard manually when you first get into the helo. And the new trim option ED added might prevent DCS world from recognizing the virtual joystick in the background. So make sure that option where DCS ignores your stick until it's centered back is not on. And make sure the helo's own trim state is cleared.
  12. I tried installing everything again. The only thing I need to add is you have to go into options and look at the buttons and the axis assignments. You might even need to "load" both the saitek and ppjoy lua files. Not sure. I did that anyway just for the hell of it. But after I went into that options menu, either the "loading" or the clicking on and selecting of the axis screen drop down box assigned everything properly. So just do both to make certain. After I did that, all the axiis are showing up and working correctly.
  13. I'm telling you, if you follow the instructions from beginning to end IT WILL WORK. It's hard to fix it with patchwork, so when in doubt try uninstalling PPJoy and going through all the steps again. I just reinstalled the EECH stuff and it worked perfectly first attempt. Match the pic with the 7 axis virtual controller, etc. It shouldn't jump around or anything. Callibration? Saitek deadzone check in the control panel. Remember, step by step. Once you've done it all, bam! It'll work.
  14. Krazsus: Be gentle and show finesse. And show some patience. The aircraft doesn't respond instantly, like real life. Boberro: Do you have the PPJoy axis assigned in Blackshark? They are virtual axiis, so if the sim is only seeing the real saitek ones, it won't do anything except talk. You can also check the script's variable values after you've activated it to make sure they are changing and the modes work. You can also go into windows joystick callibration and look at the PPJoy axiis to make sure they are moving around properly, staying put, and mostly resetting when you cycle through. Neither debugs the interface with the sim, but ensures the script, GlovePIE, and PPJoy are o.k. I don't have the patch installed yet, so I assume you need to have the old trim style on in the configs. If you cycle through all the virtual dynamic trim modes (three of them) often there will be a little bit of trim left over...usually forward. I forget why it does that since I haven't flown BS in the last few months, but it's benign and all you have to do is cycle through again. The more you have the stick centered when you cycle completely through, the less it does this...I think. Been a while. Now, if when you first get in and have just turned on the script (there is no prior trim) the red joystick/trim box on screen shows it's off center, then you need to callibrate everything and/or make a larger deadzone in the Saitek control panel. If the stick is applying any noticeable input and one of the trim update modes is active, it will slowly add trim without you knowing. And when in doubt, redo it and follow the instructions step by step. I've installed it half a dozen times and the only issues are from skipping something. Nice to see AVsim is back up!
  15. But even the old low-tech A-10A needs little or no trim most of the time due to the angle of the engines, even with its more rudimentary SAS shot out...assuming the control surfaces and weight distribution are kosher. Just because it's there doesn't mean it's needed. It shouldn't pitch down like a normal aircraft when untrimmed manually and the CoG is right. And the newer F-15's and all the F-16's & F-117's AFCS control the aircraft to 1g standard and near-zero alpha, which effectively is "autotrimming" but they still have trims. Ditto with the Hornet, Superhornet, Raptor, and JSF. Even the last versions of the Tomcat did. In the case of the viper, the pitch trim is used to increase the flight computer's demand AoA at lower speeds. Otherwise there's little point in touching it with normal operation. The early F-15A/B/C/D needed normal trimming. You cannot pilot an F-117 without that AFCS, by the way, which itself cannot work without either attitude-command, g-command, alpha-command, or a combination. And all Airbus 300 series and the newest Boeing airliners essentially "autotrim". The former also being hard limited, while the latter is soft that you can override with extra input force. But I digress. Again, they all have trims available but that's mostly for compensating for engine loss or other malfunction. On the A-10's limits, I may have read that wrong. I thought the site used the term limiter, but they may have meant written limits. I assumed the SAS was g and alpha limiting from the way it was termed. On the indicator: so it sounds like it's more a monochrome callibrated stall threshold indicator than a normal AoA dial. There were a couple compaints on the forum previously when I searched and this didn't appear mentioned. Clearly from the other posts here, this needed repeat for those of us who skimmed over that paragraph in the manual. Thanks!
  16. It reads too high in level flight, like 10 or 11 degrees. Wow. That's what you should have at low speed when landing with flaps. The real hog also has a limiter that prevents you from going past like 20-15 degrees, depending on the loudout weight programmed in. That doesnt' really bother me, or the fact I have to manually trim...which you shouldn't (the engine angle and SAS compensate enough most of the time). But the alpha indicator dial needs fixing. In fact, I don't think it's the dial but the flight model. Because the aircraft does begin to stall at just over 10 degrees additional alpha, or around 20. So it's not like it thinks it's 2-5 degrees in level flight. So a simple cockpit fix wouldn't be enough.
  17. I would love an onscreen or hud indicator or sound, like the falcon brakwind mods. Come to think of it, I'd also like corner displays in the hud-only mode like in DCS.
  18. Any way to hear the airbrake better or get onscreen or hud cueing that it's deployed? If not, where is the indicator/annunciator for it in the F-15 pit?
  19. This sucks. I just made a donation to help out. But I've also had my own problems for the last 5 days. One PC got a virus and another just spontaneously shutoff permanently. It's been years since I've had issues like that. Finally got a new partition up yesterday. Suggestions on where I can put my profiles and scripts?
  20. Any suggestions? Can all the sound be loaded in ram or soundcard buffer before they are needed? I get little freezes like Longbow 2 did years ago. Possible to turn down explosions, smoke, or their persistence? By the way, I turned down water, and it doesn't seem to be a problem up at a higher setting. Leaving the animated waves -- at least at "1" -- is fine.
  21. I also use that technique for firing around power towers. Fire off to the side slightly; when the missile is mid-flight, retarget. If the AA target is just flying perpendicular to you, try just having moving target track on. The analog EO sensor suite on the early KA-50's difficult to get a lock, though. Try changing the size of your brackets and adjust them down when you get a cue.
  22. Silicone grease is very thick. You don't want the spray. My Deoxit fader grease came in a little tub. Screwed up my dj mixer faders, but works wonders on the x52 swash plate...no, that's an understatement. It's transformed the stick's feel. To Caig Labs' credit, they did send me some other stuff that fixed my faders.
  23. I just used some Caig Deoxit Silicone Fader Grease (dhg-213) that never really worked well on my audio mixer faders, but has improved the feel of the stick by a zillion times. Just cleaned and then applied some to the underside of the plastic swash plate disk. BAM! Quiet, smooth, just the right amount of resistance, and with all the subtlety I could want in the stick inputs. Who needs fly-by-wire? heh heh
  24. Is there some other program out there that can do what PPJoy can that works with Vista? The scripts themselves are for GlovePIE. I'm just not aware of other "virtual joystick" systems out there. I wonder if there's some way of doing it natively from GlovePIE without PPJoy...
  25. My newest GlovePIE script (not uploaded yet) greatly improves this: var.0 = PPJoy1.Analog0 var.1 = PPJoy1.Analog1 var.2 = PPJoy1.Analog2 var.3 = PPJoy1.Analog3 var.4 = PPJoy1.Analog4 var.5 = PPJoy1.Analog5 var.6 = PPJoy1.Analog6 PPJoy1.Analog2 = Joystick1.z PPJoy1.Analog3 = Smooth(Joystick1.xrot, 2, .03) PPJoy1.Analog4 = Joystick1.yrot PPJoy1.Analog5 = Joystick1.zrot + (Joystick1.yrot * .5) PPJoy1.Analog6 = Smooth(Joystick1.slider, 2, .03) if doubleclicked(joystick1.button6) then begin { var.m = var.m + 1 if var.m = 1 then begin { say("Standard Dynamic Trim") press(leftctrl) press(t) release(t) release(leftctrl) } end if var.m = 2 then begin { say("Flight Director Dynamic Trim") press(leftctrl) press(t) release(t) release(leftctrl) } end if var.m > 2 then var.m = 0 if var.m = 0 then begin { say("Manual Trim") } end } end if var.m = 0 then begin { t = joystick1.button6 PPJoy1.Analog0 = Joystick1.x PPJoy1.Analog1 = Joystick1.y var.y = 0 var.x = 0 var.c = 0 var.l = 0 var.r = 0 var.p = 0 var.s = 0 } end if var.m = 1 then begin { var.c = 45 var.l = -0.575 var.r = 0.275 var.p = -0.900 var.s = 0.0 var.y = EnsureRange(Joystick1.y / var.c + var.y, var.p, var.s) PPJoy1.Analog1 = var.y + Joystick1.y var.x = EnsureRange(Joystick1.x / var.c + var.x, var.l, var.r) PPJoy1.Analog0 = var.x + Joystick1.x } end if var.m = 2 then begin { var.c = 70 var.l = -0.50 var.r = 0.0020 var.p = -0.775 var.s = 0.0 var.y = EnsureRange(Joystick1.y / var.c + var.y, var.p, var.s) PPJoy1.Analog1 = var.y + Joystick1.y var.x = EnsureRange(Joystick1.x / var.c + var.x, var.l, var.r) PPJoy1.Analog0 = var.x + Joystick1.x } end
×
×
  • Create New...