Firstly, I'd like to state that neither of the links in this post is intended to explicitely advertise for any external site; as opposed to this, their mere purpose is to relay to relevant information, the posting of which here directly may have proven cumbersome, or otherwise inconvenient.
(I included this disclaimer, staying aware of the fact that the rules of these forums seem to be rather picky in regards to linking to other sites, and as much as I'd like to rely on the common sense and reason of the admins, I'd rather avoid getting myself banned for some stupid reason ).
Strictly speaking, TFD patched with the 1.03 patch is not a completely *fresh* install anymore. However, I had not heard anywhere of any outstanding issues pertaining to the current release of the 1.03 patch, and you can trust me when I say that I always try to stay informed and do some research first.A fresh install of TFD does not include patch 1.03.
I have notified Nathancnc, who maintains TFD 1.03, of the apparent problem; he was not aware of its existence beforehand. Well, it seems no one really was. How this can be is still beyond me, as this custom WinSock library from Scorpio9a has been around for roughly a year already. And, given that it seems to be the only currently existent fix to make local networking for RA2 etc. possible without having to rely on the oh how hopelessly deprecated IPX protocol, I have good grounds to assume that its usage is fairly widespread amongst dedicated C&C fans (even more so after release of TFD 1.03 patch), and I am certain there are enough of them concerned about both LAN and XWIS online functionality. As I have been playing on XWIS only for a short time, I had not encountered the problem before, but the contents of the Help Archives, such as here, easily prove that this problem had been reported before, and the reason already had been tracked down to apparently have to do with the custom WinSock dll. Unfortunately, this fact did obviously fail to receive the acknowledgement it definitely should have.
While I completely appreciate DonCarlo's statement that sticky topics cannot be made on everything, here are three quick reasons why I still think there should be one here on this problem:
- It has severe adverse impact on RA2 (YR and TS still to be confirmed) online play on XWIS;
- It seems to originate from a widely used fix providing extended LAN functionality;
- It affects RA2 (and, potentially YR and TS) regardless of whether the game is standalone, or part of TFD.
- Workaround: For the time being, here you can obtain my current workaround; it has the form of surrogate launchers for RA2 to be used for online play (need to be placed in RA2 main folder). Each of them will ensure that RA2 will not use the problematic dll, allowing for smooth online play, while the LAN fix still remains in place when RA2 is launched normally. Should you wish to, feel free to post this on the Strike-Team site (needless to say, I guarantee the files are 100% clean).
- Fix:
Sadly, no one I have spoken to seems to know how to contact Scorpio9a... however, I seem to recall having read somewhere that you once worked with him on some network stuff for Renegade, could it be possible for you to get in touch with him? If so, it'd also be great if you could mention to him that implementing a method to select which network adapter to use (like it was the case with IPX) would be most appreciated (if that's possible, that is); these matters were discussed in a few topics in the old Command & Patch forums (these are possibly gone due to some technical problem, which fact sucks big time, but hey, that's life) and currently the only viable way to succeed with LAN play over VPNs seems to involve applying a workaround, as outlined here.Has anyone notified Scorpio already?
I created another topic because, at the time I realised the problem still persists, the original one had already been archived and closed. Similarly, I'm replying to you in this thread, as for the same reasons I wasn't able to post in the thread you commented on anymore.BTW, there was no need to open yet another topic and you still write way too much.
Finally, whilst I'll eagerly admit that my posts may tend to be quite elaborate at times, I am taking great care to keep them meaningful rather than pointless, and I strongly hope that you'll agree with me on that Please note that, in this way, I am devoting my time to convey information to others, and if people fail to recognise this and refuse to devote their time to read it, I guess it can't be helped... On the far opposite, we can encounter uncounted numbers of posts merely consisting of one or a bunch of acronyms, and as for myself, I undoubtedly prefer to read one meaningful post, rather than reading a thousand of "lol"- or "rotfl"-ones...
In the unlikely event that I'm still misunderstood, I'll take the liberty to illustrate with a tiny sketch of mine (yeah, let's have some humour here, too)...
"Hey, the author of the Readme File is writing way too much... let's skip it "
(half an hour later...)
"Heck, why isn't this working...? Grrrrrrrrrr... "
[I-¦34\/1l`/ p\/\/¦\I3¦) 8`/ 0I\¦353lp¦-I]
Once again, thanks for your time, and all you have done this far. All the best for the future.
Kind regards,
Antares376
Edited by Antares376, 08 April 2009 - 08:53 PM.