Jump to content
The simFlight Network Forums

egkkman

Members
  • Content count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About egkkman

  • Rank
    Member
  1. Hi Alan, That's great thanks very much. I will be making the purchase. Regards Dave
  2. Hello Alan, I am using P3D V2.3 and VOXATC, the AI traffic is provided by My Traffic 3D. Do you know if your product will work with this combination? I have read a post where you say the product is compatible with all addons, I'm just double checking as my setup is not just an AI addon scenario. Thanks very much. Regards Dave
  3. AI Sound Level

    Hi Burkhard, I am using MyTraffic3D in P3D V2.1. I have searched the forum for a solution and found one post but it did not answer my query. I also noted your post saying you are looking at P3D V2.1, so perhaps it's a P3D problem?! Anyway, the AI sounds are overwhelmingly loud and don't seem to respond to sound adjustment. I have turned the 'Environment' slider to zero but still the sound remains at the unbearable level. I have also found and tried use a small programme within the aircraft folder that adjusts the AI sound. It's set at 50% by default. I tried adjusting to 20% but it reverts to 50%. Good programme by the way, I'm a recent convert to MyTraffic and am pleased I made the change. Regards Dave
  4. Capt. & FO Control

    Pete, Thanks for replying. Dave
  5. Hello Pete, I have searched the forum but cannot see this topic has been brought up before, apologies if it has. I am wondering if it is possible to introduce axis assignments and calibration for captain and first officer, rather than the single assignments that exist currently. I am thinking about Ailerons, elevator, brakes and rudder. I feel certain you would have done this if it was possible but I thought I would ask. Thanks Dave
  6. rotary encoder input speed

    Pete, I am refering to this list: [JoyNames] AutoAssignLetters=Yes 0=BU0836X Interface 0.GUID={A0B7CCE0-90D8-11DF-8006-444553540000} 1=GoFlight GF-RC Rudder Control 1.GUID={A0B7A5D0-90D8-11DF-8004-444553540000} 2=SideWinder Precision 2 Joystick 2.GUID={D75A1460-97F9-11DF-8001-444553540000} 3=CH FLIGHT SIM YOKE USB 3.GUID={D93B5780-97F9-11DF-8002-444553540000} 4=GF-TQ6 Throttle System 4.GUID={DB39E6A0-97F9-11DF-8003-444553540000} A=GoFlight GF-RC Rudder Control A.GUID={A0B7A5D0-90D8-11DF-8004-444553540000} B=BU0836X Interface B.GUID={A0B7CCE0-90D8-11DF-8006-444553540000} C=CH PRO PEDALS USB C.GUID={339B9670-B83E-11DC-8001-444553540000} D=CH FLIGHT SIM YOKE USB D.GUID={D93B5780-97F9-11DF-8002-444553540000} E=GF-TQ6 Throttle System E.GUID={DB39E6A0-97F9-11DF-8003-444553540000} 5=CH PRO PEDALS USB 5.GUID={339B9670-B83E-11DC-8001-444553540000} F=SideWinder Precision 2 Joystick F.GUID={D75A1460-97F9-11DF-8001-444553540000} G=BU0836X Interface H=BU0836X Interface H.GUID={775ED880-B7F4-11DC-8001-444553540000} 6=BU0836X Interface 6.GUID={FC794690-E793-11E0-8001-444553540000} 7=BU0836X Interface 7.GUID={775ED880-B7F4-11DC-8001-444553540000} I did begin by numbering 0 and 1 but had the probolem described. I have three BU0836X cards but only two have encoders attached, those named in the above list as 'B' and 'H'. I did not realise thyis was a windows ID list. I assumed it was the list that identified the joysticks as seen in FSUIPC. I did use the HIDScanner here is the log : ********* HidScanner, Version 2.00 by Pete Dowson ********* Device at "\\?\hid#vid_045e&pid_0038#7&34e3140e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=045E, Product=0038 (Version 1.8) Manufacturer= Microsoft Product= SideWinder Precision 2 Joystick Serial Number= SideWinder Precision 2 Joystick Usage Page: 1 Input Report Byte Length: 7 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 2 Number of Input Button Caps: 1 Number of InputValue Caps: 5 Number of InputData Indices: 13 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Buttons range 1 -> 8 at indices 4 -> 11 Value Y at index 0, range 0 -> 255, using 8 bits Value X at index 1, range 0 -> 255, using 8 bits Value Sldr at index 2, range 0 -> 255, using 8 bits Value R/RZ at index 3, range 0 -> 255, using 8 bits Value POV at index 12, range 0 -> 7, using 4 bits ************************************************************************** Device at "\\?\hid#vid_05fe&pid_1011&mi_00#9&22543caa&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=05FE, Product=1011 (Version 3.0) Manufacturer= Device Product= USBice Serial Number= Device is a keyboard Usage Page: 1 Input Report Byte Length: 9 Output Report Byte Length: 2 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 2 Number of InputValue Caps: 0 Number of InputData Indices: 173 Number of Output Button Caps: 1 Number of Output Value Caps: 0 Number of Output Data Indices: 5 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 ************************************************************************** Device at "\\?\hid#vid_05fe&pid_1011&mi_01&col01#9&3a17c8ef&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=05FE, Product=1011 (Version 3.0) Manufacturer= Device Product= USB Device Serial Number= Device is a mouse Usage Page: 1 Input Report Byte Length: 6 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 2 Number of Input Button Caps: 1 Number of InputValue Caps: 4 Number of InputData Indices: 9 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Buttons range 1 -> 5 at indices 0 -> 4 Value Wh at index 5, range -127 -> 127, using 8 bits Value Y at index 6, range -127 -> 127, using 8 bits Value X at index 7, range -127 -> 127, using 8 bits Value Wh at index 8, range -127 -> 127, using 8 bits ************************************************************************** Device at "\\?\hid#vid_05fe&pid_1011&mi_01&col02#9&3a17c8ef&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=05FE, Product=1011 (Version 3.0) Manufacturer= Device Product= USB Device Serial Number= Usage Page: 1 Input Report Byte Length: 2 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 1 Number of InputValue Caps: 0 Number of InputData Indices: 3 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 ************************************************************************** Device at "\\?\hid#vid_05fe&pid_1011&mi_01&col03#9&3a17c8ef&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=05FE, Product=1011 (Version 3.0) Manufacturer= Device Product= USB Device Serial Number= Usage Page: C Input Report Byte Length: 4 Output Report Byte Length: 0 Feature Report Byte Length: 8 Number of Link Collection Nodes: 1 Number of Input Button Caps: 24 Number of InputValue Caps: 0 Number of InputData Indices: 24 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 1 Number of Feature Data Indices: 1 ************************************************************************** Device at "\\?\hid#vid_068e&pid_00f2#7&b0f9b87&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=068E, Product=00F2 (Version 0.0) Manufacturer= CH PRODUCTS Product= CH PRO PEDALS USB Serial Number= Usage Page: 1 Input Report Byte Length: 4 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 2 Number of Input Button Caps: 0 Number of InputValue Caps: 3 Number of InputData Indices: 3 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Value Z at index 0, range 0 -> 255, using 8 bits Value Y at index 1, range 0 -> 255, using 8 bits Value X at index 2, range 0 -> 255, using 8 bits ************************************************************************** Device at "\\?\hid#vid_068e&pid_00ff#8&765ce72&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=068E, Product=00FF (Version 0.0) Manufacturer= CH PRODUCTS Product= CH FLIGHT SIM YOKE USB Serial Number= Usage Page: 1 Input Report Byte Length: 8 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 2 Number of Input Button Caps: 1 Number of InputValue Caps: 6 Number of InputData Indices: 18 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Buttons range 1 -> 12 at indices 6 -> 17 Value V/RY at index 0, range 0 -> 255, using 8 bits Value U/RX at index 1, range 0 -> 255, using 8 bits Value Z at index 2, range 0 -> 255, using 8 bits Value Y at index 3, range 0 -> 255, using 8 bits Value X at index 4, range 0 -> 255, using 8 bits Value POV at index 5, range 1 -> 8, using 4 bits ************************************************************************** Device at "\\?\hid#vid_06c2&pid_004c#7&c8feb02&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=06C2, Product=004C (Version 1.0) Manufacturer= Phidgets Inc. Product= PhidgetLED Serial Number= 159572 Usage Page: FFA0 Input Report Byte Length: 42 Output Report Byte Length: 9 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 0 Number of InputValue Caps: 1 Number of InputData Indices: 1 Number of Output Button Caps: 0 Number of Output Value Caps: 1 Number of Output Data Indices: 1 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Value 0x02 at index 0, range 0 -> 1, using 8 bits ************************************************************************** Device at "\\?\hid#vid_09f3&pid_0100#8&3434ff53&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=09F3, Product=0100 (Version 1.1) Manufacturer= GoFlight Product= GoFlight GF-RC Rudder Control Serial Number= Usage Page: 1 Input Report Byte Length: 4 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 2 Number of Input Button Caps: 0 Number of InputValue Caps: 3 Number of InputData Indices: 3 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Value Z at index 0, range 0 -> 255, using 8 bits Value Y at index 1, range 0 -> 255, using 8 bits Value X at index 2, range 0 -> 255, using 8 bits ************************************************************************** Device at "\\?\hid#vid_09f3&pid_0200#6&3304c94e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=09F3, Product=0200 (Version 1.0) Manufacturer= GoFlight Product= GF-TQ6 Throttle System Serial Number= Usage Page: 1 Input Report Byte Length: 8 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 2 Number of Input Button Caps: 1 Number of InputValue Caps: 6 Number of InputData Indices: 10 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Buttons range 1 -> 4 at indices 6 -> 9 Value R/RZ at index 0, range 0 -> 255, using 8 bits Value V/RY at index 1, range 0 -> 255, using 8 bits Value U/RX at index 2, range 0 -> 255, using 8 bits Value Z at index 3, range 0 -> 255, using 8 bits Value Y at index 4, range 0 -> 255, using 8 bits Value X at index 5, range 0 -> 255, using 8 bits ************************************************************************** Device at "\\?\hid#vid_18ea&pid_0004#6&2d5ed5c4&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=18EA, Product=0004 (Version 1.0) Manufacturer= Product= Serial Number= Usage Page: FFA0 Input Report Byte Length: 65 Output Report Byte Length: 65 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 0 Number of InputValue Caps: 1 Number of InputData Indices: 1 Number of Output Button Caps: 0 Number of Output Value Caps: 1 Number of Output Data Indices: 1 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Value 0xA6 at index 0, range -128 -> 127, using 8 bits ************************************************************************** Device at "\\?\hid#vid_1dd2&pid_1001#6&3129063&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=1DD2, Product=1001 (Version 1.36) Manufacturer= Leo Bodnar Product= BU0836X Interface Serial Number= B20826 Usage Page: 1 Input Report Byte Length: 8 Output Report Byte Length: 0 Feature Report Byte Length: 18 Number of Link Collection Nodes: 3 Number of Input Button Caps: 1 Number of InputValue Caps: 2 Number of InputData Indices: 34 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 1 Number of Feature Data Indices: 1 Buttons range 1 -> 32 at indices 1 -> 32 Value X at index 0, range 0 -> 4095, using 16 bits Value POV at index 33, range 0 -> 7, using 4 bits ************************************************************************** Device at "\\?\hid#vid_1dd2&pid_1001#6&376360e3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=1DD2, Product=1001 (Version 1.36) Manufacturer= Leo Bodnar Product= BU0836X Interface Serial Number= B20825 Usage Page: 1 Input Report Byte Length: 12 Output Report Byte Length: 0 Feature Report Byte Length: 18 Number of Link Collection Nodes: 3 Number of Input Button Caps: 1 Number of InputValue Caps: 4 Number of InputData Indices: 36 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 1 Number of Feature Data Indices: 1 Buttons range 1 -> 32 at indices 3 -> 34 Value U/RX at index 0, range 0 -> 4095, using 16 bits Value Z at index 1, range 0 -> 4095, using 16 bits Value X at index 2, range 0 -> 4095, using 16 bits Value POV at index 35, range 0 -> 7, using 4 bits ************************************************************************** Device at "\\?\hid#vid_1dd2&pid_1001#7&1a6493e9&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=1DD2, Product=1001 (Version 1.35) Manufacturer= Leo Bodnar Product= BU0836X Interface Serial Number= B10154 Usage Page: 1 Input Report Byte Length: 6 Output Report Byte Length: 0 Feature Report Byte Length: 18 Number of Link Collection Nodes: 3 Number of Input Button Caps: 1 Number of InputValue Caps: 1 Number of InputData Indices: 33 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 1 Number of Feature Data Indices: 1 Buttons range 1 -> 32 at indices 0 -> 31 Value POV at index 32, range 0 -> 7, using 4 bits ************************************************************************** You say "I've a feeling that you are really outreaching your technical skills in these matters" You maybe correct, but then this whole hobby has been a steep learning curve, that's what makes it enjoyable. You also say "I'll try to help" for that I am very grateful. Rest assured I do not come for help unless I have tried every avenue I can think of. I'll get stuck into the "HidDemo.lua", but will read up on it's use first. Thanks Dave I
  7. rotary encoder input speed

    Hi Pete, I do have eight cards connected and showing in FSUIPC but they are not all BU0836X types, the first one is and the last two. So, you are saying I should number the BU0836X devices as if they are the only cards attached and not follow the numbering in FSUIPC? The normal button numbers are 26 and 27 showing in FSUIPC. I'll check connections but the joystick shows up as 'B' and the button numbers as 26 & 27, the ones that work show up as Joystick 'B' button numbers 28 & 29 and 30 & 31. (just tried numbering 0, 1 & 2 with same result) Thanks Dave
  8. rotary encoder input speed

    Hi Pete, I've tried not to come back with silly questions but I'm afraid I have failed! I have created two lua files, BU0836X_0.lua and BU0836X_1.lua each with the same content as the ipcready.lua file I used previously and placed them both in the modules folder of FSX. In FSUIPC.ini I have placed the entry: [Auto] 1=Lua BU0836X_0 2=Lua BU0836X_1 When FSX runs I can both Lua files listed in FSUIPC. I need two of the three BU0836X cards I have to operate the virtual joystick, these are Joytick B & H. These are also designated 0 and 7 in FSUIPC.ini. At the start of the lua files I have inserted 0 in one and 7 in the other as the device; thus: Vendor = "Leo Bodnar" Product = "BU0836X Interface" Device = 0 -- Multiple devices of the same name need increasing Device numbers and Vendor = "Leo Bodnar" Product = "BU0836X Interface" Device = 7 -- Multiple devices of the same name need increasing Device numbers I have the pairs listed within the curly brackets thus for dveice 0: Rotaries = {31,30,29,28,27,26} And thus for device 7 Rotaries = {31,30,29,28,27,26,25,24,23,22,21,20,19,18,17,16,15,14,13,12,11,10,9,8,7,6,5,4,3,2,1,0} I am sure these pairings are correct. In FSUPC Device 0 (joystick B) the pairs 30+31 and 28+29 are showing joystick 64 but pair 27+26 are not. None of the pairs for device 7 (joytick H) are showing the virtual joystick. I have tried using device 0 and device 1 with pretty much the same outcome. Any guidance as to where I am going wrong would be most welcome. Thanks in advance. Dave
  9. rotary encoder input speed

    Hi Pete, Thanks very much for your reply, much appreciated. I will setup Lua/FSUIPC as you describe and report back. Hope you had a good holiday. My regards Dave
  10. rotary encoder input speed

    Hi There, I have followed this thread with interest and have been able to get the 'Joystick 64' to work on one BU0836 card. The problem is I have three of these cards and need to add a second one to the Lua script arrangment. I copied the original Lua script and gave it a different name. ipcready1.lua and it appears in the FSUIPC drop down list. I have tried assigning increasing Device numbers starting from 1 and going up to 7, which is the total number identified using the HID programme. I have added the paired outputs within the curly brackets but no luck. Any advice on how I can get a second card to work would be very welcome. Thanks in advance. My regards Dave
  11. Hello Alan, I am thinking of purchasing Extreme Sounds 2009, but have a couple of questions. Is this the latest version of the programme? Does it offer shut down sounds? Does it offer reverser sounds? I have read up a bit on the programme and note it offers spool up sounds if onemanually installs them, which is not a problem. I do not use a proprietry programme for AI but install my own using mainly, but not exclusively, WOAI & AIG. Are there any issues to note regarding this? That's it I think. Thanks in advance for any advice offered. My regards Dave
×