dazzan

Could you just give me a little example for NAV1 for example. [GF166.2] D0=? D1=? Many many thanks Gilles

Hi Pete I normally run FSX first than I run GFdisplay with the gfdisplay.ini file I sent you already. Only the com1 frequency is displayed. The other radios are not displayed at all although they are defined in the ini file. I tried with your ini file I downloaded with gfdisplay, there is the same problem, only Com1 is displayed, no other radios. I did not yet define the buttons, I will do that inside FSUIPC when I got Gfdisplay to work. Thanks Gilles FSUIPC4.1.zip

Hi Pete I tried to use Gfdisplay with the Gfdev.dll and FSX. I only get to work the display for Com1. I can not display Navs or Transponder. I copied the new GFdev.dll in the same folder as GFdisplay. I attach you my gfdisplay.ini file. I already worked with GFdisplay under FS2004, never had a problem. Thanks a lot Gilles GFdisplay.zip

Hi Pete How do I have to use this file? Is it possible to get the GF modules working with it? Do I need than widedisplay or can I simply replace the file in the goflight driver with this file as there is not yet a FSX driver for goflight modules out? Many thanks for your great help. Gilles

Hi Pete I have alittle trouble with my flaps. I have read the manual and know that in FS2004 values are from -16384 to +16384, but 0 to 16384 is also recognized. I use FSBUS on the client PC connected to FSUIPC on main PC. I use UDP protocol for wideclient. What happens is that after 10 minutes of flight flaps deploy on their own. I have defined the flaps in FSbus from 0 to 16384. There is no other hardware that could command flaps to deploy. Perhaps you have a good idea what to check. I know this is a complicated question, many thanks for your help. Gilles

Thanks Pete I think I found the mistake. I have defined the keys in wideclient as T function. I will try it with the P function. But I have another question. I use an keyboard encoder card with switches connected to. I use a lot of on-off-on switches. I never managed to get the release button function to work when the switch is set back from on to off. That means the definition for the key press function works but the release function (on the same FSUIPC page under Key menu) does not work. I think there is something that I do not understand. It seems to me that FSUIPC does not notice when the key goes off and therefore the defined release function does not work. Many thanks Gilles

Hi Pete I use the buttonkeys facility in wideclient.ini for sending a button function to FSUIPC on my FS computer. Everything is working well so far, except that I have to push the key on the server computer twice (2x) for sending it as button to the main computer. Strange is that when I start FS on the server computer, the first time I push a key on the client it works with the first push, but already for the second key that I push I have to push twice to see the button in FSUIPC on the server. I can not find what I am doing wrong. Many thanks for helping me Gilles

Hi Pete I want to set offset 564A Bit 7 when pressing a key. Therefore I use the Offset Byte Setbit function from the key press menu. my question is: 1)Does 0x564A mean offset 564A? 2)Under parameter do I simply write 7 for Bit 7. When rechecking it appears under the form x07. Does x07 also mean Bit7? Thanks for your precious help Gilles

Hi Pete Is it possible to set for example offset 564D .1 through FSUIPC. Does .1 mean a value ? I want to define a key. When I push the key I want to set for example offset 564D .1 Do I have to use the option Offset Byteset from FSUIPC? The parameter is that where I have to write the value? I need to do the same for example offset 5610 1 ? Does 1 mean here bit ? Which option in FSUIPC do I have to use to set that? Thanks for helping Gilles

Hi Pete Ihave aproblem withe the pressurization Land Alt knob 0X56A9 and the FLT Alt knob 0X56A8. I use a knitter for both as hardware. When I turn the knitter to the left I get in FSBUS the value -1 and to the right the value 1. But for using the offset I need the values 1 for decreasing the altitude and value 2 for increasing. Any idea how I can get this to work? Thanky a lot fo helping. Gilles

Hi Pete Thanks I will check that up. I am not blaming FSUIPC or Wifdefs at all. I am sorry if you did understand it that way. These are really great products, without I would not be able to build my cockpit. Bye Gilles

HI Pete I have installed the new versions FSUIPC 3.601 and Widefs 6.596. I changed also to UDP protocol. I only changed that in my configuration. Now when I set my flaps through FSBUS connected to FSUIPC, the flaps are no longer going in the right position. This means if I set flaps to 5 the ProjectMagenta flap indicator moves three very small steps to position 1. It moves 3 times but only goes to position 1. If I set for example higher flaps like 25, this position works. I got this problem only after installing the new FSUIPC and Widefs version. Another problem I have since a bit longer. Again FSBUS connects to FSUIPC. If I pull my speedbreak lever I only get a setting to 24%, after it jumps to Armed. I can not set for example 25% or more. Thanks for helping Gilles

