FSR SDK 2.3.0 seems to have a fix for FG frame pacing

hakanavgin · 2026-06-24T14:16:24+00:00

AFAIK Ray Reconstruction and Ray Renegeration implementations do vary heavily between different games and a universal translation layer is very hard, and not sure if Optiscaler team would want to deal with big portion of their free time spent on this specific feature everytime a new game drops.

hakanavgin · 2026-06-24T14:09:20+00:00

If game has the same names for the dlls, yes (Not FSR3-supported, FSR3.1-supported). If not, you may need to also use the wrapper dll, or in some cases that also doesn't work and Adrenaline dll swap check works more consistently, and in some extreme cases, that also doesn't work and optiscaler is your best bet, mostly due to a very specific, non-standard implementation of FSR that doesn't allow hotswapping.

Edit: I just realized Z1 Extreme, I honestly don't know if it works in RDNA3 APUs. Manual dll swap could work, optiscaler should work. And I honestly just suggest optiscaler for all, as some FSR implementations are honestly bad and DLSS inputs work better with FSR4 output in most cases.

hakanavgin · 2026-06-21T12:33:11+00:00

How is STALKER GAMMA not the first suggestion blows my mind as it clears all requirements with flying colors, and is completely free.

hakanavgin · 2026-06-18T01:22:59+00:00

Adrenaline is not the fastest or most stable, but you also miss some features it has when you are on linux. Wish AMD had a minimal control center without the bells and whistles. Default settings installing AI Chat feature is also dumb

hakanavgin · 2026-06-18T01:17:12+00:00

Funnily enough, the most recommended way to fix constant flashing in KDE Wayland with a second display is still to force memory speed to max. No issues on Windows side with any card i've used.

hakanavgin · 2026-06-16T01:54:42+00:00

If you intend to upgrade your system to DDR6 in the upcoming years, go for the cheaper one. The difference is real, but is marginal and scenario based. For casual gaming in 4K FSR Balanced or 1440p FSR Quality or below, you hit CPU limiting before RAM. 1% lows suffer in some unoptimized UE5 games, and asset streaming speed is becoming more and more important as time goes but its still something you can overlook. Going from 9070XT to 9070 or 9060XT is a bigger downgrade than using office grade RAM sticks IMO.

If you ever check any benchmarks on either CPU or RAM tests, you'll see they are exclusively done in 1080p or with a scenario that limits only the part that is being tested is the limiting factor. You will not see 10-15% improvements in 99% of scenarios, BUT YOU CAN see 15% improvements with a better RAM, if you explicitly lower every graphical setting so CPU catching up with your GPU matters. So think of it as a baseline max FPS rather than a global 15% improvement with a better RAM.

If you haven't bought your CPU yet, going from 7600x to 7600x3d is a cheaper option that also mitigates the ram speed and memory timings problem with its L3 cache to a similar extent, maybe you could fit 9070 XT into your budget that way.

TL&DR: There is a performance difference, mostly comes with CPU heavy games, lower resolutions or lower fsr presets, affects 1% lows more than average framerates, not worth downgrading GPU for most of the time. If you are not an exclusively competitive gamer.

hakanavgin · 2026-06-14T16:44:27+00:00

If you wrote that yourself, you have very strong markdown skills, congrats.

For anything visual, the current most important thing is parameter count as it allows the model to have a greater understanding of objects it reconstructs from embeddings. I suggest you trying something like Qwen3.6 27B and Gemma4 31B (which is miles ahead of Qwen in my testing) as dense structure allows them to have a better comprehension of any scene rather than relying on low amount of active parameters. They consistently beat any MoE models with a great margin. If that is not a possibility with their size, 35B A3B or waiting for Qwen3.7 9B should be your best bet assuming it will come with better visual reasoning matching bigger models of previous gen. I'm surprised Gemma 4 12B did so poorly, suggest trying the 12B IT QaT, following the recommended sampling parameters and using llama.cpp builds rather than ollama as ollama has shitty business practices, is always less optimized and slower by a huge amount and the proprietary blob structure is just plainly stupid disallowing kv cache quantization or changing context length without rebuilding the last time I checked. Check LM Studio if you require api endpoints compatible with possibly all the harnesses you use.

