Jump to content
The simFlight Network Forums

Search the Community

Showing results for tags 'saitek'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Product Support Forums
    • FSUIPC Support Pete Dowson Modules
    • MyTraffic Support Forum
    • FeelThere Support Forums
    • FS Commander Support Forum
    • Flying W Simulation
    • AConstable Traffic Sounds Support Forum
    • Fabio Merlo Products Support Forum
    • Elite-Air Studio Support Forum
    • Nikola Jovanovic Support Forum
    • Intrasystems Support Forum
    • FScene Support Forum
    • Taburet & DanVFR Support Forum
    • Environ Scenery
  • simFlight DE
  • FS MAGAZIN (DE)
  • simRussia
  • FSUIPC Client DLL for .NET

Categories

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 38 results

  1. Hello Pete, My apologies to bother you with a problem. I am a registered user of FSUIPC and I have a new problem since I installed the update 4.5 of P3D. The problem is that the throttle and the propeller pitch of the Saitek Quadrant moves together with the Ailerons, also when trying to re-calibrate it withing FSUIPC. I have been trying for days to solve this without finding the solution. Latest FSUIPC update has been installed. Windows 10 P3D 4.5 FSUIPC 5.151 All registered. Could you please help? Many thanks. Kr, Enrico
  2. It appears that many users have problems with Saitek Quadrant drivers setting up the Registry incorrectly for one or more of the levers, with the result that either only 50% of the range use used or the values you get are only on (max value, 16383) or off (min value 0 or -16384). Here is the way to edit the Registry and fix this, at least until Saitek fixes their installers. (Thanks to a main forum reply by "goaround"): ==================================== Here is our registry calibration guide: One way to re-calibrate your device is to reset the raw data values that are held in Windows registry. To do this: 1. Remove the USB plug for your controller from the PC. 2. Press and hold the Windows key on your keyboard and then press the letter R. This will open the Run box. 3. Type regedit and then click ok. For Windows Vista/7/8/8.1 4. The Registry Editor will have a list of folders on the left hand side. Go down into the following folders in order by clicking the + next to the folder name. + HKEY_LOCAL_MACHINE + System + CurrentControlSet + Control + Media Properties + Private Properties + Joystick + OEM 5. Delete any folder inside the Direct Input folder that begins VID_06A3 or VID_0738, if you know the specific PID number or your device then you only need to delete the string that matches the VID and PID. 6. Then navigate to the DirectInput folder + HKEY_CURRENT_USER + SYSTEM + CurrentControlSet + Control + Media Properties + Private Properties + DirectInput 7. Delete any folder inside the Direct Input folder that begins VID_06A3 or VID_0738, if you know the specific PID number or your device then you only need to delete the string that matches the VID and PID. 8. Once deleted, close the editor, then plug the USB back into the original port. Move all the axes of the controller through their full range of movement four times. This will rebuild the data range for all axes.
  3. Hello, I have bought a Saitek X52 Pro (replacing a Thrustmaster 4 HOTAS) and thinking that it will work flawlessly, I plugged it into USB slot, then installed the related software and the FSX-P3D and Xp11 plugins required from the manufacturer's website, which later I found out was a mistake. As the title suggests now P3Dv4.1 crashes to desktop while loading the main scenario screen. If I disconnect the controller, the application starts fine. I followed some steps that I found here in this forums, like uninstalling the software, removing the device and the drivers from Device Manager but it still doesn't work. Also interesting is that I can't even find the device listed in Device Manager although it is connected and visible under "Devices and Printers" I am attaching the relevant files and any help is appreciated. Thanks. event viewer.txt FSUIPC5.log FSUIPC5.JoyScan.csv
  4. Hello, I've a question on how to get the mode system to work for the Siatke X52 Pro Joystick. The mode selector switch (a rotary knob) on the top right corner of the joystick is not seen/detected by FSUIPC; meaning that as i switch from mode 1 to 2 to 3, there is no joystick action registered in the "Button + Switches" tab in FSUIPC. However, the mode switches work with default windows game controller properties as three red tabs that light up as you switch the modes. The mode switch also works with Saitek ST Programming software and it allows be different functions to be set on the same key with different modes. For reference, I'm using Windows 7 Ultimate 64 bit, and X52 Pro driver version is 7.0.53.6, and ST Programming software version is also 7.0.53.6; and FSX:Acceleration Here is what I would like to do, I have a few mouse macros in FSUIPC and want to assign them to my X52 joystick buttons with mode 2. Those joystick buttons are already taken in mode 1. So, I want to assign 2 different functions to 1 joystick key using 2 modes. Mode 1, joy#1,btn#1 will perform X action, and Y action when in Mode 2. Can this be done? Anyone here has experience with the X52 controllers and modes with FSUIPC?
  5. PLEASE ALWAYS POST SUPPORT QUESTIONS IN THE SUPPORT FORUM! So, I've had the Saitek X-56 Rhino for a while, and it's worked without problems, until about a week ago. Neither the stick or trottle quadrant is working in P3D at the moment, but the wierd thing is it's working in the Saitek program. I've tried most of the usual stuff like changing USB port, I've also done a troubleshooting in Windows, with no results. I am using FSUIPC 4 and I have disabled my controllers in P3D. I've been told you can change the JoyNames in the fsuipc.ini file, but to what, and what numbers to change? Very wierd problem, seems like it should be an easy fix. Thanks in advance /Fred
  6. MOVED FROM FAQ SUBFORUM! I am running FSX Steam Edition Microsoft@ Flight Simulator X Deluxe 10.0.62615.0 (FSX.20150710-10ss) on a Windows 10 Pro build 15063, 64 bit system using FSUIPC version 4.969. I cannot get my CH Eclipse Yoke and Saitek Pro Throttle Quadrant both working together. I can assign and calibrate either device and use it standalone without any problems. However, if I configure both, the CH Eclipse Yoke seems to take control and I can only assign axes to the yoke. This happens regardless of I having "AutoAssignLetters=Yes or No." Both devices are using a USB port on the motherboard. I have tried exchanging ports with no resolution. I have tried using both devices on a USB 3.0 hub with no resolution. Whenever both devices are configured I receive the following information from the FSUIPC console ----------- 172 ---------------------- Joystick Device Scan ----------------------- 172 Product= CH ECLIPSE YOKE 172 Manufacturer= S 172 Vendor=068E, Product=0057 (Version 0.0) 172 GUIDs returned for product: VID_068E&PID_0057: 172 GUID= {6F807CF0-680B-11E7-8001-444553540000} 172 Details: Btns=26, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U1023,V1023,X1023,Y1023,Z1023 172 Product= Saitek Pro Flight Quadrant 172 Manufacturer= Saitek 172 Vendor=06A3, Product=0C2D (Version 2.2) 172 GUIDs returned for product: VID_06A3&PID_0C2D: 172 GUID= {FD6494F0-6D53-11E7-8001-444553540000} 187 Details: Btns=9, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255 187 Product= HP Wireless Keyboard Kit 187 Manufacturer= Lite-On Technology Corp. 187 Vendor=04CA, Product=008D (Version 0.97) 187 ------------------------------------------------------------------- 187 Device acquired for use: 187 Joystick ID = 1 (Registry okay) 187 1=CH ECLIPSE YOKE 187 1.GUID={6F807CF0-680B-11E7-8001-444553540000} 203 Device acquired for use: 203 Joystick ID = 1 (Registry okay) 203 1= 203 1.GUID={6F807CF0-680B-11E7-8001-444553540000} 203 ------------------------------------------------------------------- Any ideas or suggestions would be helpful. Thanks, slapstock
  7. Hi, I've had this issue before where I have two throttle quadrants (Saitek), but FSUIPC assigns the same GUID to both. So only 1 is read. I had this a long time ago and can't remember how I fixed it. I believe it was to remove something in [joyname], but I'd like to double check. Here is what I have: In the FSUIPC.txt I see: 94 ---------------------- Joystick Device Scan ----------------------- 94 Product= Saitek Pro Flight Quadrant 94 Manufacturer= Saitek 94 Vendor=06A3, Product=0C2D (Version 2.2) 110 GUIDs returned for product: VID_06A3&PID_0C2D: 110 GUID= {0BA51920-4E57-11E7-8004-444553540000} 110 Details: Btns=9, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255 110 GUID= {0BA56740-4E57-11E7-8007-444553540000} 110 Details: Btns=9, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255 110 Product= Saitek Pro Flight Quadrant 110 Manufacturer= Saitek 110 Vendor=06A3, Product=0C2D (Version 2.2) In the FSUIPC.ini I see: [JoyNames] AutoAssignLetters=No 2=VKBsim Gladiator 2.GUID={0BA58E50-4E57-11E7-8008-444553540000} 3=Saitek Pro Flight Rudder Pedals 3.GUID={0BA5B560-4E57-11E7-800A-444553540000} 1=Saitek Pro Flight Throttle Quadrant 1.GUID={0BA56740-4E57-11E7-8007-444553540000} Now I believe I should see two, throttle quads and I delete them, but I can't remember off the top of my head how I was told to solve this before. Some help would be appreciated. I did just fresh install windows and etc on my pc, so I don't have the drivers for the saitek devices when writing this.
  8. Introduction This post explains how you can use a LUA routine to access the status of the buttons/switches/selectors/gear and flaps lever and trim wheel (herewith named collectively as Buttons) on 3 Saitek panels using FSUIPC and Linda. The first section presents a quick instruction to start gathering information based on lua program attached to this post. The second section gives a simple example of a Lua program that access the Saitek panel buttons status and select specific FSX/P3D actions accordingly. The third section goes more into the details about how this LUA programs was made. You need a registered version of FSUIPC for this to work. Section 1 – Quick Start Download and install the relevant LUA routines; Attached to this post are 3 Lua programs corresponding to the 3 Saitek panels. You just need to install the ones corresponding to the panel you own. The 3 Lua programs are: - HIDRadio.lua - HIDMulti.lua - HIDSwitch.lua Note; I have renamed the 3 programs with a .txt exension for upload as the system doesnt allow to upload .lua files. You will need to change the extension back to .lua before using them. To install them, just drop the ones corresponding to the panel you own into the “module” directory of FSX/P3D. Automatic start of the LUA programs The LUA programs selected above must run in permanence to scan the status of the buttons and map (copy) this information into specific address of the FSUIPC offsets. To inform FSUIPC that those programs must start and run continuously, it is necessary to add the following lines to the FSUIPC.ini files (located in the module directory of FSX/P3D). [Auto] 1=lua HIDRadio 2=lua HIDMulti 3=lua HIDSwitch On the next start-up of FSUIPC, the Lua program will start to scan the status of the buttons and selector on Saitek panels. Checking with FSUIPC logging facility that the Lua programs are in place and operating FSUIPC has a built in logging facility that can be useful to check the proper operation of the Lua programs and the correct mapping of switches to the offset address. Go to the FSUIPC Logging tab and on the right part of the screen, enter the following information: Offset Type of data Remark 3358 U32 Saitek Radio panel offset address 335C U32 Saitek Multi Panel offset address 3360 U32 Saitek Switches Panel offset address Then click on “FS window” and you should have a green message on the top left of your screen. Move some selectors or push buttons on each of your panels and see if the values on screen change according to the position of the buttons. An annex at the end of this post gives the value of each button. Note1 : The knob just send a short pulse so the number on screen will just change very rapidly and come back to the value prior to moving the knob when you stop moving it. Note 2: The buttons just change status while they are pressed, they doesn’t indicate the status of the corresponding function. Ex: the Autopilot button will just send a ON status when you press the button. So this is not intended to test if functions like the AP are engaged or not. It’s just to test the instantaneous position of the hardware buttons. Make sure you have version 4.934 as the previous one has a problem that killed lua programs on start-up and caused me a couple of evening of head scratching... 4.934 solved this as soon as I installed it. Accessing the information from within a LUA program in Linda Now everything is in place and you have the possibility to access the information on your panel switch. For simple assignation of a single button, you usually doesn’t need complex programming as FSX, Spad or Linda menu all allow you to directly select FSX/P3D commands. On the other hand, if you want to combine the status from different buttons to trigger a specific FSX/P3D action, then you need to use a Lua program (you can also use FSUIPC conditional button programming but Lua is more flexible). Using Linda, it is possible to assign user created Lua program to a button so the program is called when the button is push (or a switch is move to the “on” position or a selector is put in a specific position). The Lua program allows you to test the status of others buttons and makes your program act accordingly to send the proper FSX/P3D command. In Linda, you can create individual LUA program module (a module can contain several Lua program) for each aircraft. Linda includes also a text editor that makes creation of Lua program easy. Some functions in the Lua library allow reading specific address in FSUIPC offsets. Each address that will be assigned to the 3 Saitek panels covered here will contain between 18 to 20 bits of useful information (not considering the LED display) that correspond to all the buttons, switches, selectors and gear and flaps lever of the panel. The switches panel for instance contains 20 bits of information that you can test. The address to use in order to read each panel information are: 0x3358 = Radio panel 0x335C = Multi panel 0x3360 = Switch panel Note : You can assign other address if those one are already used for other purposed on your setup. You will need to modify the HIDxxx.lua program that correspond to the device you want to change. Note: The "0x" in the adress above just means that its written in hexadecimal notation. You will need to include the 0x within Lua program otherwise it will consider that the address provided is decimal. Please note that in the FSUIPC logging page, you don’t need to include the 0x as this page always consider that the value entered is hexadecimal. There are two main functions within Lua programs that can help you to read buttons status. First, the following Lua program line read all the bytes of information from the Saitek Radio panel and put it in a variable named “pos”. pos = ipc.readUB(0x3358) But the value returned is not quite useful by itself as it represents the cumulative sum of all the individual bits for switches that are in the “on” position resulting in a large number of possible values. You then need to isolate the value that you are specifically interested by using the following function (here represented in a separate line). pos = logic.And(pos,mask). Here mask correspond to the specific value (or sum of values) you are interested in. For instance, if you are interested to test if the position of the magneto switch is at the “right” position on the Saitek switch panel, then the value for the mask is 32768 (see annex for all possible values) and the Lua program line becomes Pos = logic.And(pos,32768) Section 2 : Example for the Duke piston or Douglas C-47 Magneto selector In the Duke Piston from Real air (and Douglas C-47 from Manfred Jahn), the magneto animation in the VC are reversed compared to the Saitek switch magneto button for the “left” and “right” position which create a weird jump in the VC while you move the magneto selector on your Saitek panel. - Duke Piston/Douglas C-47 VC magneto selector order: Off – Left – Right – Both – Start - Saitek Switch panel magneto selector order: Off – Right – Left – Both - Start So the objective is to program a function in a Linda module that will reverse the operation of the left and right magneto position between the Saitek panel and the VC. In addition, we want to test the position of the upper mode button for the Saitek radio panel to determine if we want to operate the motor 1 or 2. Spad has a built-in functionality that allows using several switches (ex: Aternator, fuel pump, cowl, de ice) to act on motor 1 or on motor 2 according to the position of the top selector on the Radio panel and we want to replicate this functionality here. First you need to create a module for your targeted aircraft if it’s not already existing. See Linda documentation to do this. Then you need to copy the following program (or use the Magneto.txt file provided) into the aircraft module using Linda editor screen. Again, refer to Linda documentation to see how to open the editor. The title between double hash characters is recognized by Linda as a heading separator for functions. It makes easier to identify function you have created. Comments (text preceded by --) in the program below provide detailed comments for each steps. -- ## Magneto ## Function MagLeftVC () -- This function handle the reversal of the magneto in the VC panel compared to the Saitek selector. -- It is activated when the selector on the Saitek switch panel will be put at the left position. -- It will result in positionning the VC magneto selector to the "right" position. -- The Saitek Radio top left selector at position COM1 means that the left engine is considered. If the selector is at the COM2 position, then the right engine will be treated. -- The information about the radio panel status is at offset 0x3358 -- reading the offset to get all Radio panel switches current status pos = ipc.readUB(0x3358) -- The next line of lua code will isolate the bits of information we are interested in -- mask = 1 would be usefull ot test if the top left selector at the COM1 position -- mask = 2 would be appropriate to test if the top left selector at the COM2 position -- Mask = 3 accept both COM1 and COM2 and will return either 1 or 2 as the selector -- can be only in one of the two positions at a given time. -- If the selector is not at COM1 or COM2, then the logic.And function will return zero and no action will be done. pos = logic.And(pos,3) -- the next group of lines will send the command to put the magneto for left or right motor in the right position in the VC. -- 66400 is the Magneto1_set command for FSX/P3D -- 66401 is the Magneto2_set command for FSX/P3D -- The parameter 2 is for the “right” position of the magneto if pos ==1 then ipc.control(66400,2) else if pos ==2 then ipc.control(66401,2) end end Function MagRightVC () -- same approach as for the left mag function, without comments here pos = ipc.readUB(0x3358) pos = logic.And(pos,3) if pos ==1 then ipc.control(66400,1) elseif pos ==2 then ipc.control(66401,1) end end Section 3 – Nut and Bolts. This section provides some additional explanation on how the HIDRadio.lua program was created from the HIDDemo.lua program provided by Peter. Step 1: Obtain HIDDemo.lua We need to have a Lua program running continuously to scan the Saitek panel switch status then map this information in FSUIPC offset. The offset can then be read from a Lua program in a Linda module for an aircraft. Peter Dowson provided an example of a Lua program that scan HID device like the Saitek panels and write the information on offset. We just want to use his demo and modify it a bit. The HidDemo.lua program is available in the complete install of FSUIPC4. Or you can download the latest HidDemo.lua example from : http://forum.simflight.com/topic/68257-latest-lua-package-for-fsuipc-and-wideclient/ Step 2: Create HIDRadio.lua Make a copy of HIDDemo.lua and name it HIDRadio.lua (we will give only one example herewith but the same approach works for the switch and the multi panel also). Step 3 – Adjust HID device identification At the beginning of the HIDDemo.lua program, there is two lines that identify the Saitek panel (HID device) you want to communicate with. You have to insert the hexadecimal code for the vendor and for the product. For instance the lines for the Saitek radio panel are: -- Saitek Radio panel Vendor = 0x06A3 Product = 0x0D05 If you dont know the HID device codes, there is a utility provided by Peter Dowson called HIDscanner.exe that gives a report about all devices connected to your PC and their vendor rand product codes. I already run this utility to find the relevant information of the 3 following Saitek Products. Radio Panel : Vendor = 0x06A3 Product = 0x0D05 Multi Panel : Vendor =0x06A3 Product = 0x0D06 Switch Panel : Vendor =0x06A3 Product = 0x0D67 The HIDScanner.exe utility is available at the same link provided above on Peter support page. Step 4 : Change the size and destination of information blocks In HIDDemo.exe, you will find a loop of instruction toward the end of the program that read the status of the buttons on your HID device and copy it to a specific offset. The loop is initially programmed for reading 8 blocks composed of 4 Bytes of information. For the Saitek panel switches, you only need to do it once as all information fit into a double world (32 bits of information). So I cleaned the iteration loop (from 1 to 8 and adjusted the HIDDemo.lua program to do a single read of a 32 bits of information that is sufficient for the Saitek panels. Next, you need to select the destination for the button information in the FSUIPC offset table. There is an ipc.writeUD instruction in the HIDDemo.lua program that was modified to correspond to an offset that was used for mapping. The possible offset for the 9 contiguous blocks of 4 bytes (32 bits of information) are: 0x3340, 0x3344, 0x3348, 0x334C, 0x3350, 0x3354, 0x3358, 0x335C, 0x3360. See the “FSUIPC4 Offset Status.pdf” document provided with FSUIPC documentation. The Saitek version of HIDDemo.lua use the 3 last virtual joystick addresses so Joystick 71,72 and 73 located at 0x3358, 0x335C and 0x3360 respectively. Step 5 : Install your newly created Lua program Just copy them it in the “module” directory of FSX or P3D. If you have started with the quick start portion of this document, you have already done this. Step 6 : Automatic startup of HIDRadio.lua To start automatically your Lua program add the following lines in FSUIPC.ini. If you have applied the quick start instruction, its already done. [Auto] 1=lua HidRadio Step 7 : Create custom lua program See the example provided for the Duke above. Annex: Saitek panels reference of “buttons” value Saitek Radio Panel (20 bit of information + 2 bit unused) Top left mode selector 1= Com1 2= Com2 4= Nav1 8= Nav2 16= Adf 32= Dme 64= Xpdr Bottom Left mode selector 128= Com1 256= Com2 512= Nav1 1024= Nav2 2048= Adf 4096= Dme 8192= Xpdr 16384 = Top right ACT/STB button 32768 = Bottom right ACT/STB button 65536 = Clockwise turn of the top knob 131072 (2E17)=Counter-clockwise turn of the top knob 1048576 (2E20) = Clockwise turn of the bottom knob 2097152 (2E21) = Counter-clockwise turn of the bottom knob Saitek Multi Panel (20 bit of information) Selector button 1= Alt 2= VS 4= IAS 8=HDG 16=CRS 32= Clockwise rotation of knob 64= Counter clockwise rotation of knob 128= AP button 256= HDG button 512= NAV button 1024= IAS button 2048= ALT button 4096= VS button 8192= APR button 16384= REV button 32768= Auto Throttle switch ON 65536= Flaps up (2^16) 131072= Flaps down (2^17) 262144= Elevator Trim Pitch up (2^18) 524288= Elevator Trim Pitch Down (2^19) Saitek Switch panel (20 bit of information) Note: The minimum value returned corresponds to the position of the landing gear handle plus the position of the magneto knob. 262144 is returned if the gear lever is UP and 524288 if the gear lever is DOWN. 1= Battery 2= Alternator 4= Avionic 8= Pump 16= De Ice 32= Pitot heat 64= Cowl 128= Panel 256= Beacon 512= Nav 1024= Strobe 2048= Taxi 4096= Landing Magneto selector 8192= Off magneto 16384= Left Magneto 32768= Right Magneto 65536= Both Magneto 131072= Start Magneto Landing gear lever 262144= Landing gear Up 524288 (2E19)= Landing Gear Down Magneto.txt HidMulti.txt HidRadio.txt HidSwitch.txt
  9. Hi! Before anything else I must state that I have checked the forums and the FAQ. My problem is similar to what was experienced by other people but the solution that worked for others and is suggested in the FAQ does not work for me. The problem: FSUIPC (paid/registered) does not detect axes or buttons on my Saitek X-55 throttle as well as the stick The Saitek rudder pedals are detected correctly Two saitek throttle quadrants are detected correctly All the devices, in cluding the X-55 units work just fine both in the Windows calibration utility and when mapped directly via FSX I have tried to use JoysID as discussed in several places, and that had no effect. Swapping devices or assigning new IDs (not used before) to the X-55 units did not make any difference. FSUIPC still does not see them. Using FSX-SE I am on Windows 10 pro Latest Saitek drivers Latest version of FSUIPC Looked at discussions here: https://www.avsim.com/forums/topic/437639-x55-not-working-with-fsuipc-fsx-solution/ As well as other places. Everybody points me to JoysID utility, but that gets me zero results... Any other ideas? Thanks Arnon
  10. Hello everyone, this is my second post in this prestigious forum. I have the same problem with one of the levers (center) in my throttle quadrant Saitek. When I do the calibration test in the windows panel, the three levers mark the range completely normal without problem. In FSX calibration module, the the medium lever that I use for the espoiler (axis X) does not move in any sense. The other two levers move complete. I have already tried everything recommended in this forum (and others) but the problem persists. I appreciate any advice or suggestion what could be the cause of the problem. Thanks in advance Pablo from Caracas pd: Excuse my English.
  11. Hi Pete, this is about the problem of the misalignment of the Saitek trim wheel when disengaging the autopilot. As soon as you move the trim wheel the airplane bounces up or down related to the absolute position of the trim wheel. That is well known to all users of a trim wheel and really miserable. I found in a X-Plane forum an idea which leads imho to a really handy and reasonable workaround to avoid that problem: i wrote a lua to deal with the problem. what it does: in AP mode the trim wheel disconnect from the trim axis in non AP mode the trim wheel connects. in most cases the trim wheel will be physically in the wrong pos in relation to the ac trim axis, so if you move the wheel and he is out of sync, you get a display on the left side of your screen. red if out of sync, green when in sync. both values are visible so you can move the wheel to the correct ac setting. only then the wheel axis connects to the ac trim axis and you can use it. its possible you have to alter some settings due to different screen res. For me this would be a great solution to get rid of the trim wheel problem. Is it possible to realize that in FSX using a LUA? And at least a question to the community: is there anybody who is able to write that LUA and would like to do that? Thanks for your support, Juergen
  12. My new Saitek Cessna Trim Wheel is not recognized in Axis assignments by FSUIPC. I have P3D v3.4 running on Windows 10 and I can use the Trim Wheel in Windows Device settings. If i enable controllers in P3D, then I am able to assign the Trim Wheel, but not in FSUIPC. Michael
  13. Hi to all, first of all i'm sorry if this is not the right place for this question? I have brand new Switch Panel of Saitek. I have already tested original and SPAD Drivers, but my problem Continues. If i test at the setup panels the switch panel works fine. But when i'm flying (i've tested with two aircrafts KingAir C350 and LearJet 45) i've a lot of problems, for example: When i switch the beacon light the generators go Off, or when i switch any other key (no matter witch one) the engine starters switches off or on... ore the gear lights go on... really a dissaster... With the SPAD the keys go trought FSUIPC, but i can not customize o control what FSUIPC makes... with the PAID FSUIPC Version may i solve my problem? or just can i customize whatsdoes every switch of the switch panel? Thanks in Advance and sorry for my bad english.
  14. Hi, I was just wondering whether I could program my saitek controllers with fsuipc without rescripting the lua because if I did, I would break it, or do it wrong and waste time! My LINDA is playing up, so that's not working anyway. I am wanting to set the knob on the multipanel to a rudder/ nose wheel steering axis, as I would like to make a nose wheel tiller. Is this possible to do using fsuipc? Thanks a lot Harry Karmel
  15. Hi everyone! It's been a while since I got back into simming - I've been working on a home cockpit which is finally complete! It's pretty basic but considering just how bad I am at DIY I'm extremely pleased with how it's turned out. You can see it here: https://www.dropbox.com/s/h10i9t6eesuhamd/20160321_141947.jpg?dl=0 Anyway, onto the problem. I've purchased and installed Iris Simulation's Jabiru J-160 (I'm a microlight chap) and I'm trying to get all the buttons to work with my Saitek switch panel. I've got a paid for and registered latest version of FSUIPC and it works superbly. However, for the life of me I can't map the buttons on the aircraft panel with the buttons from the Saitek controller. Here's what I'm doing: > Using SPAD assign a 'virtual joystick' and button for the "fuel pump" switch > With FSUIPC open I can import that button > I assign the "Toggle elect fuel pump" to it (using parameter = 1) > Nothing happens I've been using FSUIPC perfectly fine with some other controls like toggling the fuel tap. It's just the Saitek panel I'm struggling with. I remember, a few years ago, I got the Katana X and that came with a bunch of custom variables that had to be mapped. I seem to remember these already being available inside FSUIPC's list of controls. However, I can't find such a thing for the Jabiru. Having looked in the support section for Irish Simulations I know they use custom variables for the buttons and switches. Does anyone know how to solve me problem? I'm kind of guessing that somehow, FSUIPC has to recognise the custom variables in order to show them as options in the controls list. Any ideas how I might achieve that? Many thanks everyone! Dave
  16. Can anybody explain step by step how to link FSUIPC, PMDG, and Saitek controls together, to make them all work as they should ? there are a lot of people like myself looking for help with this particular issue and struggling with it. a step by step guide would be much appreciated.please bare in mind that not all people are PC experts. please include a donation link because a lot of flyers would appreciate the work one will do. Regards
  17. Hello all Simmers, Since long time I am looking for a solution to connect AND control my FT A320 by Saitek devices Multi Panel and Radio Panel. As the FT A320 offsets are not standard FSX offsets, it is not possible to connect e.g. "set altitude" to the Multipanel. Now since some month there is a new software available called SPAD.neXt (Saitek Panel Advanced Drivers neXt Generation). This is a new driver software for the Saitek devices. But unfortunately this software needs LVARs for connections and the FT Airbus doesn't provide LVARS. But a complete list for these special Offsets is available by "FSUIPC Exporter". For an extra development to integrate the FT busses in his product, the developer needs information about how many pilot are interested in that implementation. So please respond as much as possible on my "survey" here. Thanks and regards Alhard
  18. Hi, Recently, I have noticed a disconnect while using P3d with my Saitek Throttle Quadrant(Single) when I am using my profile for 'Propeller' aircraft. As I move the throttle from lowest to highest, the throttle is maxed on the plane already at approc 25% of the levers position. I don't know what caused the issue becuase for the last few months, I have had no issues or need to change any settings from the day I installed FSUIPC into P3d. What I did to root cause the issue so far: 1) Reset/Recalibrate the throttle settings in FSUIPC - No Change 2) I did an Axis event log - I can share that is needed. 3) Verified the simple controls settings(null/sensitivity) - as they should be as per the manual 3) Tried to compare my settings in another profile with my 'props' profile -- I didnt notice anything different Any suggestions/direction would be appreciated.
  19. MOVED FROM "USER CONTRIBUTIONS" SUBFORUM so it might attract answers ... Because I am trying to understand the scenary I did: Is something wrong in this diagram?
  20. My first post: I have FSUIPC4 4.939 (registered) running in P3D 2.5; Saitek yoke, throttle, rudder, and trim fully controlled by FSUIPC (and thank you for that!). My problem exists with or without TRrackIr 5 or ASN add on programs running. When I start P3D for the first time after a PC boot everything works perfectly until I adjust the trim control; once the trim is used I lose all control inputs and FSUIPC not only quits working but is frozen to the point that the program cannot even be modified, nothing can be selected. However, if I exit P3D and restart, everything works perfectly again including the trim. The only difference in the FSUIPC4.log is the following entry in the first run: 1900890 ***** HID USB device reconnected: re-initializing FSUIPC connections The line is gone from the log on the next run. I have changed USB ports and tried resetting the trim settings (after the first run) and the problem persists. I look forward to any suggestions.
  21. Hello Guys , So I've updated the Aerosoft Airbus A320 to ver 1.30 , even though , I have bought Saitek Flight Sim Yoke . The issue is that I'am using C1 and C2 to move the rudder ( i've set it in FSUIPC ) , but there is no reaction from the aircraft ! is working on almost on all aircraft , any help regarding this ?
  22. Hello all! A newcomer to the forum here, and a complete beginner to FSUIPC, SPAD, Lua and all that jazz. My dilemma is that I do not know how to control and input multiple control axes, a Saitek Pro Flight Yoke and X52 joystick at the same time. At my ATC (Air Cadets) squadron, we have a pretty comprehensive setup, with Saitek panels, pedals, three screens and a projector. I'm in charge of the renovation project and a particular problem was the complications of having the two control inputs working at the same time; we had to reset FSX every time we wanted to swap. This is a problem and as far as I'm aware, is impossible in FSX's default binding settings. Using SPAD for the multitude of panels we have "shouldn't" be a problem (we'll see!) but I am clueless about setting up multiple axes to work simultaneously (even a method where there is a "sidestick priority-esque" system to use a button to switch between control methods is fine). Any insight is much appreciated and thanks to anyone in advance, Liam
  23. I have recently been trying to setup my Saitek Throttle and seem to be having some problems. I have Assigned to axis' on my throttle to a throttle each aka. Axis Y for Throttle 1 and Axis Z for Throttle 2. I assigned both in the Axis assignment section of FSUIPC and then pressed 'Set' for both Throttle 1 and 2 in the Calibration section but when I went into the VC I had a problem. I tried moving both at the same time and the first thing I noticed was that Throttle 1 jumped straight to about 50% even though I only pushed it forward slightly on my Saitek Throttle. Throttle number 2 seemed fine, when I move it a slight bit it only moves a slight bit in the simulator so Throttle 1 is the only one I am having problems with. I am still fairly new to FSUIPC so still trying to get the hang of it. My FSUIPC.ini file - http://pastebin.com/RGBuYGX0 Thanks, Robbie
  24. Hi all. I haev just recently purchased a Saitek Throttle Quadrant to go with the one I already own that came with my yoke however I am having problems with setting it up in FSUIPC. When I go into the 'Axis Assignment' page in FSUIPC, click 'Rescan' and move any of the 3 axis' on my NEW throttle they aren't picked up! When I move my already owned throttle's axis' they are picked up...? I hope to hear from someone soon! Any help will be appreciated. Thanks, Robbie
  25. Hi. I have been using FSUIPC for about a month now and have been very pleased with it. Although I have recently ran into a problem. I now have no control over my rudder and brake axis. I use saitek rudder pedals and therefore have a rudder and brake axis in the one controller. I tried to assign the rudder and brake axis through the Axis Assignment section of FSUIPC but every time I move either the rudder or brakes it is not picked up inside FSUIPC. I tried looking at saiteks own control panel for the pedals and everything seemed fine their, all axis working and moving in the calibration. I also tried assigning it in FSX's own controller page, it also worked their. I do not want to have it assigned in the FSX control settings though as I am on Windows 8 and have my controllers set up in their makes a lot of problems such as the controller just going off, that is one of the main reasons for me purchasing FSUIPC. Any help is much appreciated as this is really annoying me and stopping me from flying at the moment. Thanks, Robbie
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.