danpaul88

I think a key difference from Renegade is the lack of the Hotwire / Technician type character (the mechanic isn't quite the same repair rate IIRC) and, of course, the additional players on the team to field them. In the days when Renegade had a lot of players a group of vehicles could hold position outside an enemy base and continually gain ground because they had dedicated repair crews following them round / riding shotgun, allowing the vehicles to continue attacking whilst being continually repaired. This meant that the defence advantage was slightly reduced since those new vehicles would be coming up against freshly repaired attackers all the time and the attackers could wage a war of attrition until the defenders ran out of cash for useful vehicles, allowing them to move in for the kill. Of course it also led to stalemate at the base entrances quite often of course and long games sat in front of an MCT keeping a building alive until your team got their act together and repelled the attackers. So whilst not directly comparable to APB, you can see how the dynamics of fewer players and less flexibility in on-the-go repairs has an impact on the gameplay vs how Renegade works. What we do about that I couldn't say - things like auto-repair when out of combat might help somewhat, I believe APB infantry have this and AR has it with veterancy.

I've created the following two issues based on the confusion over the user data folder; https://gitlab.com/w3dhub/w3dhub-launcher-net/issues/79 https://gitlab.com/w3dhub/w3dhub-launcher-net/issues/80 There is also an existing issue for adding a link to the actual installation directory https://gitlab.com/w3dhub/w3dhub-launcher-net/issues/77

Please upload a copy of the errors.log and diagnostics.log files from the Documents/W3D Hub/Launcher folder It's normal for the user data folder to NOT exist until you've launched the game for the first time and, in the case of IA, that link is probably wrong since IA puts the user data files in the install folder rather than in My Documents (and the launcher currently doesn't check for that when generating the user data folder link). As such, the error from that link is a red herring and can be ignored. (Just for reference, what the launcher calls the User Data Folder is not, and is not intended to be, the installation folder. It's the place where screenshots, chat logs etc go and for most games this is indeed in My Documents, but since IA sets the 'useRenFolder' flag to true it's user data files actually do go into the installation folder)

Lets keep this civil - the people who need to know already know what was done and subsequently undone, lets leave it at that and try to move forward in a more constructive way. This topic has gone off on several different tangents now (IA being a more complete Renegade client than we thought, server 'competition' & listing platforms, etc). I think it's high time to wrap this up and open more focused topics on those specific issues and leave behind the heated comments and whatnot which have accumulated here. I shan't actually lock this topic immediately incase anyone has any closing remarks or thinks I'm trying to shutdown the discussion but I hope people can follow these suggestions and open new topics for the relevant subjects.

That is not what I was lead to believe so I will certainly be chasing this up. Thanks for the information (for what it's worth, I don't think I've even launched a single W3D based game, Renegade or otherwise, for a good few years now!) With regard to mixcheck, I'm not sure we can do much about that since its basically designed to download all the data for any 'Renegade' client and would probably also download stuff if you ran it on APB, TSR, etc since, as far as I know, it just assumes any "incorrect" file is corrupted and needs fixing, so I don't believe there is any way to stop mixcheck just downloading a full copy of Renegade from whomever hosts that.

It's worth pointing out that 700mb is almost the size of the stock always.dat so I think whichever server you were joining was filling in the entire always.dat from it's ttfs. You might want to let the server owner know so they can fix that - it's not what ttfs is meant for.

I will look into this once I'm home from work - my understanding is that the IA client is meant to have removed all non essential files as they've been replaced by IAs own models, maps, sound effects etc. This should render it unable to join a traditional Renegade server. You didn't indicate whether, after downloading the map, the client was successful in actually joining the server? It's possible ttfs has advanced to the point where it can effectively bootstrap an entire copy of Renegade from an empty shell, which would raise some interesting questions for those server owners in that case as they'd effectively be supplying downloads of most of the game content. Worth investigating.

Firstly, let me to clarify this - the IA client downloaded by our launcher is *not* a complete Renegade client and cannot join Renegade servers. This was and remains an explicit precondition to our hosting of the downloadable client via our launcher. Until such a time as EA chooses to release Renegade as freeware we will not change this policy. In relation to the wider topic, it may help to consider that I am actively looking into supporting users joining stock Renegade servers using our launcher and their own installation of Renegade. Thisis tricky for the launcher as a lot of code was written with the expectation that it can install any game you don't already have on your behalf, so I'm in the process of adding interfaces which allow it to check whether these features are supported for a given application and adjust the UI appropriately when they are not. Thus your Renegade servers will also get the 'best of both worlds', as you put it. I also plan to provide an alternative presence reporter which can be used in place of GSA, allowing server owners to stop opening the GSA firewall port and reduce the amount of traffic hitting them asking for player counts etc. This will be an optional alternative. It would be great if you could work with us on this to provide the best experience for all players. I'm happy to answer any questions you have about how our infrastructure works and, as always, I remind everyone that feature requests, bug reports etc are always welcome via our public issue tracker - https://gitlab.com/w3dhub/w3dhub-launcher-net/issues

The launcher uses secure.w3dhub.com, not www. Also editing hosts files leaves you vulnerable to future IP address changes since it won't pick up new address from the DNS

You should also try typing ipconfig /flushdns into the command prompt

Please post the error and diagnostic log files from documents/w3dhub/launcher

Can you share a screen shot of the problem? Is this on the website or the launcher or somewhere else?

It's possible the forum image resizing code is outputting it as jpg - perhaps it deliberately doesn't allow alpha in profile images

Make sure to save it as PNG because jpg doesn't support alpha channels

The launcher queries Windows for all the supported resolutions for your monitor and lets you pick from those - it's not got a built in list. So if whatever size you want isn't listed that's because Windows doesn't think your monitors support that size