Templates - Overview, Details, and Request for Feedback

A template manager would be awesome. I've seen others request the ability to make custom templates, but the manager would handle a bit more on top of that too.

• Template management
  • Redownload templates (I have an anecdote on this)
  • Find installed templates in your machine's file browser
  • Duplicate & upgrade templates made for older versions of Unity
• Find templates from others (from the Unity Asset Store? Could prompt users to purchase packages in the template that aren't in their purchase history - leading to more sales, maybe?)
• Create templates
  • Pick a Unity version installed on the machine
  • Pick packages downloaded from the Unity Asset Store to include
  • Pick packages found in user's specified location on the computer (or perhaps restrict to only Asset Store packages to help fight asset piracy & prevent simple reuploads)
  • Public availability / publish to the Unity Asset Store (this may obviously have issues with licencing of assets - see the bracketed sentence in the "Find templates from others")
    • May require a Super Mario Maker style verification of "play once to confirm there's no errors, and THEN you can share it"

I was changing some stuff with the post processing in a project spawned from the Lightweight VR template - imported a newer stack to try and get things working on a Windows VR headset since the default stuff wasn't showing up. Got some errors about the imported stack having some duplicate assemblies from the existing stack, so I deleted the older stack files. Little did I know that deleting the older stack files causing issues in my project would delete them from the template itself - any new projects made would say there are scripts missing on the objects for the post processing volume and on the camera itself, so it seemed that I corrupted the project template. I'm currently reinstalling Unity 2018 to repair my Lightweight VR template.

So please, PLEASE let us redownload templates at least!

 

Through the Editor - there was one set (the newer, imported PP stack) that had a regular file path in the project as per any other asset, and the other set (the older, part-of-the-template PP stack) that had a weird file path; something about Packages?
I deleted that older PP stack stuff from within Unity and it caused the issue. Unfortunately even reinstalling Unity 2018 didn't fix it - I feel like I must've messed up something major in the package system - but if that isn't repaired by a reinstall, is that handled by Unity Hub itself? The only thing I haven't tried is reinstalling Unity Hub, and I'll try that after this coming week's project deadlines have all passed.

 

I am only seeing 2D and 3D in the Templates window. The other 3 templates aren't there.

 

Sounds like good defaults, one question though. Can you have a template without all the global illumination and lightmapping stuff that is not always used in low-end projects or procedural projects (which can not benefit from pre-made lightmaps and light probes)?
Of course then it would help to have a white (not yellow!?) light in new scenes and default shaders other than the standard PBR ones!

 

This is a really nice feature!

Almost a year ago, there was a call for suggestions for starter kits/templates. We delivered a few suggestions, and the Tower Defense Template was the first one created.

Are you planning on putting those "templates" in with these "templates"? I think that would be very convenient.

 

Does the Unity Hub Self- Update on Start-Up? It really should, If not. Also I read that Patch Releases were left out on purpose. This is truly a horrible idea. Patch fixes are there to fix bugs and should be considered part of this. I did notice that Patches are installed in the Main Unity directory and not in a folder with a name showing there version # etc.. Maybe that should be changed instead so they may be included.

 

This is odd considering they are only a few days away from releasing Beta 5.

 

1 question and 1 feedback
Question: I currently have a Unity 2017.3 project. Is that possible for me to apply and overwrite the 2D template to the project after I update project to Unity 2018.1 when it's out of beta?
Feedback: Hopefully u guys can figure out best possible configuration for both 2D and 3D template.

 

Awesome. Btw will the templates configure Scriptable Rendering Pipeline too?

 

Maybe I should ask in more detail.
1) Is that 2D template configured with Lightweight pipeline?
2) Will SRP i.e. Lightweight and HD pipelines work out of the box and only need modification if there is special need for the project?

 

The naming of these templates makes understanding their pipelines somewhat unclear and this seems to be creating some confusion for users, like @optimise, jbooth, and myself!

So I think the names should be more descriptive and consistent. Here's some possible ideas:

• 2D
• 2D Lightweight
  
• 3D
  
• 3D Ultra
• 3D Lightweight
• 3D High Definition
  
• VR Lightweight
  
• Custom (empty project?)

Adding "Built-in" would make this even clearer:

• Built-in 2D
  
• Built-in 3D
  
• Built-in 3D Ultra
• Lightweight 2D
  
• Lightweight 3D
  
• Lightweight VR
  
