No joke :)

Turboman. · Post by **Turboman.** » Sun Oct 02, 2005 10:25 pm

mover bug: movers are extremely buggy in general, weird behavior both offline and online its even worse

sometimes certain movers dont function properly online, i dont know which ones exactly, but i've heard of rotatingmovers and attachmovers acting weird, afaik zora knows alot about this.

movers turn (partially) invisible various times, this happens more often on high poly movers, or when there are too many movers in a zone, a good example of this are the four towers in zora's zm4vulcan.

complex movers with sharp and angular shapes cause huge collision problems around them.

also when entering a server you can see movers returning to their first keyframe for a few seconds, this is most noticable on the first door in isv deck 3 2

afaik all of these bugs are also present in ut.

Shambler · Post by **Shambler** » Sun Oct 02, 2005 10:55 pm

As for better netcode...If it is possible we want to retain compatability for 226-224 ASWELL as include the netcode advantages for 227 players too.

However Smirftsch has looked into this and it is incredibly difficult, the replication system appears to have huge differences between 224/226/UT...that's 3 huge differences in netcode. (UT is what I would prefer 227 to be based upon, atm we are trying to work backwards as far as net compatability goes)

No idea how things are going to work in regards to that atm.

Spazzpez · Post by **Spazzpez** » Mon Oct 03, 2005 12:33 am

New bug JUST COME UP in unreal servers

UnrealHUD Nyleave.UnrealHUD2 (Function UnrealShare.UnrealHUD.DrawArmor:0078) Runaway Loop Detected (over 10000000 iterations)

History: FFrame::Serialize

Spazzpez · Post by **Spazzpez** » Mon Oct 03, 2005 12:46 am

2nd bug IN A ROW

History: FCollisionHash::ActorLineCheck

Hyper · Post by **Hyper** » Mon Oct 03, 2005 6:42 am

2nd bug IN A ROW

i cant WAIT for that 227 patch...

Looks familiar. Another CollisionHash victim.

Hyper · Post by **Hyper** » Mon Oct 03, 2005 6:43 am

New bug JUST COME UP in unreal servers

Ive NEVER seen this untill today :P

Unreal HUD crash. I get this kind of crashes too from time to time, but not too often.

Post by **Smirftsch** » Mon Oct 03, 2005 12:48 pm

if i can manage the netcode trouble i may release some 227 pre-release (like 226z or so) to test some of the fixes we made already, but for the moment i donno how long it'll take, so please be patient, we have to do this aside our usual work

Shambler · Post by **Shambler** » Mon Oct 03, 2005 3:46 pm

Nah IDK if a pre-release is good, don't want more new versions of unreal floating around than is necessary. (bad for the cheat protections)

Just let those in the "super secret squirrel club" test it

Post by **Smirftsch** » Mon Oct 03, 2005 4:09 pm

lol, my thoughts are just that more ppl find more problems- the cheat protections shouldnt take care of it, its not made for that, u know, but we can discuss that once its working

Shambler · Post by **Shambler** » Mon Oct 03, 2005 4:57 pm

Agreed more people using it means more bugs fixed

IMO it's still best not to get released publically in beta stage tho, maybe recruit up a beta test team when the time comes. (btw don't want ppl to start requesting participation in this

lets say invite only for the moment)

Hyper · Post by **Hyper** » Mon Oct 03, 2005 6:56 pm

if i can manage the netcode trouble i may release some 227 pre-release (like 226z or so) to test some of the fixes we made already, but for the moment i donno how long it'll take, so please be patient, we have to do this aside our usual work

Actually, I expected nothing else than it would take a long time to create. It's a huge project and high level skills are needed.

Verdigo · Post by **Verdigo** » Mon Oct 03, 2005 10:02 pm

Code: Select all

Critical: UProperty::ExportText
Critical: (ObjectProperty Engine.Actor.PointRegion.Zone)
Critical: UStructProperty::ExportTextItem
Critical: (StructProperty Engine.Pawn.HeadRegion)
Critical: UProperty::ExportText
Critical: (StructProperty Engine.Pawn.HeadRegion)
Critical: GetPropertyText
Critical: FPropertyItem::Draw
Critical: WWindow::WndProc
Critical: WWindow::StaticProc
Critical: WWindow::WndProc
Critical: WWindow::StaticProc
Critical: EnforceTickRate
Critical: MainLoop
Exit: Executing UObject::StaticShutdownAfterError
Exit: Executing UWindowsClient::ShutdownAfterError
Log: DirectDraw End Mode
Exit: UOpenGLRenderDevice::ShutdownAfterError
Exit: appExit
Uninitialized: Name subsystem shut down
Uninitialized: Log file closed, 10/03/05 17:25:35

Got that whie using the EditActor window, in a server. Didn't change anything, was only viewing vars. I also get this in UT200X :-/.

Squirrel · Post by **Squirrel** » Thu Oct 06, 2005 2:17 am

Nah IDK if a pre-release is good, don't want more new versions of unreal floating around than is necessary. (bad for the cheat protections)

Just let those in the "super secret squirrel club" test it

im a squirrel...

Post by **Smirftsch** » Thu Oct 06, 2005 7:04 am

lol, if it comes to this decission you are in

