Jump to content
The simFlight Network Forums

Mike...

Members
  • Content Count

    75
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Mike...

  • Rank
    Advanced Member
  • Birthday 01/16/1981

Profile Information

  • Gender
    Male
  1. Mike...

    Macro with Lvars

    LOL! I do understand, so it's probably best to leave it as is. Thanks again. ;)
  2. Mike...

    Macro with Lvars

    In the mean time I've tried the aircraft specific feature, with ShortAircraftNameOk set to Yes. Everything seems to work and in one go! I think I was overcomplicating it a bit. That latest oddity doesn't have to be looked at urgently, if at all, when you have some spare time, that will be fine. It remains just that though, odd. Anyway, thanks for all your help and patience, I really appreciate it. I'll try and do some flights soon and think about what else I can turn into macros. :grin:
  3. Mike...

    Macro with Lvars

    [Macros] Module1="PMDG_737NG_Main.gau" 1=CMD L 1.1=L:apleft_clicked=Tog 1.2=R1:X32c0*X6a90 Continues to work for X32c0*X6a90, even though the Lvar is not present. So I'm thinking that doesn't matter. 1.1 itself though, doesn't work. Standalone, this does work: [Macros] 1=L:apleft_clicked=Tog :?: Yeah, I know, I am pushing it a little. I need to rethink my strategy, but I would still like to figure this one out. ;)
  4. Mike...

    Macro with Lvars

    You've provided a wealth of info in those docs as it is. ;) Okay, so the below: [Macros] Module1="PMDG_737NG_Main.gau" 1=CMD L 1.1=R1:X32c0*X6a90 1.2=L:apleft_clicked=Tog 1.1 works fine, 1.2 doesn't. Must FSUIPC be able to execute 1.1 before it can do 1.2? In this case, the gauge is not loaded (different aircraft), so one expects it to then do 1.2. Hmmm... In a hurry now, so I'll have to look closer into that later.
  5. Mike...

    Macro with Lvars

    So it should be R1:X32c0*X6a90? Well, that misunderstanding is because of page 41, where <rect#> is defined as "Rn" or "RXxxxx*xxxx" (shouldn't that be "RXxxxx*Xxxxx"?). Instead of keeping both, you're essentially inserting something in between. Going to "R(N:)n" and "R(N:)Xxxxx*xxxx". I think. ;)
  6. Mike...

    Macro with Lvars

    Future proofing the above would then give something like this? [Macros] Module1="PMDG_737NG_Main.gau" 1=CMD 1.1=R1:RX32c0*X6a90 1.2=L:apleft_clicked=Tog Edit: that doesn't work. If I leave out 1 and R1:, it does work. Thought just 1: instead of R1: then, but no go either. There's something about that R that doesn't make sense. So, Module1 > 1.1=1:RX32c0*X6a90, but that doesn't even get recognized by FSUIPC. But there are various examples, a bit further down in the PDF and in the main FSUIPC zip (PMDG OH sample), where there is an apparent relation between Module<number> and R<number>. Module1, all R1, Module 2, all R2, etc... I should've waited until tomorrow. Maybe I forgot to reload all keys between tries... :D
  7. Mike...

    Macro with Lvars

    LOL! I knew you were going to bring that up and so you should, but I do have my reasons. Who said I missed anything? Trust me, I went through it all several times, but the old brain (it recently turned 30) simply couldn't connect the dots this evening. What confused me the most was that I would be combining different types of macros. The example you've given, the role of the gauge name, by looking at it one could assume 1.2 is associated with that specific gauge, but obviously it isn't. I wasn't sure how to merge that together. In retrospect, it may also be good idea to look at the "aircraft specific" features. After all, Shift D must do different things in different aircraft, for now. And not necessarily different things in the same aircraft. Ah, it used to be so simple, flying default aircraft around... :lol: Anyway, thanks for the example, I'll take a fresh look at it tomorrow and decide which way I want to go. ;)
  8. Mike...

    Macro with Lvars

    Still working fine, but I had a question about combining macros/actions. I currently have a joystick button that does Shift D when pressed. That triggers the above macro just fine, as Shift D has been assigned the macro in FSUIPC. What is now the best way to have Shift D do two things? The above one and a new one I have successfully generated. So far my (trial and error) tests have failed. I have a PMDG.MCRO with the following: [Macros] Module="PMDG_737NG_Main.GAU" 1=CMD=RX32c0*X6a90 Which works fine on its own, but how do I merge that with QW757.MCRO, which looks like this: [Macros] 1=L:apleft_clicked=Tog I've been through the user guide and advanced user guide, but I'm none the wiser. I suppose I could assign one to press and the other to release, but I have a feeling they can be combined and assigned as one, but how? :???:
  9. Well, thanks anyway. Hope I didn't rob you of too much free time!
  10. Thanks Pete, it seems to work fine, but, and I don't mean to sound ungrateful, it doesn't differentiate between From/Departure and To/Arrival traffic. In Ground mode for example, it shows AI departing from but also arriving at (KDFW in my test). I can sort the From column to group the KDFW departures, but as soon as I sort say the Rwy column, KDFW departures are no longer grouped and it becomes a lot harder to discern the info relevant to me. Especially at bigger airports, it's madness. That's why I was specific about From and To ("Four entries would be filter compatible, Airborne From and To and Ground From and To."). I don't suppose in addition to the general filter "Airport=KDFW", which does serve its purpose (for example in the NYC area), you could add specific filters covering those four. Like GroundFromAirport, GroundToAirport, AirborneFromAirport, and AirborneToAirport. Obviously, it wouldn't be a good idea to use both Ground or both Airborne filters (or a combination?) at the same time with the same ICAO code, although, AI that does touch and go's would still show up I think. In my example of KDFW, I would set GroundFromAirport=KDFW and AirborneToAirport=KDFW in a test. Alternatively, I'd use GroundToAirport=KDFW, the least used would problably be AirborneFromAirport. I hope I explained it well. And a happy new year by the way. :)
  11. I have no use for an FSX addon as FS9 user. ;) I do use Traffic View Board, as inflight entertainment, but it doesn't mention runways at all, so it's no good as a testing tool. I know of no other alternatives that'll do exactly what I want them to do. I'd love to learn about them though! TrafficLook is really as real close as it gets, safe for a basic airport filter. I had already thought of the implementation as well. For example, under the "Ground" section of the ini file, there's "From=13,50" on my end. The filter would simply be enabled by a third value, so "From=13,50,KDFW" would show only flights departing from KDFW, in ground mode. No third value, no filter. Four entries would be filter compatible, Airborne From and To and Ground From and To. No GUI changes would be needed as I and I assume other serious testers check Afcads one airport at a time, so an ini edit would be a perfect way to enable and disable a filter. I don't suppose you are willing to reconsider? If the above would be an ordeal to implement, I'd understand, but I have a feeling that it isn't, though what do I know about programming... and that is part of the problem. :lol:
  12. Hello Pete, I make good use out of TrafficLook to test my Afcads, especially to verify runway usage. I'm currently checking KDFW and as you'll probably know, there's a lot of AI there. That much even, that I realized TrafficLook needed a new feature. An airport filter of some sort. When in ground mode, I usually only want to see departing traffic and in airborne mode arrival traffic, for a specific airport. It would be great if I could supply a filter to TrafficLook, KDFW in this case, that would only display From traffic for KDFW in Ground mode (From = KDFW) and To traffic for KDFW in Airborne mode (To = KDFW). That would allow me to then sort KDFW departure and arrival traffic in various ways for monitoring purposes, without traffic cluttering the list that I'm not interested in. I hope you understand what I want to accomplish. Would this be easy to implement?
  13. Mike...

    Macro with Lvars

    It's working fine now and my macro is having an effect on the panel, just not what I was expecting, but we can work on that. Thanks a lot, Pete! ;) Edit: Just dropping by to say that L:apleft_clicked did the trick instead. Woot!
  14. Mike...

    Macro with Lvars

    LOL! Today is fine, I do not expect you to work through the night. :D From the Advanced Users PDF: "Where ACTION must be one of: Set, Inc, Dec, Cyclic or Toggle (but only the first 3 letters are needed)". So I assume Tog is fine. ;-)
×

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.