Jump to content

k4bn

Member
 View Profile  See their activity

  • Posts

    95

  • Joined

  • Last visited

 Content Type 

Everything posted by k4bn

  1. k4bn
    @Magix I can't really see the issues that you are describing on your in-game screenshots, it looks like standard Far Cry 5 to me. I would love to help more, but that might be why it's hard to convince other people, assuming that there is actually something abnormal going on with your system.
  2. k4bn
    Yeah, it looks like there's some aliasing left on the helmet, primarily the white parts where the light gets reflected. However, MSAA doesn't work on this particular type of aliasing, it can't solve shader aliasing from the shader on the helmet because it only works once per pixel. This can only get solved by some kind of supersampling. The white lines on the car just look low res. It's a really old game, so that's understandable. And I'm not sure about the jagged windows icons and other stuff, can you show some examples of that? The in-game screenshots are still incomprehensible, there's nothing to even comment on there.
  3. k4bn
    Not sure what you mean about the colors, reflections etc. I haven't played rFactor, but those look fine in the screenshots. The only difference is that the fence uses a high negative LOD/mip bias, probably like -5 or something. Since clamp doesn't work, the sharpness from the high negative mip bias causes the aliasing/shimmering. In the other screenshot clamp works and the mip bias of the fence gets set to 0. Compared to the fence and the road lines(and some other stuff you can see in the screenshot), the other objects seem to have a default mip bias of 0 or 1, so there is no difference when clamping. And yes, AA is not the "issue" here, both examples use 4x MSAA. The issue is that clamp doesn't work in both examples. As for the pics you posted, I'm sorry, but it's incredibly hard to tell what is going on here because I have no reference point to anything. I advise you to at least take full screen screenshots in-game and explain what you think is wrong or, like I did, provide comparison screenshots.
  4. k4bn
    Never said you had any misunderstanding about AA, only that some users in the thread do. Yeah, I read your other posts and I get the general idea, but I don't think that you have the same issues that Kelven is talking about. It's mostly this difference:
  5. k4bn
    You can only fix the first issue completely in some games that have DX9 or DX10 by using AMD driver supersampling(games like Dishonored, Half-Life 2, L4D2...) or doing manual LOD bias adjustment in regedit. For NVIDIA, you can do it with SGSSAA(DX9/10 only) or by changing LOD bias in inspector. Both AMD supersampling and NVIDIA SGSSAA do an auto-LOD adjustment so you get rid of the negative LOD shimmering/aliasing and the temporal aliasing almost completely on 8x(depends on the game though, some are better, some are worse). https://docs.google.com/spreadsheets/d/1ekUZsK2YXgd5XjjH1M7QkHIQgKO_i4bHCUdPeAd6OCo/pub?output=html You can also try to do manual LOD bias adjustment in the NVIDIA inspector. https://forums.geforce.com/default/topic/529407/geforce-drivers/clamp-negative-lod-bias/14/ All of this only works in DX9/10, for DX11 games it's impossible AFAIK. The only thing you can do is regular downsampling/VSR/DSR, but this doesn't do auto-LOD adjustment so you will never get results as good as you would with SGSSAA, thin objects like fences will still flicker in the distance. The only new AA type that works nicely with negative LOD is TAA and the developers need to implement it correctly so it's works similarly to SGSSAA. This is still one of the best implementations that I know of, and it's been modded into the game: A decent TAA + at least 2x DSR/OGSSAA is IMO the best solution for newer games for image stability if you can afford it and if the game supports it.
  6. k4bn
    The problem is that there's a variety of issues mentioned in the thread. The one that is most prominent that seems to be the case for most of the users is the universally broken LOD bias. For example: https://www.reddit.com/r/hardware/comments/3rwy5m/nvidia_will_fix_excessive_gpu_idle_power_use_at/cws4xl4/ (#6) Note that this isn't nvidia exclusive, it's tied into the rise of DX11 and the lack of DX9 and DX10 in games where the developer has full control. The next one is the misunderstanding of how anti-aliasing works and how a raw aliased image looks like in motion. For example, a lot of people still think that this is an "issue", while it is most certainly not and I've proved it countless times: https://www.youtube.com/watch?v=2XXS5UyNjjU&t=164s (at 2:44 you can obviously see what is going on) I'm not sure what issues you have, if you want further help you should show us exactly what you mean.
  7. k4bn
    I saw the video you sent me and I saw the explanation. The person is not talking about any sort of a problem. He is simply telling you how to make and add your own mipmaps to an SDK for a texture that has no mipmaps to begin with. This is only useful if you intend to do modding. I am glad that you are finding this interesting, but I advise you to first get into the fundamentals of graphics, then the details of how aliasing and anti-aliasing works before going into the more complicated bits of graphics. Trust me, these sort of ideas come here almost monthly and everyone gives up after a few days because they are trying to solve something that they don't understand. https://alfonse.bitbucket.io/oldtut/ http://naturalviolence.webs.com/generalaa.htm Also, try doing this in OpenGL to get a general idea of what mipmapping is and to test out if it works. https://www.youtube.com/watch?v=H1ogRfMsc64
  8. k4bn
    I see where the confusion is, but there is a difference between using alpha tested objects + negative LOD(these trees for example at 5:42) https://www.youtube.com/watch?v=KTyhI0BCP4U vs no mipmapping and nearest neighbour. Read this: https://medium.com/@bgolus/anti-aliased-alpha-test-the-esoteric-alpha-to-coverage-8b177335ae4f The first video is basically a person modding in his own mipmaps, so if this is what you want, my advice is to start modding every single video game that has no mipmaps, I'm fairly certain that this has nothing to do with your GPU not being able to mipmap or something along those lines. As for LOD/mip bias, read this: http://naturalviolence.webs.com/lodbias.htm Here's some reasons why developers use TAA with negative LOD, the results are pretty close to normal supersampling. https://twitter.com/SebAaltonen/status/943078228071198720 Maybe tweet some of them if you are more interested in this stuff.
  9. k4bn
    Hello and welcome to the thread! Thanks for the information, a lot of it has already been addressed and you are definitely on the right track regarding your issue. The Skyrim S.E. textures in the video most definitely use mipmapping, however, as you've probably figured out, a negative LOD bias is in use, hence the texture shimmering. The problem with your video is that you do not have anti-aliasing on(correct me if I'm wrong). The reason why the game uses negative LOD is because it uses TAA, I explained this in one of my last posts. I've booted up Skyrim S.E and the game looks pretty clean with TAA on, so make sure to check if that was the issue. Similar thing happened to Witcher 3 when the devs changed the TextureMipBias to -1 in a patch. Users quickly started complaining, so the devs put the bias in the config so you could change it back to 0. Compared to Skyrim S.E, Witcher 3 has a weaker temporal AA implementation, so it doesn't work as well as Skyrim's negative LOD does with TAA.
  10. k4bn
    Props to xquizt for making a PUBG comparison with his friend! https://www.techpowerup.com/forums/threads/anti-aliasing-not-working-for-any-game-on-my-pc.232367/page-3#post-3829357 @xquizt Even though the aliasing in this example is technically "normal", it doesn't mean that it should remain that way. The 1080 has a lot of extra GPU power on 1080p and you should be able to force a higher level of supersampling to reduce aliasing to a minimum. MrBonk's post on temporal aliasing summarizes this very well. https://forums.guru3d.com/threads/which-anti-aliasing-reduces-temporal-aliasing.394462/ Note that I don't play PUBG, so I'm not sure how temporally stable the game is on higher levels of OGSSAA/DSR.
  11. k4bn
    The "flickering on edge" is due to negative LOD/mip bias. Negative bias with TAA emulates supersampling for textures and gives you 2x AF for free, it essentially converges to temporal supersampling. Like when you do 8x SGSSAA, the driver usually does auto-LOD adjustment to -1.5 LOD bias(you had to set these values manually in the good old days), this compensates for the blur of the SGSSAA. Similar thing happens here, this is basically why TAA is used with negative LOD/mip bias and gives such a nice result both in Fortnite and in the BF1 example with the alpha tested negative bias shimmering foliage. And yes, TAA is implemented differently in different video games. It doesn't 100% remove aliasing itself and sometimes it doesn't even work on some types of aliasing(above example with moire pattern). The point is, xquizt says that changing AA settings doesn't make a difference in any game, so apparently he doesn't have the same "problem" that you have, because clearly TAA works for you in this particular instance.
  12. k4bn
    Can you record gameplay footage of a game that actually has good anti-aliasing where it should be very easy to notice the difference? Like Fortnite for example, I remember that lordante was able to get the game approx. 90% clean with "Ultra" anti-aliasing, compared to "Low", which had a lot of aliasing. If you decide to do that, make sure to record changing the different AA settings and recording the differences, or lack thereof.
  13. k4bn
    The aliasing in the last few videos is mostly due to negative LOD bias and alpha testing, this has already been discussed. I don't play PUBG, but this video seems to explain it all: Check out 1:43 for example, "Ultra AA" also has a lot of aliasing, so it's probably just the game. You can't change LOD bias in dx10+ if the dev chooses to prevent driver overrides, so best thing you can do is try out what I already mentioned in one of my posts. However, most dx10+ games don't allow you to do that, so the only thing left is probably just supersampling the game. Your 1080 should have no problem with that. http://naturalviolence.webs.com/lodbias.htm
  14. k4bn
    Hello and welcome back to the thread. Please re-read my previous posts, you seem to be be confused on what AA is and how it works. As for your friend, please post some gameplay footage showing that. Although, honestly that wouldn't really prove anything because you can still set SGSSAA x4+ and AA off in-game and "rig" your proof just to prove your point. Also, please consider that you may not have the same problem as some people in this thread. You mention that AA doesn't work for any game, but a lot of people are claiming that temporal anti-aliasing solves the "problem". That's partially correct, but even the "best" TAA methods don't work on all types of aliasing, for example: left side is TAA + triangle-geometry, right side is TAA + raytrace and jitter, but it's basically a custom shader for this particular surface
  15. k4bn
    It seems that you are mostly concerned with temporal aliasing(shown in 0:27 here https://www.youtube.com/watch?v=_V8bBLcbRIs for example) Use this to reduce it: https://www.youtube.com/watch?v=8scOOiAvyj8 if driver supersampling isn't working. You can read my older posts about this sort of stuff and there's useful stuff in here http://naturalviolence.webs.com/generalaa.htm
  16. k4bn
    Please read the thread before posting. Most cases of aliasing and appropriate types of anti-aliasing have already been thoroughly explained.
  17. k4bn
    0:04 is called z-fighting, this is common with games like skyrim and fallout and this isn't something that you can solve afaik (unless there's some sort of a tweak for the engine or something). As for the aliasing, you need to turn on TXAA in the options to get rid of the temporal aliasing. I recall that TXAA and 1440p OGSSAA looked great. For arkham knight, downsampling/OGSSAA with in-game AA should be fine. Unfortunately no SGSSAA flags for this one it seems. Would be possible if the game had MSAA and you could enhance it to get some transparency supersampling.
  18. k4bn
    I'm assuming that you have already tested out all options and that the game stays this way. I haven't played that game, but this looks like a case of a negative texture mipmap bias. Your driver might be forcing it in Rocket League(and some other games) or the game uses it now, so your textures alias more than usually. To simplify it, I'll call the mipmap bias LOD bias. Since Rocket League is DX9 you might actually be able to override this. Go into inspector and under the Rocket League profile set the Antialiasing - Transparency Supersampling to 0x00000008 AA_MODE_REPLAY_MODE_ALL. After that set the LOD Bias(DX) to 0 or 1 and set Negative LOD Bias to Clamp under Texture Filtering. I'm not sure if this works for Rocket League, but I tested it out for Serious Sam 3 and Far Cry 3 and I was able to replicate insane amounts of alpha tested foliage shimmer with a negative LOD bias. If this doesn't work, it shouldn't be too much of a problem, there is still an option that is commonly used, especially in newer games. The negative LOD bias works very nicely with SGSSAA because it compensates for the blur of the AA. In that case, you follow this guide to force SGSSAA: https://forums.guru3d.com/threads/nvidia-anti-aliasing-guide-updated.357956/ If that doesn't work either, try this: https://www.reddit.com/r/RocketLeague/comments/57qzfu/simple_trick_to_make_rl_look_much_nicer_and/ The goal post and the other opaque thin metallic objects aliasing is most likely the infamous Unreal Engine 3 specular and shader aliasing and this can only be improved by SGSSAA(This is the "minor aliasing" that should be present). If the LOD bias tweak doesn't actually work, try using my SS3 profile settings as your Rocket League profile and use 4x MSAA in-game. Again, this might not work, but it's worth a shot. https://imgur.com/a/O4QO8 Also, I'm not sure whether SGSSAA actually works in Rocket League. Try using default AA compatibility bits or one of the usual UE3 ones in the guide if that doesn't work or ask for them on guru3d. In SS3 and Far Cry 3 I had to use specific AA bits to replicate this. This could be problematic because you may not be able to modify the LOD bias either if Rocket League needs specific bits. https://www.reddit.com/r/RocketLeague/comments/4bom0j/has_anyone_found_good_antialiasing_compatibility/ Edit: Oh also try to turn off MSAA(if it's even on) to see if the texture aliasing is still present, I already mentioned that CS:GO had a specific case where a ground texture aliased when 4x+ MSAA was present. This turned out to be an AMD driver issue.
  19. k4bn
    PUBG: use "Ultra" AA(temporal supersampling/UE4 TAA), it works on all types of aliasing, but it can introduce some blurring and ghosting depending on the quality of the filter Destiny 2: use resolution scale(downsampling), not SMAA, it should work on most types of aliasing, apart from temporal aliasing from sharp specular highlights on thin surfaces, it can usually only partially reduce this sort by decreasing the number of white lines (example: https://www.youtube.com/watch?v=S3GyFfYBZkw), depending on the game. It's not as good at dealing with shader and specular aliasing as temporal supersampling and TXAA though, but it does reduce it very nicely in most games, but not all(I'm looking at you, Alien Isolation!). Aliasing on the stairs and the bottom of the statue(8:57) might be tricky to tackle with resolution scale, haven't tested it out myself, but bear that in mind. Same goes for the specular aliasing on the yellow horizontal surface at 9:01 https://www.youtube.com/watch?v=Am_BTlDkFaE A high level of resolution scale/downsampling should at least partially reduce it though, from 4k to 1080p maybe even remove most of it Overwatch: resolution scale Assassins Creed 4 BF: use TXAA, it should work on most types of aliasing, especially works great on temporal aliasing and foliage shader aliasing AC4 BF AA comparison: https://www.youtube.com/watch?v=l2vm-Hm5dP0
  20. k4bn
    In what game?
  21. k4bn
    Maybe for some other users, sure. I meant streetburger's case, his AA is working perfectly. As for others, no one seems to know or care enough to prove or disprove anything unfortunately.
  22. k4bn
    Well, it seems that it took a few years for the OP of another thread like this to realize that there is literally nothing wrong with his system(the image quality one or w/e). Don't worry, you'll get there as well one day. As I've said, your games look absolutely fine, supersampling is working like a charm. I already gave you info on most types of aliasing that exist and why they exist. Use this as your guide and you'll be fine. https://forums.guru3d.com/threads/nvidia-anti-aliasing-guide-updated.357956/
  23. k4bn
    I don't have BF1 to try to replicate this stuff unfortunately. One more thing that you could do is setting texture filtering to clamp in nvidia control panel. @lordante has BF1 I think, he may be of some help here. Some useful stuff might be in this thread if you haven't read it already, there are similar complaints. https://forums.battlefield.com/en-us/discussion/94743/low-texture-even-if-set-as-ultra-anyone-notice-that-after-new-patch
  24. k4bn
    Looks like the low resolution LOD is still loaded. Pretty weird, since the high res LOD for some of the other trees in the distance has already been loaded, I don't have BF1 to test this out though. I think the mesh quality setting controls that. If you don't figure it out, you should address this to the developers. Apart from engine LOD, the only other way to control the LOD is with driver overrides, but most of those are broken ever since dx10 and dx11 came out, since they do LOD filtering differently compared to dx9. There was an example where Buck posted a similar video of PUBG water dithering where the high res water LOD doesn't load while you are in the airplane. Turned out it's something that the developers just didn't fix. I don't play PUBG, but funnily enough I watched a Forsen PUBG stream the other day and it seems that they still haven't fixed that particular bug. This is why it may be best to check with the devs first, just to rule out that it isn't something that they messed up, because it looks like only particular trees haven't been loaded, so it makes it look like a game issue. Also, to address your LOD bias question, one of the ways to change the "LOD bias" for NVIDIA users was the famous workaround, basically in the NVIDIA inspector you change AA - Transparency supersampling to - AA_MODE_REPLAY_MODE_ALL, then you can test out LOD bias values in the inspector, such as -1, 0 and 1.., I think the range went from -5 to 5, could be wrong. Note that this is a completely broken feature that was used ages ago on dx9 games. Some game engines interpreted this LOD bias as the mipmap bias and actually blurred or sharpened some of the textures to reduce/increase some of the aliasing caused by the sharpness of the texture. For example, Witcher 3 is one of the games that allows you to modify the mipmap bias(mentioned in last post), ever since they changed it from 0 to -1 in one of the patches. This is a similar thing, although a lot more unstable, it depends on the game. This helped for some older games with sharp or blurry textures, but in newer games that use deferred PBR rendering there's a lot of shaders, sharp specular highlights, aliasing from subpixel features etc., blurring the sharp texture mipmaps usually isn't enough to counter more intrusive types of aliasing. Ideally, you still need a decent temporal filter to get a temporally stable scene. I suggest trying this with some older, dx9 games first, because it might not make too much of a difference, if any, in newer titles. The workaround could've also been patched, so bare that in mind. The actual LOD bias has more functions than that, it's basically supposed to control the LOD switching distance. An example of LOD switching in action:
  25. k4bn
    Try to set TextureMipBias to 0 in Steam\SteamApps\common\The Witcher 3\bin\config\base\rendering.ini. Make sure to check if it's properly applied after entering the game. If that doesn't work, try lowering anisotropic filtering and make sure that sharpness is set to low/0 or whatever. I recall being able to replicate a similar "texture flickering" bug if hardware MSAA was on 4x+ in Serious Sam 3. Also, old Dust 2 B tunnels on CS:GO had a weird texture that would do that if you set MSAA to 4x+. So make sure that anti-aliasing is set to application-controlled in nvidia control panel, just in case. For the rest of the aliasing I would suggest to use some stronger AA method that can deal with things like the foliage and temporal/shader aliasing in Witcher 3. Unfortunately, the main AA method is basically a postprocess AA with a temporal filter. I'm guessing it's something similar to SMAA T1X or T2X. This might've been state of the art for deferred when Witcher 3 was released, but it's inferior to modern AA tech. Anyway, apart from that, I think that 4k DSR should anti-alias most of the aliasing. I say most because some extreme cases of temporal aliasing cannot be solved unless you make your own mod for that, since no one has made one AFAIK. See starting room in Witcher 3 on one of the windows or whatever, that's something that normal supersampling/downsampling will not be able to handle. Check this window at 12:50 for example, this is a case where Witcher 3 would benefit from some sort of a TAA/TXAA: https://www.youtube.com/watch?v=bWL68YzNb0M&t=770s How to DSR: https://www.youtube.com/watch?v=EHu7K1plz8U There's a great comparison of using DSR on Witcher 3 on youtube, so you can compare your results if you want. There's an uncompressed video in the description that you can download. Youtube destroys some aliasing with compression, so it's best to compare with the uncompressed video. https://www.youtube.com/watch?v=906EEPlB3Ao&t=525s Note that the above video renders Witcher 3 at 1080p, so comparing it with your game only works if you are using 1080p yourself.
×