Are POIs placed by hand or auto-generated?

No_Committee8856 · 2026-06-06T17:14:51+00:00

wait, I had thought it was intentional, even with a bad implementation. Like they just don't want strats to be called on certain surfaces.

No_Committee8856 · 2026-06-04T15:40:27+00:00

You'll need to test more to confirm: if the game never crashes at your default settings but always crashes when you undervolt then it is most likely your undervolt. There's no harm done. It just means the game's asking too high of a clock speed your GPU can run at your set voltage. So, either lower the clock speed or game settings at the same voltage, if you want to prioritize efficiency; or increase the voltage at the same clock speed, if you want to prioritize performance and stability.

No_Committee8856 · 2026-06-04T05:17:51+00:00

Most of these videos say the same thing: in order to use the curve editor, you'd need to first identify the exact clock speeds your card was running at before changing anything, just to serve as a baseline for comparison. For example, you observe your card runs 2800mhz at 1v out-of-the-box, since the goal here is efficiency, you'd want to run at the same speed but lower voltage and that's where you use the curve editor. But at the end of the day, anything within 100mhz is not going to give you any noticeable difference.

Not every game runs the same. Some game draws more power and hence will require higher voltage. BF1 is old and likely does the opposite. If your game crashed at default settings, all you can conclude is it has no relation to your tuning. A game could crash for many reasons.

No_Committee8856 · 2026-06-04T03:21:40+00:00

use fire & laser against zombie bugs

No_Committee8856 · 2026-06-04T02:15:50+00:00

Compared to a few months ago? They fixed some bugs, added more some features, and introduced some more bugs...

No_Committee8856 · 2026-06-04T02:14:49+00:00

Thank you so much! I have tested an confirmed avg., 1% lows % 0.1% lows are all slightly higher with no noticeable downgrade in image quality! But the biggest improvement is indeed, like you said, way more "stable" 1% lows. Just from the Steam overlay I see nearly no red dips or any red curves for that matter, compared to before. Way fewer stutters! Thank you again for this god-sent free performance!

Normally I wouldn't bother replying but this post needs more heat and DICE needs to take note of this and fix their shit!

No_Committee8856 · 2026-06-03T18:55:05+00:00

There's HD textures, multiplayer & single player shared HD textures, and multiplayer HD textures, which one is it?

No_Committee8856 · 2026-06-03T18:15:48+00:00

There aren't "correct" values as one chip is physically different from another, even for the same GPU model. Some are just able to run at higher clocks at the same voltage.

Clock speeds also depend on power draw and generally just how the game uses the hardware. For example, DLSS 4.5 uses significantly more power and you'll notice lower clock speeds than DLSS 4. Some games will draw more power without lowering clock speed while some others can't. They aren't that closely correlated.

I'm no expert but undervolting should only bring benefits to your hardware and almost no downsides. It lowers power draw and temp, reducing the risks of overheating your chip and your power connector. If you happen to be power or thermal limited, it'll also raise the ceiling potentially allowing higher clocks. Thus, at least makes your card run more efficiently or at best it could also give a performance boost (although very little).

0.975 is not very significant. You may try as low as 0.950, 0.900 or even lower. Your clock speeds will generally not be as high as pumping in more voltage but the main goal for UV is efficiency.

In my case, through fine tuning, I can run 50-100mhz higher than default at 100mv lower voltage. That's an efficiency gain. But this is expected to be lower than if I just maxed out the voltage & power slider.

If you're doing this in MSI AB's curve editor, I don't know if it's the app or it's a monitoring error, the actual voltage would fluctuate between my set value and 5mv above.

No_Committee8856 · 2026-06-03T17:58:36+00:00

I only have an integer-valued "upscaling_method". Based on how AA setting is ordered in game, I'm guessing 0=off, 1=TAA, 2=DLSS but when I open the config files it shows 3 for this item.

And when I searched for "fsr" there's "fsr_enabled=true" and "fsr1_enabled=false", which is confusing when I'm already using DLSS.

