Well I didn’t think I was ignoring anyone here but apologies!
So a little bit of peak behind the curtain here, which hopefully I don’t get in trouble for but I think it helps, but there are always things going on that I’m actively not allowed to comment on, whether that’s a confirmation, or denial or anything due to some internal rules, embargoes, and things like that. With those kind of things, I have to be very, very careful about what I say which can be interpreted incorrectly and be seen as confirmation that something is or isn’t coming. I too am beholden to the chains of PR.
Some more broad info on things like FSR4.1 on RDNA 3 (not that specifically, but more how these things work on this side of the fence) but these things take a lot of work to get to a state where it can be released, so there are many internal steps and checks and things like that before it can even be talked about, because if you talk about it too early, or something comes out about it, but then it gets delayed due to technical issues, or any of the thousand other potential issues, then it goes from being a great new feature, to a broken promise. So information is generally tight lipped, but it’s not something that is developed over a couple of weeks. There’s a lot of people much smarter than myself who work on this every day.
I’m new to AMD but have been in and around the industry for quite some time and I can say things always take more time than you’d think and there’s more steps and phases and all of that fun stuff than you would expect.
So all that to say, yes, I saw the FSR comments but unfortunately, couldn’t comment on them until I got the all clear (even though I really wanted to) and sometimes that’s just the case! I’m definitely reading everything and passing it on internally, so even if I’m not commenting or responding directly to things, everyone knows what folks are thinking and saying.
I’ll see if I can figure out a better way to make sure folks know I’ve heard them and am not ignoring them in the future!
Cheers!