Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Building a mobile project in UE? Explore how in-engine profiling tools like Unreal Insights complement platform-native tools for iOS and Android, as well as when to use each type. Dive into mobile profiling in this tech thread based on Paul Georges’s recent Unreal Fest Chicago talk 🧵 You can...

20,004 görüntüleme • 2 ay önce •via X (Twitter)

11 Yorum

Unreal Engine profil fotoğrafı
Unreal Engine2 ay önce

Use Unreal Insights to diagnose bottlenecks from inside the engine, then switch to platform-native tools to understand why they occur. Unreal Insights gives you the big picture, platform-native tools show the detail—like which functions are costing CPU time or limiting your GPU.

Unreal Engine profil fotoğrafı
Unreal Engine2 ay önce

On iOS, Xcode and Instruments cover most of what you need to profile CPU, GPU, rendering, memory, and energy use to explore bottlenecks and optimize performance. Here, Paul shows which tools to use and when.

Unreal Engine profil fotoğrafı
Unreal Engine2 ay önce

Android provides several platform-native profilers to choose from based on what you’re profiling and which device you’re on. Use them to assess CPU/GPU load and thermals, analyze thread scheduling and core contention, sample CPU call stacks, and diagnose GPU or frame bottlenecks.

Unreal Engine profil fotoğrafı
Unreal Engine2 ay önce

When a phone runs hot, the OS can shut off performance cores and pin the GPU to the minimum frequency. Your profiling data could no longer match what players experience. That means it’s important to pay attention to different thermal states to ensure accurate player experience.

Unreal Engine profil fotoğrafı
Unreal Engine2 ay önce

Check out the UE 5.8 documentation to learn more about profiling mobile projects: ⚫Android: ⚫iOS:

QDY profil fotoğrafı
QDY2 ay önce

@paulgeorgesepic great profile tool.

Andrew Green profil fotoğrafı
Andrew Green2 ay önce

@paulgeorgesepic This is awesome to see I love oceanhorn 3 as well

yongheng shouhu profil fotoğrafı
yongheng shouhu2 ay önce

@paulgeorgesepic I've already tested the Substrate version (5.6-5.8). As soon as I enable two ray tracing settings in semi-transparent mode, the Niagara effect immediately becomes bugged and malfunctions, disappearing completely...

yongheng shouhu profil fotoğrafı
yongheng shouhu2 ay önce

@paulgeorgesepic Why hasn't the serious incompatibility bug between the two ray tracing functions in the semi-transparent mode and the Niagara particle effect and materials with masked textures been resolved yet...?

yongheng shouhu profil fotoğrafı
yongheng shouhu2 ay önce

@paulgeorgesepic In UE5, the Niagara particle effect suffers from a long-standing and severe incompatibility bug with PostProcessVolume: enabling Translucency (ray tracing mode) causes the Niagara particle effect to malfunction and become undetectable. When will this major bug be fixed...?

yongheng shouhu profil fotoğrafı
yongheng shouhu2 ay önce

@paulgeorgesepic ---Selecting the semi-transparent mode: One out of two ray tracing options is selected; however, many semi-transparent materials with masks or overlays also experience a major bug where they disappear completely

Benzer Videolar

If you're a mobile engineer or interested in iOS and Android, this podcast episode is as good as it gets: How Notion builds its iOS and Android apps. Two of Notion's founding mobile engineers help us dive deep into the productivity app used by tens of millions of users on mobile. Listen to it or watch it here: Spotify: YouTube: Apple: Web & transcript: -- This episode is brought to you by DX the engineering intelligence platform designed by leading researchers. Learn more about them here: (Coincidentally, DX have just launched a very interesting dev productivity framework called DX Core 4: -- Three interesting takeaways from this conversation: 1. Notion’s native mobile team is surprisingly small! Notion employs about 600 staff, but the mobile team is only 11 people – including iOS and Android. This team size is very small, especially considering how Notion serves more than 10M users on both iOS and Android. We’re likely talking about one engineer for every ~2M or more users! 2. Moving from web-based to native was an incremental process by necessity. Thanks to a small native team, and the need to keep the mobile apps up-to-date with the latest Notion features, the native mobile engineering team didn’t have the luxury of doing a large mobile app rewrite. Instead, they did the sensible thing of slowly migrating parts of the app. Today, most of Notion’s apps are fully native, save for the editor. The editor remains one of the most complex parts of Notion. 3. Notion releases their app on a weekly cadence. Native mobile apps need to go through an app review flow from Apple and Google, and so many native apps are released less frequently, to account for this overhead. Notion doing a weekly release cycle is impressive – and it can serve as inspiration for other native mobile teams. If Notion, with 10M+ native users and a small team, does this, other native teams can as well! Thanks to the Notion team for sharing all these details!

Gergely Orosz

45,536 görüntüleme • 1 yıl önce