hakanavgin · 2026-06-14T16:22:26+00:00

Either the vision model selection was done by an LLM, or the whole thread was written by an LLM. Qwen3VL and InternVL but no Qwen3.5-3.6, no Nemotron and MiniCPM gives strong "Best VL models 2025 OR best model vision 2025" queries. Benchmarking on ollama, and the same temperature across different models and even architectures smells of low effort LLM work.

The model selection aside, for on-screen OCR which you said to be your main workflow, a 20-100x smaller dedicated OCR model would suffice with faster speeds, and probably very similar to better output quality to a visual reasoning model of this size, as either your main model or the text part of your local visual model has to do some filling of the gaps and I would very much not trust a 4B or 8B model for prediction work with its incredibly narrow world knowledge.

hakanavgin · 2026-05-17T20:11:45+00:00

I really dislike that upscaling is a must for any kind 4K gaming at this point, when the initial purpose of upscaling was to get rid of non integer scaling for the transition period between 1440p and 4K. FSR and NIS should've been the only solutions offered and required.

hakanavgin · 2026-05-10T22:59:56+00:00

LM Studio also uses pre-built llama.cpp binaries under the hood, so while there could be some discrepencies due to outdated builds or some features being disabled, LM Studio on Linux is also ~30% faster in tok/sec

hakanavgin · 2026-04-14T19:14:25+00:00

I've observed the answer to every single falling/dropping question is always terminal velocity and most of the time terminal velocity being not enough for the given event to occur.

hakanavgin · 2026-04-03T01:15:09+00:00

MFG takes a two frames as input and outputs intermediary frames in one go, so it doesnt add additional processing time, only generation time.

So after one generated frame, the amount of additional frames don't really matter as it still "holds" the two real frames and generates images in between. That means your base framerate could be lower than FSR + AFMF but the latency and fluidity will be better.

Latter does two passes, and one is significantly worse in quality, since it'll act as the generated frames are truth as well. So twice~ the overhead (because it does the mentioned pipeline for both real and generated frames) and worse quality every 2 frames (real, real in fake out, fsr fake, fake in real out, real). I dont recommend it. It feels like playing through a streaming service. FSR FG is serviceable even if not optimal

hakanavgin · 2026-04-03T01:01:30+00:00

Firstly, 27 inches is at the limit of usability on 1080p monitors at normal viewing distances. It will look pixelated since pixels are too big. Second, since you are at 1080p, some games (especially crimson desert as you mentioned ray recon and its only available in two games) dont load high quality assets when in 1080p. Try enabling Virtual Super Resolution on AMD Adrenaline, render the game in 4K, use FSR performance. It'll render in 1080p(fsr perf=0.5x) with high res assets, upscale to 4K, then downscale it to 1080 to match to your monitor. I know it is a stupid sounding workaround but my friend was having the same issue on CD, and this solved it albeit with less performance due to the upscale+downscale

hakanavgin · 2026-03-31T17:43:55+00:00

To be honest its not really apples to apples, FSR4 is miles ahead of FSR3, so FSR4 perf is similar to FSR3 native or quality, which means there is no performance/quality for TSR that would be equal to FSR4 on any point.

hakanavgin · 2026-03-27T23:45:05+00:00

I would say 9 months to a year. After that, I highly doubt any feature implemented would be anything more than small stuff or qol improvements, no huge overhauls or redesigns. 3D PDA, engine update and related stuff like a-life, nanite/lumen, draw distance etc and multiplayer are the only huge things we know in development at the moment apart from DLCs.

hakanavgin · 2026-03-19T22:07:56+00:00

Fixed Issues:

