Disco (SRP Batcher) Bug?

Unity Engine
,
1

Hi all,

I’ve been trying to reproduce a strange flicker bug on 2020.1.a12 that I had (as seen on this unrelated topic: Disabled Physics Components vs. Removed Physics Components , click the GIF).

I’m now using 2020.1.a13 on OSX, together with the Hybrid Renderer 0.1.1 and the URP 7.1.2. With the SRP Batcher enabled on the UniversalRP-HighQuality settings.

In the (very helpful) frame debugger, when I go back and forth between set render target > clear and render opaques, the flickering is well visible:

5181809--514655--disco-bug2.gif

When doing this, I noticed that there is a correlation between the flickering in the scene tab and the game tab. When there was no flickering in the scene tab, the issue did not occur in the game tab, but when it occurred in the scene tab it occurred in the game tab:

5181809--514658--disco-bug3.gif

Not sure if this is helpful…?
(first there is no flickering, but then it reoccurs later in the GIF)

There is no flickering when I switch off the SRP Batcher.
Please let me know if I can provide more infos.

Cheers,
Florian

P.S: These are the packages I use in this otherwise completely freshly created Unity scene (plus the cube with ConvertToEntity):

5181809--514652--Screenshot 2019-11-16 at 14.25.43.png
5181809--514652--Screenshot 2019-11-16 at 14.25.43.png606×722 46.8 KB

P.P.S: Reported as case 1198948.

1 Like
Subscene + URP + SRP batcher are an explosive combination
2

(Also occurs in URP 7.1.5, if that helps)

3

According to this message (just now) Are Unity Subscenes and LWRP Compatible ? - #25 by superpig , this has been reported already in Unity Issue Tracker - Universal RP Lit Shader is flickering on Entities when SRP Batcher is enabled.

4

Universal + Hybrid Renderer is not yet supported.

5

Yes, thank you, and according to the message I link to above we can expect it to work mid 2020 (just noting this for others as the linked message is in the DOTS forum).

6

If I could have one wish it would be great to put that fact right here: https://docs.unity3d.com/Packages/com.unity.rendering.hybrid@0.1/manual/index.html

This would help with people like me deciding for a pipeline – thank you in advance! :slight_smile:

2 Likes
7

Something like this would be fantastic. Ran into this issue updating to the URP over the weekend and assuming it was a bug on my end spent far too many hours unsuccessfully trying to fix it. In the end to figure out what was happening I had to dig around in these forums to find a post mentioned that the URP and hybrid renderer don’t work together, but hopefully the team would be able to start looking into it by mid 2020.

I understand the dots hybrid renderer is a preview package so there are no guarantees of what will and will not work, but it would be great if front and center in the documentation it was stated that the hybrid renderer package is currently not fully compatible with the URP, and if you want to use the dots hybrid renderer you currently need to be using the HDRP (or use the older unity built in renderer? Or is that not compatible too? It doesn’t seem to be documented).

2 Likes
8

I forwarded this request to the Hybrid Renderer development team :slight_smile:

1 Like
9

Does anyone know if the hybrid renderer works with URP on Android currently? Everything works perfectly fine on my Windows 10 laptop (in-editor and builds). When I run on Android, I get this:

Or maybe there’s a setting I need to change for Android builds?

I’m worried that the psychedelic LSD tripping might cause seizures.

10

@lclemens AFAIK it should work. Can you please report a bug?

11

I realized that for android I hadn’t added ENABLE_HYBRID_RENDERER_V2 .

After I did that, I wished for the disco mode back because anytime I build for Android it gets 1fps for a few seconds and then crashes. I have commented out ALL of my systems… so it’s basically a blank URP project with nothing except for a terrain mesh and a material using the URP/Simple Lit shader.

I spent the last 8 hours trying out different settings and building for Android, which is a slow process. I only found one thing that worked - disabling Multi-threaded Rendering. Of course, doing this greatly reduce frame rates such that I could only get 20fps or so on Android with such a simple scene and no systems running.

Using Unity 2020.1.0f1 with packages: Hybrid Renderer 0.7.0 preview 24, Entities 0.13.0, Jobs 0.4.0, Burst 1.3.2, SRP 1.9.0, Shader Graph 9.0.0, Physics 0.4.1, and collections 0.11.0-preview 17.

