openmw.org

We have to implement vanilla behavior for the sake of mods, too. Just because it's annoying to certain mods doesn't mean it's a bad behavior. The vanilla behavior is not a workaround for a bug. It affects way more than just that one thing. They just implemented birthsign bonuses that way so that the...

That sounds like a problem.

Using the nodemask system is definitely the right way to go for something like this, even if it seems gross. "Doesn't cast shadows" is a pretty general thing. For example, future full conversions would probably love to do something like apply it to animated foliage and have AO simulate the...

I checked and vanilla does show shadows for invisible NPCs: https://imgur.com/a/3Ik4WTc

It is to be assumed that any permanent changes to the character that happen during chargen as a result of character configuration should act as though they are inherent to the character. That is more basic and fundamental than what the effects look like on the HUD. I was never once confused by birth...

That is not a valid reason to not replicate the vanilla behavior. It affects more than just restore attribute, it affects how you level and your training, as if it were an inherent bonus, just like how different races have different base stats, and that's the way it should be . (In other words: what...

Yeah, some people think that way about FOSS because of the GPL , but the GPL shouldn't have that kind of influence on how people think about FOSS. The GPL is absolutely not a good standard for what kinds of dependencies should render something no longer FOSS. Game maker is proprietary. Let's say som...

That's about the GPL's system library exception, not whether a non-GPL project is FOSS or not. FOSS is not defined by the GPL.

Unity is basically a very elaborate platform library or VM or whatever you want to pretend it is. Using it as a target doesn't make the project itself stop being FOSS. Same with things like game maker. Likewise, any FOSS projects that run on proprietary gaming hardware don't suddenly become "tr...

Sounds like some kind of LOD bias option could be implemented for this. 0 being the default, but if you lower it to be negative the full LOD mesh remains in use farther into the distance (e.g. for an extra cell or two), before it would switch to a lower LOD (i.e. nothing when there's no LOD mesh to...