Jump to content
The simFlight Network Forums


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About DLuis

  • Rank

Profile Information

  • Gender
  • Location
  1. Hi, I've tested my software and the "wideFS Test.exe" with the WideClient7140 and guest what??? IT WORKS, WOW, EVERYTHING WORKS NOW :D So, what can I say, you are the one that invented one of the "must have" Add-ons and still keeps this project alive and running. AMAZING. Maybe is just me that don't like to see a "process.exe * 32" in the Taskbar Manager, but you make it possible, a 64-bit talking with a 32-bits and it's working like a charm. I'm going to still test my software and if I find something, will let you know. All that I can say now is a big thank you Pete, from now on It's possible to have 64-bit compiled software working with FSUIPC and WideFS.
  2. Hi Pete, I'm really sorry, the private message stay in the drafts. Meanwhile, I've tested with the WideClient7130, but the result is the same. It just work if I made one FSUIPC_Process for each FSUIPC_Read. I've compiled a 64-bit program (no password protected...) with all the reads that a make in my software, 11 FSUIPC_Read in a total of 18 Bytes. It display the returned values once. In the server side, work great, but not with WideClient. Try to test and tell me if works with you, because can be something wrong with my setup. WideFS Test.zip
  3. Hi Pete, I send you the password in a private message right after my post. Tomorrow I will test with the new wideclient and let you know how many FSUIPC_Reads are possible before the FSUIPC_Process. So far, only one, the reason why V2 works.
  4. Hi Pete I've finished my program and it's a privilege to share with you. There are two version. V1 is the one that only works in the "server side". V2 works in server and client with WideFS. The source code that is reference to FSUIPC is also in the attachments and a "how it works" explanation. The difference between V1 and V2 are the number of FSUIPC_Process calls. https://1drv.ms/f/s!Aso3Tkv5pPmGar6mvGQRhMsvQY4 Thanks a lot for the attention.
  5. Hi Pete, What a great news, really very happy to see this effort. I already compiled my software with the new source code (can't use the lib because I'm using Code Blocks with GCC x64 compiler) and WOW, my 64-bit now connects like a charm and read/write offsets with the provided WideClient 7110. With this change, I believe that more people will start to program native 64-bit software. Now I believe that a have a code problem. I'm calling FSUIPC_Read 12 times (total of 20 bytes) before calling the FSUIPC_Process. In the "server side", everything works great, but in the "client side", not really. How many calls of FSUIPC_Read or total of bytes (DWORD size) can I make before the FSUIPC_Process in the 32-bit WideFS?
  6. Wow, what a quick response. I don't have any kind of hurry, besides, just to know that within days the WideFS maybe is compatible with 64-bit software is amazing. I could program in 32-bit, but since I'm going to start from scratch, why not in 64-bit, since in these days most of the software are. Once again, thank you for the quick response.
  7. Hello, I want to make a 64-bit software (from scratch), so I tried the connection with WideFS that I've downloaded the from schiratti.com and I made this simple test: Opened the WideClient.exe, then UIPChello.exe and I get the message "Maybe running on WideClient, but FS not running on Server, or wrong FSUIPC". Since FSUIPC was not running, I believe that UIPChello.exe connected correctly to the WideFS. But when I made the same test with UIPChello64.exe, I get the message "Cannot link to FSUIPC or WideClient". Well, since WideFS is a 32-bit, i believe that is not possible to connect 64-bit compiled software to WideFS. If so, can someone tell me how? If not, is there a 64-bit WideFS or will be?

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.