Fffreak9999

I've locked the previous one, and will merge them into this one later

Since the only one I can currently see is AGN's

@Cronus - I just checked, I am not getting the banner when I look on the launcher. Is it still pointing to our old IP address?

Thanks

One for CT. 145.239.130.118

Potentially could be something along the lines of particular graphic settings.

We can use Dyno (discord bot) for this. Like we currently have in the CT discord to choose a role of Plays: (X), you can limit it to 1 per user, they can choose the role they want and stick with it, or if they want to be a different role on another pug, they can just change their active role using the bot.

DefaultRenegadeX.ini is what UDKRenegadex.ini is based off, meaning the default overrides the normal where key information doesn't match. Also I haven't had any issues with settings changing either.

The only INI I had change yesterday was UDKRenegadeX.ini, which holds version information, and since the version changes every patch, it has to alter this file.

I've not encountered anything like this even after doing multiple commander switches.

What system is flagging this as dangerous?

It will by default load the 32 bit client, if you wish to load the 64 bit client, you will need to use the \Renegade X\Binaries\Win64\UDK.exe This should be more than sufficient for most cases, as you can look through the in-game browser. If you need to enter a password protected server, it is a little more difficult. You would need to use the following command line open <Server IP>:<Server Port>?password=<Password>

The server list is indeed down, this is not a problem on any individual client.

Please don’t necro threads when there exists a main thread for this.

Neither of those 2 categories apply to me then

Try checking the option boxes for Graphics in the menu, and search for things like Dynamic lights and other things like that. Try changing a mixture of them until you find a stable solution.

Honestly, there are problems with straight up disabling the use of beacons when under a player limit, since if a person quits after another player buys a beacon which then drops the player count beneath the threshold, they have effectively lost 1k credits until another player joins (or is killed) (and in a low pop game, that can be quite significant).

@Redarmy - Can you try this on the PUG Server, I will load this map up for you. If it crashes the server, it would be good to know. Edit: Redarmy has provided log files from his client from NetPlay and Skirmish. I will grab the server logs when I get home Launch.log Launch-backup-2018.02.07-11.22.27.log

All feedback from this post onwards should be for Patch 5.32.

You have already posted this in another forum, Locked

True, but its probably too much work for little to no benefit. Also if a person gets killed by their own airstrike, they probably deserved that death

There is little reason to worry about that though. The enemy is not privy to that information, since if they fail to notice the big green pointer coming from the casting unit, they don't deserve to know. Also allies don't need to worry about it, since they are not injured by friendly fire (Unless by bugs)

There already is a >>>>>> symbol for GDI

I know this is outputted to IRC, so it should be rather easy to implement a player feedback (other than the receiving target). You can use the console to rebind it, but again should be somewhat easy. You can do this anyway, its in your config files in UDKGame, just take a copy of them before doing an update/re-install, but know that some files cannot copy over without causing you issues. Such as UDKRenegadeX.ini (which holds version information). Your section for "Friendly Airstrikes" (Assuming a non-commander power version), this would be different to how they behave, since GDI have directional airstrike. You could implement it for Nod though, since they just hit an area, not a line based attack like GDI. Otherwise, should be somewhat good QoL changes

Unfortunately even disabling the AFK kicker in the settings, doesn't truly disable it. You remain "dead" in spectator mode and it kicks dead players after a short while. I often use Kill player to check if the person is active, because if they respawn during that time, then the AFK kick timer is reset