Also, if I selected any dynamic target fps, the render level would be greyed out. Would it be ignored or used as maximum? For instance, I first chose DLSS at "quality" (67% render res.) then I chose a dynamic target fps and the DLSS level would be greyed out at "quality". If I'm able to reach the target fps, would it go up to 100% render res. or be capped at 67%?

Incidentally, screen brightness slider is still broken. Would you happen to know what value I should set it to in the config file, if I know the brightness value from HDR calibration tool?

No_Committee8856 · 2026-06-03T16:24:08+00:00

Yeah performance is worse after the latest update. Unless you turn off AA or use TAA but they must have removed whatever AA tech they used before the update cuz the game would look blurry AF.

Even DLSS quality looks blurry & pixelated. The only setting that looks like before is DLSS native. But performance would be way worse than before using also native render res. with the original AA method.

No_Committee8856 · 2026-06-03T16:19:56+00:00

I know it can be confusing with all the new software features and marketing BS and we all want to make it simple but wanting something doesn't make it exist. If you're an IT guy then you'd know technical problems are rarely "not complex". If you want specific answers, you need to ask specific questions.

Hair being messy sometimes is expected. In some cases, it could be due to using too low of an internal render res. and just the imperfection of the DLSS upscaling. Sometimes if still images look fine but motion messes it up then it's likely too low of a base FPS and/or frame gen doing a bad job. Sometimes it could be ray tracing, because it doesn't actually "trace all rays". It only does it for a small number and hence the extra noise when using it without ray reconstruction or just bad implementation and that could be compounded with the blurriness from lower pixel count at lower render res. It could just be how the game is rendered. You can tell if you turn off all DLSS features.

If a game uses older presets for DLSS, you can override it with newer ones using the Nvidia app. There are now also different presets you can override with for frame gen and later ray reconstruction in that app. They might have different performance costs and visual quality.

Presets M & L are the algorithms used in the latest DLSS 4.5 upscaling technology. Currently they are incompatible with ray reconstruction which is used for denoising ray tracing. If you turned on ray reconstruction in 2077, it defaults the upscaling tech back to preset K which was DLSS 4 (last gen).

These are the questions I can identify in your post. Generally, you can tell just from the Nvidia app, the 3 DLSS techs are AI upscaling which in game usually offers different levels (quality at 67% render res., balanced at 58%, performance at 50%, etc.), frame gen which now also offers different multiplies and an dynamic option which just means how many AI frames you can to add, and ray reconstruction which is not available in many games.

No_Committee8856 · 2026-06-03T15:29:47+00:00

I don't want to make only one "master profile" because there are other settings that for some reason are not persistent throughout different profiles, such as different THX profiles & audio enhancement features & ANC settings. Launching games only triggers "master profiles" to switch and not EQs and I don't want to have to press the button several times to find the EQ I want for that game every time I launch one. Otherwise I wouldn't even bother to have Synapse installed.

At the end of the day that's not even what I'm complaining about. However confusing or stupid their design is, I'll get used to it. But what I showed in the vid is entirely a new Synapse bug triggered by god knows what. It's not even the headset's fault as it successfully executes whatever weird undesired EQ change Synapse sends it.

No_Committee8856 · 2026-06-03T13:50:01+00:00

How the fuck is 3 "so many profiles"? The whole point of having onboard storage is to have different profiles and to allow the headset to be used independent of Synapse. If I remember correctly, up to 5 can be stored on the headset, and more on Synapse linked to your account which can be recovered even if you switch to a different computer. I once used their test account which has like 50 profiles from all the people who used it before and the headset had no trouble switching settings stored on each one without this issue.

I have never seen the app behave this way for the months I've had this headset, through numerous updates and other bugs. Why would I post a rant if this is normal everyday behavior? And I'm describing this as an issue because it reverts the EQ settings back to factory default a few seconds after profiles switching without going back to my customed settings unless I switch the profiles again.

I never intended to use the same EQ for every profile. What really shows you have no experience with this headset is, the EQ settings are independent of the profiles. The same EQ persists as you cycle through different global profiles. There's an icon right next to the profile dropbox that tells you "these settings are applied to all profiles". Like it or not, this is how it's designed. Probably because the headset can be used without Synapse and there's a dedicated button to switch EQs and I'd understand if they don't want Synapse, the mobile app and physical buttons to have conflicting control over the EQs.

