Quote from euphoria4949»
I'm getting a weird bug again with Ruins for 1.9, the exact same bug I had once before with Ruins for 1.7.5.
I've installed it correctly, Ruins are spawning just fine, but, no config file has been created in the config folder, so I can't change the spawn rates.
I've tried removing the mod entirely, playing MC for half an hour then reinstalling Ruins, started new worlds, removed all mods except Ruins.... but nothing has worked, still no Ruins.cfg
Any advice peoples???
If I understand correctly, this is not a bug per se; it's just peculiar design.
Ruins DOES NOT have a config file in the config folder. Rather, after you've created at least one world with Ruins installed, check in the mods folder, and look for "Ruins.txt." That is basically the equivalent of a "config" file, and it's propagated with whatever biomes are defined for your installation.
For more information on this, please check out the "readme.txt" file included in the ZIP for Ruins, as it should be helpful.
3
Intel HD Graphics we meet again
You will need to ask on the Sildurs Shaders thread as he knows the issues with Intels HD drivers, which ones that are poop, and which ones that are a little bit less poop 
Basically, Intel HD Graphics really struggle with things like shaders because they are not a graphics/video card. Plus they have many issues due to buggy drivers and Intel's refusal to conform with industry standards.
So they cause a lot of issues when trying to run shaders and other mods.
But ask on the Sildurs shader thread, he *should* be able to help you with which driver version to use.
1
IT WORKS!!!
Arrrh man, your idea to change the first letters to be upper-case worked perfectly, it was just Forge that was stopping it from working perfectly last night.
I wasn't updating Forge past 1832 because I tried a few versions above that a few days ago and B3M didn't like those versions, so I stayed on version 1826-1832. I didn't realise B3M was working with Forge 1850+, it must have just been a few random versions it didn't like.
Anyway as soon as I ran it on Forge 1850+ everything worked perfectly
Jeez, how you thought of changing the letters to upper-case I do not know. How stupid that such a small tiny thing could make such a difference
Sincerely Sedridor, thank you, thank you so much for taking the time to help. That was really kind and thoughtful of you.
4
HAPPY BIRTHDAY OPTIFINE!!
And a sincere thank you to everyone and anyone that has worked on it, your hard work and dedication is massively appreciated by the whole community.
1
That link does not work.
Also, as with any bug/issue report, no one can help without knowing what they are dealing with. Help us help you by providing this info:
1
[Edit] MaxCraft548 ninja'ed me with his reply
DOF = Depth of Field. The natural blurring of peripheral vision when the central visible is focused on something. Like when you hold up a finger just in front of your nose and stare at it, everything else in your vision becomes blurry, except your finger.
Example:
Huh, I could have sworn that's what I did to gain clarity underwater. Bear with me, I'll double check and report back later.
More than welcome, happy to help
2
I believe the 30-40fps is a conservative estimate, but also with the in-game render distance at somewhere close to 16, so depending on you render distance, your FPS will vary accordingly.
Also, are you running Continuum 1.1.5 or the newer 1.8.9 Preview 2?? Because the newer 1.8.9 has around a 10-15fps increase due to DOF being disabled. Or if you have disabled DOF in 1.1.5, that will gain you 10-15fps.
The dev team posted a video recently showing that in the new version, coming soon, the white noise around the edge of the screen when MB is enabled, has been fixed. So the new fixed version should be available soon.
I also found it to be a little too dark for me underwater, so I tweaked mine slightly.
If you want the underwater to be very clear, open "composite1.fsh", line 76 = "#define UnderwaterFog", change it to "//#define UnderwaterFog" for clear underwater.
Not personally noticed this as I don't use the lens flair.
Open "gbuffers_terrain.fsh", line 365 reads: "spec.g *= max(0.0f, clamp((wet * 1.0f + 0.2f), 0.0f, 1.0f) - (SPEC_BRIGHTNESS - w) * 1.0f);"
Change the first * after the spec.g to a +, so the start of the line reads: "spec.g += max... etc..", save and exit.
Hope this helps
1
As with any bug/issue report, no one can help you without knowing what they are dealing with. Help us help you by providing this info:.
If you're unsure how to get your CPU and GPU info, just Google how to find it. It's very simply and basic info to find, it only takes 30 seconds.
1
Sorry, but my attitude would be different if people did what they are supposed to do first, read descriptions and check if their PC's are capable. Or if people used basic common forum etiquette known by everyone across the web, and checked the forum thread first, did a quick search, found and read 1 of the "Over 1800" posts regarding the same exact thing.
Everyone gets a little frustrated on here when the same question is asked over and over and over again continuously daily for month after month year after year, literally 1800+ times on this one thread.
We know that not everyone is a tech expert, but common sense tells you to Google your PC first before randomly installing things. You wouldn't just fit some random generic brakes to your car without checking if they will work, are compatible or even capable first.
Always check first with "Any" software before installing it to your PC, otherwise next time it could be damaging to your PC, or something nasty like Malware, maybe something that corrupt your game and saves.
Please check first.
2
As already said above, Continuum Ultra Shader, running on a single 980Ti, 16 render distance, 128x resource pack with POM enabled, POM water, Vom Clouds, GI, Vol lighting, AA and everything else.... Yep that is bang on normal. Continuum is the most intensive and resource hungry shader out there, bar none, as it has more effects and features than a AAA game like GTA5 or The Witcher 3.
1
Yes and No
This older shader core mod does not work, but the new shader core mod does work.
After Minecraft 1.8 this shader core mod was merged and integrated into the OptiFine mod, as it says on the front page, but for some reason it says it was merged for 1.8.9 onwards which is incorrect.
Anyway, visit the Optifine page for the 1.8.8 download http://optifine.net/downloads, and in case you're the 1 person on earth that doesn't know what Optifine is, this is the Optifine MCforum thread http://www.minecraftforum.net/forums/mapping-and-modding/minecraft-mods/1272953-optifine-hd-b1-fps-boost-hd-textures-shaders-and