Jump to content
The simFlight Network Forums

Pete Dowson

Moderators
 View Profile  See their activity

  • Posts

    38,265

  • Joined

  • Days Won

    170

 Content Type 

Everything posted by Pete Dowson

  1. Pete Dowson
    Closer, but 66C0 will not work as it stands as it looks like a decimal 66 with C0 stuck on. It's a hexadecimal number and needs 0X in front of it (or quotes round it). ipc.writeUW(0x66C0, ALT_set) If you had started out just stating what it was you were trying to do, which you still haven't done, it might have been quicker. Why do you want the value in an offset in any case? Pete
  2. Pete Dowson
    No! Please please do read the Lua library documentation! The event library is there to call a function in the Lua plug in when something happens! event.offset("66C0", "ALT_set") is actually wrong in any case, You missed a parameter out! which specifies the type of value being tested. A more correct line: event.offset("66C0", "UW", "ALT_set") would tell FSUIPC to call a function called ALT_set when the Unsigned Word at offset 66C0 changes. You have no function called ALT_set and you are not writing anything to 66C0. I think you are completely out of your depth, or just haven't actually studied the documentation or any of the many examples provided for you, to help. Writing to offsets is done by other functions in the ipc library. Please go and look them up. Pete
  3. Pete Dowson
    The INI file has all Button assignments in sections called [buttons], obscurely perhaps? :-) There are no separate parts just for FS controls as opposed to FSUIPC direct or offset assignments. You have to check the button (actually a checkbox) yourself -- you choose whether to assign to FS control, direct to FSUIPC calibration, or to offsets. It's part of the USER choices offered! Please please please refer to the User guide, in your FSUIPC Documents subfolder! Pete
  4. Pete Dowson
    There are no 'normal offsets" for L:Vars! The L:Vars are LOCAL to specific gauges. I cannot include in FSUIPC a general facility for all possible LVars in all possible add-on aircraft! As you've already been told, you can READ or WRITE LVars, once you know their names in Lua plug-ins. If you need a value in an offset, write the result of reading one to an offset. I already told you this, and I also told you that you can use the offsets 6C00-6CFF which are reserved for general uses like tihs. Pete
  5. Pete Dowson
    Er, where are you "returning" the value to? I have no idea what you are attempting to do. Pete
  6. Pete Dowson
    You'd need to write it to a User Offset (one in the range 66C0-66FF). There are Lua ipc Library functions for writing to offsets. Pete
  7. Pete Dowson
    Who or what are you quoting? Would you like to ask a question of your own? Pete
  8. Pete Dowson
    Do you mean Mouse macros? When you "created" them, did you TEST using the TAB key, as documented? Did you create them with the version of the aircraft you are using? If the version is changed, the location in the code which is recorded in the macros will be wrong. You must re-create them. Offsets listed in that document refer to the systems implemented in FS, not necessarily in sophisticated add-on aircraft. If the offsets are working for the aircraft you can assign FSUIPC contorls in the drop down to change them -- they controls ore named Offset ... and they are dmany for different data types and changes Sorry, I don't really understand this question. Pete .
  9. Pete Dowson
    Sorry, I've no idea whatsoever what the names in that SDK section refer to. If they are Lvars (local panel variables, often named with L: beforehand), then, yes, Lua can read the values But names are strings, so it should look like ALT_value = ipc.readLvar("AB_AP_ALT_Select") You'll need to read and understand the SDK to decide, I think. Pete
  10. Pete Dowson
    That's a common Saitek installation fault. I don't know why they never fixed it. You have to edit the Registry I think -- see the thread about this in the FAQ subforum above. Pete
  11. Pete Dowson
    These are the variables used by FS when it is controlling the sub-systems. Sophisticated aircraft like the PMDG 737NGX, the 777X and the Aerosoft Airbuses implement their own subsystems. There may be some overlap, you'd have to check. The variables you mention are available in FSUIPC offsets if you are not using SimConnect. The Lua program method is the only way to real local gauge variables (LVars) without writing a module or gauge to go inside FS. Pete
  12. Pete Dowson
    Does FS recognise the axes? If not you need Saitek support. If it does, then the most likely problem is that Windows is not assigning it an ID numberr for some reason. Take a look in the FSUIPC INI file, in the FS Modules folder. Is there a [JoyNames] section with the device listed? There is a utility you can use to assign an ID. See this thread http://forum.simflig...not-recognized/ Pete
  13. Pete Dowson
    It's DOWSON, actually. Sorry, I know nothing about any Flight1 aircraft, and certainly not "EGPWS". What is it? How is it related to anything in this Forum? Pete
  14. Pete Dowson
    I am 72 years old and have used computers since 1963. But I'm not sure where the history is relevant. I was not insulting you -- it was just that in the last message you explicitly said "So I enter name and email and paste the 12 -character key" Do you not see the difference and significance to me? Please email me at petedowson@btconnect.com. See if there is a file called "FSUIPC4.KEY" in the FSX Modules folder. If so, please rename it (KEY files won't get through), eg to FSUIPC4.TXT, and attach it. If there is no KEY file, see if you can capture a picture of the Registration screen after you have entered the details. Also include the FSUIPC4 Install LOG from the Modules folder and, if you have run FSX since installing FSUIPC, the FSUIPC4.LOG file too. I'll get back to you by email. Pete
  15. Pete Dowson
    You purchased version 4, not a specific version 4. And yes, 4.943 is the latest. I checked your order and everything is correct and works fine. I am sure you are making an error. So you did not copy and paste the name and email? Check again. ALL THREE PARTS MUST CORRESPOND EXACTLY WITH THAT SHOWN ON YOUR ACCOUNT! This is why we place the emphasis on copying and pasting all three parts. So many people spell their names differently each time, or maybe add a space or a stop. I can tell you here the exact name and email if you cannot find what you entered in your order. Pete
  16. Pete Dowson
    You buy either FSUIPC3 or FSUIPC4, not a "latest version". You download the "latest version". -- 4.923 for FSUIPC4 or 3.999z8 (or z9) for FSUIPC3. You only say "FSUIPC" not mentioning the major version which is crucial. Maybe you are using FS9 or before and bought FSUIPC4 by mistake? Or vice versa, you are using FSX or P3D and bought FSUIPC3? You need first to check that.. But anyway, I don't fully understand your description of the problem. You say on the one hand that "everything seem to work fine by installing, no error reports." but on the other that "when attempting to put the key I get the same answer". Since the key is input to the Installer, the error you are reporting must come from the installer, right? Please clarify. What is the "answer" (message? Error?) and where do you see it? The system used to generate keys is automated and there is really no way a properly entered registration will be rejected at the installation stage. There are possible reasons for it to not be accepted in the FSUIPC DLL proper, after you run FS, but not before you run it. If you tell me which version you downloaded, and give me your order number or your email address I can check you bought the right one. Pete
  17. Pete Dowson
    The name "mg_airbus_pedestal" is too long. Needs to be 15 characters or less. Pete
  18. Pete Dowson
    The Lua ipc library supports a function to read the local panel variables (Lvars) too, not just write them. The function is value = ipc.readLvar("name of Lvar") You can even declare an event ("event.Lvar") to call a function when the value changes, with an interval specified to define the polling rate. The Lua library documentation is installed in your FSUIPC Documents folder, inside the FS Modules folder. Pete
  19. Pete Dowson
    No one else (officially) uses that area. I've registered it for FSSymphony now. Pete
  20. Pete Dowson
    See the logging tab. The console window is a separate option on the left. The title bar and other Monitor options are on the right. They are entirely separate and not related to each other at all. Strange. did you report this on the ActiveSky support forum? Pete
  21. Pete Dowson
    I don't think so. No one has ever reported it here with FSX. Pete
  22. Pete Dowson
    Hmm. Getting very tight these days. Would you ever envisage FSSymphony being used on X-Plane with XPUIPC? If not then you could share part of its dedicated area, 6F00 - 6F7F. Let me know. Pete
  23. Pete Dowson
    This is not really "similar" and in fact in not at all related to FSUIPC, so I'm afraid I've no way to help. The crash is in FS's own user interface. Maybe your installation is corrupt and a reinstall would help? Pete
  24. Pete Dowson
    There's no such facility in FSUIPC4. Pete
  25. Pete Dowson
    Doesn't Aerosoft provide any controls for it other than Mouse? 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.