• High Definition 3D

 

I really like the idea of these templates but as of right now... I can't seem to get them to work.

Using 2018.1.0b8, starting a new project using the High Definition template I get a few errors like this one:

C:/ProgramData/Unity/cache/packages/packages.unity.com/com.unity.render-pipelines.core@0.1.27/CoreRP/Shadow/ShadowUtilities.cs(250,51): error CS0227: Unsafe code requires the `unsafe' command line option to be specified

This is without me touching anything. There are also a lot of warnings like this one:

Shader warning in 'DeferredDirectionalShadow.compute': loop only executes for 1 iteration(s), consider removing [loop] at kernel DeferredDirectionalShadow_Contact at ShadowSampling.hlsl(204) (on d3d11)

They're fairly descriptive errors / warnings but I'm not sure why there are errors showing on a template created project. Have I missed a step in the installation process of 2018 perhaps? I installed it via the Hub.

 

@Charles_Beauchemin, why 2D template does not apply lightweight pipeline?

 

@optimise that is because the 2D and 3D template are just recreations of the original 2D/3D toggle for new projects found in previous version of Unity that simply setup the editor and had nothing to do with render pipelines



The "3D Ultra" template only causes further confusion here because that's just the built-in render with all settings on max and post-processing.

I also found these template names somewhat ambiguous at first, and the common confusion between templates and render pipelines is what prompted me to suggest we give them more explicit names above.

 

What is "built-in"?

"2D built-In" as opposed to "2D custom"? How is custom differentiated?

If the differentiation is simply the SRP then should it not be default rather than built-in (if default is even a thing anymore in SRP)... Why have 20 different options which are essentially variations of 3 toggle options when you could separate the single drop down into the different options; 2D or 3D, SRP you want to use, packages to automatically add, etc. Essentially building the template you need from components.

Just seems like separating it would would lead to less confusion is all. Having to look for the specific version of the template you need from 10 options becomes harder if people can add custom templates to the list and there is no clear difference between them.

Food for thought

 

As in Unity's built-in (legacy) rendering pipeline versus the new scriptable rendering pipeline. This is exactly how Unity describes it (Unity Built-In Pipeline vs Lightweight Pipeline), however, they also plan to ship "built-in" SPRs in the future, which makes the term somewhat ambiguous. So it's probably not any more helpful or less confusing to use here.

"Custom" was just a placeholder term for basically a project with no pipelines, but then I guess you're really just using "built-in" again, so kind of redundant and probably pointless now that I think of it.

As for making the templates more modular; I don't think that's possible and goes against their whole design, but maybe I'm mistaken and someone from Unity can enlighten us on the subject. My suggestions are really just about improving what we've got now. Maybe a "legacy" prefix would work better?

 

Makes sense, I tend to stick to stable versions of Unity for fear of betas messing up my projects so I haven't tried the 18.1 beta... hence why I don't know the terminology.

I don't think so, from what i read in the first post it doesn't go against it (at least not entirely) 2D or 3D is still more or less a toggle of which mode Unity gets put in, settings are preset depending on the (for lack of a better word) "quality" settings that you want (lightweight, ultra, etc) and some have additional content. So in my mind there are 3 areas that a template covers. So in theory the first two could be easy to implement with some filtering to get valid options for the content so that it is compatible with the other settings.

 

Anyway I would like to see 2D Lightweight Pipeline template available that able to support 2D game development optimally and it will able to support Shadergraph for this 2D game development too.

 

The problem I see with your suggestion is that templates cover all aspects of a new project (editor, graphics, assets, etc.) and are just a quick way to get things setup. The 2D and 3D templates are just recreations of the editor only settings found in previous versions of Unity (see this), so they're somewhat inconsistent with the new templates.

I also think separating templates out into components would kind of defeat their purpose and make them not templates anymore. If you actually want to pick and choose each setting for your project, then a template isn't really what you want. You can already do that by just using presets, the package manager and/or importing asset packages, etc.

 

Yeah, maybe. Perhaps have basic templates and advanced ones? I'm sure that whatever Unity end up doing will be fine. I guess it would only save 5-15 mins once at the start of the project anyway...

 

The ability to create custom templates would be awesome!

 

Can you maybe add a OpenVR controller input example script (with a Input Manager mapping for VR controller inputs) to the Lightweight VR Template?
For example trigger/button input and touchpad axis etc.