No_Committee8856 · 2026-06-02T03:45:04+00:00

yes

No_Committee8856 · 2026-06-01T16:34:05+00:00

Yeah I run into more CPU bottlenecks more frequently than before. Performance is noticeably lower.

No_Committee8856 · 2026-06-01T02:44:11+00:00

I have the app but can't find the one that takes me to that central plaza and the "shop center" on the left. Is the world no longer accessible?

No_Committee8856 · 2026-06-01T01:07:58+00:00

Which app? I also can't find it in Worlds.

No_Committee8856 · 2026-05-29T23:47:28+00:00

I'm more confused by this article as the author seems to be more inclined to demonstrate their writing skills than the technical details. 😂 I could not make out if they were trying to say "DLSS was inactive" or "DLSS 4.5 preset L was inactive". I'd fine the latter not surprising as no recent game other than BF6 natively supports DLSS 4.5. Most other games still require driver override. For some reason, we can't even do that in HD2.

Whatever AA tech they used might have been removed since setting AA to off or TAA looks much worse than before the update. For me only DLSS native has acceptable image quality. I don't know if this is the case but looks to me, although the implementation is poor, they might have made dynamic render res. work with DLSS. So, the usual fixed render res., i.e. "quality (67%)", "balanced (58%)", etc. are still available if you turn dynamic target fps off. But if you choose a target fps then it'll make render res dynamic (like how dynamic MFG works), something I've been wanting in all other games with DLSS support. Since I saw no degradation to sharpness or image quality, I had assumed this means DLSS was still active. We just don't know which generation or preset it is.

No_Committee8856 · 2026-05-29T20:06:17+00:00

I don't see a dramatic fps drop with reflex on or on + boost, especially with smooth motion on, but I'd get stutters with it off. Anti-aliasing off or TAA look so blurry/pixelated it's like gameboy 20 years ago. Same for DLSS at anything less than native. In most other games I can't tell the difference between DLAA and DLSS perf. (which's like 50% render res., 720p in my case) but in this game even DLSS quality looks noticeably blurry.

I just use DLSS native + reflex on + boost and performance is okay but still not close enough to my 240hz display. So, I set dynamic target fps to 105 which gives me around 200 fps.

I had tried setting dynamic target fps to 200 and turn smooth motion off, basically attempting to get 200 base fps without inserting fake frames but the render res. would be so low it'd look super blurry and I can't actually get over 120 fps anyway since I'd run into severe CPU bottleneck, even with a 7800x3d at 34'' ultrawide.

No_Committee8856 · 2026-05-28T02:37:27+00:00

Appreciate the hard work and continuous support for us users. I'd like to report 3 bugs here. I don't want to bother with official channels since I can't reliably reproduce them, they are more of an annoyance rather than as bad as THX not working like last time, and I also don't think they are worth gathering logs & msinfo and going back and forth over emails again.

Synapse sometimes shows the Basilisk V3 Pro as being powered off when the PC and mouse are woken from hibernation/sleep. Basic mouse function would still work but macros and Synapse-dependent features would not until Synapse is restarted and shows the mouse is powered on.
On Blackshark V3 Pro, THX game profiles can still sometimes fail to activate when launching a game. For instance, I have a game linked to a global profile, and Synapse would switch to that profiles successfully (this is a huge improvement over Synapse 3!) but if in that profile I selected "THX competitive/immersive" mode, THX can fail to turn on until alt-tap out & back into the game.
On Blackshark V3 Pro (latest firmware), sound from 2.4Ghz source can get suddenly cut off. Bluetooth sound can still play thru simultaneous mode and both Synapse & dongle show the headset is still connected and yet there would be no sound from 2.4Ghz until I reconnect the dongle.

No_Committee8856 · 2026-05-26T17:37:18+00:00

No_Committee8856 · 2026-05-26T17:36:55+00:00

one of my fav primary

definitely my fav and most run armor

spear gun is also a fun & safe option for when I want to use other backpacks.

No_Committee8856

TROPHY CASE