Connection To Server From Wideclient

[chucksteinmetz]

I encountered a problem where WideClient.exe wouldn't connect to the server. After some troubleshooting, I discovered the cause:

If you start WideClient.exe using a shortcut that was dragged out of the WideClient folder, it won't connect.
It must be launched from within the WideClient folder itself.

I seem to remember dealing with this issue once before (a long time ago) and it may even be documented - I just didn't see it this time around.  This may be due to dependencies or configuration files (like WideClient.ini) that are path-dependent. Running it from outside the folder likely prevents it from accessing the necessary resources.

Hopefully, this helps others who run into the same issue.

[John Dowson]

That really shouldn't be the case...running via a shortcut should run exactly the same as running the exe directly from the installation folder - at least it always worked that way. Just tested with FSUIPC7 and it still works that way (i.e. it picks up the ini in the exe folder location, and logs to the logfile in the exe folder location). I can check with WideClinet at some point, but can you try again. Once you have a connection with WideClient (starting it from the installation folder), exit and re-start if via the shortcut - does it not still connect?

[chucksteinmetz]

Thank you for the note - I think the difference is that I 'dragged' the .exe file to my desk vs. created a shortcut (Send to Desktop).  I tested both ways and the shortcut worked, the file I dragged did not.  Chalk it up to operator error :).