One Batch: Combine hundreds of materials into one draw call

Could you take a look to the OneBatchData function for the Amplify Shaders and see if everything is working fine? In my previous message I described what I've found, but sadly I have no idea how to solve it.
I was sure it would have worked out-of-the-box and now I'm stuck with an incomplete optimization :'(

 

Yes, I'll take a look soon.

 

Thanks. I'm on a razor's edge for a demo that I should show, so here it is why I'm so annoying

 

I had some issues :

• The occlusion map slider on onebtach config is handling the emission of my materials;
• Emission slider isn't handling anything at all (with or without a map);
  
• Metallness and smoothness values are not handling anything at all (with or without a map);
• Cutout value isn't handling the cutout value of my vegetation and it's weirdly handling the opacity of my detail maps;
  The emission color nor the albedo color are not HDR as the standard shader does;
• Trying to increase the resolution of my maps from 1024 to 4096 is causing my unity to crash;

Few things i would be really thankful if you could implement them (even on another paid extension pack of shaders variants) :

• Compatibility with LWRP/HDRP;
• Compatibility with most of the uber shaders on Assetstore : Uber / Lux Plus / Apollo;
• Different Versions of OneBatchShader : vegetationVfx / snowVfx / mossVfx / wetVfx / puddlesVfx / rainVfx / sandVfx / GlassVfx;

 

I've upgraded my project to 2019.1 (not any scriptable render pipeline, just the old default one), and suddenly all my onebatched objects became completely black - seems like a shader issue?

Anything I can do about it?

 

You might try reverting them and recombining them. I did a quick test of one batch on 2018.1, but maybe something didn't upgrade right on the already batched assets?

 

@jbooth Thanks for the reply. Tried reverting - it did absolutely nothing, and also some of the meshes are no longer assigned to the meshfilter - show up as "missing mesh", even though the meshes created (copied?) by your module actually exist in the Onebatch folder. So I ended up undoing all this manually, cause I have to move on with the project.

So as far as you know all should work OK on 2019.1?

 

So, I may remove all of those sliders and settings in a future version of One Batch. The thought is to make the workflow such that you uncombine the objects and change settings, then recombine them. The main reason to do this would be to make supporting more shaders easier- because right now the process of supporting shaders is very labor intensive. If there's no GUI to write for each shader, then it makes it a lot cheaper to add new ones.

The main way I've seen One Batched used at the studio level is as part of the build process, which doesn't need a GUI for. But I do realize some people use it for individual assets and such, not project wide.

It's unlikely that one batch can be made to work with 3rd party shaders and released- this is because it would require taking their shader code and heavily modifying it all, which would mean releasing their shader code as part of my asset. You could do those modifications on your own branch of course, but depending on how those shaders are structured it might be quite difficult.

 

Like I said I tested on my example project and it worked fine, but it's quite possible your setup has some new complexity which causes an issue. There is a new prefab workflow and they may have changed some internal or something.

 

Hi, could you make an update for 2018.3? I'm running 2018.3.14 and the example scene is just black. All the examples are there but no textures are being displayed.

 

I’ll take a look

 

eu comprei o ativo oneBatch porem nao consigo usar cutout, fade e tranparencia funcionam, mas o cutout nao. oque devo fazer? Agora não funciona frente verso "double sided" Existe algo que pode ser feito? obs: cheguei aqui clicando em "Site Suport".

 

@JasonBooth Hi have you make any progress on this yet? Totally unusable in 2018.3.14 at the minute unfortunately.

 

I installed on 2018.3 and 2019.1 and can't repro your issue. If you are installing into an existing project you might try installing it into a new project to verify.

 

Hmm, not sure what's wrong then. I installed into a fresh project, opened the demo scene and the examples are still just completely black. The textures are set, but blank on the material, though you are able to see a preview.

This is across all views - Scene, Game and Play Mode. Is there some extra step required for installation apart from importing from the store?

 

nope, can you try a different unity version and see what happens? When I get back home I can test on windows as well (on OSX laptop).

One other thought- make sure your not running under graphics emulation..

 

Hi,

My materials also turn black when using One Batch on Unity 2018.3.0f2 (even example ones)

Is there a fix to it? Is it maybe a version issue?

Thanks!

 

That's odd since that's the development version. On windows? OSX? I take it your materials are using the standard shader?

 

It was on Windows. Originally I was using a different shader but I switched to Standard and it still didn't work.

I also tried just using the example and still got black spheres.

https://gyazo.com/860c0d8b3710ed27d4fa131b16c4b448

I'll probably be updating soon so I can let you know if that fixes the issue, maybe I just did something wrong somewhere.

 

Actually, check to make sure the example scene isn't already converted (using the one batch shader).

 

HI,
awesome asset! But since my project relies heavily on HDRP - do you maybe have some ETA about srp compatibility for OneBatch?

 

Not working on this currently, especially as the pipelines are not really stable yet.

 

Maybe I am wrong but it seems that LWRP is out of preview state. HDRP is scheduled for 2019.3 I belive.

 

LWRP is “out of preview” but yet they are doing massive breaking changes to it. You can believe the hype, but neither pipeline is near stable enough for the average asset store project. If you have a graphics engineer on hand, great, but most don’t. Producing anything of significant shader complexity for the SRPs is just a massive headache right now, especially since they scrapped the surface shader abstraction.

 

Hi Jason, in regards to LWRP, etc., do you suggest that projects starting now should just stick with vanilla 3D workspace, with optimizers like Microsplat and One Batch (and other optimizers for vanilla 3D Unity)?

Given the Unity history of needing years to work out bugs in new stuff...??

I ask because I'm beginning an important new project that will take a few years to complete. If you could give me your thoughts I would appreciate it. From what you've said (and I implicitly trust your opinion), I'm thinking these pipelines are a gamble at the moment, and might be for a while, considering that my studio is trying to create a professional product to release on the market.

 

Do you have a graphics engineer? If you do then something like LWRP might make sense. Without one it’s a harder decision.

 

Hey Jason, I bought this tool but unfortunately I'm still working in Unity 2017 and it would not let me download it. Switching over to 2018 is not an option. Any way possible you could do a build for 2017?

Thanks,
Rod

 

No, it uses 2018 only features.

 

Any way that I could get a refund?

 

PM me..

 

Hi Jason, does this work with the Hybrid Renderer?

 

You mean rendering from DOTS? Shouldn't care- there's no runtime component what so ever, it just generates meshes/materials at edit time that share a single material.

 

Yes, that is what I meant Sounds good, will give it a try!

 

Another question we have an in-game editor where we assemble our assets, is it possible to do the generation at runtime?

 

Not really designed or suitable for that.

 

Got it, thanks.

 

Hi!
I need a clue: I have lots of (3d objects) meshes that share over 50 materials here and there + 6 material are Uber Shader. And baking is fine if all uses Standard Shader, but not if some are Uber, so...?

 

switch them to the standard shader - or remove those objects and keep them as the Uber shader.

 

Hi. We have a semi-large project with 60 or so materials made with OB. Each material has several textures. As soon as I instantiate the first object the screen freezes for 10 seconds. Subsequent instantiations are instant. Is this normal? Any way to stream the loading process in the background?

 

You should catch it in a profiler and see what is causing it. It's possible that you're not prewarming your shaders and since the standard shader is massive (and OB uses a modified version of the standard shader) that it's compiling it on the fly, but that depends on what platform your running on (some use precompiled shaders, some compile on first use). But the sure fire way is to look in the profiler and see what is happening.

 

The profiler just hangs for 10 seconds just like the editor so additional data points there. So, the behavior is, while in the editor there's a 10-second hang when the first of 60 OB materials is rendered. While in the build, there's a 10-second hang when you launch the app which is the best place for it but it still adds 10 seconds to loading time. I'm on a PC which I assume uses precompiled shaders in the build.

Correction: all 60 objects actually share one OB material. Our 3d artist really optimized these objects.

 

You’ll have to use a non-unity profiler that can show you what unity is doing while it’s paused. Without that it’s impossible to say what it might be; on Windows the shader would already be compiled, so it’s not that.

one rare case I’ve seen is Unity serializojg texture arrays into YAML instead of binary when set to forced ascii, but that’s only in the editor.

 

Hi

Awesome tool

What about URP support for 2019.3-4?

 

not working on it currently..

 

Hello. I'm getting the following error when building for Oculus Quest (aka Android) :

Texture Creation failed 'ASTC_RGBA_8x8' is not suported on this platform

Would you be able to provide any guidlines for settings for this platform please? (I'm trying some things, but Unity rebuilds the whole project when you change such settings, so it's quite a slog)
Cheers!

Further to this, its worth pointing out that this results in a NullRefException Error, which results in at least one of the meshes not being set to the OneBatchStandard shader. Additionally it leaves me unable to revert the combine.

 

That seems a little odd since I'm pretty sure ASTC is the suggested format in the Quest docs. Note that the texture format can be overriden on the config, so you don't have to reimport your whole project to test. Your other option would be to try ETC2.

 

Hey @jbooth - I've not been able to get this to function with my scene.

Setting all 'Default Texture Settings' to ForceETC2 did eventually allow the process to run with no NullReferenceException error.
I do still get warnings though...

ETC2_RGB' is not supported on this platform. Decompressing texture. 

(also for RGBA8)
The result is a scene with texture arrays that appear ok, but black geom in the scene with the oneBAtch shader applied with these tex's - presumably due to the decompress error above.

Also some geom prefabs got corrupted by the process...
Specifically, those prefabs that have multiple geom objects in them - IIUC these are the meshes OneBatch reconstructs. In these cases it appears that the transform was ignored.

If I send my scene could you take a look and tell me where I'm going wrong please? Cheers.

 

Sure, and this is on android as a build target right? I recently updated MicroSplat to do a fallback method until if finds a texture format which is supported, so I could port that over as well.. Even though ETC2 is required by the openGLES3.0+ specs it seems some hardware is still saying it doesn't support it, which is odd.

 

Hi @jbooth! I'm also getting the ASTC error that the above folks are..I'm on Android platform, and the error seems odd as my build settings are also ASTC...

Oddly enough, even changing the compression setting to 'Force ETC2' causes the same error for me :

Texture creation failed. 'ASTC_RGBA_8x8' is not supported on this platform. Use 'SystemInfo.SupportsTextureFormat' C# API to check format support.

its that setting there, right? (I also tried putting in a platform override for android with the same results.



edit: forgot to post my unity version: I'm currently on 2019.2.11f1

 

A thought just occured to me; I'm using Amplify Shader editor with my material, and it happens to come with a texture array creator. The main functionality of your tool that I need is the part where vertex colors are applied and the PropTex is generated..so is there a workflow method with this tool where I can choose to just perform that part of the operation and use my own premade texture arrays?

I understand if that's a big feature ask, and if it is no worries, just wondering if that would make the whole pipeline easier for us with texture arrrays ready to go.