ACE 1.3m have problem

[Patrick Bateman]

I don't see here official release of version 1.3m, but on SOP Snipers New Stalking\Camping server it is already present and kicks me for having Launch.exe - Sebastian 'Hanfling' Kaufel's UnrealEngine Custom Launcher for dealing with AMD Cool'n'Qiuet CPU frequency change. It is a very old file that i use much more than a dozen of years and all previous ACE versions didn't react on it. Now 1.3m kicked me for that. Please fix it.

ACE1 3m fail.png

[SilverSound]

Update to version 469e. You shouldn't need any sort of launcher to run the game anymore.
Otherwise to join that server you will need to remove the file. This isn't a bug.

[Patrick Bateman]

Update to version 469e. You shouldn't need any sort of launcher to run the game anymore.
Otherwise to join that server you will need to remove the file. This isn't a bug.

How can i remove the file - it is basically renamed and modified UnrealTournament.exe. Do you understand what are you saying?

Update to version 469e

I don't wanna.
Why all previous ACE versions didn't have problems with Launch.exe and 1.3m have problems? Just put Launch.exe in WHITE LIST !

[SilverSound]

Nope. Sorry. We can't help you. You must update/remove the file in order to play on new ace servers.
This will not be whitelisted.

Stick to older server versions. You have no reason to use that launcher with an updated game patch.

[Patrick Bateman]

Nope. Sorry. We can't help you. You must update/remove the file in order to play on new ace servers.
This will not be whitelisted.

Stick to older server versions. You have no reason to use that launcher with an updated game patch.

I do not use 469 patch at all. Thus why i use Launch.exe with my 451 version of game.

This will not be whitelisted.

Why not? 1.2e have no problems with it.

Stick to older server versions.

Stick to what? Meaning?

P.S. Are you a part of anth team that create ACE and 469 patch ?

[SilverSound]

451 is generally a bad client patch and is more for servers to run. This was before the latest patch version released though.

I'm a patch tester and work with patch devs to fix and find bugs. The launcher you're using isn't needed anymore with the latest version of UT.

For now you will have to avoid servers running ace 13 as long as you use that Launcher.

If you want to join a ace 13 server you can update with the latest release patch to gain your UnrealTournament.exe back.

If you want to re-install your game go to OldUnreal.com to get the UT99GOTY full game installer.

[Patrick Bateman]

451 is generally a bad client patch and is more for servers to run.

I know that, i play UT99 more then 20 years. This thing (451) work for me so why should i bother...

I'm a patch tester and work with patch devs to fix and find bugs. The launcher you're using isn't needed anymore with the latest version of UT.

So you are not developer. I am interested in what anth will say. Also his last post here was in 2023 i hope he will find time to answer here. Adding Launch.exe in WHITE LIST is no big deal in my opinion and will not broke things.

Also i want to say, that when, you guys started with 469 you many times said: "it will be compatible with 436\451". And now you do broke compatibility with basic things that used for more than a decade, and your answer is: upgrade to 469. I see a stubborn people who could not do even one step back and be more humble.
Through many years you never fixed one thing that bothered me the most in online UT99 gaming - you can not edit your message, you need to delete text until cursor got to place in text you want to edit and then you should type what you deleted again. Quake 3 allow edit text messages without deleting it in 1999. And you still can not fix it in 2025!

[SilverSound]

Join the discord https://discord.gg/gACqxmRX


The bug you claim with text was fixed in 469e. The bugs you are encountering are BECAUSE of your old version. There are people in the discord server that are willing to explain things to you in ways you'll better understand.

All you have to do is install the latest patch and your issues will go away.


Also 469 IS compatible with previous versions. Your issue with ACE kicking you is because the ADMIN updated ace. That's just how things go.
That has nothing to do with the new patch.

[Metallicafan212]

451 is generally a bad client patch and is more for servers to run.

I know that, i play UT99 more then 20 years. This thing (451) work for me so why should i bother...

I'm a patch tester and work with patch devs to fix and find bugs. The launcher you're using isn't needed anymore with the latest version of UT.

