FTransform trans = GetSocketTransform(TargetActor, TargetSocketName);

-
FTransform trans = GetSocketTransform(TargetActor, TargetSocketName);
//FVector A = GetSocketTransform(TargetActor, TargetSocketName);
//GetSocketTransform(MeshComp, TargetSocketName)->

}

FTransform UAnimNotify_Footstep::GetSocketTransform(AActor * Actor, FName SocketName) const
{
UMeshComponent* Mesh = Cast<ASJ_Character>(Actor)->GetMesh();
//ReturnLocation = GetSocketTransform(SocketName, RTS_World)->GetTranslation();

return Mesh->GetSocketTransform(SocketName, RTS_World);
}

댓글

댓글 쓰기

이 블로그의 인기 게시물

About AActor!!! "UObject" has no member "BeginPlay"

-
AActor An AActor is an object that is meant to be part of the gameplay experience. AActors are either placed in a level by a designer or created at runtime via gameplay systems. All objects that can be placed into a level extend from this class. Examples include AStaticMeshActor, ACameraActor, and APointLight actors. AActor derives from UObject, so enjoys all of the standard features listed in the previous section. AActors can be explicitly destroyed via gameplay code (C++ or Blueprints) or via the standard garbage collection mechanism when the owning level is unloaded from memory. AActors are responsible for the high-level behaviors of your game’s objects. AActors are also the base type that can be replicated during networking. During network replication, AActors can also distribute information for any UActorComponents owned by that AActor that require network support. AActors have their own behaviors (specialization through inheritance), but they also act as containers for a hie...
자세한 내용 보기

Shader informations nice blog ~ ~

-
이미지
 https://halisavakis.com/my-take-on-shaders-geometry-shaders/ My take on shaders: Parallax effect (Part II) By  Harry Alisavakis   on  Monday, March 11, 2019 Welcome to the second part of the tutorial on Parallax effects! Now, initially I intended for this tutorial to only have two parts, with which I so naively open on the  previous post . However, there’s probably going to be a third part on the series, the subject of which I won’t reveal now, for some dramatic tension. The subject of this part was what I initially intended to achieve and it led me to stumble upon the previous and next tutorials, for which I’m really grateful. It’s the effect that got me so excited about parallax, as I mentioned in the backstory of the previous post, and it’s the very same effect covered in that tutorial I mentioned before, but without the Shader Graph: 1 2 3 4 5 6 7 8 // Calculates UV offset for parallax bump mapping inline float2 ParallaxOffset( half h, half height, half3 vi...
자세한 내용 보기

Unity #pragma target 2~5.0

-
  https://docs.unity3d.com/Manual/SL-ShaderCompileTargets.html Default compilation target By default, Unity compiles shaders into almost the lowest supported target (“2.5”); in between DirectX shader models 2.0 and 3.0. Some other compilation directives make the shader automatically be compiled into a higher target: Using a geometry shader ( #pragma geometry ) sets the compilation target to  4.0 . Using tessellation shaders ( #pragma hull  or  #pragma domain ) sets the compilation target to  4.6 . Any shader not explicitly setting a function entry point through  #pragma  for geometry, hull or domain shaders will downgrade internal shader capability requirements. This allows non-DX11 targets with broader run-time and feature differences to be more compatible with the existing shader content. For example, Unity supports tessellation shaders on Metal graphics, but Metal doesn’t support geometry shaders. Using  #pragma target 5.0  is still valid,...
자세한 내용 보기