700+ Hours, My Feedbacks and Thoughts

[Vystrix]

Patch Notes

[Mix-Master]

@Nevieth

Unity has it’s own issues, but I’m overall fine with it. I think they’ve done impressive things with it so far, but there’s always more they can do. Updating the engine itself so as to allow FSR and DLSS would make heaps of help for a lot of people, and I know they’re working on it, albeit slowly and carefully.

Unity does support DLSS i believe, Its a 4 step process too. Nvidia would even send people over to assist i hear too.

https://docs.unity3d.com/Packages/[email protected]/manual/deep-learning-super-sampling-in-hdrp.html

[Nevieth]

Yep, but the current version of Unity used to develop Last Epoch doesn’t support it. Mike has talked about it before on his streams. EHG is working slowly and carefully on updating the version of Unity to enable DLSS and FSR, but they don’t want to rush it and break stuff.

[Mix-Master]

Ah ok, Makes sense.

[JunkHeadJoe]

My dude! Thoughtful and well written post. Great write up. Thanks for taking the time. I really hope the devs take a look at it.

[kangst]

Unity compiles down to CPP using IL2CPP. Thats been around a VERY long time. Its not some .net assembly laying around waiting for reflection and decompilers.

[Vystrix]

@JunkHeadJoe

My dude! Thoughtful and well written post. Great write up. Thanks for taking the time. I really hope the devs take a look at it.

Hey, thank you for your kind words.

@kangst

Unity compiles down to CPP using IL2CPP. Thats been around a VERY long time. Its not some .net assembly laying around waiting for reflection and decompilers.

I have experience with Unity, so I’m familiar with it. What I’m referring to is a different situation, and I’m sure EHG is aware of it. I wouldn’t want to delve into details here to avoid drawing attention, but the use of IL2CPP doesn’t change the situation. Nonetheless, thank you for the information.

[kangst]

Fair enough, and yes probably best not to advertise it

I agree with a lot of your feedback. This feels more like a consequence of reaction vs planned in defect leakage from a software perspective.

The 1.0 patch (aside from the service bottlenecks) - was a fairly stable build. And it feels the team panicked and quality suffered and things that should not have been merged may have been merged unintentionally.