Bake mesh with lighting

[sirkitree]

Would it possible to bake an existing mesh's texture with the lighting setup within Neos?

[Frooxius]

That's essentially lightmapping. It's planned, but it's a very major feature that involves a lot of complex work, so it won't happen anytime soon unfortunately. I'd recommend using 3rd party tools like Blender to bake lighting for now.

[Ruikio]

Hey all, small brain here.

Not sure if -JUST- voting is going to give this any visibility, but I'd like to just share my support for this feature.

Complex features is what we want in Neos, right? At some point stuff like this and terrain manipulation or whatever big words we wanna use is something that's going to be help push Neos passed other social platforms.

Since there isn't any easy way to find links or to have this info if they aren't around the proper word of mouths, it's kind of up in the air of what is being worked on currently.

Taking time for easy things and putting that time into features like this is probably the go to, yeah? In fact isn't this a decent boost for world optimization as we don't need as many light sources?

[H3BO3]

Froox has stated he would check Godot's 4.0 open-source lightmapper for integration viability when it releases. It's mainly a matter of finding something compatible with neos (and with unrestrictive licensing) or else froox has to invest a lot of time into making his own custom solution

[Ruikio]

See, this is info. This is something that definitely should be copy pasta'd to every post regarding baked lighting if this is what is going on. If it's stated to just be a complex system, putting the time, even if it's small, for say things that don't matter.. like say bhaptics probably isn't the go to. Take that small amount of time and put that somewhere needed to push the platform.

[TehTurk]

Not necessarily the case, there's a fine line what needs to be worked on now vs later. Alot of Rendering/Lighting stuff is typically being saved for last in some cases too because once that's touched you don't really want to be messing with it again. Typically with stuff like bhaptics which your comparing too is time sensitive and there is often contractual obligations or Froox has the kit for only so long so it needs to get added immediately. So please be mindful when your saying stuff doesn't matter because they do. The issue is sometimes people ask the same questions over and over expecting a different response which then makes a conversation circular and doesn't help anyone. This isn't really an issue of time management but planning/resources. You can't boil down everything to one aspect with development. If you want info, comments like these are perfectly fine, as long as they are focused on spreading the information or inquiring for the future.

[Ruikio]

I'm glad you think they're fine, I did too!

The point of that comment was to bring to light that the comment received by Sirkitree did not have the extra information that was provided by H3BO3, effectively deflecting it and putting it on the back burner with no further discussion. I'm sure a lot of things are planned here in Neos. Just which ones are next.

As far as I'm aware, there was also no real public information on it being a contract or not. If I recall, the situation was someone showed up using it and out of nowhere we ended up getting support for it. That's what me as a consumer sees. Does Solirax need to announce all contracts they received? No.

When you have features like this that are here to push world building and optimization forward, which bhaptics does not, it's a little frustrating not being in the loop or in the right place at the right time in a world that is most likely private.

If information is needed to a major feature like this, it needs to be there. Copy pasta if need be. Otherwise you have people like myself or other individuals who see this as another feature blow off like the ones collecting dust pages back.

Off topic: Things like feature voting have been removed from the Patreon tiers if I recall without a change log, so it comes down to what's next?

Edit: To clarify what's next as in what's next feature wise since we can no longer vote for features. Where do we get this info for those not in the right worlds at the right time

[TehTurk]

I mean it wasn't a deflection it was adding information to the conversation, answering what you wana know. Where you wana focus the conversation matters too. Hey even I don't have all the public info, this is my response on what the reason could be or to give clarity to the situation. Instead of making assumptions.

Oh I completely agree, that's definitely something that needs to be worked on, the loop is a bit bumpy atm due to the holidays, and stuff is kinda getting ready for the next year.

And this conversation is the point of adding that. You yourself could be adding this too ya know instead of demanding it, the team only has so many resources doing certain things. The point of github isn't to be this checkoff list, it's to make sure everything is kinda account for so when the issue is closed you don't need to go back.

Then this is something to bring up in the discord, your now turning the issue of the Mesh Baking into something else entirely so please use the proper channels for situations like these. Which I have asked before not to do in here.