Leo T_C_K · Post by **Leo T_C_K** » Thu Oct 06, 2005 2:18 pm

Another bug at network play, I dont know if it is already fixed, but currently when playing online, when at skybox is something more like decorations, it isnt visible online. (Gateway at coop) Also other translucent problems I saw. When floor is translucent, you mostly can't see through it too.

Post by **TCP_Wolf** » Thu Oct 06, 2005 4:24 pm

When floor is translucent, you mostly can't see through it too.

If by that, you mean, you are not seeing players, weapons and other items through translucent floors/walls, that is a known replication issue, caused by Unreal's "intelligent" decision when NOT to inform clients about locations of actors.

If you meant that, translucent walls/floor may indeed appear as fully solid, then that's something I don't know about yet :-)

Post by **Smirftsch** » Thu Oct 06, 2005 6:03 pm

Leo, some screenies plz.

Leo T_C_K · Post by **Leo T_C_K** » Thu Oct 06, 2005 8:08 pm

Leo, some screenies plz.

As I have seen, it appears only at coop. I will try take a shot of that, at deathmatch is everything ok I think.

Spazzpez · Post by **Spazzpez** » Fri Oct 07, 2005 12:02 pm

When vertex editing, i make a pyramid and i get an error about little polys and too less vertex's

Turboman. · Post by **Turboman.** » Fri Oct 07, 2005 2:20 pm

When vertex editing, i make a pyramid and i get an error about little polys and too less vertex's

not really a bug, it sounds like you dropped multiple verticles ontop of eachother (i think its because they both are on the same coordinates and the poly/line between them cannot exist)

regarding unrealed i do like to see a fix for the fmod bug causing the editor to crash when you stop a sound in the sound browser.

Post by **Smirftsch** » Fri Oct 07, 2005 5:06 pm

honestly, please DONT report like "I've seen once an error which i believe was in this version or maybe another and it appeared somewhere"

Those resports are USELESS, please verify the bug and check its reproduceable, so it can be found and fixed, detailed informations are needed, and if possible screenshots.

asgard12000 · Post by **asgard12000** » Wed Oct 12, 2005 5:28 am

yes, removing the if ( Level.NetMode != NM_DedicatedServer ) "fixes" it, but its more a workarround, the source of why it isnt working is the real problem, because as you may have seen, exactly with the same code its working on 224 and 225. Indeed its a problem in the network replication code. Wish me luck that i can find it, its probably the cause of many other problems with 226 servers as well

{ASMD and ringexplosion}

The " if ( Level.NetMode != NM_DedicatedServer ) " shouldnt be removed, its the way its supposed to be.

I think the problem is with bNetTemporary.

If you set the ringexplosion class to bNetTemporary = false it works fine. Theres other effect classes that also have this problem such as the WaterImpact, I havent been through all the classes to see.

I guess they changed it after 225 the effect classes have this by default. bNetTemporary isnt working properly.

At Wiki
http://wiki.beyondunreal.com/wiki/Actor_(UT)/Advanced

cheers

Post by **Smirftsch** » Wed Oct 12, 2005 8:08 am

i stumbled already about bNetTemporary, but didnt see anything unusual in the code, will have a deeper look, thanks asgard, thats really usefull informations, will go digging directly

asgard12000 · Post by **asgard12000** » Wed Oct 12, 2005 9:25 am

YW

.... The bNetTemporary is kinda missleading in the actor class descrpition, from what I can gather its to give authority to the client and let the server forget about it. This is kind of happening.

If for example i do
if ( Level.NetMode != NM_DedicatedServer )
log("im here......................");

It logs client side ONLY, the million dollar question is why isnt it animating if its logging, too many wild guesses again.

Anyways I crossed checked this with 224,226 and the checked UT's code and didnt notice anything in the script that would cause the prob eg. replication and UT uses the same code and works fine.

Go figure

Cheers

Post by **Smirftsch** » Wed Oct 12, 2005 10:31 am

yes, this million dollar question is good.
But no, bNetTemporary isnt causing it, it seems. It only means that it is, like any projectile, only replicated once, means initiated, and then left alone. If its set to false the server takes care about its replication. So the question is - why is a 224 or 225 server taking care about it ALTHOUGH its temporary, and / or why the server has to take care about it - starting to think from this idea, the bug must be in the client, not in the server, and was just corrected in 226 server because it really shouldnt take care in the server for it, while 224 and 225 servers still do it.

Or am i wrong here ?

Another possibility to make it visible is to set the role for the Ringexplosion from SimulatedProxy to AutonomousProxy. Seen this way it makes sense to set it to autonomous since it is bNetTemporary.

OldUnreal (Engine)

No joke :)

Re: No joke :)

Re: No joke :)

Re: No joke :)

Re: No joke :)

Re: No joke :)

Re: No joke :)

Re: No joke :)

Re: No joke :)

Re: No joke :)

Re: No joke :)

Re: No joke :)

Re: No joke :)

Re: No joke :)

Re: No joke :)

Re: No joke :)

Re: No joke :)

Re: No joke :)

Re: No joke :)

Re: No joke :)

Re: No joke :)

Re: No joke :)

Re: No joke :)

Re: No joke :)

Re: No joke :)

Re: No joke :)