Hi Pete I use the latest widefs versions for wideserver and wideclient. I have the following problem. In my computer I use 2 network cards. One is used for connection to the internet. The second connects via a hub to FS2004. When the first card is set to "obtain IP address" the internet connection works. For the second card, which should connect wideclient to wideserver I have defined an IP address manually (192.168.0.31), but widefs never connects. When checking the connection in windows explorer I have access to all the files on FS2004. It seems only wideclient is not working. Now when I change the first network card (which connects to the internet) to the IPaddress 192.168.0.31, the internet connection does not work anymore but the widefs connects normally ?? Please give me a hint Pete I am a little bit lost. Thanks for helping.

Hi Pete I am using for programming my GF 45 rotaries the following lines: 165=B66C0=4 P125,14,C1046,0 166=B66C0=4 U125,14,C1046,0 167=B66C0=4 P125,15,C1046,0 168=B66C0=4 U125,15,C1046,0 169=B66C0=4 P125,13,C1047,0 170=B66C0=4 U125,13,C1047,0 171=B66C0=4 P125,12,C1047,0 172=B66C0=4 U125,12,C1047,0 173=B66C0=4 P125,10,C1048,0 174=B66C0=4 U125,10,C1048,0 175=B66C0=4 P125,11,C1048,0 176=B66C0=4 U125,11,C1048,0 177=B66C0=4 P125,8,C1049,0 178=B66C0=4 U125,8,C1049,0 179=B66C0=4 P125,9,C1049,0 180=B66C0=4 U125,9,C1049,0 181=B66C0=5 P125,14,C1050,0 182=B66C0=5 U125,14,C1050,0 183=B66C0=5 P125,15,C1050,0 184=B66C0=5 U125,15,C1050,0 185=B66C0=5 P125,13,C1051,0 186=B66C0=5 U125,13,C1051,0 187=B66C0=5 P125,12,C1051,0 188=B66C0=5 U125,12,C1051,0 189=B66C0=5 P125,10,C1052,0 190=B66C0=5 U125,10,C1052,0 191=B66C0=5 P125,11,C1052,0 192=B66C0=5 U125,11,C1052,0 193=B66C0=5 P125,8,C1053,0 194=B66C0=5 U125,8,C1053,0 195=B66C0=5 P125,9,C1053,0 196=B66C0=5 U125,9,C1053,0 The problem is when decreasing for example the Adf (1or2) from 400 it should go to 399 but instead it jumps to 500 But for example from 399 it decreases to 398 and so on. The problem seems to be when changing the hundreds. Shall I use perhaps the fs2004 controls like: 165=B66C0=4 P125,14,65668,0 166=B66C0=4 U125,14,65668,0 167=B66C0=4 P125,15,65668,0 168=B66C0=4 U125,15,65568,0 and so on THanks

Hi Pete I would like to use the leds on the GFT8 with GFDisplay for indicating that Nav , strobe, logo , taxi, wing, recognition, beacon, landing lights are on. I think i have to use offset 0D0C. To program the buttons I have used the toggle navlights (for example) in FSUIPC. In GFdisplay I do not know how I could manage to get the appropriate led to work when a button is on. [GFT8.0] L0=XD0C ????? (landing lights) L1=XD0C ????? (nav lights) L2=XD0C ????? (taxi lights) and so on Thanks

Hi Pete I still have problems in version 3.5 with copilot setting. When moving the copilot axis there are no changing value in fsuipc setup. However when moving the copilot axis in Fs2004, I always get only half of the movement than I get on the captain side. I tried already to recalibrate the copilot joystick in windows, but it did not change anything in FS2004. The last working version I remember must be 3.41 Thanks Gilles

Hi Pete Version 3.45 did already not work

Hi Pete, The only version of FSUIPC I found back was version 3.4.1.1 Everything was OK there for: aileronB=66422 elevatorB=66425 rudderB=66428 I noticed also that fsuipc 3.48 takes the same axis for reverser 1 to 3. I changed the values to 0, but the B axis were still not working. Thanks

Hi Pete Since I have copied the new FSUIPC 3.48 version over an older FSUIPC version the following axis on the copilot side do no longer work. aileronB=66422 (Mixture1 in FS2004) elevatorB=66425 (Mixture2 in FS2004) rudderB=66428 (Mixture3 in FS2004) I did not change the FSUIPC.ini file at all. Everything is there as before. Even when I try to calibrate the pilot joystick axes via FSUIPC 3.48, there is absolutely no change in the calibration values (even after pushing "set"). What can I do? Thanks Pete

With Roger Wilco I had assigned the transmit key to a button on the joystick and sent it via FSUIPC and widefs to the client computer where Roger Wilco is installed. With Teamspeak I do not manage to get it work, even when I assign a keyboard command to the joystick button it is not recognized by Teamspeak, where I have assigned that command for transmit. Does anybody found a solution to this problem. Many thanks Gilles