Andrew Dowell

In a recent project, we had some issues with CSM lighting. The directional light is set to stationary but not performing as expected on Android ES3.  Tim Hobson nailed it on the unreal engine forums with a complete run-through. Following these steps for success: In the Project Settings enable Static and CSM Shadowing. Select the meshes that should receive shadows and in the details panel enable Receive Combined Static and CSM Shadows from Stationary Lights. Select the Light source and set a value for Dynamic Shadow Distance StationaryLight. In the Light Source disable Inset Shadow for Movable Objects. Build Lighting Mobile Preview/Launch on Device/Package for your device At this point you should see dynamic shadows for movable objects that have the value set to receive them. For instance, you don’t necessarily need to set the value for the actual movable object, but the floor is receiving the dynamic shadow so it needs to make sure it has been enabled to receive the shadow via the flag

An advanced technique for packing data into texture channels that allows you to represent all of the texture data needed for a material in just two texture samples. Using this method saves both texture memory and performance, but since you're packing non-normal data in with the normal map, you do lose a little bit of quality in the normal. It also requires doing some extra steps in the shader to unpack the normal data Traditional 5-Map set-up: 1. Albedo / Diffuse 2. Metalic 3. Roughness 4. Normal 5. Ambient Occlusion ORMS 3-Map set-up: Does exactly the same as the 5-Map material but in 3. 1. Albedo / Diffuse  2. Metal, Roughness and AO  3. Normal Advanced Channel Packing 2-Map set-up: Does almost exactly the same as the 3-Map material but in 2. 1. Albedo / Diffuse + Roughness in the Alpha Channel 2. Red and Green Channel for Normal, Blue for AO *Make sure SRGB is set to off and to use BC7 in the compression settings for the textures. Watch the tutorial here:

If you are completely new to Gaea terrain software, start with watching the 6-minute video to create your first landscape terrain and to familiarize yourself with the Gaea Interface in the Getting around documentation. 3D Viewport, 2D viewport, the graph and properties panel: The Using Gaea section explains various concepts in detail, such as using Create with Primitives to build scenes, harnessing the power of Eroding Terrains to make realistic terrains, creating Procedural Textures , and outputting using the Build Manager . https://docs.quadspinner.com/Reference/ The Node Reference gives you access to details about every node and sculpting tool in Gaea. Use the top menu to navigate the different node type groups. In individual node pages, you will find detailed descriptions, usage advice, parameter reference, and usage examples. The Tutorials section contains complete tutorials that show you how to accomplish a complete project. The QuickStarts section has over 50 scenarios of di

How to use Unreal Insights with Oculus Quest Unreal Insights is a great new profiling and analysis tool that allows you to quickly find bottlenecks, performance spikes, threading patterns and much more. Any Unreal Engine developer building a game or app for Oculus Quest should have Unreal Insights in their toolbelt. The set-up process takes a short amount of time and after you do it once, it's set up forever and you’ll wonder how you ever lived without it. Let’s get started.   Requirements: Unreal Engine version 4.24+  Tracing enabled in built development app (on by default) Unreal Insights Executable built or downloaded (<CloneDir>\UnrealEngine\Engine\Binaries\Win64\UnrealInsights.exe and Solution ‘UE4’ > Programs > UnrealInsights in solution explorer) 1. Setup your UE4 project for Oculus as described here: https://developer.oculus.com/documentation/quest/latest/concepts/unreal-quick-start-guide-quest/ Then run Unreal Insights tool which is located in C:\\Program File