Jump to content
The simFlight Network Forums

Pete Dowson

Moderators
  • Content Count

    36,366
  • Joined

  • Last visited

  • Days Won

    128

Pete Dowson last won the day on May 28

Pete Dowson had the most liked content!

Community Reputation

251 Excellent

About Pete Dowson

  • Rank
    Advanced Member
  • Birthday 08/27/1943

Contact Methods

  • Website URL
    http://

Profile Information

  • Gender
    Male
  • Location
    Near Stoke-on-Trent, UK
  • Interests
    Flight Simming, Steam Railways, Travelling, Real / Craft Ale,, worldwide

Recent Profile Visitors

35,053 profile views
  1. Yes, but if your "PTT" (Push to Talk) button is on a joystick connected to the Simulator then you need to do some assignments and settings to enable it to broadcast correctly. There is help for this on the Pilot2ATC support forum. Pete
  2. I see Thomas replied just before me. Thanks Thomas. Just adding to this: I use Pilot2ATC quite happily on a WideFS client PC. I like it that way because the sound from it is directed to different speakers, or my headset, and of course the speech recognisition is easier to get set up and running well on a spearate PC to the Sim. BTW the Server is the one which needs registration, not the Client, and it has it's own log called "WideServer.log". There's always two ends to a connection! 😉 Pete
  3. Autosave merely calls the SimConnect function to save a flight. Nothing else. The action then is exactly the same as when you save a flight manually, for example by using the ; keypress and entering a name for the flight. PMDG aircraft are programmed to detect the saving of a flight and freeze the performance temporarily whilst collecting the data relating to the aircraft state. Sometimes folks report that this causes a slight hesitation. Of course it should not actually change any of the values being collected. If it is doing this then it is a bug in the PMDG code and should certainly be reported. Pete
  4. If you are using a method that has to invoke a control to change a dial or value in a gauge, this is because the updates are flowing too fast and a queue has built up. For a dial or gauge in a cockpit there are usually better ways. If you have direct control over the local cockpit display, then make the increments there, NOT updating the Sim until there's a pause in the rotation of the encoder. Then write the value reached. The pause need not be very long - eg 1/2 second maybe. I've used this method in cockpit display drivers for many years. I'd need to know a lot more about exactly what you are doing to even have a guess at that. Pete
  5. Correct, though it isn't a "backup". All of FSUIPC5's settings are in the FSUIPC5.INI file, in the Modules folder. There is no relation at all between FSUIPC settings and P3D settings. It is up to you to make a backup for safety, by copying the file and any Lua plug-ins, Profile files and macro files from the Modules folder to a backup place of your choosing. By resorting to default P3D settings you have probably re-enabled all of its controllers and the resulting default P3D assignments would interfere with any joystick settings you made in FSUIPC. You'll need to go into P3D and disable controlers (again). Pete
  6. Before your query I had never heard of such a facility. Looking through the Controls list I do see it, but I've never used it. The controls list, for assignment, is generated automatically by requesting the list from the Sim. Whilst FSUIPC does add a few of its own (as listed near the end of the Advanced User's document), it isn't responsible for the built in ones, nor their names. As an FS control that one is simply sent to P3D for it to deal with. If there's any way to make the text size larger then it will be in P3D settings somewhere. However, I suspect that the only way would be to make text size larger in Windows' settings (eg. 100% to 150%), but this depends on whether P3D is generating its own font for those labels, or using standard Windows facilities. I think the Windows scaling facility does affect menus and so on. Pete
  7. No. Those offsets are solely under control of the application -- FSUIPC only scans them to flag keypress occurrences. Pete
  8. What dd you try? Did you look in the documentation for mouse macros? There's a section in the FSUIPC for Advanced Users document, a whole section on Mouse Macros. On page 38 there's the list of mouse actions: 1 Right single click 2 Middle single click` 3 Left single click 4 Right double click 5 Middle double click 6 Left double click 7 Right button & drag 8 Middlebutton & drag 9 Left button & drag 10 Move 11 Right elease 12 Middle release 13 Left release 14 Wheel up 15 Wheel down 16 Leave 17 Count In your macro line: you can see that the "3" means left single click. The list shows 13 as "left release", so you just needed 11=AP Up release=RX400000b9,13 or similar (your choice of name). If line 11 is already used just pick a free number. I suppose you tried assigning to the normal FS controls first? Much easier if they work: AP ALT VAR INC AP ALT VAR DEC Pete
  9. You buy it on SimMarket. Just search for FSUIPC4. Pete
  10. So on this joystick you are trying to program a button to do this? So you want button press to be assigned to that mouse button being pressed and button release to the same mouse button being released? Is that correct? If so, then in your macro file duplicate the line you have with a different line number and name, and change the mouse action code at the end to a 'release' instead of a press. Then program the first to your button press and the second to your button release. As I said, mouse macros are there to try to duplicate the actions of the mouse with a button or keypress. But when creating the macro in the first place it is only told about the first mouse action, which is the press. What you call a "clcik" is a press and release. When asking for support it is always quicker to provide as much information as possible right at the beginning to avoid us having to keep asking questions to find out what it is you want to do and with what. Pete
  11. How do you do it on screen, with the mouse? By "keystroke" do you mean button press and release? Or are you programming your joystick to send keystrokes? Pete
  12. You need hardware and some sort of programmed interface to drive an LED. If you can determine what conditions you deem a 'crash' and find suitable values in the FSUIPC offsets list, then you can get your harware driving software to read it and operate the LED. If you are not a programmer I assume you have already supplied software for your LED? There is of course offset 0840 which is the 'crashed' flag. that shows when the Sim itself detects a crash. Otherwise for a landing hard enough to be possibly deemed a 'crash' i think the relevant offsets to check are 11B8 (as Thomas suggested) and 030C (vertical speed). I have one of those somewhere but I don't remember how to program one. But it should do the job, and from offsets. Pete
  13. I assume you are talking about a mouse macro? Made in which flight sim and for which aircraft? Aslo your question seems to have a self-contradiction in it. you want the button to 2bounce back" but "stay pressed". How can it do both at the same time? In P3D4 or 5 the mouse macro records whatever it is you do with the mouse. So, left click, right click, whatever. With earlier Flight Sims you usually have to experiment with the mouse action codes (they are listed in the Advanced Users guide). But not knowing what you are trying to replicate, nor in what or for what it is difficult to advise further. Pete
  14. You should really read the offsets list as I just did. For 3210 it says: 56 DWORDs containing zero (when free for use), or a Hot Key specification. Notice that zero (when free for use)? There are 56 DWORDs starting at 3210. You must scan them to find a zero one which you can use. Other applications or plug-ins may be using others. THEN, you can write the specification of the key you want detected. Well, 0x42 is 'B', but how do you work out that 0x08 is bit 4? Bit 4 = 2^4 = 16 = 0x10. If you do not understand hexadecimal and bits please see this thread in the FAQ subforum: About bits, numbers and hexadecimal Probably because of your error above. But don't forget the offset address will be whatever slot you found empty and so used + 3, not necessarily 0x3213. Best to keep a note of it. Also after detecting it remember to write zero to that byte offset so it can be triggered again. Pete
  15. Assuming users haven't made their own assignments or changes in the Sim's key assignments, there are plenty of combinations of Ctrl + Shift + another which aren't defaulted in the Sim. The only problem with the choice of TAB + G was that TAB isn't used as a shift key in the Sim. I don't remember details of the 3210 method, but they are documented and i can look them up. But it would be better for you to ask specific questions about things you don't understand than for me to basically write the code for you. Pete
×
×
  • 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.