LuciferSam86

Looks like you're inside a OneDrive synced folder , try to put everything outside like c:\games\d64 . IIRC another user had a similar problem with gzdoom and he fixed the problem moving the game outside onedrive

Hoping to not sound harsh or disrespectful, as a developer that sounds disrespectful pooping like this on other work especially if done for a hobby. Of course, some features will never implemented like disabling the ability to save manually ( I would not accept such PR, too). IMHO costs nothing to fork the project, other devs might come if they find your alternative interesting, no need to "take over" projects, because they are "wrong" and there is nothing to "take over", the source is there.

I'm not a C++ dev, just a C# dev, so I might take a bit more time but I was able to make a new Zscript function for damage modify like the AbsorbDamage just for fun. Let's see for the mapinfo part , and if not accepted, I just learned some c++ 😁

I think changing that default is kinda too late , and then you have the other side complain. The best course would be a new MAPINFO setting. Right now I'm looking at the parser and how it works, let's see if in the week I can make a PR for that.

That for sure , but on my first days I was enjoying gzdoom with texture filtering, then something changed my mind so no filtering anymore even in games is supposed to be there like Q2, Half life and tomb raider 2

and then change the default, the user with the older config will say "Hey! I like texture filtering enabled, why did you change that!?". It will be the same problem but from the other side, and the user will re-enable it doing ¯\_(ツ)_/¯ Maybe a ZMAPINFO setting, like the sector-lighting mode? The sanest thing to do is put a README, explaining how to do it IMHO

That was really clear, and I like your approach.

Oh yeah I totally agree with you, since I have a nice 4070, and I like the vision you have for your project. Let's say I would like to see a support for at least two generations of GPUs like the current and the previous one for vkDoom, and not just the latest. Of course everything is imho :)

I mean another option might be on your readme just put "hey my mod was designed without the texture filtering, so please follow these instructions" , then it's up to the user to follow the instructions. Their computer their rules. vkDoom is cool, but you might cut some users from using your mod because of hardware too old, or just not compatible. I was reading they are interested to put bleeding-edge features if they were interesting for them, so for absurd they could implement a vulkan feature found for the RTX 5090 but not for 4090.

I suppose the samples, which everything is under their licenses . GM itself is a standard, another thing are the soundfonts which are recorded from someone and they might be under a precise license

I still how the "texture filtering" is a deal breaker, because it's just an option you can change in less time than make a thread to complain 😅

"I'm too young to die" all the way

I mean making a fork is kinda easy, but keeping your fork updated with the latest features from upstream might be more complex. When moq author put a spyware-like functionality on his library everyone started to fork to remove that thing, but keeping new features/bug fixing (and squashing) and so on, that's another level. I suppose it's the same with a source port, especially with new features, and if such changes are other than changing a default cvar value, maybe keeping compatibility with older hardware (and for older I mean +5 years which starts being centuries for the IT world). vkDoom looks interesting since looks more than a "rolling release" of GZDoom breaking compatibility by design. and of course: before accepting a suggestion, there should be some controls before to be sure everything doesn't break.

How you can say "no" to that smile or don't enjoy that?

At least you have asked the Arachno author if you can redistribute his work?