Tomorrow I will try starting a new project from scratch and if I can’t get that to work I’ll submit a bug report. The documentation says that Hybrid Renderer V2 is supposed to work with Vulkan, but maybe it still doesn’t work for Android? Honestly I’m pretty frustrated right now and wishing I hadn’t gone the DOTS route.

12

Thank you, this would be great!

It should work.

Hybrid Renderer V2 is in preview mode, so it might not always work everywhere.

13

I created a new project and reproduced the crashing. It does work in BlueStacks, but crashes after a few seconds on my Motorola X4. The project contains just a single 512 terrain mesh and a single material+URP/Simple Lit shader that has a convert-to-entity script on it. It’s such a simple scenario that I’m hesitant to do a bug report, because I’m wondering if I’m missing something really stupid, or perhaps the Hybrid Renderer isn’t ready for Android yet.

14

Keep in mind that Unity doesn’t officially support any emulators.

Out of curiosity, is it the version with 3 or 4 GB of RAM?

Is there anything in the logcat?

15

Those are really good questions…

It’s the 3GB version.

Yes, it appears that an out of memory problem is causing the trouble.

If I remove the convert-to-entity script from the mesh, everything runs perfectly on the phone. Also, things were running well on Android last month with 2019 and pretty much everything except for the camera was converted to entities (I was using Hybrid Renderer v1 back then). This leads me to believe that the mesh isn’t too large to fit in memory on Motorola X4 phone. The mesh has everything set to static. According to blender, the fbx mesh has: 13,122 vertices, 26,214 faces, 26,214 Tris, and 1 object. Blender doesn’t say how much ram is used to hold the fbx, but subtracting the memory with and without the FBX loaded comes out to about 9.8MiB. The fbx file on disk is about 1.08MB (1,087,196 bytes).

There is also a message about being unable to find lib_burst_0_0 and _burst_0_0. There was a post yesterday about something very similar here: https://answers.unity.com/questions/1755666/cannot-load-lib-burst-0-0-on-android-builds.html .

I changed the lines that that stood out as relevant to the app in question to bold. It seems like a lot of other things crashed too… perhaps because they didn’t have enough memory? I’m not sure if the DeadObjectException lines are related. The name of the test app is SpeedyBugs.

logcat

