UT99.org | Unreal Tournament Community

Feralidragon wrote: ↑Thu Sep 24, 2020 4:42 pm You're free to submit bug reports and be able to explain everything in 1 or 2 full sentences without following a specific format.
That's absolutely fine as long as the problem or feature request is simple enough and crystal clear to both sides, and it's actually better to keep it as simple as possible since developers do not like to read much either or go through a lot of stuff to get to the core of the problem, so you don't need to go the other extreme, as that wouldn't help anyone either.

All you have to do is to "care", care enough to put in just a bit more work to actively help the developers, than just to give them chores to do.
And one-liners like simply "X is broken" or "add support for X" , without any more detail, context, anything really, and without even a justification in the latter example, are indeed extremely lazy and do not really contribute towards anything at all.

Feralidragon wrote: Picking your example of "The progress messages disappear when the voice menu is open", you would need to describe the exact steps to reproduce this, ideally with screenshots or a video to show off the problem, maybe even trying different renderers from the start to check if the problem only happens with a specific renderer or is engine-wide.

Ferildragon wrote: developers may wonder what exactly you even mean with this, may try to reproduce it and being unable to

PrinceOfFunky wrote: ↑Thu Sep 24, 2020 5:33 pm

Feralidragon wrote: Picking your example of "The progress messages disappear when the voice menu is open", you would need to describe the exact steps to reproduce this, ideally with screenshots or a video to show off the problem, maybe even trying different renderers from the start to check if the problem only happens with a specific renderer or is engine-wide.

Beyond the fact that the bug report didn't specify the renderers affected by this problem etc, what do you understand from that one-line sentence?

Feralidragon wrote: ↑Thu Sep 24, 2020 7:49 pm @PrinceOfFunky: Like OjitroC mentioned, it's hard to tell what you mean with "progress messages", I don't know what that is either.
Maybe some people do, but not me, maybe not even the devs.

Feralidragon wrote: ↑Thu Sep 24, 2020 7:49 pm Here's an example of what a good, yet simple, report looks like:
https://github.com/OldUnreal/UnrealTour ... /issues/22

sektor2111 wrote: ↑Thu Sep 24, 2020 10:54 pm "Progress Messages" which I'm using in my path finders tools didn't bugged me. What exactly is the problem with them ?

PrinceOfFunky wrote: ↑Thu Sep 24, 2020 3:11 am "The progress messages disappear when the voice menu is open".

OjitroC wrote: ↑Thu Sep 24, 2020 11:34 pm

sektor2111 wrote: ↑Thu Sep 24, 2020 10:54 pm "Progress Messages" which I'm using in my path finders tools didn't bugged me. What exactly is the problem with them ?

PrinceOfFunky wrote: ↑Thu Sep 24, 2020 3:11 am "The progress messages disappear when the voice menu is open".

PrinceOfFunky wrote: ↑Fri Sep 25, 2020 12:00 am You are kidding right? It's 500% obvious that he's doing it on purpose, he knows it so clearly that those are not progress messages,

....
function DoSayReach()
{
	if ( P != None )
	{
		if ( bWorking )
		{
			P.ClearProgressMessages();
			P.SetProgressMessage("Destination is Reachable!",1);
			clMsg.R=255;
			clMsg.G=128;
			clMsg.B=0;
			P.SetProgressColor(clMsg,1);
			P.SetProgressTime(3);
			DoResetChilds();
			NewRot = Rotator(P.Destination - P.Location);
			P.ClientSetLocation(P.Location,NewRot);
			bWorking=False;
		}
	}
...
}

sektor2111 wrote: ↑Fri Sep 25, 2020 6:18 am

PrinceOfFunky wrote: ↑Fri Sep 25, 2020 12:00 am You are kidding right? It's 500% obvious that he's doing it on purpose, he knows it so clearly that those are not progress messages,

Code: Select all

....
function DoSayReach()
{
	if ( P != None )
	{
		if ( bWorking )
		{
			P.ClearProgressMessages();
			P.SetProgressMessage("Destination is Reachable!",1);
			clMsg.R=255;
			clMsg.G=128;
			clMsg.B=0;
			P.SetProgressColor(clMsg,1);
			P.SetProgressTime(3);
			DoResetChilds();
			NewRot = Rotator(P.Destination - P.Location);
			P.ClientSetLocation(P.Location,NewRot);
			bWorking=False;
		}
	}
...
}

You are one of those with "issues" about warps through servers, messages, etc. Clearly you did not even see BotyMan3 and others... This is a sequence from my MHBotyMan5. If these are not public it's because navigation in UE1 is happily crapped up by Epic and only adjusted servers can use these tools. You can call such a message without ServerPackages, lol...
I want to see first what such sort of path testers can you do, and after that I'll ask if you are kidding...

PS - lol signature - you are kidding there:
My stuff is not known as being buggy because I did not release it so is unknown in all ways, and I tested it more than you can imagine, including XC stuff with dynamic arrays throwing out "names" buggers...

Okay, have a nice day !Job is waiting me...

PrinceOfFunky wrote: ↑Fri Sep 25, 2020 3:36 pm Can you please explain me how do you open the Voice Menu in Unreal Editor?

sektor2111 wrote: ↑Fri Sep 25, 2020 6:20 pm

PrinceOfFunky wrote: ↑Fri Sep 25, 2020 3:36 pm Can you please explain me how do you open the Voice Menu in Unreal Editor?

I do NOT OPEN ANY SORT of VOICE Menu in Editor because simply I have other things to do in Editor than Voices - perhaps this is the most hilarious thing called bug, excuse me but I'm testing voices in game not in Editor... What I was saying about path finders testers it's about MUTATORS in GAME not mutators in Editor... Poor Editor, it's guilty for everything...

Okay keep going, I wanna see what else was "ignored" in UT469 patch, because for me in UT469 and XC_Engine25 Starting-Progress-Messages are back after releasing voice <V> key, I don't even understand what and where is the bug.