Hehe, time to start whining again.
So I'm new to modeling and I have an RPG that fires off its rocket. Now I made 2 models for that because if I save the no-rocket one as an animation of the rocket one, such as 'Select2', it get's all scrambled up.
anyway, the plan is to change the weapon's mesh when it fires from the one with the rocket to the one without. It does that just fine... in 226. 227 doesn't change the mesh :S
Code:

function PlayFiring()
{
	Owner.PlaySound(FireSound, SLOT_None,2.0*Pawn(Owner).SoundDampening);
	Mesh=Mesh'RisingModels.RPG3rd2';
	PlayerViewMesh=Mesh'RisingModels.RPG3rd2';
	ThirdPersonMesh=Mesh'RisingModels.RPG3rd2';
	PlayAnim('Fire',0.8);
} 

So any tips on this one?

Well that's the weird part. It doesn't say that it can't find anim 'Fire' (mesh 1 doesn't have Fire anim, mesh 2 does). So it does change the mesh, but visibly nothing changes.

First part 226f, second part 227h.
And switching to a masked texture is out of the question too for now, since I have no idea how to UV wrap crap.

First intuition would be whether this has something to do with replication as gopostal stated. I know for a fact that mesh changes are replicated from server->client (i.e. mesh is not bNetInitial) because I've set the mesh of various actors in-game hundreds of times online (on all versions). Is this behavior happening both offline and online?

Since it works in 226f this hints towards a redefinition of  the replication statement. Here's what I dug up from 225f vs 227h...

225f:
Code:

	unreliable if( Role==ROLE_Authority && DrawType==DT_Mesh )
		Mesh, bMeshEnviroMap, bMeshCurvy, Skin, MultiSkins;
 

227h:
Code:

	unreliable if ( Role==ROLE_Authority && DrawType==DT_Mesh )
		Mesh, bMeshEnviroMap, bMeshCurvy, Skin, MultiSkins;
 

They match, so scratch that it's unlikely to be replication of mesh.

When you say that 227 doesn't correctly change the mesh, do you mean the server or client? Guessing you mean that it doesn't render the change in mesh on the 227 client, but works on the 226f client (regardless of whether the server is 226f or 227). This would hint to me that something in DrawActor has changed and I've heard rumors over the years about DrawActor being different in 226f than other versions...

edit: maybe DrawActor is rendering other.default.mesh instead of other.mesh? good way to check this is to client-side it and set the actor's default mesh = mesh every frame.



more edits: just saw the "f" on 226. fixing babble. also 226f is colloquially known as "226crappity smacked" because it has a lot of inconsistencies with the other versions... since 227 was based on gold's source, I wonder if this bug shows up on stock gold as well as 227?

Oh crap, The forsaken version.. 226fucked?

Uhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh

Hmm...

Since that stuff was bound to fail in multiplayer anyway I didn't bother about making third person actor sync up mesh with the variable, but anyway to fix this:
Code:

function PlayFiring()
{
	Owner.PlaySound(FireSound, SLOT_None,2.0*Pawn(Owner).SoundDampening);
	Mesh=Mesh'RisingModels.RPG3rd2';
	PlayerViewMesh=Mesh'RisingModels.RPG3rd2';
	ThirdPersonMesh=Mesh'RisingModels.RPG3rd2';
	if( Attachment!=None )
		Attachment.Mesh = ThirdPersonMesh;
	PlayAnim('Fire',0.8);
} 

The way pre-227 draws third person actor is to temporarily swap mesh, change draw coords, draw mesh, reset to old state (this will horribly mess up some vertices caching on the mesh due drawing 2 different meshes in same time on one actor).

Bleeder91[NL] wrote on 07/19/12 at 19:47:56:

At least 227 has working special effects for things like RingExplosions and uses up a lot less CPU cycles to run client and server.
At least it's possible to add custom tools for UnrealEd 2 aswell.
At least UnrealEd 2.1 has more path building options.
At least AI is better on navigating in 227.

GenericHero wrote on 07/19/12 at 20:36:45:

Yeah, but that leads to problem nr. 1:
I made 2 meshes because if I save the no-rocket one as an animation of the rocket one, such as 'Select2', it get's all scrambled up. And by scrambled up I mean that it get's cut all over the place stretching across the whole screen.

3ds max and blender, the way i tried was removing the vertices alltogether cuz i couldnt find a way to scale them. I'm really new at this, I've just learned the basics of importing and exporting existing meshes and animating them at a rotate/move scale. Nothing complex yet

Won't you run into collision issues? It won't spawn if it's touching. Maybe I'm not really seeing what you guys are trying to do here.