Jump to content
The simFlight Network Forums

Zoandar

Members
  • Posts

    10
  • Joined

  • Last visited

Zoandar's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. It is very likely that bits of what I had read in your user manual silently evaporated before I was able to put those documented steps into use. Sadly the state of learning in an aging mind. It happens all too often, I am sorry to say. Thanks for explaining everything. Kind Regards, Zoandar
  2. THAT single statement, which is something I had not understood from the beginning, nullifies all my previous comments! I understand now, and I have just finished re-creating my key assignments by gathering all the 'gauge module addresses' (a.k.a. mouse click function names) in a single session within the VC, assigning all of them to the AFCS macro. Sweet. It is exactly what I had been trying to ask you if you had intended as a feature in the future, because I did not understand that it works that way NOW. :) Perhaps the terminology was part of what led to my misunderstanding. Up until tonight's epiphany, to me a 'macro' was a set of any number of events, assigned to an individual trigger (most often for me, a key on a programmable keyboard or a function within, say, a word processor) but ALL OF THEM executed when the trigger was engaged. Whereas, here, the term Macro is being used to describe essentially a whole library of 'possible' events, any one or more of which could be assigned to any one or more trigger events. So this was a whole new definition of the term macro for me. I apologize for the frustrating confusion. I have learned that when something doesn't make sense to me, it usually means I am missing some information. That was the case here. My continued reference to "mouse clicks on the screen" was simply because that is a step in the acquisition of the gauge module address using the FSUIPC macro creation feature. I understand fully that when I utilize the assigned keystroke to one of the macro functions attached to a gauge module address it doesn't actually "click the mouse on a button". I was just using terminology to which I am accustomed. I think the reason why the macro failed, when I tried to acquire 3 gauge module addresses "in succession" in one macro creation session as I mentioned cryptically above, was due to something I learned just now while re-running this whole procedure. I wanted to start over from scratch, to see if in fact I could do all the VC panel buttons at once as you suggested. So I wanted to completely undo the macros I had created last night. When I went into FSUIPC and deleted the keypress assignments I had previously made, and then deleted the .MCRO files I had previously created, I could not get the Create New Macro procedure to work until I shut down and re-started FSX. The text listing the gauge module address would never appear in the VC view when I clicked on a button. I restarted FSX and then it worked just fine. So when I had tried that last night I'll bet I had done something requiring an FSX re-start and did not yet realize I needed to do so, and thus the procedure failed. I've got a handle on this now, and I have to say this is really cool! And yet I get the feeling I have barely scratched the surface of the full potentials of FSUIPC. Much of the modification I have done all this year to my FSX installation starts out with an idea. "What if I could do this.........". Then I try to find a way to make it happen, if possible. Thanks to your tool, you brought another one of my dreams to reality. Thank you!! :)
  3. Perhaps I could have better worded my intent here. What I meant to suggest was to refer to the stage of mouse macro creation where you are looking at the FSX screen and the name of the control on which you just clicked is being displayed, along with a prompt to ask you to enter 'your' name for the function. It seems this is geared toward creating a single click event and name, although I did try doing 3 of them in succession as an experiment. The resulting macro that was created did not work, so I had to delete it and start over. Perhaps the better way to word it would be to ask if you have plans to allow 'harvesting' of multiple click events during this stage. I understand. When I first started dealing with keyboard and mouse macro programs and such I quickly learned what a headache it is to try to emulate a mouse click on a specific spot in a program window. I try to avoid doing that whenever at all possible. The FSUIPC utility is a very nice alternative, harvesting the name of the control on such a "spot" and allowing a key to be assigned to it. It is unfortunate Windows doesn't have such a feature built into the GUI. The control panel I am working with sometimes requires the helicopter pilot to press 3 buttons in succession to get into certain types of hover mode. It would be nice to have one key or joystick button handle all 3 of the on-screen click events, so that turning hover mode on is similar to engaging an airplane's autopilot. I presume the vendors of this payware helicopter were after recreating the most realism possible. But sometimes it it nice to just flip a switch. ;) Especially when using both hands on helicopter controls. Thanks!
  4. Mouse macros turned out to be just the ticket! When I was first reading about them I got the mistaken notion that a mouse macro was a set of actions which were put in motion by use of the mouse, for example using the scroll wheel to adjust the heading bug. So I didn't immediately think to try them. But once I did try them, I found the process easy to use and it does exactly what I needed. :) Thanks! Have you considered allowing multiple mouse clicks in sequence to be assigned a single key press? There are a few instances where it would be handy to have pressing a single key click more than one control on the screen. Ultimately this can be accomplished by programming a keyboard or joystick control to execute sequential keys, each singly assigned to click one button, but I just wondered if you had any plans to add that feature?
  5. I am also looking for a way to assign a mouse click, and I have so far learned that the log lvars.lus tool does not even see when these mouse clicks are taking place. Is there some other way to capture them or perhaps are the mouse clicks not an LUA event at all?
  6. I have been working on trying to figure out how to assign Saitek X52 joystick buttons or else keyboard buttons to some VC controls in Aerosoft's payware Seahawk + Jayhawk helicopter addon for FSX. I tried following the nicely written guide here: http://a2asimulation...hp?f=23&t=19751 But after getting a registered copy of FSUIPC 4.79e set up, what I learned was that operating these controls do not appear in the VARS LUA log as "normal" aircraft controls do. Specifically, my current goal is to map the buttons used on the AFCS Control panel, which is a flight stabilization and autopilot system on these helicopter models, so that I can engage some of them from my joystick or the keyboard rather than clicking on them with the mouse. Is there some other way (aside from making use of the "log lvars.lua" ) that I can discover what events these mouse-clicked buttons are generating and then build them into a macro? I use these controls most of the time from a windowed view of the AFCS panel, which is always in exactly the same place and size on my displays. So one possible alternative might be to map the joystick to some kind of on-screen mouse click on a specific spot (over the desired button), if anyone can recommend a way to implement that. I have used macro programs which can emulate mouse clicks on screen coordinates, such as Quickeys, but that one in particular interferes with the operation of other assigned control keys and buttons in FSX, so I have to shut it down when flying.
  7. That's a really nice, and well detailed, document on installing and registering FSUIPC that came with the 4.75 installer I just used. I was able to update FSUIPC to 4.75 and register it without any problems. :) But I have a question that I suspect I know the answer to, although I'd like to verify it. Despite that I did read the whole installation PDF document, my short term memory being what it is, I accidentally forgot to run the installer as Administrator in Windows 7x64. What followed was something I have seen a few other times under Win7. Once completely finished and registration was acknowledged, the window popped up which, in short, offers to re-install the app I just installed "with the correct settings". Is that Win7's automatic way of correcting when something 'should have been' installed as administrator but was not? It went through the second time, confirmed the installation and registration, and I'm good to go. :) Thanks for making this really cool FSUIPC utility! Although FSX may be considered 'long dead' by Microsoft, I find incredible the amount of support, modifications, and user base which carry on through this day and for who knows how long into the future. I have had many hours of fun from it, and hope to continue for a long time. Your utility has given me the opportunity to add features I had once only dreamed of, and now with the registered copy I hope to learn how to do even more. Last night I found a nice tutorial website telling how to utilize the registered version of FSUIPC to assign keyboard keys and joystick controls to events normally inaccessible in the standard set of FSX controls. That's where I am headed now, to do just that. Have a great day!
  8. OK. Thanks for clarifying all that! Have a great day! :)
  9. Hi, I have been using the free version of FSUIPC with FSXA for awhile and it has worked well. But I am getting interested in doing some custom key and button assignments for which I read that I need the registered version of FSUIPC. So I went to your site to get it, but I have a question about what I see there. I see FSUIPC4 4.70 (B) and it says that it includes WideFS 7. Below it is a listing for WideFS 6.86 Below those, are SimMarket links to either FSUIPC or WideFS for FSX. It appears to me that you are incorporating the WideFS program into FSUIPC. So do I just need to get FSUIPC and I would then have both it and WideFS 7 ? At the moment I do not know what I would use WideFS for, but I suppose at some point in the future I might need it. Also, if I buy the latest FSUIPC and want to install it, do I have to remove the currently installed version, which is version 4.60? I see it in the FSX Addons tab, and I can open it there, but it isn't listed in the Programs and Features section on my Win7 x 64 Home Premium OS on my PC. I would like to end up with the latest version if possible, but I also am hoping it doesn't cause problems with what I have running alongside FSX (currently FSWidgets GMap). I see in the unregistered version I have installed it says to register it, shut down FSX and re-run the installer. So can I just run the installer for 4.75, which I downloaded from the link in your FSUIPC updates thread, right over top of the installed 4.60 version?
×
×
  • 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.