So Enlighten really turned out to be a waste of everyone's time.

First, I find it amazing how single devs can release much more efficient alternatives in all of the different lighting departments and approaches:

With that said, once upon a time, Unity was ‘an indie friendly’ engine, but not only it takes a huge team of professionals to make something out of Enlighten baking, but it turns out even with Microsoft’s backing, the makers of Recore had a ton of lighting challenges and the end results suck and did not look current gen.

This entire Unity cycle was met with complaints about Enlighten ridiculous bake times and in the end, they were never solved.

I am just saying next time plan better your acquisitions. Because not only did Unity waste 2 years trying to build something functional out of the Enlighten codebase that won’t be reusable, but now you will have to clean this mess out of the engine veins and every single corner that it infected (dependences).

Brigade3 is of course a step in the right direction. But Unreal is getting that too so it seems like it wasn’t really Unity’s initiative but OTOYs… while Enlighten feels as if Unity stepped in their door as beggars considering how much more of a better treatment they give Unreal.

3 Likes

Am I the only one who likes enlighten? LOL

Don’t forget

https://blogs.unity3d.com/2016/09/28/in-development-progressive-lightmapper/

Yeah, there’s a new lightmapper in development because the Enlighten one is so terrible that it was the only course of action.

6 Likes

Only really for bigish open levels. I’ve had no real issues with my one room game :slight_smile:

That’s only because you still haven’t finished the whole room :stuck_out_tongue:

4 Likes

Im guessing you didn’t read this 9 part guide to Precomputed Realtime GI which shows how to optimise an example scene’s bake time from 7.5 hours to 2.25 minutes?

https://unity3d.com/learn/tutorials/topics/graphics/introduction-precomputed-realtime-gi?playlist=17102

14 Likes

That’s an oxymoron Andy. :stuck_out_tongue:

3 Likes

[quote=“Dustin-Horne, post:7, topic: 652620, username:Dustin-Horne”]
That’s an oxymoron Andy. :stuck_out_tongue:
*[/quote]
*

Eh, its what its called in Unity. From the doc I shared:

“When working with Precomputed Realtime GI, a lighting precompute is the process of calculating the bounce of light around the static geometry within a Scene in the Unity Editor and storing this data for use at run time. This process reduces the number of lighting calculations that must be performed at run time, allowing realtime bounced lighting while maintaining interactive framerates.”

2 Likes

I would say that enlighten NEEDING such guide (and 30 minute long manual scene preparation) is a problem.

20 Likes

I’d just like to add to OP’s original post.

Link #1 looks decent but very similar to unity’s planned progressive lightmapper, probably isn’t as great as enlighten for GI, most likely is closer to what ‘beast’ was ← never used beast mind you.

Link #2 looks like an unbiased render, somewhat similar to cycles in blender. Not really getting the point of that in games other than static shots. Unless I’m otherwise mistaken.

Link #3 still unusable unless the guy can match the R&D of cryengine, plus requires a beefy graphics cards and windoze machine, not great for a mac user :slight_smile:

So meh…

1 Like

Clearly you boys haven’t seen this :stuck_out_tongue:

https://www.youtube.com/watch?v=BJy0B1uWfTM

6 Likes

I disagree; any and every piece of complex software requires a tutorial to learn and understand it. Id argue that a 30 minute scene preparation guide for Realtime GI bake optimise times (and the wealth of knowledge you’d get with it) is pretty damn amazing!

Anyway, we are working on a Progressive Lightmapper for statically baked Lightmaps; so users can have the best of both worlds.

8 Likes

The other lightmapping system was better and faster

2 Likes

You are right. It makes me wonder why Unity is wasting their time on this:
https://blogs.unity3d.com/2016/09/28/in-development-progressive-lightmapper/

The links are about how Unity made a deal with Geomerics, the ‘leading lighting solution’ of the market and it turned out into this mess, while single developers are able to make a functional solution that with a staff a little bigger would be production ready so it should be an even smoother process with Unity staff size and R&D, but instead it is only now that they have addressed and admitted to their lighting issues.
You can thank ReCore for that.

Link #1 wasn’t chosen for a particular reason other than showcasing a small dev able to get done a lightmapper in his spare time, while Unity even being fully aware of the current lighting issues [which some still ironically try to claim do not exist] is still taking all this time to address them.
Problem is that if you never used Beast, you won’t know that it was a much better lightmapper that was only limited by Unity 32bit RAM limitations and to this day we have people not moving to Unity5 and still using 4 because Lighting in Unity5 is a no go. Unity5 would have been perfect. BUT ENLIGHTEN RUINED IT.
When I call it A MESS I am not trying to be annoying. They ruined MANY people plans and vision and hold them back for a whole cycle.
Beast with 64bit support would have been PERFECT. Zero complaints!
Their GI+baked and GI could have been a separated experimental builds or asset store asset or anything they wanted.
… But guess things were looking too good to be real.