So you are not developer. I am interested in what anth will say. Also his last post here was in 2023 i hope he will find time to answer here. Adding Launch.exe in WHITE LIST is no big deal in my opinion and will not broke things.

Also i want to say, that when, you guys started with 469 you many times said: "it will be compatible with 436\451". And now you do broke compatibility with basic things that used for more than a decade, and your answer is: upgrade to 469. I see a stubborn people who could not do even one step back and be more humble.
Through many years you never fixed one thing that bothered me the most in online UT99 gaming - you can not edit your message, you need to delete text until cursor got to place in text you want to edit and then you should type what you deleted again. Quake 3 allow edit text messages without deleting it in 1999. And you still can not fix it in 2025!

Official OldUnreal developer here (I lurk in the discord server(s) not the forums, so I didn't have an account until now).

The issue you're having here is not with 469, it's with ace. 469 has and always will continue to have compatibility with 436/451. Ace is a separate item, and starting with the newest versions, blocks before 469 as a security measure. There's too many native hacks out there, and 469 has more built-in protection that ace leverages, it's not easy to keep an anti-cheat going for a codebase you can't even "touch" (stock 436/451). Custom launchers aren't a part of this scope, they're excluded because they can be modified to inject items into the game. At this point in the game, blindly trusting users isn't good enough.

Now, onto your gripes: in 469e you can cursor just fine in the console or the in-game chat. You can insert text or delete only specific characters all you want. 451 is a "bad" patch because it breaks many things, the editor included. It wasn't meant to be the final UTPG patch, but the next patch was canceled, so the community was left with the broken and half-finished patch until OldUnreal picked it up.

If you have further questions about ace, the patch, or anything compatibility-wise, I suggest reaching out to us on discord, as there's a HUGE community of UT players there. It's mainly where people talk and interact these days.

[sektor2111]

Quake 3 allow edit text messages without deleting it in 1999. And you still can not fix it in 2025!

Probably more things won't get solved soon - they don't understand this chapter (perhaps don't want to...)
UT469d
- PlayerCanSeeMe was sanitized but it's the same piece of crap as it was since day 1 - look at U227/XC_Engine - those are BETTER fixes;
- In MonsterHunt some creatures in MyLevel are not shown according to their class-name "BomberTentacle" it's "Tentacle" an so on - WinXP version;
- UScript works slower and I don't see anything improved at this point ->

Code: Select all

EndTime = Level.TimeSeconds + 3.0;
	for ( P=Level.PawnList; P!=None; P=P.nextPawn )
	{
	...
	...
	}

It happens because there is no access at any clocking system even if in Engine's natives there is TIME support since day 1... but XC_Engine demonstrated what sort of codes are used.

Next... in 469e there are no major changes... but there is not XC_Engine support over there due to X changes done which makes every single update incompatible with it.
Note: XC_Engine is a good tool "anti-moron". When mapper has no time to wrap his brain, XC_Engine can access paths and solve X issues during map's run-time (and not only there...). Also XC_Engine still does replacements for natives demonstrating that these weren't really fixed.

469e RC7 - playing a map with no lights - using zone lightning (flat lightning). After going in Window mode and then back to full screen everything is dark/black - only flag is visible (using OpenGL - NVidia k600 WinXP). UT440 doesn't have such problems with OpenGL.

After 469 coming with new problems, if ACE brings new ones then clearly I won't play On-Line and probably and update is postponed for undefined period.

[Metallicafan212]

Quake 3 allow edit text messages without deleting it in 1999. And you still can not fix it in 2025!

Probably more things won't get solved soon - they don't understand this chapter (perhaps don't want to...)
UT469d
- PlayerCanSeeMe was sanitized but it's the same piece of crap as it was since day 1 - look at U227/XC_Engine - those are BETTER fixes;
- In MonsterHunt some creatures in MyLevel are not shown according to their class-name "BomberTentacle" it's "Tentacle" an so on - WinXP version;
- UScript works slower and I don't see anything improved at this point ->

Code: Select all

EndTime = Level.TimeSeconds + 3.0;
	for ( P=Level.PawnList; P!=None; P=P.nextPawn )
	{
	...
	...
	}

Next... in 469e there are no major changes... but there is not XC_Engine support over there due to X changes done which makes every single update incompatible with it.
Note: XC_Engine is a good tool "anti-moron". When mapper has no time to wrap his brain, XC_Engine can access paths and solve X issues during map's run-time. Also XC_Engine still does replacements for natives demonstrating that these weren't really fixed.

469e RC7 - playing a map with no lights - using zone lightning (flat lightning). After going in Window mode and then back to full screen everything is dark/black - only flag is visible (using OpenGL - NVidia k600 WinXP).
After 469 coming with new problems, if ACE brings new ones then clearly I won't play On-Line and probably and update is postponed for undefined period.

469 can't do XC engine type changes because those break stock content/maps. 470 will integrate more changes and will be more 227 style with real behavioral changes, but there is absolutely no timeline for 470.

Also: for your issues, where's the github ticket? CacoFFF would need to investigate GL issues if it's with the 469 GL driver. We don't magically know every issue, nor do any of us actually have active XP machines to test on. Hardware that can natively run the OS is getting harder and harder to maintain these days, especially if you don't have space for it.

[SilverSound]

Feel free to report any and all problems to the github repo. We are always constantly trying to find and fix said issues. The next best thing is to join the discord because that's where patch devs and testers (and really a lot of the community) reside.

Stop bringing up XC engine, it's a terrible way to go about fixing issues with hacks.

Windows XP is way past end of life and definitely won't be supported post 469.

individual Render issues can't be confirmed unless you run version 469e with the latest included renders. Any and all bugs found should be reported to the individual render devs. (again active on discord)

Not a single person is testing against a b c d because 469e is the latest. so any and all bugs you are talking about MUST be replicated on the latest released version. otherwise you are just posting to the wind.

[sektor2111]

469 can't do XC engine type changes because those break stock content/maps. 470 will integrate more changes and will be more 227 style with real behavioral changes, but there is absolutely no timeline for 470.

Oh well... XC_Engine or such optional extension could be embedded directly in 469 - it doesn't change maps (files) but allows doing some changes exactly as STOCK UT does in maps like CTF-Coret and DM-Pressure.
I did patches that work in separate format. Paths, Events etc are Server-Side, the rest of visuals are going only for client - all done in prior UT variants before any 469, to not forget the superior power of DevPath used by XC_Engine capable to handle maps in 436/440 where any 469 have no deal in stage except where XC_Engine might be used. Unfortunately XC was not really ready and it needed some dodging - disabling several features but as average you can run a comfortable server and client game. For me disabling it will be a major loss, I do not have plans to get rid of it. AND for ACE's "attitude" - certain patches for clients made ACE to reject client for "miss-behaving" when actually those packages were sent by server itself and they were done exactly for such a purpose (lightning tweaks, etc.) there was no reason to kill player that way - because player used what server has sent.

[Metallicafan212]

469 can't do XC engine type changes because those break stock content/maps. 470 will integrate more changes and will be more 227 style with real behavioral changes, but there is absolutely no timeline for 470.

Oh well... XC_Engine or such optional extension could be embedded directly in 469 - it doesn't change maps (files) but allows doing some changes exactly as STOCK UT does in maps like CTF-Coret and DM-Pressure.
I did patches that work in separate format. Paths, Events etc are Server-Side, the rest of visuals are going only for client - all done in prior UT variants before any 469, to not forget the superior power of DevPath used by XC_Engine capable to handle maps in 436/440 where any 469 have no deal in stage except where XC_Engine might be used. Unfortunately XC was not really ready and it needed some dodging - disabling several features but as average you can run a comfortable server and client game.

XC will never be embedded into the engine, the source is a hacky nightmare. Ideas and concepts can and will be reused for a 470, but the actual XC you can consider mostly "retired".

[sektor2111]

Then I'll wait for 470.