Instalar Steam
iniciar sesión
|
idioma
简体中文 (chino simplificado)
繁體中文 (chino tradicional)
日本語 (japonés)
한국어 (coreano)
ไทย (tailandés)
Български (búlgaro)
Čeština (checo)
Dansk (danés)
Deutsch (alemán)
English (inglés)
Español de Hispanoamérica
Ελληνικά (griego)
Français (francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (húngaro)
Nederlands (holandés)
Norsk (noruego)
Polski (polaco)
Português (Portugués de Portugal)
Português-Brasil (portugués de Brasil)
Română (rumano)
Русский (ruso)
Suomi (finés)
Svenska (sueco)
Türkçe (turco)
Tiếng Việt (vietnamita)
Українська (ucraniano)
Comunicar un error de traducción
Normas y directrices sobre discusión
Denunciar este mensaje
Google or DuckDuckGo:
> minecraft ram settings guide
> minecraft graphic settings guide
Best bet also for MC is set the in-game FPS to Unlimited.
Within NVIDIA Control Panel do not use VSync, set that to Application Preferred.
If you use GSync then sure you can enable that. Then set Low Latency Mode to On or Ultra.
I would not apply AA Supersample Transparency for this game in NV-CP; instead you can get plenty of free Graphics Mods that help with the overall graphics and visuals.
There are a number of mods you can install, but some have their own downsides. For example optifine makes enemies sometimes invisible or messes up your textures and makes you see through stuff randomly.
(the alternative, fabric with sodium is likely better)
If you mod it properly you just mod the engine without affecting gameplay, so you still have your vanilla java minecraft experience.
(do not use both of these mods as they both mess up the rendering engine and are incompatible)
The correct mods would also allow HD shaders, but I think the latest version of minecraft supports that by default in the resourcepacks.
Do not let software outside of the JVM mess with minecraft. (vsync lowers fps for example, don't use it, don't force other stuff to use it). It can conflict, especially when you also use mods to improve performance.
If you're going to get mods, get them from either curseforge or modrinth. Most sites are reposts that leesh from the mods, some of them even modified the mod for more income or claim to have non-existing versions. (you can also get mods from planetminecraft, github and some japanese sites. Some mods can only be obtained form their creator's home page, Optifine is one of those, keep that in mind)
Edit: Post below this one is right. Don't max out your view distance. Put it on something more decent. Most servers force it on 10. Vanilla is 12 by default.
Keep in mind in Java, everything is loaded in at full display, even things you don't see. The further away you let the engine load the more stuff it has to process. (textures in caves no where near you + mobs and such)
Get a better Java environment from somewhere, easiest might be to just use the Oracle one:
You will need to get a version that is compatible with the version of MC you want to play (look in the links for the general available releases of Java 17, 18, and 19 - I think 18 should work)
https://jdk.java.net/18/
(link for reference https://openjdk.java.net/install/ )
I had the same issue as you op, very low performance - especially when moving fast and loading new chunks caused a massive fps stutter. Using a better Java edition made it smooth as butter. You will have to make sure MC is using the correct binaries, by setting the path to the Java install to use.
get the chipset/audio/usb/lan drivers from the mobo site, and gpu drivers from nvidia
https://www.msi.com/Motherboard/X470-GAMING-PLUS-MAX/support#driver
Then you want to disable Windows auto driver install feature. DDU app makes turning this off very simple. Then with DDU (in safe mode) wipe out all 3 brands of GPU.
Reboot and then install latest drivers for everything.
Amd ryzen chipset driver from amd.com
GeForce gtx/rtx desktop gpu driver from nvidia.com
And then the rest... audio, Lan, wifi, bt; etc.
Lucky s Tale , Ni no Kuni II Revenant Kingdom and etc.
I can't see trying to play MC on a 22 inch or larger Monitor/TV; that's for sure.
However there are plenty of graphical mods for MC that can make the game look totally different. But none the less, it's still going to be a game of blocks in the end.
Minecraft is indeed blocky, yes, because the game is made up of blocks of course, but jagged, it doesn't have to be. I've been playing Minecraft for a decade and there's two primary things that result in a jagged look.
The first is what OP already mentioned, though this results less in general jaggedness but more in "moire patterning" on large faces of the same texture. The game nominally didn't use mip-mapping, which means with a combination of a high enough render distance and/or a low enough resolution, distant faces (especially larger ones of the same texture) would show this issue. Mip-mapping was introduced some time back now (1.7 or 1.8 I want to say?) but you then need anisotropic filtering to counteract the loss of detail it can introduce, and even then you get some bluriness on extreme angles that you didn't before (plus the performance loss of anistropic filtering, and unlike most titles where this hasn't caused performance loss for ages, I've noticed it can cause a substantial difference, notably if you turn it on with shaders). I can't offer much help here as I just leave mip-mapping off for personal preference.
The other thing would cause jaggedness would be, of course, a lack of anti-aliasing (or a poor method of anti-aliasing, like FXAA). Unfortunately, anti-aliasing was in a bit of a lull increasingly after 1.7, when deferred rendering was added and simply forcing it increasingly stopped working (initially you could set the "fboEnable" string to false, but this later disappeared so I believe you can't do that anymore). Worse, nVidia's drivers after approximately 373.06 (this is why I stuck with this version for ages) had a flaw that was never fixed if you ever did that method on drivers newer than that. It's a bit better now with OptiFine supporting it again, and modern shaders offering more methods of anti-aliasing than just FXAA, but this might mean using OptiFine over some of the newer things like Phosphor, Lithium, Sodium, et al. (unless one of these can do anti-aliasing but I'm not versaed in these to know) or TXAA with more and more shaders, which has some faults of its own (ghosting on slower motion changes and reintroduction of some aliasing in motion). But, you absolutely can remove the jaggedness in this game, let alone improve on the base look. I should know because I've been refusing the play the game without it for many years now.
https://imgur.com/a/wwynSb6
As for the performance issues OP, that's sort of par for the course with Minecraft Java. Allocating more RAM is probably the most common misconception about this game. That is only going to help if the default allocation is lacking badly to begin with (I think modern versions allocate 4 GB now so for a "default-ish" installation this is unlikely to be insufficient). You can raise it anyway, but giving it more does nothing at best, and can hurt at worst if the garbage collections are more spread out but thus larger when they occur. Would need to see a screenshot with F3 enabled to make a more proper guess, but given you are explaining higher frame rates in one instance and lower after changing a given setting, I'm going to say it's the setting.
In general, settings that may help are you can turn down entity distance (from 100% to 50%), especially if playing with shaders this helps for some reason, and the big one is to keep the render distance in check. Keeping biome blend lower helps reduce micro-spikes of lag when altering things near those borders (but it shouldn't cause a general frame rate drop otherwise). I have the same CPU as you and with 1.16 and a few prior versions, I was finding I was actually able to play with a rather high (for Java) render distance rather fine, like 32 and maybe up near 48 was actually playable, but with 1.18, performance demands yet again went way up.
Currently the game is allocating 2MB of ram, and in the F3 menu it says it's using about 60% of it at any given time, but I may up that to 4GB like you said and see if that will change anything. I'll also mess with the graphics settings you mentioned and get back to you on that. I might also send in an Imgur link with how my game looks as well as the F3 menu in the same screenshot.
https://imgur.com/a/LGmHe6z
If switching anti-aliasing on and solely doing that causes you go down to to around 20 FPS to 30 FPS then that is strange with that GPU. My 3700X is paired with just a GTX 1060. If you're playing with v-sync, you may want to try enabling triple buffering (in the nVidia drivers, it's not game options). This is what I do as it keeps my sub-60 FPS moments from going down that low, but it may increase VRAM use.
Thanks for the help and suggestions.
Playing with shaders adds another layer to the mix.
I avoided shaders for the longest time for a number of reasons, partly preference but also because of performance reasons and specifically the lack of clean anti-aliasing. Minecraft is just... difficult for me to play without clean antialiasing.
FXAA is a rather poor method of anti-aliasing (IMO) as it's not as "clean" or sharp. If you're using a lower internal rendering resolution or any form of scaling, it will result in a similar result. I'm personally using TXAA in my screenshots, and I have the sharpness turned quite high, but this isn't for everyone. It looks nice in my stationary screenshots, but TXAA introduces its own issues in motion that I mentioned.
I use BSL shaders (and tuned quite differently from the default, which leaves a bit to be desired) and your hardware is better than mine so it'd be capable of whatever mine is, but shaders are preference so I'm not necessarily suggesting you have to change them to get the desired results. I'm not familiar with the shaders you're using, but places to start would be making sure rendering scale matches your native resolution, disabling any forms of FXAA, and seeing if it offers other methods (likely only TXAA), but again you'll be dealing with the drawbacks of TXAA. I know BSL shaders have a fork of it called Complimentary shaders which sort of gets around the issues with TXAA by applying TXAA to the scene but not to entities (so you don't get the ghosting issues with them, but they aren't anti-aliased to begin with but at least most of the scene is).
Keep in mind that shaders alone can be taxing, and shaders plus anti-aliasing is taxing. Some shaders offer "advanced" sorts of settings like POM and rain reflections and that sort of things, and just having the advanced features toggled on in BSL (even if all the individual settings within that tree are off and the resource pack doesn't offer POM or anything anyway) really, really drops my frame rate for some reason regardless. Shaders for Minecraft aren't aren't known to be performance efficient so it's partly par for the course.
Lastly, render distance is crucial in this game, especially with shaders. I noticed you're using 20, and you might want to scale this back to 16 or so, at least to start and then scale it back up after you've dialed other things in if you have performance to spare. But that is if you want more performance. Your frame rate numbers look good there considering the scenario (the stutter drops are mostly just Minecraft being Minecraft). I personally have difficulties going above 16 in 1.18 with the shaders I use, personally, though I can adjust it to 24 in some less demanding places (you're near a jungle in that video and that's like the worse biome for performance).