Nice! And MIT too. Perfect; I’ve given it a star now.
Shine Get
Nice! And MIT too. Perfect; I’ve given it a star now.
I agree. I don’t have the time but someone should point this out to the dev via an issue on GitHub.
So basically don’t use this in anything commercial because the phrase “feel free” is different to legally libre and gratis. I personally wouldn’t touch this until it’s released under a reputable license.
Shame they didn’t use a proper license when publishing.
Exactly. Source it from upstream at build time or something so it’s transparent.
You’ve been on vacation for 5+ months?
Also wouldn’t it be best to post this communication in the issue thread?
Given how long this has gone on now, it’d probably be best to inform your community that you’ll be removing BLOBs from the source and for them to be produced during build otherwise this shadow is going to remain.
This was the first time I’ve ever heard of your software and has kind of made me want to steer clear of it.
This is StackOverflow after all. Your question is wrong. Your problem is wrong. You are wrong. I am right. Thread locked. Go read this other post that is totally unrelated to your problem I’ve decided isn’t the problem you’re facing because. I. Am. Right.
Yeah we’ve been going by primary-secondary where I am for the just 6 to 7 years now but I don’t think a universally agreed replacement for the terms exists yet.
Yes. What’s modified about it?
What’s modified about it? Certainly not the readme.
deleted by creator
It does need! I wonder if they’re using an open source library or wrote it themselves. I’ll have to go dig through the GitLab source code. Thank you.
What tool did they use to make that diagram? Looks awesome!
Both DLSS and FSR are software leveraging the GPU to do the heavy lifting.
FSR is using HLSL shaders to do its thing whilst DLSS is using nvidia’s tensor cores to run an ML model.
Both solutions are great in different ways but I wouldn’t call FSR limited. If anything, Nvidias is the more limiting given it only works on specific hardware, is proprietary, and requires a lot more from developers to implement it vs FSR which is hardware agnostic and MIT licensed.
I love your passion but I think you published on GitHub a little too soon. Rather than pitch solutions, keep it to the problem space definition for now.
Then, reach out to the upstream developers and see what their thoughts are and how you can contribute. I’m sure there is definitely space for a interoperability library that makes it easy for any creative FOSS app to integrate and enter into this open ecosystem concept but rather than inventing it for upstream, you should invent it with upstream.
Good luck and stay this passionate - the FOSS community needs people like you!
So all they have is a boilerplate script that doesn’t do anything yet?
I’d rather see this as a collaborative effort between upstream rather than a “layer” of scripts, not to mention their “phase 3” is forking upstream which we really don’t need.
I’d rather see this project’s team simply working with upstream and sending PRs / patches.
Adding to this:
In the United Kingdom, people just add a contact to their phone book called “ICE”. You can learn more here.