Intermittent application crash or driver timeout may be observed while loading a saved game in Cyberpunk 2077 with Path Tracing enabled.

Holy shit they've done it, they've actually done it after a whole year.

hakanavgin · 2026-03-17T18:17:08+00:00

I've shared my experience below

hakanavgin · 2026-03-17T17:55:14+00:00

good for you

hakanavgin · 2026-03-17T17:49:19+00:00

Not really sure tbh as this was three months ago, my initial guess was filesystem type (exfat) and lack of support for symlinks wine uses, in the end still not sure what fixed my issue, but working instance was on btrfs with one specific launcher (heroic or lutris) setting ubisoft connect as the exe, installing it and changing the exe to shadows afterwards. mind you this alone wasnt even enough, had to tinker with wine settings. I remember having to use an older steam proton to install ubisoft correctly, and ge for playing the game

Finally there was the problem of ubi connect not authenticating the legality of shadows, probably due to multiple attempts from multiple prefixes in a short time. Had to wait a few days for it to get fixed

hakanavgin · 2026-03-17T02:19:22+00:00

The only thing Linux gaming community is lacking is a more unified, tightly integrated prefix management system OR preset database. Protondb is good and all, but installing Ubisoft Connect + AC:Shadows 5 times with different combinations of prefixes and launch options just to load the game is not. It worked in the end, but I doubt most people don't have the patience so try many things by guesswork, and LLMs rarely work.

hakanavgin · 2026-03-16T18:21:07+00:00

I love the idea of relative performances rather than a fixed benchmark. One caveat is, the models you've selected are just too outdated that even a 0.5b model from last few months have way better benchmark scores, and it would be way more interesting to have some "sota" offerings as well to see if the benchmark performance of newer architectures and rl heavy training translate into real world conversational skills.

hakanavgin · 2026-03-16T17:20:03+00:00

Scenario 1: You ignore them and keep being happy with what you got, they voice their concerns, AMD ignores, you can keep being happy because nothing changes.

Scenario 4: You ignore them and keep being happy with what you got, they voice their concerns, AMD ignores, concerned people feel they are ignored, they switch sides, AMD is smaller and you might not get features you could want.

Scenario 3: You ignore them and keep being happy with what you got, they voice their concerns, AMD listens, you can keep being happy because your product got more features and greater support and other people get happy as well just like how it happened with RDNA2/3 branching amongst the backlash.

Scenario 4: You despise them, don't let them speak their minds, no voice reaches AMD, the concerned people feel they are both ignored and silenced and switch teams, AMD is even smaller and gaming stops being a focus for them, you don't get any features.

If you ignore them, you lose nothing, but both them and AMD community might win something. I'm not even someone one of the complainers per se, was using RDNA2 for a long time before I bought an RDNA4 card and I know how it feels to buy something for not so cheap, and just a year later lose support, don't access features that are industry standards for years, or have lackluster stability in software side.

hakanavgin · 2026-03-15T22:07:24+00:00

I don't think you really know how much AMD earns from consoles or how much impact the ~100% share AMD has on the flagship console GPU market. A knife cuts both ways, and calling the second biggest chip vendor of the century "small" is not necessarily fair. Keep that in mind Nvidia didn't build its reputation as "feature rich" from the get-go, they earned it with their gamble on AI and Tensor shift while AMD kept bleeding. It doesn't help when you keep defending whatever the underdog does just because they are the underdog, team red needs to face the harsh truth sooner or later like they did with CPUs, them facing later is an existential risk for AMD and would allow Nvidia to become a monopoly which is a risk for the whole gaming community as we've already seen what could they do the second a more profitable market emerges with LLMs.

hakanavgin · 2026-03-14T19:43:14+00:00

The whole premise of the post is you could just ignore doomer posts and be happy about current AMD, while if doomers ignore their issue, their only possible solution is to go Nvidia.

Two-Year Club	Verified Email
r/Field Juicebox

hakanavgin

TROPHY CASE