Jump to content
The simFlight Network Forums

Pete Dowson

Moderators
  • Posts

    38,265
  • Joined

  • Days Won

    170

Everything posted by Pete Dowson

  1. The max I referred to was for the Offset word inc and Offset word dec controls. Nothing to do with a Lua solution for the axis control of panning. I'll post an idea for the latter later. Pete
  2. Those numbers are NOT offsets!!! I already told you that! If you are assigning those controls to buttons you can send a sequence of such controls with different parameters by simply adding the extra assignment lines in the INI file. The format of button assignments is provided for you in the FSUIPC Advanced User's guide. Pete
  3. Hmmm. Maybe they are only processed by the CH software. they can't be normal joystick axes otherwise fSX and FSUIPC would see them. Try this program: HidScanner. It produces a log (and screen copy) of all the details it can find out about HID devices on your system. It may be useful. Paste the log into a message here if you want me to help analyse it. Pete
  4. The offsets mapped into FSUIPC from the NGX are all read only. You have to use the NGX custom controls as documented by PMDG in their SDK (the .h document I think). Your so-called offsets "69850" and "69852" actually seem like control numbers in any case, certainly not offsets which can't go that high. I'm afraid I don't have the NGX and don't know any of its controls. For more help I think you might need the PMDG support forum, but check the User contributions subforum to see if anyone else has the answer there. Regards Pete
  5. Oh dear. It is in the documentation! UB = Unsigned Byte. UW = Unsigned Word Look at the FAQ subforum. There is a guide there to bits and bytes and numbers. Byte = 8 bits, 0-255 unsigned or -128 to +127 signed Word = 16 bits (0-65535 unsigned or -32768 to + 32767 signed. Et cetera. Don't forget also the offsets are at 1 byte intervals (normal memory addressing. So for a 2-byte spacing you need 66C0, 66C2, 66C4 etc. You list 1 byte spacing. You really have not read any of the documentation, have you? :-( Run it by assigning to a button or keypress, then using that button or keypress, OR Run it by naming it ipcReady.lua, OR Run it by executing it like a macro in an [Auto] section in the INI file. Please please please use some of the documentation. It was hard work writing it. i don't want to have to do it all again here. Regards Pete
  6. My reply was to this: because the Java API for FSUIPC would apply to WideClient as well, as the interface is identical. Sorry, I missed the point that you are developing for Android. Of course there's no FSUIPC nor WideClient for Android, despite the fact that their interfaces are identical. So, yes, you'll need to write your own client. But a server can be quickly written as a Lua plug-in as the examples show. Regards Pete
  7. I don't think you need to be a programmer, exactly, but you'd need someone to do it for you who actually has that aircraft. There's no general solution. Each add-on is different. Your best bet is to see if anyone else has done it already (look in the User Contributions subforum, or in the add-on's own website). Pete
  8. You#d need to define variables with those names, then use those. for instance: ZoomIn = 65655 Zoomout = 65656 To have this pre-set for you in Lua for all 500-600 controls would take an extra 20k or more of stack space for each and every Lua plug-in running even if they used none of them. To do it using string names and have these looked up in a table could work okay but would be a lot slower. I'm really not sure it is worth it, especially since you'd usually need to look up the precise names in any case -- one character wrong and it would fail -- so if you are checking that from the document supplied you might as well use the number alongside it. Regards Pete
  9. Only that you won't be able to have any FSUIPC options or assignments etc saved when changed. I've not had time today, but I'll have a look at why the docked position isn't saved and restored when I do get time. It is on my list. Pete
  10. It'll be bug in the NGX then, as the complete set of offsets is merely a mapping of the data they supply. Please report it to PMDG using the name for that value in the .h file provided in your NGX SDK folders. Regards Pete
  11. Hmm. Axes don't work quite like that. However, you could do that with a Lua plug-in, allowing axis values through when increasing from 0 or decreasing from 0 but not when returning to 0. It would be quite easy. Have a look at the Lua facilities. if it looks too complicated let me know and i'll knock something together. I've got to go out now so it'll be a while. Max zooms can be handled by a max on the increment. Regards Pete
  12. No. SimFlight do not sell or supply FSUIPC. SimMarket sells the keys. They provide a link to the ZIP for downloading which is hosted here .The software is also downloadable directly from here (in the Download Links subforum) or over in www.schiratti.com/dowson. The link on the SimMarket page is identical to that on the Schiratti "Dowson" page. The versions in all correct places are kept slap bang up to date, and in fact all those links point to ZIP packages i have direct control over. Sorry, but I've not idea where you got an old copy from, but I respectfully suggest you check again. Maybe your internet supplier is caching old files and you need to get that cache cleared. Or go to Download Links and get use the link with the version number built in. Oh, also BTW, your wording suggests that you think you buy a specific version. You do not. You purchase either FSUIPC3 (for FS9) or FSUIPC4 (for FSX or P3D), but ALL versions. You are asked to keep it up to date if you want support because I cannot support old versions. Regards Pete
  13. I don't know that particular add-on, but I'm pretty sure it must be possible. You probably need to talk to other Wilco Airbus users. Do they have a forum? FSUIPC has many flexible assignment, mapping and calibration features and not many such problems defeat it. BTW you can install FSUIPC and read the documentation before you purchase in any case. You only need to purtchase it once you decide to use the user features. Regards Pete
  14. Hmm. Strange. What about when it is saved? I'll check the FSUIPC INI method here, maybe tomorrow. Pete
  15. I assume you are talking about FSUIPC axis assignments tab? Which version of FS is this, and which version of FSUIPC? Without information it isn't possible to help. Does FS recognise all 6? Does Windows? Are you sure there's no CH software installed which is already handling those axes? Have you tried CH support? Pete
  16. Hmm. Well if the RC4 PC is hard wired on the Network I'm afraid I've no idea why it has problems, providing FSX's frame rate is regular. Hmm. I've not seen any of that. There's almost nothing to say about FSUIPC weather settings -- only whether you want its additional smoothing or not. I can't imagine what else there is to discuss. It isn't like FS9 where there a loads of effective FSUIPC weather settings and ActiveSky actually uses FSUIPC so they are all applicable! Pete
  17. Ah! Great! It was only an experiment, so i'm glad it worked. no idea what 8.1 was doing differently! I'll release it in place of 4.920 tomorrow. Thanks, Pete
  18. If the plug-in isn't running it cannot do anything! There's really no such magic in the computer world. You show me the INI file before you removed everything and I'll check it, but without information what you say simply does not make sense. Pete
  19. This has been reported before. It seems to be Win8.1 only and i think it is SimConnect which it messes up. Please see this thread and try what I suggest. windows 81 rtm and fsuipc 491 crash/. Let me know please because the original poster there isn't able to test it. Pete
  20. There are virtually zero weather settings in FSUIPC for FSX when using ActiveSky which controls weather through Simconnect not through FSUIPC. Things like wind and pressure smoothing can be used as well as those in AS if you wish, but they have zero impact on performance. That will be due to traffic on the connection and overloading on the RC PC. Move ActiveSky off the RC PC. Certainly it would if that happens whilst running RC. But surely RC isn't even started till after that? A low end machine, Active Sky, RC and WiFI! Phew. Try hardwire connection first. Move AS second. I've used AS for years and have never had any "snapshots" loading when giving it any plan. Is that an option? Mind you I rarely give it a full plan, only the destination. Pete
  21. This seems to be a question for FSC support. Have you tried there? Pete
  22. You need to buy it. See the Installation and Registration Guide supplied with FSUIPC and follow the links, or just go straight to SimMarket and buy it. Pete
  23. Same answer, then. see above. Pete
  24. Did you check the FSUIPC log to confirm this? Without such information everything is pure guesswork. If SimConnect and FSX don't get enough processing time, there's no answer but to give them more -- a more powerful PC or less loading on the one you have. Pete
  25. Ouch! Don't mess in the INI file, just assign it in the Axis assignments. The stuff in the [Axes] section is encoded to access Lua files by number, just as in the Buttons and Keys sections! The LuaFiles section simply Lists the Lua files. It doen't do anything else. The numbers there are the references used in assignments. ALL of the Lua files ever seen in your modules folder will get listed there! Sorry i've no idea about that. Added to modules INI? What does that mean? You have to either start it in an [Auto] section, or run it by assigning a Key or Button to it. PLEASE please please read some of the documentation. Unless you elect to have a separate log file for Lua plug-ins (an option in the Log tab -- as documented) all logging goes to the FSUIPC LOG file, of course. 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.