Iceking007

Okay, thank you.

doh! I'm so sorry John, I'm such an idiot! The control I was looking for was the Gyro drift; I must have had the wrong control numbers in a backup. ini file that I used. It's working properly now. Do you know if there's a way to export "keypresses" from fsuipc to my Swift VATSIM client. I want to control Swift 'hotkeys' with cockpit hardware. Fsuipc can see this hardware but Swift doesn't. I understand I'm outdated, I appreciate all the assistance you've offered. It has helped immensely.

I had assigned a couple keys to rotate the compass (HSI) to correct for wind drift. This has been working well, until lately, I think a potential culprit is RXP and the problems I have been having with their new software. However even when I completely uninstalled and removed it I did not get the compass functionality back. I tried changing the keys but that had no success either. The log file is attached, INDUCTOR_COMPASS_REF_INC/DEC (66577/66578). I'm not sure if something is broken in FS, as it seems these are seen by fsuipc correctly and passed through. Is there some way I can troubleshoot or fix this? Do I need to completely reinstall fs or can I just replace a couple files? Thank you for your time. FSUIPC.log

Okay, I think I sorted it, I put it at -65532,0,0,65016/1542 It looks close from the digital indicator from the ground but I'll have to take it flying to see; it might still be too much, I wonder if the real Mooney has this much trim deflection!? I cannot fathom why you would ever need that much given the flight characteristics in the simulator. But I find too that the "takeoff setting" areas for horizontal and vertical trim are both aggressive and not very practical in my experience. More fun at the airfield. Have a good one.

That's okay. So this goes into the [JoystickCalibration] section? As: Rudder Trim=-65532,0,065016/16? What do these numbers mean? Why is RudderTrimControl=0, should that be 1 or something? Another oddity while I have you here... fsuipc won't let me set the Throttle and Mixture up (my vernier ones). These are in the same usb control box as this rudder trim. FSUIPC sees them in the calibration tab but not in assignments, I have to assign the via the fs menu. I think it's something to do with PFC/Windows labeling these axis as "dial" and "y rotation"; however luckily fs does see them correctly. I'm trying to make use of the fsuipc custom configurations so that when I change between my vernier and other throttles I don't have to go and reassign everything like I have in the past. That makes changing aircraft even more cumbersome than it already is. Thank you.

Is that entered in the Axis Management tab, or the Calibration tab? I'm only able to enter values in the Axis tab when setting up ranges... Also, is the divided only on the last one? Thank you John.

Hello, I am using a PFC USB throttle system, it includes a rudder trim knob. The problem is that when I fly the Mooney Bravo (M20M), it requires VERY little and extremely precise trim adjustments. This works okay with the factory trim buttons, but I don't have hardware trim buttons, only this hardware knob. FS does not recognize this axis so I can't configure that in there and use the sensitivity adjustment. I have been unable to create the desired affect in fsuipc. I can make the knob FAR more sensitive, but not less. Ideally I probably only need 25% or even 10% of the current range on either side. As it is now I can select maximum trim deflection in only 20° of rotation... I'd like to get 25% deflection at 120° of rotation. Barring that, perhaps I can get it to use the rudder button like a jog/shuttle wheel would. I could see doing that with the range adjustments in the axis tab, but that would take painstaking configuration to say map every 5 degrees in both directions to a single button press. Thank you for your time.

Okay.

This is my file so far... It does run in fs. The # and "" as used above are just place holders, and obviously just forgot it was only event.key instead of event.keypress; I cannot memorize everything you know. Yes, the 2 was supposed to track the key up; if you recall I was using that earlier and it was not working, then you suggested just tracking the key up/down variable; as you will see, that is what I am using now; however tracking it both as 1 or 0 in my timer code doesn't yield the results I'm after. FYI: As a side note, I'm planning on separating my 'display' code into a separate Lua file, it has some bugs currently, so please ignore it. Please don't laugh at my work, remember that I am not a programmer or I wouldn't even be here in the first place.

Hi John, Well... it seems no matter what I do I am unable to get a key up reaction. Is there a quick method you would suggest to viewing the key state changes? It seems to me that the key up does occur somewhere in the chain as my key downs are tracked without fail; I need to be able to verify if the key release (key up after a precursor key down) is being seen in Lua and how it's being interpreted. I'm loosing a lot of wind in my sail with this whole fiasco, I sincerely appreciate all the assistance, it's just I was expecting to take less than a week on this and now it's been a couple months. I just recently purchased a used pc, and so I am slowly changing over to a Windows 7 64bit build for my fs. I should be then able to run the software, but I'm not giving up on this coding project, I forsee the ability to implement it, and I don't like to stop just because something is broken that should work. The other problem with going away from Windows XP is that some software I want to run is only XP compatible, I'm hoping I can still run it on W7 in compatibility mode. To add insult to injury, as if I don't have enough on my mind, I just recently lost my job... and so now in this uncertain economy I need to get that sorted ASAP; the bills are already piling up! I miss flying, I'm hoping I can get back up into the air soon! I didn't have much luck with event.keypress(#,#,2,""), but if I use: event.keypress(#,#,kd,"") and then: function ""(#,#,kd) if kd == 1 then ipc.display("Key is Down") else if kd == 0 then ipc.display("Key is Up") else ipc.display("Key is Other") end end That's simple and should work? - you're probably going to poke all sorts of holes in my code, but at this point I just don't care... I haven't been sleeping very well lately and now I'm up in the middle of the night typing this out without much though, so I guess I deserve it. Funny how we all get what we deserve. Thank you for your time and your patience, I hope to one day not be a burden!

Re: offset 05CC appears to be "The viewpoint Bank" according to my documentation. Are these offsets an fsuipc thing?! I was under the impression they were fs memory locations; but if so then they would not change with fsuipc updates, only with fs versions (ie fs9, fs10).

So I completely misunderstood the hex BCD reference, that is until you spelled it out for me of course. I apologize for my stupidity; much to learn I have. I believe I've made all the corrective changes to my code now, I'm hoping to test it sometime in the next week. With any luck it should all work. I'll try not to pester you with my learning; I have spent a lot of time (most of my time as of late in fact) learning Lua, and reading all the documents, and going through other Lua programs both related and unrelated to fs. But I'm sure you are aware, these skills cannot be mastered in two weeks. Thank you for your guidance; IF I get my code working as intended I shall post it online to share with others.

No I don't believe it is a limit as I already have that call and all the functions run. But I'm just trying to toddy up my code and make it more efficient.

Okay I appreciating all of that. Yes by skipping the downup function I was referring to your keyUpDown(); I should be able to just use that within my current function rather than shooting another one. I'll get it sorted out, thank you.

Hi John, I'll have to try those out in the Sim to see what I'm actually getting; I don't think there's much extra processing to convert the hex?! But I certainly was not aware there was also a decimal registry; I didn't seem to find it in the offset document but I will look that up as well. So with the keys and buttons, then I'm assuming fsuipc just automatically assigns a down/ up (1/0) bit to every input and that is 'catalogued' in the third "slot" ie(1, 2, 3)? I haven't added conditions to any of my functions, they seem to be working, save for this issue. However if what I'm thinking above is correct... then I'm thinking I could bypass the downup function and just pass that indicator bit onto my actually function and qualify it with a simple if statement; less code I figure that way, as I don't need a discreet return of this state. Thank you.