On the other hand, if the correct values from the above tests are being received, then the hardware is working fine. If the hardware is indeed calibrated correctly in the operating system, the hardware itself is malfunctioning. If the correct values (according to the tests above) are not being received in X-Plane, and you have calibrated the controls in X-Plane per the section “Calibrating the Hardware” of Chapter 4 of the X-Plane 10 manual, then the issue is with the hardware’s calibration in your operating system, not X-Plane. The ruddr should indicate 1.0 or near 1.0.īy moving the stick and pedals and seeing what values they are sending X-Plane, you can see if X-Plane is getting proper stick input. The ruddr should indicate – 1.0 or near – 1.0. The elev should indicate – 1.0 or near – 1.0. The elev should indicate 1.0 or near 1.0. The ailrn should indicate 1.0 or near 1.0. The ailrn should indicate – 1.0 or near – 1.0. Each axis should indicate 0.0, or close to it. A box in the upper right should be displaying the elev, ailrn, and ruddr commands (elevator, aileron, rudder, respectively) being received from the joystick.This box will cause X-Plane to display the input it is receiving while running the simulation. Select the rightmost box next to joystick ail/elv/rud.Move your mouse to the top of the screen and open the Settings menu.A similar procedure may be used for other malfunctioning controls. In the following example we’ll assume that the plane’s pitch, yaw, and roll are not matching the way the joystick is being moved. Thankfully, X-Plane makes it easy to find out how the software is perceiving the flight controls’ input. Or to turn the PC on first after a power outage.If the joystick and other flight controls appear to be configured correctly (according to the steps outlined in the article Configuring Flight Controls), but are not giving the desired response in the simulator, it’s time to troubleshoot. The solution was to never turn the PC off, either. And that stupid plotter had a 20-minute initialization/self-test/warmup cycle, so he never turned it off. If the plotter was powered on before the PC, the PC wouldn't power up at all. With an onsite service call, I figured out that it was actually his parallel interface HP Paintjet large format plotter causing the problem. In his shop, it wouldn't power up at all. Back in the dark ages, I had a customer with a PC that wouldn't power on. If I'm nearby, the problem will go away again. When someone complains about an intermittent problem that was "fixed" & comes back, I tell them that it's because of my magnetic personality. Usually, when it's fixed, it's fixed - not just hiding. I'd much rather have something that fails every time. does the DX work with RF7 & earlier? I know that the X doesn't, and that caused problems for some people, too.Īnd I totally agree about the intermittent problems. But I have a very vague recollection that someone might have posted a similar problem with an X a long time ago, too. I'm aware that the problem is specific to the DX. They don't look pretty - but they work great. Most of them demand cosmetic perfection even if the bungs don't affect the operation. My older laptop has a broken corner on the display enclosure. Oh well, the price was right since I work for a PC refurbisher & can get cosmetically challenged PC's for GREAT (scrap) prices. HhhMmmm I wonder why I bothered to upgrade - except for the video card. The biggest difference I see between them is that the GTS450 gives me about 100fps & the GTX960 gives me about 220 on Henson Field with the same aircraft on "high" graphics settings. They both work perfectly with both InterLink Elite & X in any USB port. Both boot from SSD & have a RAID data volume. I even tried hooking up my old PC & tried testing on that & still can't reproduce whatever the problem was to jog my memory. Select the rightmost box next to joystick ail/elv/rud. But I can't reproduce it now, and don't remember exactly what the problem was. Move your mouse to the top of the screen and open the Settings menu. But I have a VERY vague recollection that I had some sort of trouble with it when I first got it & plugged it into a USB3 port that went away when I connected to USB2. And the cable has a blue tongue, so I guess it's probably native USB3 anyway. I have an InterLink X not a DX so we're talking apples & oranges. I admit that my speculation is based on "head games" not any sophisticated testing or equipment.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |