Jump to content
The simFlight Network Forums

Pete Dowson

Moderators
  • Posts

    38,265
  • Joined

  • Days Won

    170

Everything posted by Pete Dowson

  1. Generally things which use FSUIPC don't get loaded by SimConnect (which is what DLL.XML is primarily for), and do not get "trusted" or otherwise by FS -- because FS is not aware of them. they interface through FSUIPC, not directly to FS. The installer has no Network related code in it whatsoever. However, all my products are codesigned, so maybe all this is to do with the Windows trust mechanism. maybe there's something missing in your Windows setup and it doesn't have the correct trust authority certificates installed. At least two of the sites you mention are Trust Authority sites (Cybertrust and Verizon are part of the same Trust Authority I think). CloudFlare is listed as "a content delivery network and distributed domain name server service marketed as improving website performance and speed and providing security", so perhaps relates to this as a DNS source, But where Telecom Italia Mobile comes into it I've no idea. Check the Install log file. If the installer finds the needed certificates missing it automatically runs a little program supplied by GlobalSign to fix that. Right click on any of my signed programs (the Installer or the DLL itself), select "Properties" then "Digital Signatures". Select the signature and click "Details". Make sure it tells you that the signature is ok. Does this process try to access any websites? If the signature is not confirmed as "ok" then the file has been tampered with or become corrupted. Pete
  2. There is no code in FSUIPC which has any possibility of connecting to the Internet, and there never has been. Then something else which relies on FSUIPC being installed for some other purpose is doing this. It is an absolute certainty that it is not FSUIPC itself. Regards Pete
  3. Sorry, you mean the whole thread? A lot of the stuff at the start doesn't belong there. Which parts are you talking about? The first XML Gauge solution is already posted on that subforum. Regards Pete
  4. Sorry, I really do not want to add more facilities to FSUIPC except where they are not practical any other way. This is why I implemented the Lua plug-in facilties, so folks xcould add their own little utility facilities and so on. A small plug-in could do it easily enough. There is a standard Lua function "os.date" which returns date and time -- in fact optionally UTC (Zulu) time, which would fit the bill very well. This sort of thing is also done quite well by other programs, as well as FSRealTime -- such as Aivlasoft's EFB data provider, for example. Incidentally, there's no way I know for me to check someone's legitimate purchase or even existence of other programs. Regards Pete
  5. I can't really support other folks' software, so this is really a question for FTX/Orbx. It sounds like you are using scenery designed for FSX specifically and it includes a module which does not recognise P3D. It may or may not matter -- try ignoring the errors and carrying on. Otherwise you must ask FTX. I don't have any of their sceneries and I don't use P3D. Regards Pete
  6. Sorry, but that is old and unsupported. The current main release is 4.827, with updates up to 4.839b available in the Download Links subforum. Well, if assigned they will be sent. You can check by logging button and key events (FSUIPC logging tab) and viewing the Log file. But update FSUIPC4 first please. Pete
  7. If it says it is not valid, then there's no point in repeating the same over and over. Either you are making a mistake when entering your name, email or key (use cut and paste if you are not sure), OR you purchased the wrong Key -- e.g. an FSUIPC3 key instead of FSUIPC4. [LATER] I just checked, and you did buy FSUIPC4. Your key is correct -- I just checked it here -- so you are making an error in one or other of the three entries. Regards Pete
  8. Thanks. I've taken the liberty of reformatting the code parts to match the original formatting. Okay, thanks! Pete
  9. Too many images? Sorry, I don't understand that. Maybe the cut-and-paste doesn't preserve some of the quoting correctly? You probably need to go into Edit mode on your original and copy from there, then paste into a new-thread-message in the SubForum. Obviously you need to create the new message with an appropriate title in order to paste into it. You can't past a thread or message. Regards Pete
  10. Thanks. That's very clever. I didn't realise you could do gauges purely with a short XML file like that. This thread will scroll off out of sight again quite quickly, which would be a shame. D you think you could re-post to the "User Contributions" subforum, with a suitable title, so it is saved and more readily accessible to others? I could do it, but I think it should be in your name. Thanks again! Pete
  11. Are you talking about assigning FS controls in FSUIPC? You don't provide the context. If you are using FSUIPC, what version? And where are you programming it, and to what controls? What exactly do you mean by "key commands"? Regards Pete
  12. Sorry, no. I don't understand. FSUIPC of course scans joystick ("directInput") devices on initialisation, and also when you go into FSUIPC options, but this really does only mean joystick types, not all HID devices and certainly not all USB devices. Neither of the ones you are concerned with are classified as joysticks (which interface has no display options in any case, of course). There are COM and HID programming facilities in the Lua libraries -- LINDA uses these to handle many devices. Have you looked at using LINDA? Regards Pete
  13. Never heard of them. Are they keyboards, or joystick-button devices? [LATER] After Googling them I see they are just programmable keyboards -- so, just like your normal PC keyboard except you can ptogram sequences and key combinations et cetera on some or most (don't know) of the keys. Since you can program FS functions on a normal PC keyboard I'm not sure hat advantage one of these would offer, except possibly more of the same? I can't see how they could possibly compete with proper switch and button modules like those from Goflight. Regards Pete
  14. That only appears if the place on screen you click with the mouse is valid for mouse macro creation. Not many are these days. Only gauges made strictly to the Microsoft C/C++ gauge SDK are amenable to mouse macros. Most new FSX aircraft panels are designed using XML, and are not amenable. Many use local gauge variables, though (L:Vars)., which you may find useful. Check out examples in the User Contributions subforum. Pete
  15. I think you have a bad misunderstanding. Offset 6506 is ONE BYTE containing the Captain's Master Warning, and there's a second BYTE, at 6507, with the First Oficier's Master Warning. I thought I already explained this. BYTE values are one BYTE each, not two! You needn't test individual bits. Each byte with be TRUE (non-zero) or FALSE (zero) according to the indication. Sorry, I can't help with SIOC parameters. I know nothing about this program. Pete
  16. Sorry, but FSUIPC does not support Saitek displays. You need to talk to Saitek support. Regards Pete
  17. One thing you can do, which their support should really have thought of, is to enable ipc Read logging in the Logging tab of FSUIPC. Make sure you are using no other FSUIPC-interfacing applications, so that all the logging is related to VAFS 5. Then you or they can see what it is actually reading, or even whether it is reading anything, from FSUIPC. I can help them work out what is going on but they'd need to look at it first because they should know what the program is doing. I wouldn't be able to tell if it was reading what it wanted or not since I wouldn't know what it wanted. Regards Pete
  18. It sounds like it certainly is usng FSUIPC, and creating a display window via FSUIPC too. This must mean it isn't a problem of privilege levels, or it would not be able to link up in the first place. But as to why it then fails I couldn't say -- FSUIPC is running okay according to that log. You do really need VAFS 5 support for this. I'm afraid I cannot debug other folks' programs, and especially ones I do not even use. Regards Pete
  19. That's fine, nothing wrong with FSUIPC's operation. FSUIPX is a module of FSX, it runs as part of FSX. you can't have different parts of a single program or process running at different privilage levels. You run FSX "as administrator" or you don't. Whose "Configurations Settings" file? You need the filename. FSX has many such files, like FSX.CFG. FSUIPC's is called FSUIPC4.INI. Looks like it uses FSX windows -- that's just the pixel position and size. without knowing the file it is in I can't help further. What's the date on the file? If you cannot run the program now, that's presumably an old relic or when you could run it? Pete
  20. Sorry, what do you mean? Where there are two BYTE values, they asre separate values -- usually one for Engine 1 and other for Engine 2, or maybe one for Captain and one for First Officer. They are still BYTE values, just more than one. Pete
  21. Okay. Don't forget you need to make the small required change to a PMDG ini file, to allow the data to be supplied to FSUIPC. There's a note in the document about it somewhere. Regards Pete
  22. I've no idea how to use SIOC, but all the data values which can be provided for the PMDG 737NGX, if you've configured it correctly, are mapped into FSUIPC offsets, and those offsets are all listed in the document included with all recent FSUIPC updates. The facility was added in FSUIPC 4.82 soon after the PMDG SDK was published. The current FSUIPC interim update is 4.839b. See the Download Links subforum. Regards Pete
  23. Something is screwed up on your Network, or in the parameters you added. I've never seen this Windows error before: 2715 Trying TCP/IP host "FSX" port 8002 ... 2715 Error on client gethostbyname() [Error=11004] Valid name, no data record of requested type I googled this error, and possibnly the best list of possible causes is shown on this web page: http://www.instantte...error-11004.php Is that IP address correct for your FSX PC? (192.168.1.10). You could try deleting the "ServerName=FSX" line in the INI and instead using "ServerIPaddr=192.168.1.10". Next time please show the WideServer.log from the FSX Modules folder too. The Client log is only half the story. Regards Pete
  24. As far as I can see, looking at the VAFS 5 web-site, it doesn't use FSUIPC. At least I can't find it mentioned there. I think you need to use VAFS 5 support to investigate your problem. One of the things I do see mentioned on their website is the instruction to run the program "as administrator" all the time. I've no idea why they need this, but if it does use FSUIPC after all then running an FSUIPC application "as administrator" with FS not running "as administrator", or vice versa, will certainly prevent any communication between the two -- Windows prevents programs of different privilege levels sharing data in the manner the FSUIPC interface requires. That's normal. I can't really help any further, but I can check that FSUIPC is operating correctly from the FSUIPC4.LOG file which you could paste here -- you'll find it in the FSX Modules folder. Close FSX down first. Regards 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.