Jump to content
The simFlight Network Forums


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About d3h872

  • Rank
  • Birthday 01/01/1970

Contact Methods

  • Website URL
  1. That was just my latest iteration. I've tried Com1 on the laptop as well.
  2. I've tried a bunch of times to get my Garmin 196 working with FSX as I did with FS9. I have a clean connection to the FSX computer. I've tried using the Port=WideFS as well as using the virtual serial port through my laptop. I get this from the WideClient log: ********* WideClient Log [version 6.70] Class=FS98MAIN ********* Date (dmy): 14/11/06, Time 20:27:25.531: Client name is PT13547 250 Opening GPSout port WideFS, speed=9600 -- FAILED! Anyone know what is causing this to fail? My firewall is off. From FSUIPC4.ini (registered): [GPSout] Port=WideFS Speed=9600 Interval=1000 PosTo6Decimal=Yes Sentences=AV400 GPSoutEnabled=Yes And from WideClient.ini [User] Log=Errors+ [GPSout] Port=WideFS Sentences=AV400 Interval=1000 Speed=9600 Thanks in advance for any thoughts. iniFiles.zip ClientAndServerLogs.zip
  3. I'll have to look later to see whether the AdvertiseService line was left in. Not being a programmer, I'd tried a lot of permutations, so I don't know where I left it. I'll be out of town for a while.
  4. I changed the Protocol=TCP in the wideClient.ini config section -- seemed to do the trick. (I at first changed the workgroup to match, and it seemed unaffected.) Ryan
  5. Actually, I'd tried both. Done. Done. Resent. FS Computer (Server) Windows XP Pro, fully updated, firewall off. Dual-core 2.4 GHz AMD 2 GB RAM Client Computer Windows XP Pro, fully updated, firewall off. Dell Latitude D610 1 GB RAM
  6. Tried AdvertiseService=0. Tried adding server name to wideClient. Nothing :!:
  7. Ah, Peter's first mistake was listening to Microsoft. :shock: I can't get wideFS to work on my machines. I paid for FSUIPC and WideFS. I read ALL the documentation over and OVER! I've turned off my firewall. I've viewed my logs: ********* WideClient Log [version 6.70] Class=FS98MAIN ********* Date (dmy): 26/10/06, Time 12:19:51.455: Client name is PT13547 140 Attempting to connect now 1140 Trying to locate server: Protocol not yet decided 1140 Failed to connect: waiting to try again 3140 Attempting to connect now 67203 Trying to locate server: Protocol not yet decided 127625 ****** End of session performance summary ****** 127640 Total time connected = 0 seconds 127640 Reception maximum: 0 frames/sec, 0 bytes/sec 127640 Transmission maximum: 0 frames/sec, 0 bytes/sec 127640 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0 127640 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) ********* Still can't connect. I've looked at all other posts. And in them you insult people's intelligence as you sound off from your soap box. So you can understand why I don't bother posting the question to your "support" forum: after a couple posts, you just refer back to your dear-gawd-it's-so-bloody-brill documentation. Prove me wrong.
  8. IMNSHO, the documentation is lacking and terribly verbose. (No, that's not an oxymoron.) And the apps could benefit from either a better interface or the existence of an interface!
  9. What you have to know is that Peter is very proud of his products. And he should be -- they do stuff that helps us out a lot. But you should also know that he's a grumpy old curmudgeon, and he can't write documentation to save his life. (If it makes sense to him, then it just has to make sense to everyone, right?!)
  10. Mine looks quite similar, sans the RW stuff. I think what was most confusing was finding the difference between KeySend and Send Key, which is what I assumed was the case. It's all so simple and clear, once that distinction is made. Thanks for posting your info. Here's hoping that Flight Sim X works as well (which is supposed to handle online ATC, from what I understand). Ryan Scott
  11. For you users looking for the answer: This was a simple post from a user in another forum. Although the RW KeySends are unnecessary, this method (and specific instructions) works great. - Ryan Scott
  12. Your complete lack of courtesy is unfortunate. I am a paying user, and I have worked long and hard to comprehend your stilted application. To be rebuffed in such a way has made it impossible for me to recommend your products to others. I'm an interface designer by trade. This interface is, at best, lacking; the fact that one is forced into gargantuan, verbose documentation says it all. Do not attempt to improve the documentation -- vie to improve your interface and the documentation will become almost unnecessary. The one compliment I must pay you is your responsiveness. If your quickness to respond means doing so in the heat of your frustration, however, I suggest providing slower, less vehement responses down the road. With hope for the future, Ryan Scott
  13. I've looked at the documentation for hours, especially concerning KeySend issues (even before asking for assistance) -- and I have spent many more hours in troubleshooting this single problem. Do not question my efforts: you have no way of knowing just how much time I have spent on this single great frustration. Please try to remove any emotional reponses you may have in your posts; it only serves to cloud the issue. I realize you have built a powerful tool, and I'm trying to learn it. You describe the mechanisms by which I am to have clients respond to the keysend, but an example would be most helpful. I've seen this example in another forum, but I am having trouble understanding (1) what the number following the comma means [though I have a vague interpretation, this is where the documentation begins to lose me] or (2) how to set up FSUIPC to "send key number 123 (F12)," for example: KeySend1=123,16 ; Press F12 KeySend2=123,24 ; Release F12 Thank You, Ryan Scott
  • 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.