Jump to content
The simFlight Network Forums

Sea2Sky

Members
  • Content Count

    13
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Sea2Sky

  • Rank
    Member

Profile Information

  • Gender
    Male
  • Location
    : BC, Canada
  • Interests
    Aviation, Astrophotography, Woodworking
  1. I've resolved my issue, and wanted to post the solution here in case anyone in the future is searching for a similar answer. The bit mask was on the bottom right corner 'Mask if Bit cmd'. In the past, I was using the bit flag values of 0-9, rather than the bit values of 1, 2, 4, 8, 16, 32, 64, 128, 256, and 512. If anyone has this issue, I hope that this can help. Much thanks to the FSUIPC team for dealing with me, and for clearing up any misunderstandings I had with the offset hex values.
  2. Thank you, I will start troubleshooting more with the FSUIPC logging facilities in the future. Yes, that was the case. I would hope that there is a way somewhere to configure this bit, and I will continue to troubleshoot the software in question. Thank you, this makes total sense. My original assumption was that FSUIPC hex offsets were based on an adjustable programmatic FSUIPC value changing the bytes in the initial offset, not an additional byte/parameter set. Understanding that it's an actual byte in memory definitely clears things up for me. Due to the options presented to me in my hardware's software, I was making an incorrect guess and changing the initial offset value. I required a deeper understanding of FSUIPC. I will sit down and start reviewing the Lua code better understand how it's designed to work. Clearly my understanding was misunderstood. I will also make some time to sit down and read through all the FSUIPC manuals I have in front of me, rather than skimming to what I'm after. Thank you all for your time. I feel more at ease being educated on the subject, and knowing where to look next.
  3. I am so frustrated and disappointed in myself that I can't comprehend what is being said. I understand in theory what you mean, but not in practice. Unfortunately, when I set a particular bit in a byte, the offset value changes for me, and all I can do is enter an offset value to set the function within my software. If you only knew how many times I've read, and re-read that article. 😞 Once again, when I change any bit, the offset value changes for me, and that is the only thing I can enter in my software is an offset value. There are other data types I can change as well other than Bytes, which include Integer, Unsigned Integer, Long, Double, and BCD Code. As mentioned, 0000 1101 0000 0010 = 502 was the second bit, and did not work within the default Cessna 172 aircraft supplied by FSX. This did work when assigning a yoke button directly in FSUIPC as 'Offset Work Togglebits' FS control, so the switch does appear to work for that aircraft using that method only. I appreciate all your advice, and thank you for your support, but it doesn't appear that I can get it working after spending full days attempting this. Thank you so much for trying, but I am at a loss of what to do anymore. I can sense that some of you are as frustrated with me, as I am with setting the bits. So I think it is best for me to walk away as this has caused aggravating stress for both me and you. My current assumption is that the issue lies in the software I'm using for my hardware which only uses offset values to define the functions. I will reach out to them and see if that is the case. I will continue to support and praise your project, and was looking to donate for all your time, but I no longer see the donation contribution page.
  4. Thanks Thomas, So to my understanding, offset 0D0C are 2 bytes, (2x 8 bits) which is: 0000 1101 0000 1100 = 0D0C I've been tying to figure out which bit to flip within which byte in the 0D0C offset. I'll limit my example to just the beacon light. Here's the attempt flipping bit 1, by flipping the bit in the second bit, which changes the offset value to 502. As expected this doesn't work as the offset value has changed in only the second byte. 0000 1101 0000 0010 = 502 Attempting to change the beacon bit to the first byte also doesn't work, as expected, since the offset value changes: 0000 0010 0000 1100 = 20C So let's clear all the bits, and try the following which also does not work as expected because the 0D0C offset no longer exists: 0000 0000 0000 0010 = 2 No need in even attempting this, since the offset would be 2, which does not make sense, and would not apply to other offset function values that have bit flags. So then I thought, what if we make it 4 bytes, keep the 0D0C 2 byte offset, and then added 2 bytes previous to the offset which would look like this: 0000 0000 0000 0010 0000 1101 0000 1100 = 20D0C This seemed promising at first since the offset 0D0C remained, with an additional bit added. And attempted flipping another bit to test landing lights: 0000 0000 0000 0100 0000 1101 0000 1100 = 40D0C This unfortunately did not work as well. So I guess my question is, which bit am I flipping, while still keeping the 0D0C offset value? I'm guessing there is a bit outside of the offset that needs to be flipped that I'm not aware of to retain the 0D0C offset? Otherwise, I would assume my question would have been answered with a unique offset value per individual light. Is there a missing bit flag field within my G-Step configuration software that I pasted in an earlier post? Am I on the right path of flipping bits, but just not in the right byte?
  5. I found this to be completely helpful when assigning the FS control function parameter to a button on my yoke. Testing it allowed me to toggle each switch accordingly, and gives me much hope in finding a solution! I need to figure out if converting it to a new hex offset value is the right or wrong path. I'm using an IO board from Flight Illusion which has its own function configuration that maps to my switches, and I've been trying to figure out the offset conversions for each individual light. I've been trying to convert binary to hex by changing the bit values to calculate the offset value. My original assumption was that 0D0C was the main offset, and I had to replace the bits at the end, which was incorrect. To give you an example of what I'm working with, here is the NAV light function which is set to 0D0C. I've also noticed an offset of 280 which also appears to be used as NAV (NAV, Taxi, and Wing lights), but am currently using 0D0C, which converts to binary 1101 0000 1100: There is also an offset of 28C (binary: 0010 1000 1100) which also activates the Landing lights switch: So using the Nav and Landing lights function, I am seeing the following binary: Nav (280): 0010 1000 0000 Landing (28C): 0010 1000 1100 But don't understand how those are related to the binary offset of 0D0C (they might be completely unrelated): Nav (0D0C): 1101 0000 1100 I want to understand very badly what you two are saying, but maybe I'm approaching this completely wrong. I appear to be missing something in regards to converting the binary from the 0D0C offset value. Are there any other fields within the offsets function field that need to be updated shown above other than the offset field, or am I on the right track on assuming that the offset value is recalculated by changing bit values within the converted 0D0C hex to binary string? Unfortunately, the only working offset examples I have for the lights are 280, 28C, and 0D0C as listed in the offset guide. I'm starting to think that it's not the offset value that I need to change within the IO board software, but something else? Once again, apologies if there's any frustration on your part from something that I might be missing here. I'm trying really hard to understand what it is that I'm doing wrong as far as the offset hex conversion (if that's even the case). I might be trying to apply the offsets for beacon, taxi, strobe that might not even exist based on incorrect binary conversion? Or maybe the offset field is to remain as 0D0C, and there is another bit/flag elsewhere that needs to be added? I promise you, there is a dram of really fine scotch waiting for you in Canada if you can help me solve this. 🙂
  6. I think you are correct and hit the nail on the head. In the end, I did remove all device button mapping for each device within P3D. But yesterday, I may have missed vJoy device in P3D. As of last night, all assignments were cleared up in P3D, and FSUIPC did use the correct device ID 1. Since everything is working now, I will walk away from this with hopes of it not reoccurring. Thank you for your help throughout my post ramblings. :-)
  7. I guess my struggle is this: vJoy device 0 *is* device CLSE NG 1, and vice versa. The yoke can use both devices for button mapping in FSUIPC. When the yoke buttons work correctly, FSUIPC identifies the yoke buttons as device 1. When it does, all buttons are mapped to device 1, and the hat switch works accordingly. The buttons will use P1:0, P1:1, P1:2. When FSUIPC includes vJoy device 0 as part of the yoke button configuration, then I get a mishmash of yoke buttons using both joystick devices, and certain hat switch directions become device 0. Example: when FSUIPC loads the yoke buttons properly, only CLSE NG device 1 is used for all yoke button mappings, including the hat switch. But sometimes on load, FSUIPC uses both device IDs for button mapping, and then P0:5, P0:6, P0:7 overrides P1:0, P1:1, P1:2. I'm trying my best to identify the situation I'm seeing in FSUIPC, it would have been better to create a video to explain what I'm speaking about if the above doesn't make sense, which I would be willing to do if necessary. Next time this issue persists, I will try changing to Joy Letters to see if that resolves the issues. Thank you for your patience Pete, as this is a bit of an odd issue, and I don't think is normal. All USB inputs are set in a USB extender, and are never removed.
  8. It was more related to the annunciator panel hardware that I'm trying to configure. It has warning indicator lights for L/R VAC, and I was trying to find the offset values for this in particular. Regarding the Avionics Bus1 and Bus2 switch, once again, this is hardware specific to my simulator. If there are no offsets for these, please let me know and I will move on and will ignore some of hardware limitations. Regarding the instrument light bits, I'm very well aware of what a bit is, but might not understand how they are used as flags if the following bits aren't working for individual Beacon, Landing, Taxi, and Strobe lights. Let's convert my hex example to binary to discuss what I mean: 0D0C: Nav = 1101 0000 1100 ***WORKING*** (reducing to 12 bit for simplicity, otherwise 0000 1101 0000 1100) 0D0D: Beacon = 1101 0000 1101 0D0E: Landing = 1101 0000 1110 0D0F: Taxi Lights = 1101 0000 1111 0D10: Strobe =1101 0001 0000 0D11: Instrument = 1101 0001 0001 ***WORKING*** I've flipped each bit, and Nav and Instrument light switch works according to the bits set above. According to the Offsets Guide, the bits go from 0 (Nav) to 9 (Cabin), in which in this case, I'm trying to make use of bits 0-5. If I've misunderstood flipping each bit in the offset between Nav and Instrument bits, please help me understand. Since Instrument lights do work with 0D0C + 5 bits = 0D11, and 0D0C = 0 bit switch, then why wouldn't 0D0C + 1 = 0D0D? If Beacon is not 0D0D, could you please give me a freebie on what the Beacon light offset is, so I can get a better grasp on what you're talking about.
  9. I've tried to uninstall/reinstall my hardware control devices but kept running into joystick conflict issues. I replaced a lot of my Saitek controls with more professional simulation hardware, and after going over the controllers in the registry, and old driver removal, I eventually gave up. I did a fresh reinstall of Windows 10, P3D, hardware controls/drivers, scenery packages, and FSUIPC. I've cleared out all controls within P3D, and am exclusively using FSUIPC. I just finished setting up my hardware in FSUIPC, and everything is looking good (except the individual light switches, as mentioned in a separate post). One issue that I've noticed which seems to be random is in regards to my Brunner CLSE NG yoke. It has it's own software and support, but does require vJoy to also be installed. Sometimes FSUIPC recognizes half my buttons on the yoke to be from the vJoy device ID, and other times, it's recognized as the CLSE NG Yoke device ID. Is there any known conflicts with vJoy and CLSE NG devices, and how can I keep the buttons consistent to the appropriate ID. The best case working scenario for me is when all the yoke buttons are identified in FSUIPC as the CLSE NG device ID. I've attached a copy of my FSUIPC.JoyScan.csv file for reference: Good?, flags, VID, PID, Name, INIid, REGid, RegEntry, INIguid, REGguid, HIDguid, ValsOK?, ReadsOk? ,,, HIDscanning completed N, x00, x241D, xFE4E, , -1, -1, 0, {NULL}, {NULL}, {52571BC0-6B69-11EA-8005-444553540000}, Y, N N, x00, x1234, xBEAD, , -1, -1, 0, {NULL}, {NULL}, {0FB96D90-6B69-11EA-8002-444553540000}, Y, N N, x00, x1DD2, x1020, , -1, -1, 0, {NULL}, {NULL}, {DEC169D0-6B73-11EA-8002-444553540000}, Y, N N, x00, x25BB, x008B, , -1, -1, 0, {NULL}, {NULL}, {52560A50-6B69-11EA-8003-444553540000}, Y, N ,,, REGscanning completed N, x00, x241D, xFE4E, JAY Rudder, -1, 2, 0, {NULL}, {52571BC0-6B69-11EA-8005-444553540000}, {52571BC0-6B69-11EA-8005-444553540000}, Y, Y N, x00, x1234, xBEAD, vJoy Device, -1, 0, 0, {NULL}, {0FB96D90-6B69-11EA-8002-444553540000}, {0FB96D90-6B69-11EA-8002-444553540000}, Y, Y N, x00, x1DD2, x1020, GarSim 530, -1, 3, 0, {NULL}, {DEC169D0-6B73-11EA-8002-444553540000}, {DEC169D0-6B73-11EA-8002-444553540000}, Y, N N, x00, x25BB, x008B, CLSE NG Yoke, -1, 1, 0, {NULL}, {52560A50-6B69-11EA-8003-444553540000}, {52560A50-6B69-11EA-8003-444553540000}, Y, Y N, x00, x25BB, x008B, CLSE NG Yoke, -1, -1, 1, {NULL}, {52565870-6B69-11EA-8004-444553540000}, {NULL}, N, N ,,, User settings imported N, x00, x241D, xFE4E, JAY Rudder, 2, 2, 0, {52571BC0-6B69-11EA-8005-444553540000}, {52571BC0-6B69-11EA-8005-444553540000}, {52571BC0-6B69-11EA-8005-444553540000}, Y, Y N, x00, x1234, xBEAD, vJoy Device, 0, 0, 0, {0FB96D90-6B69-11EA-8002-444553540000}, {0FB96D90-6B69-11EA-8002-444553540000}, {0FB96D90-6B69-11EA-8002-444553540000}, Y, Y N, x00, x1DD2, x1020, GarSim 530, 3, 3, 0, {DEC169D0-6B73-11EA-8002-444553540000}, {DEC169D0-6B73-11EA-8002-444553540000}, {DEC169D0-6B73-11EA-8002-444553540000}, Y, N N, x00, x25BB, x008B, CLSE NG Yoke, 1, 1, 0, {52560A50-6B69-11EA-8003-444553540000}, {52560A50-6B69-11EA-8003-444553540000}, {52560A50-6B69-11EA-8003-444553540000}, Y, Y N, x00, x25BB, x008B, CLSE NG Yoke, -1, -1, 1, {NULL}, {52565870-6B69-11EA-8004-444553540000}, {NULL}, N, N ,,, Values matched and decided Y, x1E, x241D, xFE4E, JAY Rudder, 2, 2, 0, {52571BC0-6B69-11EA-8005-444553540000}, {52571BC0-6B69-11EA-8005-444553540000}, {52571BC0-6B69-11EA-8005-444553540000}, Y, Y Y, x1E, x1234, xBEAD, vJoy Device, 0, 0, 0, {0FB96D90-6B69-11EA-8002-444553540000}, {0FB96D90-6B69-11EA-8002-444553540000}, {0FB96D90-6B69-11EA-8002-444553540000}, Y, Y (Y), x16, x1DD2, x1020, GarSim 530, 3, 3, 0, {DEC169D0-6B73-11EA-8002-444553540000}, {DEC169D0-6B73-11EA-8002-444553540000}, {DEC169D0-6B73-11EA-8002-444553540000}, Y, N Y, x1E, x25BB, x008B, CLSE NG Yoke, 1, 1, 0, {52560A50-6B69-11EA-8003-444553540000}, {52560A50-6B69-11EA-8003-444553540000}, {52560A50-6B69-11EA-8003-444553540000}, Y, Y N, x11, x25BB, x008B, CLSE NG Yoke, -1, -1, 1, {NULL}, {52565870-6B69-11EA-8004-444553540000}, {NULL}, N, N Here are the JoyNames, Axes and Buttons to reference how vJoy has configured some of the yoke buttons in the past. As you can see under buttons, 1-3 used the vJoy device in FSUIPC, but when FSUIPC loaded the CLSE NG buttons correctly, it would use 6-8, which are the same buttons as vJoy 1-3 (2, 3 were set differently for testing). I've also added JoystickCalibration just to reference the Axes brake configuration, which is working fine. [JoyNames] AutoAssignLetters=No 0=vJoy Device 0.GUID={0FB96D90-6B69-11EA-8002-444553540000} 1=CLSE NG Yoke 1.GUID={52560A50-6B69-11EA-8003-444553540000} 2=JAY Rudder 2.GUID={52571BC0-6B69-11EA-8005-444553540000} 3=GarSim 530 3.GUID={DEC169D0-6B73-11EA-8002-444553540000} [JoystickCalibration] RudderBlendLowest=1 AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=66731 RudderTrimControl=66732 CowlFlaps1Control=66162 CowlFlaps2Control=66163 CowlFlaps3Control=66164 CowlFlaps4Control=66165 SteeringTillerControl=0 MaxSteerSpeed=60 LeftBrake=14500,16380 RightBrake=14348,16380/16 [Axes] PollInterval=10 RangeRepeatRate=10 0=1P,0,F,66416,0,0,0 -{ TO SIM: PAN_VIEW }- 1=2X,256,D,7,0,0,0 -{ DIRECT: LeftBrake }- 2=2Y,256,D,8,0,0,0 -{ DIRECT: RightBrake }- [Buttons] PollInterval=25 ButtonRepeat=20,10 1=P0,5,C65561,0 -{PAUSE_TOGGLE}- 2=P0,6,C67036,0 -{CINEMATOGRAPHER_TOGGLE}- 3=P0,7,C65567,0 -{VIEW_MODE}- 4=P1,4,C65906,0 -{PANEL_1}- 5=P1,3,C66482,0 -{TOGGLE_WATER_RUDDER}- 6=P1,0,C65561,0 -{PAUSE_TOGGLE}- 7=P1,1,C66653,0 -{VIEW_COCKPIT_FORWARD}- 8=P1,2,C66654,0 -{VIEW_VIRTUAL_COCKPIT_FORWARD}- I'm wondering what determines the button mapping to P0, or P1? Would this be fixable to remain consistent with P1 only instead of FSUIPC switching between P0 and P1 randomly? Or is this something more related to the yoke manufacturer as they are using two joystick devices to operate the same buttons?
  10. I did print out the FSUIPC5 Offsets Status a while back and refer to that guide frequently. I can't believe I missed the FSUIPC5 History guide. Thanks for pointing that out. I was unable to find the specific offsets for Avionics Bus 2, and the Vacuum L/R warning indicators. Do they exist? Regarding the individual light switches, these are the offsets I currently have configured. The offsets are increased by 1 bit, but are not functioning (other than Nav at 0D0C). Hex Val: Name (Int) - bit 0D0C: Nav (3340) - 0 0D0D: Beacon (3341) - 1 0D0E: Landing (3342) - 2 0D0F: Taxi Lights (3343) - 3 0D10: Strobe (3344) - 4 0D11: Instruments (3345) - 5 I apologize if there's something I'm missing here, but I assume the additional offset bit is added to 0D0C as shown above? I've tried searching the internet, but unfortunately to no avail. ***UPDATE*** Interesting enough, 0D11 did work for my instrument lights, but 0D0D - 0D10 do not engage the switches on the panel, or the exterior lights themselves.
  11. I've been looking for advice on some FSUIPC5 offset codes that I've been having issues with. Has anyone had any luck programming the following offsets in P3Dv4? - Avionics Bus 1 - Avionics Bus 2 - Vac Left Warning - Vac Right Warning The individual light offsets listed below for the Cessna 172 does not seem to work, is this a limitation with the aircraft, or the simulator? - Beacon - Landing - Taxi - Nav - Strobe ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ I also had a couple secondary related questions as well: ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ I noticed that FSUIPC5.154 was just released this month. Is there a changelog available between 5.152 and 5.154 for P3Dv4? ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Is there a raw fsuipc5 offset list available? I have printed out the fsuipc5 offset status guide, and currently browse through it, but my current raw offset list for my hardware's software uses an older fsuipc4 raw offset list. I would like to update the list to v5. This is a csv based file in text format that looks like this: &h0000, 0,"Not USED","","","","" &H0020, 4, "Pos/Attitude", "Ground elevation", "#*3.28084/256" , "Read Only" , "in metres * 256, See also 0B4C" &H0024, 4, "Misc", "Startup situation/flight", "#" , "Read Only" , "Path from FS folder is included. The string continues through more than the four bytes shown here." &H012C, 1, "Simulator", "Log Book name [FS2002+]", "#" , "Unknown" , "Zero terminated ASCII string, but just 'logbook' by default." &H0238, 1, "Environment", "Clock Hour", "#" , "Read/Write" , "0-23" &H0239, 1, "Environment", "Clock Min", "#" , "Unknown" , "0-59" &H023A, 1, "Environment", "Clock Sec", "#" , "Unknown" , "0-59" &H023B, 1, "Environment", "Zulu Hour", "#" , "Read/Write" , "0-23" &H023C, 1, "Environment", "Zulu Min", "#" , "Read/Write" , "0-59" &H023E, 2, "Environment", "Day of Year", "#" , "Read/Write" , "Counts from 1, not 0" &H0240, 2, "Pos/Attitude", "Year", "#" , "Read/Write" , "" &H0246, 2, "Environment", "Time Zone offset to Zulu (minutes)", "#/60" , "Read/Write" , "Determines local time from Zulu and aircraft position (+ve=behind Zulu, -ve=ahead)" &H0248, 2, "Unknown", "Season", "#" , "Read/Write" , "0=winter, 1=spring, 2=summer, 3=fall" &H0262, 2, "Misc", "Pause control", "#" , "Write Only" , "Write 1 to pause, 0 to unpause" &H0264, 2, "Simulator", "Pause flag", "#" , "Read Only" , "0=Running, 1=Paused" &H0274, 2, "Misc", "Frame Rate", "32768/#" , "Read Only" , "" &H0278, 2, "Controls", "Auto-rudder", "#" , "Read/Write" , "1=on, 0=off. Also known as auto-coordination. Changing this works but doesn't affect Menu setting." &H0280, 1, "Cockpit", "Nav Lights", "#" , "Unknown" , "Operates NAV, Taxi, Panel and Wing light (but only reflects NAV settings). See $0D0C for more control" &H0281, 1, "Cockpit", "Strobe/Beacon Lights", "#" , "Read/Write" , "Operates Strobe and Beacon Lights. See $0D0C for more control" &H028C, 2, "Cockpit", "Landing Lights", "#" , "Read/Write" , "Operates Landing Lights. See $0D0C" &H029C, 2, "Cockpit", "Pitot heat", "#" , "Read/Write" , "0=Off, 1=On" &H02A0, 2, "Pos/Attitude", "MagVar", "#*360/65536" , "Read Only" , "-ve is West, +ve East. Convert Mag to True by subtracting this, True to Mag by adding it." &H02B2, 2, "Simulator", "Zoom factor (FS2002+)", "#/64" , "Read Only" , "64=x1, 128=x2 et cetera. Read only, FS2002 only" &H02B4, 4, "Pos/Attitude", "Ground Speed", "#*3600/65536/1852" , "Read Only" , "Metres/sec * 65536. Not valid in Slew mode!" &H02B8, 4, "Pos/Attitude", "True Air Speed", "#/128" , "Unknown" , "Knots * 128" &H02BC, 4, "Pos/Attitude", "Indicated Air Speed", "#/128" , "Unknown" , "Knots * 128" &H02C4, 4, "Pos/Attitude", "Barber pole airspeed", "#/128" , "Read Only" , "Knots * 128" &H02C8, 4, "Pos/Attitude", "Vertical speed", "#*60*3.28084/256" , "Unknown" , "VSI / 256 = VS per sec (in meters)" &H02CC, 8, "Pos/Attitude", "Whiskey Compass", "#" , "Read Only" , "Degrees" &H02D4, 2, "Radios/Navigation", "ADF2 freq (FS2004)", "#" , "Read/Write" , "Main 3 digits in BCD" &H02D6, 2, "Radios/Navigation", "ADF2 Extended Freq (FS2004)", "#" , "Read/Write" , "BCD, high byte=1000's digit, low byte=fraction digit" &H02D8, 2, "Radios/Navigation", "ADF2 Rel Bearing (FS2004)", "#*360/65536" , "Read Only" , "" &H02DC, 4, "Radios/Navigation", "NDB2 identity (FS2004)", "#" , "Read Only" , "six byte character string including zero terminator" &H02E2, 4, "Radios/Navigation", "NDB2 name (FS2004)", "#" , "Read Only" , "25 byte character string including zero terminator" &H02FB, 1, "Radios/Navigation", "ADF2 ident sound switch (FS2004)", "#" , "Read/Write" , "1=enabled, 0=disabled" Ideally, I would like to not type out the entire fsuipc5 list in a text/csv file if there is one already out there. Thank you for your support and product.
  12. Thanks John for clarifying. I have all my hardware that I need installed and finalized, so I will remove all the software installations for my hardware, and install one by one and examine the generated logs to see if that resolves the issues.
  13. I'm troubleshooting an issue I've been having with some conflicts/issues between FSUIPC v5 and P3D v4. Initially, I had it configured appropriately so that all my flight sim hardware was working between FSUIPC5, and P3D. During my Flight Sim build, there were some newly added hardware, and USB re-connections to a newly installed 7 port powered USB hub attached next to my flight dash. I'm also a registered user of FSUIPC v5. The old working version looked like this: [JoyNames] AutoAssignLetters=No 1=TRC 32DIGITAL IN 15 1.GUID={62C61340-2D60-11EA-8001-444553540000} 2=JAY Rudder 2.GUID={A7B66F40-1B31-11EA-8001-444553540000} 3=GarSim 530 3.GUID={836103C0-2276-11EA-8001-444553540000} 0=Pro Flight Cessna Yoke 0.GUID={51842490-A618-11E7-8003-444553540000} My current FSUIPC5.ini configuration under [JoyNames] look like this (auto detected, updated changes): [JoyNames] AutoAssignLetters=No 1=vJoy Device 1.GUID={DA0C7E80-36D4-11EA-8004-444553540000} 3=GarSim 530 3.GUID={713A11F0-36D0-11EA-8001-444553540000} A=<< MISSING JOYSTICK >> << MISSING JOYSTICK >> 2=JAY Rudder 2.GUID={A7B66F40-1B31-11EA-8001-444553540000} Note: There is a missing joystick listed under 'A', and no device 0 listed in the new JoyNames config. I've since updated my Saitek Cessna Yoke to a Brunner NG yoke, so that has changed. I've also removed the TRC 32DIGITAL IN 15 switch panel with the Flight Illusion GSA-055 central interface, which should be the vJoy Device. However, I'm not seeing CLSE NG Yoke listed under JoyNames (but is listed in Windows USB Game Controllers). The yoke is working in P3D, so my assumption is that the Brunner software is handling the yoke axis hardware completely. I've manually wiped the [Buttons] configuration in FSUIPC5.ini, then configured 5 buttons on the Brunner yoke in FSUIPC under P3D addons to confirm the device ID's being used by the yoke: [Buttons] PollInterval=25 ButtonRepeat=20,10 1=P1,5,C65561,0 -{PAUSE_TOGGLE}- 2=P1,6,C65606,0 -{VIEW}- 3=P1,7,C65567,0 -{VIEW_MODE}- 4=P3,4,C66653,0 -{VIEW_COCKPIT_FORWARD}- 5=P3,3,C67036,0 -{CINEMATOGRAPHER_TOGGLE}- The yoke is using two separate devices, P1, and P3, but no input from the GNS 530 GPS as the buttons are not recognized under FSUIPC5 buttons and switches tab, but P3 is picked up by the Yoke device. The old FSUIPC buttons configuration had the following extra buttons mapped when it did work with the GNS 530 hardware: 7=P3,12,K81,40 -{Key press: alt+Q}- 8=P3,0,K83,40 -{Key press: alt+S}- 9=P3,1,K83,40 -{Key press: alt+S}- 10=P3,13,K87,40 -{Key press: alt+W}- 11=P3,2,K89,40 -{Key press: alt+Y}- 12=P3,3,K90,40 -{Key press: alt+Z}- 13=P3,7,K75,40 -{Key press: alt+K}- 14=P3,6,K74,40 -{Key press: alt+J}- 15=P3,5,K118,40 -{Key press: alt+F7}- 16=P3,4,K117,40 -{Key press: alt+F6}- 17=P3,14,K78,40 -{Key press: alt+N}- 18=P3,16,K120,40 -{Key press: alt+F9}- 19=P3,17,K86,40 -{Key press: alt+V}- 20=P3,18,K124,40 -{Key press: alt+F13}- 21=P3,19,K65,40 -{Key press: alt+A}- 22=P3,20,K67,40 -{Key press: alt+C}- 23=P3,21,K113,40 -{Key press: alt+F2}- 24=P3,10,K119,40 -{Key press: alt+F8}- 25=P3,11,K79,40 -{Key press: alt+O}- 26=P3,8,K123,40 -{Key press: alt+F12}- 27=P3,9,K121,40 -{Key press: alt+F10}- 28=P3,15,K122,40 -{Key press: alt+F11}- 29=R3,27,K72,40 -{Key press: alt+H}- 30=R3,26,K73,40 -{Key press: alt+I}- 31=P3,25,K114,40 -{Key press: alt+F3}- 32=P3,24,K115,40 -{Key press: alt+F4}- 33=R3,23,K116,40 -{Key press: alt+F5}- 34=P3,22,K50,25 -{Key press: alt+shft+2}- 35=P3,29,K126,40 -{Key press: alt+F15}- Onto my current issue; the Emuteq Garmin 530 GPS hardware now has no buttons mapped or being recognized by FSUIPC buttons and switches input. My Yoke uses a combination of both device 1, and 3 under FSUIPC buttons and switches tab; but the FSUIPC should be using the Garmin 530 as device ID 3. When I activate any knob or button on the Emuteq GNS 530 GPS device, no button commands are being sent to the FSUIPC button and switches tab. The GNS 530 config is mapped to use the appropriate shortcut keys, but not being received anymore by FSUIPC. I'm not sure if this is related to the issue, but the P3D's calibration menu device ID do not match the FSUIPC device ID. 0 Mouse Yoke 1 Mouse Look 0 vJoy - Virtual Joystick 1 GarSim 530 2 Jay Rudder 3 CLSE NG Yoke I'm also attaching the FSUIPC5.JoyScan.csv output for reference as it appears that the yoke and GPS are using conflicting device IDs: Good?, flags, VID, PID, Name, INIid, REGid, RegEntry, INIguid, REGguid, HIDguid, ValsOK?, ReadsOk? ,,, HIDscanning completed N, x00, x241D, xFE4E, , -1, -1, 0, {NULL}, {NULL}, {A7B66F40-1B31-11EA-8001-444553540000}, Y, N N, x00, x1234, xBEAD, , -1, -1, 0, {NULL}, {NULL}, {DA0C7E80-36D4-11EA-8004-444553540000}, Y, N N, x00, x25BB, x008B, , -1, -1, 0, {NULL}, {NULL}, {713A6010-36D0-11EA-8002-444553540000}, N, N N, x00, x25BB, x008B, , -1, -1, 0, {NULL}, {NULL}, {713A11F0-36D0-11EA-8001-444553540000}, Y, N N, x00, x1DD2, x1020, , -1, -1, 0, {NULL}, {NULL}, {A7B66F40-1B31-11EA-8001-444553540000}, Y, N ,,, REGscanning completed N, x00, x241D, xFE4E, JAY Rudder, -1, 2, 0, {NULL}, {A7B66F40-1B31-11EA-8001-444553540000}, {A7B66F40-1B31-11EA-8001-444553540000}, Y, Y N, x00, x1234, xBEAD, vJoy Device, -1, 1, 0, {NULL}, {DA0C7E80-36D4-11EA-8004-444553540000}, {DA0C7E80-36D4-11EA-8004-444553540000}, Y, Y N, x00, x25BB, x008B, CLSE NG Yoke, -1, 0, 1, {NULL}, {713A6010-36D0-11EA-8002-444553540000}, {713A6010-36D0-11EA-8002-444553540000}, N, N N, x00, x25BB, x008B, CLSE NG Yoke, -1, 3, 0, {NULL}, {713A11F0-36D0-11EA-8001-444553540000}, {713A11F0-36D0-11EA-8001-444553540000}, Y, Y N, x00, x25BB, x008B, CLSE NG Yoke, -1, 0, 0, {NULL}, {836103C0-2276-11EA-8001-444553540000}, {NULL}, N, N N, x00, x25BB, x008B, CLSE NG Yoke, -1, -1, 2, {NULL}, {DB75AB70-36D4-11EA-8010-444553540000}, {NULL}, N, N N, x00, x25BB, x008B, CLSE NG Yoke, -1, -1, 3, {NULL}, {DB73AFA0-36D4-11EA-800C-444553540000}, {NULL}, N, N N, x00, x1DD2, x1020, GarSim 530, -1, 3, 0, {NULL}, {713A11F0-36D0-11EA-8001-444553540000}, {713A11F0-36D0-11EA-8001-444553540000}, Y, Y N, x00, x1DD2, x1020, GarSim 530, -1, 0, 0, {NULL}, {836103C0-2276-11EA-8001-444553540000}, {NULL}, N, N ,,, User settings imported N, x00, x241D, xFE4E, JAY Rudder, 2, 2, 0, {A7B66F40-1B31-11EA-8001-444553540000}, {A7B66F40-1B31-11EA-8001-444553540000}, {A7B66F40-1B31-11EA-8001-444553540000}, Y, Y N, x00, x1234, xBEAD, vJoy Device, 1, 1, 0, {DA0C7E80-36D4-11EA-8004-444553540000}, {DA0C7E80-36D4-11EA-8004-444553540000}, {DA0C7E80-36D4-11EA-8004-444553540000}, Y, Y N, x00, x25BB, x008B, CLSE NG Yoke, -1, 0, 1, {NULL}, {713A6010-36D0-11EA-8002-444553540000}, {713A6010-36D0-11EA-8002-444553540000}, N, N N, x00, x25BB, x008B, CLSE NG Yoke, 3, 3, 0, {713A11F0-36D0-11EA-8001-444553540000}, {713A11F0-36D0-11EA-8001-444553540000}, {713A11F0-36D0-11EA-8001-444553540000}, Y, Y N, x00, x25BB, x008B, CLSE NG Yoke, -1, 0, 0, {NULL}, {836103C0-2276-11EA-8001-444553540000}, {NULL}, N, N N, x00, x25BB, x008B, CLSE NG Yoke, -1, -1, 2, {NULL}, {DB75AB70-36D4-11EA-8010-444553540000}, {NULL}, N, N N, x00, x25BB, x008B, CLSE NG Yoke, -1, -1, 3, {NULL}, {DB73AFA0-36D4-11EA-800C-444553540000}, {NULL}, N, N N, x00, x1DD2, x1020, GarSim 530, 3, 3, 0, {713A11F0-36D0-11EA-8001-444553540000}, {713A11F0-36D0-11EA-8001-444553540000}, {713A11F0-36D0-11EA-8001-444553540000}, Y, Y N, x00, x1DD2, x1020, GarSim 530, -1, 0, 0, {NULL}, {836103C0-2276-11EA-8001-444553540000}, {NULL}, N, N ,,, Values matched and decided Y, x1E, x241D, xFE4E, JAY Rudder, 2, 2, 0, {A7B66F40-1B31-11EA-8001-444553540000}, {A7B66F40-1B31-11EA-8001-444553540000}, {A7B66F40-1B31-11EA-8001-444553540000}, Y, Y Y, x1E, x1234, xBEAD, vJoy Device, 1, 1, 0, {DA0C7E80-36D4-11EA-8004-444553540000}, {DA0C7E80-36D4-11EA-8004-444553540000}, {DA0C7E80-36D4-11EA-8004-444553540000}, Y, Y N, x12, x25BB, x008B, CLSE NG Yoke, -1, 0, 1, {NULL}, {713A6010-36D0-11EA-8002-444553540000}, {713A6010-36D0-11EA-8002-444553540000}, N, N Y, x1E, x25BB, x008B, CLSE NG Yoke, 3, 3, 0, {713A11F0-36D0-11EA-8001-444553540000}, {713A11F0-36D0-11EA-8001-444553540000}, {713A11F0-36D0-11EA-8001-444553540000}, Y, Y N, x11, x25BB, x008B, CLSE NG Yoke, -1, 0, 0, {NULL}, {836103C0-2276-11EA-8001-444553540000}, {NULL}, N, N N, x01, x25BB, x008B, CLSE NG Yoke, -1, -1, 2, {NULL}, {DB75AB70-36D4-11EA-8010-444553540000}, {NULL}, N, N N, x01, x25BB, x008B, CLSE NG Yoke, -1, -1, 3, {NULL}, {DB73AFA0-36D4-11EA-800C-444553540000}, {NULL}, N, N Y, x1E, x1DD2, x1020, GarSim 530, 3, 3, 0, {713A11F0-36D0-11EA-8001-444553540000}, {713A11F0-36D0-11EA-8001-444553540000}, {713A11F0-36D0-11EA-8001-444553540000}, Y, Y N, x11, x1DD2, x1020, GarSim 530, -1, 0, 0, {NULL}, {836103C0-2276-11EA-8001-444553540000}, {NULL}, N, N I see a conflict between the two device: Y, x1E, x25BB, x008B, CLSE NG Yoke, 3, 3, 0, {713A11F0-36D0-11EA-8001-444553540000}, {713A11F0-36D0-11EA-8001-444553540000}, {713A11F0-36D0-11EA-8001-444553540000}, Y, Y Y, x1E, x1DD2, x1020, GarSim 530, 3, 3, 0, {713A11F0-36D0-11EA-8001-444553540000}, {713A11F0-36D0-11EA-8001-444553540000}, {713A11F0-36D0-11EA-8001-444553540000}, Y, Y Adding logging details as well for registry conflict reference: 94 ---------------------- Joystick Device Scan ----------------------- 94 Product= JAY Rudder 94 Vendor=241D, Product=FE4E (Version 0.1) 110 GUIDs returned for product: VID_241D&PID_FE4E: 110 GUID= {A7B66F40-1B31-11EA-8001-444553540000} 110 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X1023,Y1023,Z1023 110 Product= vJoy - Virtual Joystick 110 Manufacturer= Shaul Eizikovich 110 Serial Number= 2.1.9 110 Vendor=1234, Product=BEAD (Version 2.25) 110 GUIDs returned for product: VID_1234&PID_BEAD: 110 GUID= {DA0C7E80-36D4-11EA-8004-444553540000} 110 Details: Btns=128, POVs=(0, 18000, 27000, 9000), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767 110 Product= CLSE NG Yoke 110 Manufacturer= Brunner Elektronik AG 110 Serial Number= XXX 110 Vendor=25BB, Product=008B (Version 1.0) 110 GUIDs returned for product: VID_25BB&PID_008B: 110 GUID= {713A6010-36D0-11EA-8002-444553540000} 110 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0 110 GUID= {713A11F0-36D0-11EA-8001-444553540000} 110 Details: Btns=6, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X65535,Y65535,Z0 110 Product= GarSim 530 110 Manufacturer= www.emuteq.com 110 Serial Number= xxx 110 Vendor=1DD2, Product=1020 (Version 1.3) 125 ------------------------------------------------------------------- 156 WARNING: Joystick ID 0 is duplicated in Registry 172 Device acquired for use: 172 Joystick ID = 2 (Registry okay) 172 2=JAY Rudder 172 2.GUID={A7B66F40-1B31-11EA-8001-444553540000} 172 Device acquired for use: 172 Joystick ID = 1 (Registry okay) 172 1=vJoy Device 172 1.GUID={DA0C7E80-36D4-11EA-8004-444553540000} 172 Device acquired for use: 172 Joystick ID = 3 (Registry okay) 172 3=CLSE NG Yoke 172 3.GUID={713A11F0-36D0-11EA-8001-444553540000} 172 Device acquired for use: 172 Joystick ID = 3 (Registry okay) 172 3=GarSim 530 172 3.GUID={713A11F0-36D0-11EA-8001-444553540000} How can I reset/flush the devices in FSUIPC/P3D and reregister them? Will I need to manually update particular registries, configs, etc; or can I perform a full registry clean?
×
×
  • 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.