Intro

What is Google Helper process

Can you disable Google Helper?

How to reduce CPU usage

Check your plugins and extensions

Check for CPU-consuming apps

Update the macOS

Declutter your desktop

Disable Google Chrome Helper renderer

Reset Chrome to default settings

Outro

Intro

Chrome is Eating my GPU

Disable Hardware Acceleration

Testing the fix

Reduce the amount of geometry in the scene

Close other programs

Reduce Texture Resolution

Get a GPU with more Vram

Summary

Tweak 2: Disable Chrome "Use Hardware Acceleration When Available"...

Tweak 3: Open chrome://flags

Enable the Override software rendering

Enable the "Override software rendering list"...

Close All Un-Used Tabs...

1. Eliminate render-blocking JavaScript and CSS

2. Prioritize visible content

Load scripts asynchronously

Client-side rendering

Server-side rendering

Identifying critical CSS

Loading the remaining, non-critical CSS

Render blocking CSS recommendations

Recommendations for instant mobile web apps

Demo

Example of a scroll effect

Recording a Timeline

What are frames?

Using requestAnimationFrame

Timeline recording with a loop

What are reflows?

Using two loops to get offsets

How to enable Frame Mode

Conclusion

Adhere to copyright laws

Different map areas have different resolution

Starting RenderDoc, and initializing the Injection

Injecting into the Process ID for the Google Chrome GPU process

What you see is what you will get

Beware of too big data captures

Evaluating the amount of data captured based on the file size of the capture

Make sure to release the injection

Importing the .rdc file

Processing times can be excruciatingly long

Reducing the number of material slots, by baking to one texture

Removing all material slots of the duplicate

Exporting the unwrapped mesh from MeshLab

Verifying the unwrapped UV map imported from MeshLab

Configuring settings for the texture baking process

Noticing erroneous results due to inadequate projection settings

Noticing erroneous results due to insufficient margin

Connecting the baked texture to the single material

Noticing erroneous results due to excessive Extrusion distance

Further decreasing the Extrusion distance and rebaking

Considerations to improve the resolution of the texture

Evaluating the result of the final baking settings

Testing the result by exporting the refined mesh as an OBJ

Creating a material to render the baked texture

Showcase of Benjamin Bardou's experiments

Intro

Krunker Client

Brave Browser

Brave Settings

No Textures & Map Details

Map Details

FPS Test

Setting up Brave

Optional Code

Conclusion

New Defaults

Arnold Performance

Progressive Shadow

Background Blur

Viewport vs Rendering

Point Helper

Progressive Skylight Fading Speed

Color Correction Shader

Object Projectors

Conclusion

Learning how Ray Length settings can affect your render time

Discover the difference between global AO vs. Material based AO

Using AO Cache

How to render AO as a separate pass for compositing inside of After Effects

Baking AO into a texture & uses for game asset design

Stream Start

Intro + Community News

Opening the 3D Editor

Overview of the 3D Editor

General Settings Tab

Lighting Tab

Materials Tab

Post Processing Tab

Annotations Tab

Animations Tab

AR/VR Tab

Refraction & Opacity Demo

Subsurface Scattering Demo 1

Subsurface Scattering Demo 2

Clear Coat Demo

Anisotropy Demo

Emission + Bloom Demo

Outro

Intro

Reduce Polycount

Use Proxies

Reduce Texture Resolution

Optimize Materials Color

Minimize Displacement

Optimize Lighting

Don't Use Depth of Field

Render Elements

Use ChaosCloud

Introduction

What we tested

Test Setup

16GB & 32GB Results

Shadow of the Tomb Raider

4GB benchmarks

Rainbow Six Siege

Mark vs Prime

RAM Punisher Flow Simulation Benchmark

Conclusion