Forum:Why don't we use bloom for screen shots?

From the RuneScape Wiki, the wiki for all things RuneScape
Jump to: navigation, search
Forums: Yew Grove > Why don't we use bloom for screen shots?
This page or section is an archive.
Please do not edit the contents of this page.
This thread was archived on 8 June 2012 by Urbancowgurl777.

Title says it all, sure that would be more accurate, but from I can see, no photos utilise bloo.  —The preceding unsigned comment was added by Kriad (talk) on 21:11, 2012 May 30.


Someone called?


kitty.pngPsycho Robot talkSilver bar.png 01:16, May 31, 2012 (UTC) svco4bY.png3Gf5N2F.png 01:46, May 31, 2012 (UTC)

Comment - For starters it's not compatible with most computers right now, and AA doesn't cooperate with bloom with DirectX settings which is the preferred graphic settings. For the most part it's extremely blinding to most users and in some cases I have been told that it gives epilepsy, which is something we would prefer to avoid. --Recent uploads SpineTalkGuest book 01:43, May 31, 2012 (UTC)

Question - Why should we make bloom our standard? What are the advantages and disadvantages? From what I hear either bloom or AA can be active, not both, so why is bloom superior if that is true? What I've done Ciphrius Kane Talk 01:43, May 31, 2012 (UTC)

Bloom SHOULDN'T be our standard, Some users have managed to bypass the incompatibility for bloom and AA for various reasons such as excellent graphics cards or up to date hardware, etc. However not every filemaker can use bloom and so it's not a standard. It's just preferred not to be used because of imcompatibility, blinding light, and in some cases, epilepsy. --Recent uploads SpineTalkGuest book 01:50, May 31, 2012 (UTC)
Photosensitive epilepsy is caused by flashing lights, and therefore is irrelevant. bad_fetustalk 13:31, May 31, 2012 (UTC)

Comment - Bloom and AA only cooperate on OpenGL, which does not support high water detail, as where you can only have one or the other on DirectX. I'll correct the opening statement in that most of the Kiln monsters have been taken with Bloom on and AA (see TokHaar-Jad versus his un-bloomed self.). Other issues that come with bloom is that it makes some areas of the game hard to see like Daemonheim and Zanaris. As well, we have very few people that can "fake" the translucency for such images. If it wasn't that we liked to add transparency from your inventory icon to the largest monster in the game, this wouldn't be a problem. So no, bloom should only be used where appropriate. Doesn't really matter anyway since we appear to have to retake many if not most of the worn images for the combat rework when rears its head about. Ryan PM 01:57, May 31, 2012 (UTC)

The previous comment references discussion in Forum:Water: DirectX or OpenGL.  a proofreader ▸  06:58, May 31, 2012 (UTC)
Perhaps bloom could be utilised, then, when an image of a landscape or panorama is being taken (not an armour picture or anything that needs to be trans'd or translucencied) and the landscape contains no water, so that OpenGL + AA + bloom can be used. But then you fall back into the discussion in Forum:Water: DirectX or OpenGL: can editors all use OpenGL? Is it any better?  a proofreader ▸  06:58, May 31, 2012 (UTC)
OpenGL should be used in places where DirectX causes glitches, such as tiny cat and squirrel eyes, invisible and glitchy objects (Such as the area from Within the Light, and a cellar in Taverthorpe), and of course disabling Anti-aliasing with bloom. By editing your graphics driver settings it is possible to force Bloom to work with Anti-alising on Directx, but this should probably not be reccomended, as you could potentionally screw up your graphics settings. Adventurer's log Wahisietel (Talk) Quest map icon.png 13:57, May 31, 2012 (UTC)
Eh, I'm not sure if it's just because I use a Mac, but whenever I use AA and Bloom effects on OpenGL it causes substantial screen tearing. Smuff [citation provided] 11:21, June 1, 2012 (UTC)

Comment - I don't use it for a couple of reasons: 1) Doesn't work with AA (not that my AA works atm, but...), 2) It blinds. Really. And 3) It doesn't work at all. Even with AA. User_talk:Fswe1 Fswe1 Brassica Prime symbol.png 12:49, May 31, 2012 (UTC)

Comment - Bloom looks awesome in some cases, but in cases like the Quest Cape emote it looks terrible. So use common sense really. The reason we don't use more bloom probably has something to do with the Orb of Oculus disabling it on use for some reason. Adventurer's log Wahisietel (Talk) Quest map icon.png 13:57, May 31, 2012 (UTC)

Comment - There's nothing to support or oppose here. However, we have nothing saying you should have to use bloom, nor anything saying you should use bloom. I consider anti-aliasing to be more important than bloom, which means you'd have to use OpenGL to utilize bloom (as DirectX is still unable to have both bloom and AA, due to Jagex's incompetence). But at the same time, OpenGL makes for "worse" (at least noticeably different) water, and we already decided by consensus that the DirectX water is the way to go. At any rate, I think using bloom is great. Bloom is better than no bloom. However, if it means the water is entirely different or that there's no anti-aliasing, it's just not worth it (fix your stuff, Jagex). Hofmic Talk 23:23, May 31, 2012 (UTC)

Request for closure - The reasons for not advocating or prohibiting bloom have been stated multiple times above, this does not require a community thread and there is nothing to reach consensus on. Ronan Talk 12:37, June 1, 2012 (UTC)

It's hasn't even been open for two days. I still have things to add and I'm sure other people would too if they had the time. Besides, not every thread has to have resulting consensus in mind. Matt (t) 12:53, June 1, 2012 (UTC)

Comment - A relatively big number of images are taken with the Orb of Oculus, and this item kindof disables the bloom lighting effect. That's why we don't (seem to) use it. Adult chameleon (automatic).png Anurin Talk · Sign! . 22:39, June 4, 2012 (UTC)

Closed - I think everything relevant has been said. sssSp7p.pngIjLCqFF.png 04:22, June 8, 2012 (UTC)