07-29 01:40:11.900 1968 8582 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.DefaultCompany.SpeedyBugs/com.unity3d.player.UnityPlayerActivity bnds=[639,260][839,528]} from uid 10045
07-29 01:40:11.995 1968 2040 I ActivityManager: Start proc 19042:com.DefaultCompany.SpeedyBugs/u0a222 for activity com.DefaultCompany.SpeedyBugs/com.unity3d.player.UnityPlayerActivity
07-29 01:40:12.032 1968 8582 I ActivityManager: Config changes=20000480 {1.0 310mcc260mnc [en_US] ldltr sw360dp w592dp h336dp 480dpi nrml land finger -keyb/v/h -nav/h winConfig={ mBounds=Rect(0, 0 - 1080, 1776) mAppBounds=Rect(0, 0 - 1776, 1080) mWindowingMode=fullscreen mActivityType=undefined} s.14 spnnull gid544d}
07-29 01:40:12.098 1968 8582 I ActivityManager: Override config changes=20000480 {1.0 310mcc260mnc [en_US] ldltr sw360dp w592dp h336dp 480dpi nrml land finger -keyb/v/h -nav/h winConfig={ mBounds=Rect(0, 0 - 1080, 1776) mAppBounds=Rect(0, 0 - 1776, 1080) mWindowingMode=fullscreen mActivityType=undefined} s.14 spnnull gid544d} for displayId=0
07-29 01:40:12.124 1968 8582 W ActivityManager: Slow operation: 105ms so far, now at attachApplicationLocked: after mServices.attachApplicationLocked
07-29 01:40:12.537 1968 2060 I ActivityManager: Displayed com.DefaultCompany.SpeedyBugs/com.unity3d.player.UnityPlayerActivity: +564ms
07-29 01:40:13.054 19042 19066 I Unity : SystemInfo CPU = ARM64 FP ASIMD AES, Cores = 8, Memory = 2746mb
07-29 01:40:13.054 19042 19066 I Unity : SystemInfo ARM big.LITTLE configuration: 4 big (mask: 0xf), 4 little (mask: 0xf0)
07-29 01:40:13.055 19042 19066 I Unity : ApplicationInfo com.DefaultCompany.SpeedyBugs version 0.1 build 6197eee8-1888-4ee7-b07c-e82bea448be2
07-29 01:40:13.055 19042 19066 I Unity : Built from ‘2020.1/staging’ branch, Version ‘2020.1.0f1 (2ab9c4179772)’, Build type ‘Release’, Scripting Backend ‘mono’, CPU ‘armeabi-v7a’, Stripping ‘Disabled’
07-29 01:40:20.614 19042 19066 E Unity : Unable to find lib_burst_0_0
07-29 01:40:20.615 19042 19066 E Unity : Unable to find _burst_0_0
07-29 01:40:24.359 19042 19066 I Unity : Hybrid Renderer V2 active, MaterialProperty component type count 52 / 128
07-29 01:40:24.359 19042 19066 I Unity : (Filename: ./Runtime/Export/Debug/Debug.bindings.h Line: 35)
07-29 01:40:24.359 19042 19066 I Unity :
07-29 01:40:27.530 1968 2548 I ActivityManager: Process com.android.settings (pid 17286) has died: cch+6CEM
07-29 01:40:27.715 1968 8572 I ActivityManager: Process com.android.chrome:sandboxed_process0 (pid 18018) has died: cch+4CEM
07-29 01:40:27.715 1968 8572 W ActivityManager: Scheduling restart of crashed service com.kyriakosalexandrou.coinmarketcap/org.chromium.content.app.SandboxedProcessService0 in 1000ms
07-29 01:40:27.774 1968 7029 I ActivityManager: Process com.motorola.carriersettingsext (pid 17292) has died: cch+4CEM
07-29 01:40:27.900 1968 3913 I ActivityManager: Process com.novvia.fispy (pid 18394) has died: cch+4CEM
07-29 01:40:27.907 1968 8741 I ActivityManager: Process com.tmobile.pr.mytmobile (pid 18094) has died: cch+4CEM
07-29 01:40:27.968 1968 8741 W ActivityManager: Exception when unbinding service com.tmobile.pr.mytmobile/org.chromium.content.app.SandboxedProcessService0
07-29 01:40:27.968 1968 8741 W ActivityManager: android.os.DeadObjectException
07-29 01:40:27.968 1968 8741 W ActivityManager: at android.os.BinderProxy.transactNative(Native Method)
07-29 01:40:27.968 1968 8741 W ActivityManager: at android.os.BinderProxy.transact(Binder.java:1138)
07-29 01:40:27.968 1968 8741 W ActivityManager: at android.app.IApplicationThread$Stub$Proxy.scheduleUnbindService(IApplicationThread.java:1130)
07-29 01:40:27.968 1968 8741 W ActivityManager: at com.android.server.am.ActiveServices.removeConnectionLocked(ActiveServices.java:2902)
07-29 01:40:27.968 1968 8741 W ActivityManager: at com.android.server.am.ActiveServices.killServicesLocked(ActiveServices.java:3301)
07-29 01:40:27.968 1968 8741 W ActivityManager: at com.android.server.am.ActivityManagerService.cleanUpApplicationRecordLocked(ActivityManagerService.java:20691)
07-29 01:40:27.968 1968 8741 W ActivityManager: at com.android.server.am.ActivityManagerService.handleAppDiedLocked(ActivityManagerService.java:6240)
07-29 01:40:27.968 1968 8741 W ActivityManager: at com.android.server.am.ActivityManagerService.appDiedLocked(ActivityManagerService.java:6439)
07-29 01:40:27.968 1968 8741 W ActivityManager: at com.android.server.am.ActivityManagerService$AppDeathRecipient.binderDied(ActivityManagerService.java:2056)
07-29 01:40:27.968 1968 8741 W ActivityManager: at android.os.BinderProxy.sendDeathNotice(Binder.java:1204)
07-29 01:40:27.975 1968 8741 I ActivityManager: Killing 18234:com.android.chrome:sandboxed_process0/u0a130i8 (adj 904): isolated not needed
07-29 01:40:27.997 1968 2003 I ActivityManager: Process com.google.android.apps.maps (pid 16635) has died: cch+6CEM
07-29 01:40:28.020 1968 8582 I ActivityManager: Process com.android.providers.calendar (pid 18795) has died: cch+4CEM
07-29 01:40:28.025 1968 3554 I ActivityManager: Process com.kyriakosalexandrou.coinmarketcap (pid 17936) has died: cch+4CEM
07-29 01:40:28.026 1968 3554 W ActivityManager: Exception when unbinding service com.google.android.gms/.chimera.GmsBoundBrokerService
07-29 01:40:28.026 1968 3554 W ActivityManager: android.os.DeadObjectException
07-29 01:40:28.026 1968 3554 W ActivityManager: at android.os.BinderProxy.transactNative(Native Method)
07-29 01:40:28.026 1968 3554 W ActivityManager: at android.os.BinderProxy.transact(Binder.java:1138)
07-29 01:40:28.026 1968 3554 W ActivityManager: at android.app.IApplicationThread$Stub$Proxy.scheduleUnbindService(IApplicationThread.java:1130)
07-29 01:40:28.026 1968 3554 W ActivityManager: at com.android.server.am.ActiveServices.removeConnectionLocked(ActiveServices.java:2902)
07-29 01:40:28.026 1968 3554 W ActivityManager: at com.android.server.am.ActiveServices.killServicesLocked(ActiveServices.java:3301)
07-29 01:40:28.026 1968 3554 W ActivityManager: at com.android.server.am.ActivityManagerService.cleanUpApplicationRecordLocked(ActivityManagerService.java:20691)
07-29 01:40:28.026 1968 3554 W ActivityManager: at com.android.server.am.ActivityManagerService.handleAppDiedLocked(ActivityManagerService.java:6240)
07-29 01:40:28.026 1968 3554 W ActivityManager: at com.android.server.am.ActivityManagerService.appDiedLocked(ActivityManagerService.java:6439)
07-29 01:40:28.026 1968 3554 W ActivityManager: at com.android.server.am.ActivityManagerService$AppDeathRecipient.binderDied(ActivityManagerService.java:2056)
07-29 01:40:28.026 1968 3554 W ActivityManager: at android.os.BinderProxy.sendDeathNotice(Binder.java:1204)
07-29 01:40:28.034 1968 3347 I ActivityManager: Process com.google.android.gms (pid 16191) has died: cch+2CEM
07-29 01:40:28.038 1968 3393 I ActivityManager: Process com.wilysis.cellinfolite (pid 17406) has died: cch CEM
07-29 01:40:28.044 1968 5461 I ActivityManager: Process com.google.android.googlequicksearchbox:search (pid 16131) has died: cch CACC
07-29 01:40:28.045 1968 5461 W ActivityManager: Scheduling restart of crashed service com.google.android.googlequicksearchbox/com.google.android.apps.gsa.nowoverlayservice.DrawerOverlayService in 1000ms
07-29 01:40:28.818 1968 3913 I ActivityManager: Process com.google.android.ims (pid 16066) has died: svc SVC
07-29 01:40:28.873 1968 3913 W ActivityManager: Scheduling restart of crashed service com.google.android.ims/.services.RcsService in 1000ms
07-29 01:40:29.003 19042 19105 E Unity : Vulkan - Out of memory!
07-29 01:40:29.003 19042 19105 E Unity : (Filename: Line: 211)
07-29 01:40:29.003 19042 19105 E Unity :
07-29 01:40:29.021 19042 19066 E Unity : Vulkan - Out of memory!
07-29 01:40:29.021 19042 19066 E Unity : (Filename: Line: 211)
07-29 01:40:29.021 19042 19066 E Unity :
07-29 01:40:29.193 1968 8582 I ActivityManager: Process com.touchtype.swiftkey (pid 16724) has died: prcp IMPB
07-29 01:40:29.193 1968 8582 W ActivityManager: Scheduling restart of crashed service com.touchtype.swiftkey/com.touchtype_fluency.service.FluencyServiceImpl in 10678ms
07-29 01:40:29.193 1968 8582 W ActivityManager: Scheduling restart of crashed service com.touchtype.swiftkey/com.touchtype.KeyboardService in 20678ms
07-29 01:40:29.202 1968 3393 I ActivityManager: Process com.google.android.inputmethod.latin (pid 17647) has died: vis IMPB
07-29 01:40:29.203 1968 3393 W ActivityManager: Scheduling restart of crashed service com.google.android.inputmethod.latin/com.android.inputmethod.latin.spellcheck.AndroidSpellCheckerService in 30669ms
07-29 01:40:29.208 1968 4094 I ActivityManager: Process com.motorola.launcher3 (pid 16037) has died: vis BFGS
07-29 01:40:29.208 1968 4094 W ActivityManager: Scheduling restart of crashed service com.motorola.launcher3/com.android.launcher3.notification.NotificationListener in 40663ms
07-29 01:40:29.208 1968 4094 W ActivityManager: Scheduling restart of crashed service com.motorola.launcher3/com.android.quickstep.TouchInteractionService in 50663ms
07-29 01:40:29.319 1968 2060 W ActivityManager: setHasOverlayUi called on unknown pid: 16037
07-29 01:40:29.352 1968 2490 I ActivityManager: Process com.joaomgcd.join (pid 17714) has died: vis BFGS
07-29 01:40:29.352 1968 2490 W ActivityManager: Scheduling restart of crashed service com.joaomgcd.join/.service.ServiceNotificationIntercept in 50519ms
07-29 01:40:29.352 1968 2490 W ActivityManager: Scheduling restart of crashed service com.joaomgcd.join/.service.ServiceAccessibility in 60519ms
07-29 01:40:29.754 1968 2040 W ActivityManager: Slow operation: 68ms so far, now at startProcess: returned from zygote!
07-29 01:40:29.755 1968 2040 W ActivityManager: Slow operation: 68ms so far, now at startProcess: done updating battery stats
07-29 01:40:29.755 1968 2040 W ActivityManager: Slow operation: 68ms so far, now at startProcess: building log message
07-29 01:40:29.755 1968 2040 I ActivityManager: Start proc 19144:com.motorola.launcher3/u0a45 for service com.motorola.launcher3/com.android.quickstep.TouchInteractionService
07-29 01:40:29.755 1968 2040 W ActivityManager: Slow operation: 69ms so far, now at startProcess: starting to update pids map
07-29 01:40:29.755 1968 2040 W ActivityManager: Slow operation: 69ms so far, now at startProcess: done updating pids map
07-29 01:40:29.900 1968 2040 I ActivityManager: Start proc 19157:com.google.android.ims/u0a16 for service com.google.android.ims/.services.RcsService
--------- beginning of crash
07-29 01:40:31.712 1968 8582 W ActivityManager: Force finishing activity com.DefaultCompany.SpeedyBugs/com.unity3d.player.UnityPlayerActivity
07-29 01:40:31.894 1968 2040 W ActivityManager: Slow operation: 52ms so far, now at startProcess: done updating battery stats
07-29 01:40:31.895 1968 2040 W ActivityManager: Slow operation: 52ms so far, now at startProcess: building log message
07-29 01:40:31.895 1968 2040 I ActivityManager: Start proc 19199:com.google.android.gms/u0a32 for service com.google.android.gms/.chimera.GmsBoundBrokerService
07-29 01:40:31.895 1968 2040 W ActivityManager: Slow operation: 52ms so far, now at startProcess: starting to update pids map
07-29 01:40:31.895 1968 2040 W ActivityManager: Slow operation: 53ms so far, now at startProcess: done updating pids map
07-29 01:40:32.011 1968 2040 I ActivityManager: Start proc 19215:com.google.android.apps.messaging/u0a115 for service com.google.android.apps.messaging/.rcsmigration.RcsMigrationService
07-29 01:40:32.262 1968 2003 I ActivityManager: Process com.DefaultCompany.SpeedyBugs (pid 19042) has died: vis +99TOP
07-29 01:40:32.385 1968 2060 W ActivityManager: setHasOverlayUi called on unknown pid: 19042
07-29 01:40:32.415 1968 2002 W ActivityManager: Receiver with filter android.content.IntentFilter@a66467f already registered for pid 19157, callerPackage is com.google.android.ims
07-29 01:40:33.341 1968 2040 I ActivityManager: Start proc 19293:com.google.android.googlequicksearchbox:search/u0a72 for service com.google.android.googlequicksearchbox/com.google.android.apps.gsa.nowoverlayservice.DrawerOverlayService
07-29 01:40:33.395 1968 2040 I ActivityManager: Start proc 19310:com.motorola.timeweatherwidget/u0a131 for broadcast com.motorola.timeweatherwidget/com.motorola.commandcenter.row2.WallpaperChangeReceiver
07-29 01:40:33.523 1968 2060 I ActivityManager: Displayed com.motorola.launcher3/com.android.a1launcher.AndroidOneLauncher: +1s530ms
07-29 01:40:33.545 1968 2040 I ActivityManager: Start proc 19343:com.touchtype.swiftkey/u0a114 for service com.touchtype.swiftkey/com.touchtype.KeyboardService
07-29 01:40:33.562 1968 2003 W ActivityManager: Stopping service due to app idle: u0a114 -24m14s376ms com.touchtype.swiftkey/com.touchtype_fluency.service.FluencyServiceImpl
07-29 01:40:35.563 1968 2040 I ActivityManager: Start proc 19496:android.process.acore/u0a12 for content provider com.android.providers.contacts/.ContactsProvider2
07-29 01:40:36.808 1968 2040 I ActivityManager: Start proc 19537:com.google.android.as:nonpersistent/u0a180 for content provider com.google.android.as/com.google.android.apps.miphone.aiai.allapps.contentprovider.ActionSettingContentProvider
07-29 01:40:38.448 1968 4091 W ActivityManager: Background start not allowed: service Intent { cmp=com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService } to com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService from pid=19215 uid=10115 pkg=com.google.android.apps.messaging startFg?=false
07-29 01:40:44.393 1968 8582 W ActivityManager: Background start not allowed: service Intent { cmp=com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService } to com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService from pid=19215 uid=10115 pkg=com.google.android.apps.messaging startFg?=false
07-29 01:40:45.414 1968 8582 W ActivityManager: Background start not allowed: service Intent { cmp=com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService } to com.google.android.apps.messaging/.shared.datamodel.action.execution.ActionExecutorImpl$EmptyService from pid=19215 uid=10115 pkg=com.google.android.apps.messaging startFg?=false