Link #2 eventual goal is realtime. The same as Brigade3 from OTOY which Unity is also getting (go watch the presentation and the press release). And we will get there.

Link #3 point is that with Unity’s staff size and R&D, you could have that exceptional looking GI baked into lightmaps for the whole production cycle and only go do the full baking at release, which would be insane. Lightmaps update in a second!

What Unity needs to solder into their skulls is that once they get their lighting, Unreal Engine is DEAD.
Of course I like competition, but I want people to get off their heads that mess of an engine is production ready.

Unity has always been production ready. It is always been the lighting and they know that it is the lighting hence most of the Unity5 showcase being around lighting.
It just didn’t work! The main feature of Unity5 was its most disappointing one. It did not deliver.

/not-a-rant

1 Like

Highly opinionated ranting. Enlighten is so much faster than the “solutions” you mention at run time when it matters. For example on console, mobile or any normal desktop that didn’t cost many thousands.

Assuming you want “realtime” GI and not just baked lightmaps which Enlighten again isn’t the problem, but the shadows and UV packing.

Enlighten isn’t the problem here, but integrating it in an evolving engine is.

5 Likes

Enlighten works amazingly for Precomputed Realtime GI. Progressive Lightmapper will work amazingly for Baked Lightmaps. Different tools for different setups. You just need to research and learn how the systems work before utilizing them; same with any software, tool or craft. :smile:

Quoting that blog post you shared:

"It is not a replacement for realtime GI. It only works for baking in the Unity Editor, so you cannot bake from within your game. This rules out baking GI for procedural scenes in-game, or the ability to change the lighting setup for time of day and baking on load. We want to nail the baking workflow in the Editor before we take it further.
Also, it is not necessarily faster than baking with Enlighten. If you setup your scene well for Enlighten it can be very fast, so we cannot guarantee that all scenes bake faster with the Progressive Lightmapper. However, the time between starting a bake and getting some visual feedback will be significantly faster with the Progressive Lightmapper."

And about the two systems working together, from the comments section of that blog post:

Both lightmappers will work seamlessly with the new mixed lighting system. This will offer a mode using baked indirect + AO in conjunction with realtime lights and shadows or realtime lights with baked shadows.

3 Likes

You are only corroborating the point I made:

Unity brought Enlighten to the table as an improvement over Beast lightmapping but it ended up as a downgrade in the lightmapping department while bringing Precomputed Realtime GI as a new feature rather than a replacement one because there wasn’t Realtime GI before Enlighten.

That means the ideal course of action would have been as it is being done now: to make both lightmapping and realtime GI separate. But it has taken you long to admit that. I put it in Enlighten never being conceived as a tool for baking lighting, not on Unity’s end. Problem is that Unity wanted a convenient hybrid that simply does not exist and as shown by ‘Also, it is not necessarily faster than baking with Enlighten. If you setup your scene well for Enlighten it can be very fast, so we cannot guarantee that all scenes bake faster with the Progressive Lightmapper.’ still do not admit to it.

Either the Progressive Lightmapper is bad or they do not know the difference between having zero feedback if Enlighten has locked up or is still going :smile:

Efficient UV packing is the main challenge behind lightmapping, not the lighting equations sir :smile:

And I wouldn’t agree with this point of view. If following the guide speeds things up by factor of 200 hundred it means that unity comes with horribly misconfigured default settings. There’s really no other way to say this.

It is important to realize to that people do not need PERFECT results. The user should be able to press a button on a default and get a reasonable result in reasonable amount of time. Those who want more need those guides. 7.5 hours on default settings is not a reasonable amount of time.

In unreal engine lightmapper “just works” out of the box. If user wants to tweak, they can do, but Unreal’s lightmass is faster on maximum settings than unity is on default.

Besides, WHY should I need to fine-tune positions of individual light probes manually? This stuff should be done automatically. Also, where is GPU acceleration and network swarm support? Where are translucent surfaces affecting light that passes through them? What about situation when people don’t need gi and just want a lightmapper?

There was a very big thread about it, actually:

6 Likes

Correct me if I’m wrong, but I’m pretty sure there’s never been a proper easy solution to bringing outside lightmaps into Enlighten. Up until Unity 4 we could lightmap in a separate program then bring it into Unity. Not so with 5. That’s the way it was when we first started working with 5, at least. So, we had to use Enlighten instead, and it took forever, and it cramped our style. If there’s a decently easy way to import external light maps (as simple as it was with previous Unity versions), can someone point me in the right direction?

3 Likes

I believe “Bring beast back” thread mentioned some interface with possibility of connecting to external lightmapper, but if I remember correctly it was incredibly arcane. So the best idea for lightmaps would be probably either a legacy shader or something like plugging existing lightmaps into emissive channel (and possibly writing shaders for making this happen).

2 Likes