UE4 Fire

-
 
 
 

댓글

댓글 쓰기

이 블로그의 인기 게시물

UE get player controller

-
이미지
  UGameplayStatics :: GetPlayerController ( GetWorld (), 0 );   Then you don't need to iterate through all of them. For example if you are in a Singleplayer Game. 더 ▼ 답변됨  Nov 13 '14 at 4:29 PM eXi 7.2k   ●   340   ●   195   ●   482 18 Depends on what you want to do and where you want to do it. The main way you'd do this is here. for ( FConstPlayerControllerIterator Iterator = GetWorld ()-> GetPlayerControllerIterator (); Iterator ; ++ Iterator ) { }   Some things have the owner variable as a  APlayerController  (`APlayerState`, etc) Clients only have 1 controller, their own. Servers have ALL controllers. You'll want to use  IsLocalPlayerController  to differentiate on the server. 더 ▼ 답변됨  Jul 02 '14 at 2:38 AM Crzyhomer  STAFF 1.3k   ●   35   ●   26   ●   104   dbrizov  Jul 02 '14 at 2:47 AM I see, thank you very much :)   Mungyun  Nov 13 '14 ...
자세한 내용 보기

Raytracing

-
이미지
https://reindernijhoff.net/2019/03/wolfenstein-raytracing-on-using-webgl1/ https://www.shadertoy.com/view/3dfGR2  https://github.com/Kevinsomnia/Raytracing https://github.com/keijiro/UnityDxrTest https://github.com/SIZMW/unity-raytracer https://medium.com/neosavvy-labs/webgl-2-0-ray-tracing-34866baca7c1 http://blog.three-eyed-games.com/2018/05/03/gpu-ray-tracing-in-unity-part-1/ https://github.com/kamyy/webgl-ray-tracer https://davidpeicho.github.io/blog/cloud-raymarching-walkthrough-part1/ https://codesandbox.io/s/github/sschoenholz/WebGL-Raytracer/tree/master/ https://medium.com/@evanwallace/rendering-realtime-caustics-in-webgl-2a99a29a0b2c https://www.opengl.org/pipeline/article/vol003_6/ https://github.com/evanw/webgl-water https://github.com/martinRenou/threejs-water https://github.com/shanecelis/water-demo https://github.com/ibesora/webgl-raytracer https://github.com/FoxelFox/voxel-octree Live Demo:  https://64f.de/voxel-octree-rt-v7/
자세한 내용 보기

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,...
자세한 내용 보기