16

Hybrid Renderer V2 is very different from V1.
I don’t think I can help with other problems you outlined here, but I suggest that post on the related forum pages (e.g. with Burst).

To figure out what crashes it’s better to use a development build instead of release.

17

Click on the “View latest version” on the top of the document page to get the newest version of Hybrid Renderer package documentation. At the top of the main documentation page there’s a chart for pipeline compatibility with different Unity and SRP package versions, including the built-in renderer.

https://docs.unity3d.com/Packages/com.unity.rendering.hybrid@0.7/manual/index.html

18

Hybrid Renderer V2 is an early experimental version in Unity 2020.1. We just released the first experimental version behind #if guards. This version is not yet tested extensively with different mobile hardware. We have internally tested it with a couple of new Android phones (including Qualcomm and ARM GPUs). It’s not tested with emulators yet, and not tested with that particular Motorola phone.

The issue might also be in package compatibility. Currently the DOTS package ecosystem and the SRP package ecosystem are completely separate. Unity doesn’t release compatible verified SRP and DOTS packages in lock step. It can be tricky to find compatible packages. The whole DOTS ecosystem is in preview, and issues like this will be fixed before DOTS packages are validated and production ready.

This is the set of external packages we use in our internal hybrid.renderer (0.7.0) test project:
“com.unity.platforms.android”: “0.7.0-preview.6”,
“com.unity.render-pipelines.universal”: “9.0.0-preview.42”,

Minumum supported Unity editor version (for hybrid.renderer 0.7.0 package): 2020.1.0b15 (2020.1.0f1 is fine)

1 Like
19

Hybrid renderer URP support was added in hybrid.renderer 0.5.0 and needs URP version 8.0.0 and Unity 2020.1. You are using very old hybrid.renderer package. You need to update it. URP package also needs to be updated to 8.0.0. More information in the documentation:

https://docs.unity3d.com/Packages/com.unity.rendering.hybrid@0.7/manual/index.html

1 Like
20

Thank you! This is an old post of mine, from last year – I’m currently on the latest URP and hybrid renderer and I am happy to report that all is working fine :smile: However I sadly have to disable static batching for it to work, but that is a small sacrifice.