Jump to content
The simFlight Network Forums

abz

Members
  • Posts

    80
  • Joined

  • Last visited

Posts posted by abz

  1. I am trying to make a network installation for FSC and FSX. I have FSX installed on a Vista 32 system and it is working well. I have been reading the Introduction in the FSC manual about how to do this but I have a question. This is in regards to the location of the scenery.cfg file that one is requested to make a copy and call it scenerycfg.fsc. Other than the one in the root FSX directory, I have found my scenery.cfg file in the following location: C:\ProgramData|Microsoft\FSX. Is this the one that I need to make the copy of and place it in the root folder of FSX? Thanks, Al

  2. Hi Pete: FInally moved up to FSX. I just purchased both FSUIPC4 and WIDEFS and have 2 keys. I installed and registered FSUIPC4 last night and all went very well. Today I was going to register WIDEFS. I should have done them both at the same time last night. Now the question. In order to register WIDEFS separately, should I just re-run the FSUIPC installer to get to the registration window and enter the required information? Thanks, Al

  3. Great work Pete!!! Success-Success! Your dedication and determination to find a solution made it work. All the switches work perfect. Really like the engine start switches working now. And that APU switch returning to center is really nice. I cannot thank you enough for all your support on this little project. I certainly had a lot of fun working with you on it. And it seems that you learned a few new things for FSUIPC. And BTW, that Progress Window works fine now. Take care, Al

  4. Pete: Just read your PM. Thank you so much. Was busy taking care of my granddaughter yesterday. Talk about support; this is the ultimate in support. You are a genius. This is great news and I can't even try it out since I am now at work and have to wait till tonight to give it a try. Agree it is an expensive plane but this business jet is really nice to fly. I am hooked on it right now. Will report back after I try your new macro assignments.

    I will tell you that I have gotten almost all switches and push buttons to work in this plane using your mouse macro program. Now we can add the APU switch as well. However, there are still 2 switches (actually push buttons) I have not been able to program. I was not going to try any further with them and just keep using my mouse. I know you are very busy with everything else but maybe now that you have the plane you can give them a quick try. It is the left and right engine start push buttons and the the XTIE (battery cross tie) push button - all are on the same tilt panel. I tried them but never had any success. Everything else seems to work fine.

    Thanks again and will be back in touch after I try the APU switch. Al

  5. I edited the previous macro file line 22 by adding ",17" as suggested and this did not change how the switch functioned.

    When I use the switch on my CH throttle quad to put the APU switch to the start position, the switch just goes there and stays there; it does not return to Norm with release of the CH switch. If I switch APU off it goes to off and stays there.

    Some additional information for you about that progress window staying on.

    I noticed, for example, when I checked off "Buttons and Keys" in the logging window, when I said OK to exit, I saw that progress window flash very briefly before the main FSUIPC window closed. It did not stay on. If I open FSUIPC and then immediately close it, that window again very briefly flashes before going off. So it is working correctly some times. It was only when doing the create macro file that it stayed on.

    Al

  6. Hey Pete: This is like talking on the phone with you.

    1. Regarding the behavior of the switch, I was just reporting to you what I saw different from the last time. You're right. This is what we want to happen.

    2. That message - NEVER DISAPPEARED. I just went back and tried it again and it remained even after I closed FSUIPC and even after I clicked on the desktop with the mouse. It remained there (all by itself) until I closed out FS. It then closed.

    3. Here are the two Macro file entries:

    1=APUstart=RX70280*X8bcc,17

    2=APUoff=RX70310*X8bcc,17

    I cannot create one for the Norm, since the switch just self centers after I release the mouse.

    4. Yes I have to release the mouse to deal with the macro file details. If I hold down the mouse, I just get the macro name entry colored window flashing between the two colors.

    Thanks, Al

  7. Pete: Here goes. After I opened my flight I opened FSUIPC. I checked off logging for buttons and keys. After that I went to Create Macro and named it APUtest. When I clicked OK, it went back to the main FSUIPC window but I had this small square window pop up in the center of the FSUIPC window that said:

    "Saving and/or reloading FSUIPC settings. Please wait." Unfortunately, this message NEVER disappeared --- until I closed FS. What is this?

    I went ahead and created the Macro. The only thing different this time was the fact that after I mouse clicked the APU on, it came back to NORM. I made a macro anyway but it failed to respond to the TAB key. I did the same with the APU off - created a macro for it - same no response to the TAB key. I then went ahead and assigned a switch to these 2 macros and neither worked with the APU. I have included the Log file below:

    44476 KEYDOWN: VK=18, Waiting=0, Repeat=N, Shifts=4

    44476 .. Key not programmed -- passed on to FS

    44585 KEYUP: VK=18, Waiting=0

    49983 *** Entered Buttons option page ***

    49998 FirstButtonChange res=00000220 (0.2, 32)

    66175 *** Exiting Buttons option page ***

    71136 Mouse by function: RX70280*X8bcc Module="ESDG_CitationX.GAU"

    71370 Mouse by function: RX70280*X8bcc,17 Module="ESDG_CitationX.GAU"

    74912 KEYUP: VK=255, Waiting=0

    75348 KEYUP: VK=65, Waiting=0

    75816 KEYUP: VK=80, Waiting=0

    76784 KEYUP: VK=85, Waiting=0

    76924 KEYUP: VK=16, Waiting=0

    77564 KEYUP: VK=79, Waiting=0

    77876 KEYUP: VK=78, Waiting=0

    82197 KEYUP: VK=8, Waiting=0

    82368 KEYUP: VK=8, Waiting=0

    82805 KEYUP: VK=83, Waiting=0

    83148 KEYUP: VK=84, Waiting=0

    83741 KEYUP: VK=65, Waiting=0

    84162 KEYUP: VK=82, Waiting=0

    84428 KEYUP: VK=84, Waiting=0

    89778 User Macro: APUstart=RX70280*X8bcc,17 (Module="ESDG_CitationX.GAU")

    89981 KEYUP: VK=13, Waiting=0

    93039 Mouse by function: RX70310*X8bcc Module="ESDG_CitationX.GAU"

    93195 Mouse by function: RX70310*X8bcc,17 Module="ESDG_CitationX.GAU"

    95457 KEYUP: VK=65, Waiting=0

    95800 KEYUP: VK=80, Waiting=0

    96393 KEYUP: VK=85, Waiting=0

    96533 KEYUP: VK=16, Waiting=0

    96939 KEYUP: VK=79, Waiting=0

    97625 KEYUP: VK=70, Waiting=0

    97875 KEYUP: VK=70, Waiting=0

    102758 User Macro: APUoff=RX70310*X8bcc,17 (Module="ESDG_CitationX.GAU")

    102961 KEYUP: VK=13, Waiting=0

    105862 KEYDOWN: VK=18, Waiting=0, Repeat=N, Shifts=4

    105862 .. Key not programmed -- passed on to FS

    105971 KEYUP: VK=18, Waiting=0

    113366 *** Entered Buttons option page ***

    113366 FirstButtonChange res=00000220 (0.2, 32)

    117812 *** Exiting Buttons option page ***

    123865 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=2

    123865 .. Key not programmed -- passed on to FS

    123958 KEYDOWN: VK=67, Waiting=0, Repeat=N, Shifts=2

    123958 .. Key not programmed -- passed on to FS

    124489 System time = 14:48:55, FS2004 time = 19:16:31 (00:16Z)

    124489 *** FSUIPC log file being closed

    Memory managed: 64 Allocs, 7505 Freed

    ********* FSUIPC Log file closed ***********

  8. OK Pete: I copied the new (3.865) FSUIPC.dll file into my modules folder. When I do this experiment, is there anything unique that I have to check off or do I just go through the exact same procedure that I did before to make the macros for the APU switch (On, Norm, Off)? I will make a log for you but I just wanted to make sure that I should do exactly the same procedure I followed before. Thanks, Al

  9. Hi Pete: Sorry, but when I received your reply on Jan 23rd after I tried the left mouse, you replied that "Mouse button up" controls that you added won't do any good (see below). When I read this I did not try any further. I certainly can try your new update. But I will not be able to check it till later this week when I get home. Thanks, Al

    FYI: I tried to reply to your PM to me but it just would not send - kept saying no receipient even though I inserted your name. Not sure what the problem was.

    "1. I did try the left mouse button as you requested and nothing happened. No movement of the switch.

    In that case the "Mouse button up" controls I've added won't do any good. Sorry."

  10. Thanks Pete for the clarification on editing the mouse macro file.

    I do have a question. If, for example, I eliminate line 22 (APU Norm) as you suggested, do I have to re-number all entries below, so 23 would become 22, etc? Or do I just leave the remaining numbers as they are?

    Another strange thing happened and I was wondering if you could help. I connected up 2 other GoFlight modules to my PC. Now what I had assigned through mouse macros for one GoFlight module seems to have transferred to another one, not the one that I initially did the assignment on. It seems that the joy numbers 174, 175 and 176 have been interchanged. Other than editing all this through the FSUIPC.ini file, do you know if there is a way to reassign the joy numbers of the GoFlight module back to their original? Any idea why they would have changed like that? Thanks, Al

  11. Hi Pete: Thank you so much for all your help on this switch question.

    1. I did try the left mouse button as you requested and nothing happened. No movement of the switch.

    2. Thank you for providing the update for me to try which I will do soon (over the weekend).

    Just want to make sure - if I place the updated 3.864 FSUIPC.dll in my modules folder to replace the one I now have, will this have any effect on my current FSUIPC settings? Any thing to back up first?

    3. In my current Macro file that I have been generating all these repeat mouse macros for the same function for testing purposes, I see in this file multiple entries as shown below:

    21=APU Start

    21.1=RX70280*X8bcc

    21.2=RX70280*X8bcc

    21.3=RX70280*X8bcc

    22=APU Norm

    22.1=RX70280*X8bcc

    22.2=RX70280*X8bcc

    22.3=RX70280*X8bcc

    22.4=RX70280*X8bcc

    23=APU Off

    23.1=RX70310*X8bcc

    23.2=RX70310*X8bcc

    23.3=RX70310*X8bcc

    Can I just delete all the extra entries for the same function, like 22.1, 22.2, 22.3, 22.4, etc

    Thanks again, Al

  12. Pete: I created the log and I have included it here since fairly small. Hope I got it right this time. Thanks, Al

    DebugStatus=15

    764 System time = 17:10:53

    764 \\FLTSIM6\Flight Simulator 9\

    764 System time = 17:10:53, FS2004 time = 12:00:00 (00:00Z)

    1622 C:\Users\ABZ\Documents\Flight Simulator Files\StartupC172.flt

    1638 AIRCRAFT\c172\Cessna172SP.air

    2059 Aircraft="Cessna Skyhawk 172SP"

    7644 Advanced Weather Interface Enabled

    7644 Traffic File #14 = "scenery\world\scenery\traffic030528"

    24445 C:\Users\AZ\Documents\Flight Simulator Files\CX2.1.flt

    24461 AIRCRAFT\Eaglesoft Citation X 2.0\CitationX.air

    24664 Aircraft="Eaglesoft Citation X 2.0 N1220M"

    26988 Clear All Weather requested: external weather discarded

    64319 WeatherOptions set, now 4000B627 (timer=0)

    67002 KEYDOWN: VK=18, Waiting=0, Shifts=4

    67002 .. Key not programmed -- passed on to FS

    72852 *** Entered Buttons option page ***

    72852 FirstButtonChange res=00000220 (0.2, 32)

    87251 *** Exiting Buttons option page ***

    104520 Mouse by function: RX70280*X8bcc Module="ESDG_CitationX.GAU"

    124239 Macro: mouse action="ESDG_CitationX.GAU":X70280*X8bcc

    133193 User Macro: APU Start=RX70280*X8bcc (Module="ESDG_CitationX.GAU")

    140557 Mouse by function: RX70280*X8bcc Module="ESDG_CitationX.GAU"

    155158 User Macro: APU Norm=RX70280*X8bcc (Module="ESDG_CitationX.GAU")

    158185 Mouse by function: RX70310*X8bcc Module="ESDG_CitationX.GAU"

    172599 Macro: mouse action="ESDG_CitationX.GAU":X70310*X8bcc

    175719 User Macro: APU Off=RX70310*X8bcc (Module="ESDG_CitationX.GAU")

    181944 KEYDOWN: VK=18, Waiting=0, Shifts=4

    181944 .. Key not programmed -- passed on to FS

    187763 *** Entered Buttons option page ***

    187778 FirstButtonChange res=00000220 (0.2, 32)

    192193 *** Exiting Buttons option page ***

    200648 KEYDOWN: VK=17, Waiting=0, Shifts=2

    200648 .. Key not programmed -- passed on to FS

    200758 KEYDOWN: VK=67, Waiting=0, Shifts=2

    200758 .. Key not programmed -- passed on to FS

    201272 System time = 17:14:14, FS2004 time = 19:17:21 (00:17Z)

    201272 *** FSUIPC log file being closed

    Memory managed: 26 Allocs, 15258 Freed

    ********* FSUIPC Log file closed ***********

  13. Hope you got a good night sleep.

    Pete: Sorry for all this confusion on my part. Just to clarify (I hope), that APU switch is oriented vertically, not left to right. That is why I asked what left button? It is a standard toggle switch on the APU panel.

    Actually I am using one of the toggle switches on my CH throttle quad for this (no buttons). I can use the CH switch to make the APU switch move up (it stays there).

    The problem is that when I click my CH quad switch down to move the APU switch to the center position, it goes to the down or off position. I can NOT get it to go in the center position. When I created the macro, it goes to the center position but in real life when I actually try it, the APU switch goes down to off, NOT in the center. When I created the macro to go to the center position, there is no way for me to test it with the "TAB" because it was alreay centered. So maybe it never actually created it in the first place.

    OK, I can check just 'Key and Logging". I know you said this is all I have to do but do I have to hit "START" before clicking OK to get out?

    Thanks, Al

  14. OK. I set the APU switch up with the assigned button on my GoFlight module. Now what do you mean by "click and release the LEFT button" What LEFT button? Do you mean the left mouse click button?

    Also I looked at that log file. It looks small in size to me and looks like the original log file that was there. It is now called FSUIPC.1.log. Maybe I did something wrong in creating it. Under logging, I checked off "button and key operations", "New Log" and "display to normal log file" Correct?

    I hope that I am not giving you a headache with my inability to get this correct the first time. Thanks, Al

  15. OK Pete: I made the log. How do I send it to you?

    Also, I tried what you suggested about moving the mouse away from the switch.

    I left clicked the mouse over the switch and the switch went to the up (start) position. As long as I stayed there the switch stayed up. However, as soon as I moved 2cm away from the switch, even with the left mouse held down, the switch released to the center position. Same thing with the down (off) position.

    Al

  16. Pete:I just want to make sure I understand what I am doing (never did this before). I went into the logging window. Now when you say enable button logging I assume you mean to place a checkmark in the Buttons and key operations. Correct? Where will I find the Log of the Button/Mouse actions? Will this be the TEST macro file?

    FYI. Yes it is a center-to sprung type switch from both the up (ON) and down (OFF) positions. I created the mouse macro when I had it in the up position after creating the macro that kept it up. Then I mouse clicked it down to the center and made a new macro. Still want me to do the test file?

    Thanks, Al

  17. Thanks Pete. Still cannot get it to work perfectly. It is the new Eaglesoft Cessna Citation 2.0 (fantastic plane). Its APU switch has 3 positions, NORM in the center, Start (up) and Stop (down). If you mouse click the APU on, the switch must be held (with the mouse) for 5 seconds and then released - it then automatically goes back to the center NORM. I have tried to program the back to NORM but it does not work. When I assign a macro to it, the switch does go up but stays up - no big deal since it stills turns on the APU. If I assign the switch release to center, nothing happens. Must be different than the 737 that you mentioned. If I program the 'off' to get the switch back to center, the AP just turns off. I guess it is one of those switches that cannot be simulated perfectly - unless you have another idea for me to try. Thanks, Al

  18. Hi Pete: I have been using your mouse macro functionality with much success and I thank you very much for this capability through FSUIPC. I just came across a switch that is self centering switch. I hope I can explain this clearly. It is for turning on an APU. Without using a mouse macro, If I mouse click the switch and hold the mouse down for 5 seconds then the motors turns on. I then let off the mouse and the switch goes to its center position automatically. Through FSUIPC, I set up the mouse macro to turn on the switch. I can get the switch to go on but I cannot get it off to go to the self center position. Can this be done through Mouse macro and FSUIPC programming? In other words, I would like to simulate this function by holding up a switch on my CH throttle quad for 5 seconds and when I let go, the switch in the plane self centers. Thanks, Al

  19. Pete: I programmed 2 mouse macros using FSUIPC for my add on Reality XP GNS 530 GPS unit in the Beech Baron (B58) plane. I programmed 2 buttons, one to increase range and one to decrease range on this GPS unit. At the time I programmed it, it worked fine. I then closed FS. However, now when I open any plane that has that particular GPS unit installed in it, I get an error message that says "Can't start the Reality XP Garmin". The plane opens and the GPS unit is there but it will not turn on. I have no idea why this happened but occurred right after I did the macro programming. Any suggestions what to do from here? Can the programming be edited via the Macro file or the FSUIPC.ini file to get rid of those 2 macros to see if the unit will work again. Does the Macro programming do anything to the Gauge file for the Reality XP 530 unit? Thanks, Al

  20. Exactly what I said, and as explained at greater length in the documentation, which is why I wrote it. Please read the section entitled "Programming the buttons". I shouldn't need to repeat extracts here! :-(

    Thanks Pete. You are absolutely right. I do not want to create any more work for you. You already give so much of your time to all us users. Sorry, but I initially quickly looked on page 26 under Buttons and totally missed the information on page 28 about Pogramming the Buttons since I did not see it in the table of contents. Should have kept reading on. It was all there. An over site on my part.

    As always, thanks for your help, Happy New Year. Al

×
×
  • 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.