Strict Standards: Redefining already defined constructor for class wpdb in /home/vintfalk/public_html/wp-includes/wp-db.php on line 57

Deprecated: Assigning the return value of new by reference is deprecated in /home/vintfalk/public_html/wp-includes/cache.php on line 36

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /home/vintfalk/public_html/wp-includes/cache.php on line 384

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl($output) in /home/vintfalk/public_html/wp-includes/classes.php on line 541

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl($output) in /home/vintfalk/public_html/wp-includes/classes.php on line 541

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el($output) in /home/vintfalk/public_html/wp-includes/classes.php on line 541

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el($output) in /home/vintfalk/public_html/wp-includes/classes.php on line 541

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el($output) in /home/vintfalk/public_html/wp-includes/classes.php on line 560

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl($output) in /home/vintfalk/public_html/wp-includes/classes.php on line 659

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl($output) in /home/vintfalk/public_html/wp-includes/classes.php on line 659

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el($output) in /home/vintfalk/public_html/wp-includes/classes.php on line 659

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el($output) in /home/vintfalk/public_html/wp-includes/classes.php on line 659

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el($output) in /home/vintfalk/public_html/wp-includes/classes.php on line 684

Deprecated: Assigning the return value of new by reference is deprecated in /home/vintfalk/public_html/wp-includes/query.php on line 21

Deprecated: Assigning the return value of new by reference is deprecated in /home/vintfalk/public_html/wp-includes/theme.php on line 540

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_query_vars() should not be called statically in /home/vintfalk/public_html/wp-includes/plugin.php on line 59

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_posts_where() should not be called statically in /home/vintfalk/public_html/wp-includes/plugin.php on line 59

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_search_where() should not be called statically in /home/vintfalk/public_html/wp-includes/plugin.php on line 59

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_posts_join() should not be called statically in /home/vintfalk/public_html/wp-includes/plugin.php on line 59

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_search_join() should not be called statically in /home/vintfalk/public_html/wp-includes/plugin.php on line 59

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_posts_groupby() should not be called statically in /home/vintfalk/public_html/wp-includes/plugin.php on line 59

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_tag_templates() should not be called statically in /home/vintfalk/public_html/wp-includes/plugin.php on line 164
Diffuse Glow the Grid | VintFalken.com
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_add_meta_keywords() should not be called statically in /home/vintfalk/public_html/wp-includes/plugin.php on line 164
VintFalken.com

Diffuse Glow the Grid

April 23, 2007 5:51 am

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_the_content_filter() should not be called statically in /home/vintfalk/public_html/wp-includes/plugin.php on line 59

Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in /home/vintfalk/public_html/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line 655

Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in /home/vintfalk/public_html/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line 655

Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in /home/vintfalk/public_html/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line 656

Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in /home/vintfalk/public_html/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line 656

Strict Standards: Non-static method UltimateTagWarriorActions::replaceTagWithLink() should not be called statically in /home/vintfalk/public_html/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line 660

There are two sentences in Torley’s post ‘Be Luminous enjoy with “RenderGlow = TRUE”‘ that I don’t like at all:

  1. (if your graphics card supports it) because for me the answer is: ‘probably not’.
  2. Download Second Life 1.15 because I’m very busy being conservative and sticking to the 1.13 that _actually works_ for me.

But I must admit, judging from Torley’s screenshots it does make SL look less ‘flat’ and more ‘alive’. Luckily one can achieve - sort of - the same effect with the ‘Diffuse Glow’ filter in Photoshop. (Make sure in your tools palette the upper color layer is black and the one on the back is white and go to ‘Filters’, ‘Distort’, ‘Diffuse Glow’ and experiment with the sliders. ;))

Torley’s snapshots:

RenderGlow = FALSE

VS.

RenderGlow = TRUE

  • No Related Posts

7 Responses to “Diffuse Glow the Grid”

Raul Crimson wrote a comment on April 24, 2007
MyAvatars 0.2

I confess, as you know, i’m quite an addict to Distort Glow Filter. I know maybe i use it too much, but i agree with you it gives a better look to the images.
Kisses.

Lizardbeth Lulu wrote a comment on April 25, 2007
MyAvatars 0.2

I personally don’t like the glow, because it’s TOO glowy and TOO distorted. A medium somewhere between flat and radioactive would make me happy.

Vint Falken wrote a comment on April 25, 2007
MyAvatars 0.2

Maybe try the glow but lower the gamma settings?

Abdiel Nimbus wrote a comment on April 25, 2007
MyAvatars 0.2

[quote]Luckily one can achieve - sort of - the same effect with the ‘Diffuse Glow’ filter in Photoshop.[/quote]

Well copy+pasting every single frame to photoshop, apply a filter and get the image back to your client 24+ times a second can become fairly difficult u know… ;)

We’re talking about realtime glow here and comparing it to photoshop filters or even raytraced images is something you can’t do. Sure it needs to be tweaked some more, but i think it’s quite impressive what it actually can do to the visual appearance of SL.
My thoughts,
Abdiel Nimbus

Vint Falken wrote a comment on April 25, 2007
MyAvatars 0.2

Obviously I’ve posted this in ‘Photography’, not Machinima, no? =)

And for daily things like exploring, buildling, chatting, … I’d like to run SL as FAST as it can. And without to much viewer crashes. I don’t say it’s not impressive, I do say that - like many things, for instance the 1.14 client - it will not work for me. I still feel the irony of going ‘deaf’ the day LL introduced ‘voice’. :p I’m willing to buy a new PC every 4 to 5 years. Not every 2 to 3! Innovations are good, but first solve the current problems, please!

I was merely offering an alternative for people taking snapshots that don’t have state of the art machinery. Can we agree on Diffuse Glow relating to RenderGlow as Gimp relates to Photoshop? :D

OddesE Oh wrote a comment on April 26, 2007
MyAvatars 0.2

“There are two sentences in Torley’s post ‘Be Luminous enjoy with “RenderGlow = TRUE”‘ that I don’t like at all:

2. Download Second Life 1.15 because I’m very busy being conservative and sticking to the 1.13 that _actually works_ for me.”

Lol… That’s kind a hard challenge you put to the developers no? Adding features and fixing problems usually requires upgrading :-)

Oh and about your willingness to buy a PC every 4 to 5 years… I totally understand that you don’t want to spend to much money on your PC, but only buying a new one every five years might not be the best strategy to save money. Considering that processor performance doubles every 1.5 years or so, you should not hope yours to last longer than 3, max 4 years. I have found that it pays of to invest in IO devices such as mouse, keyboard, monitor, speakers etc. and buy the cheapest processor, ram, harddisk that you can. Then after two years, buy a new PC but without monitor, keyboard speakers and the lot. It’s not more expensive then buying an entirely new machine every five years but you stay up-to-date much more. The idea is to invest your money in those components that last long, such as speakers, and spend as little as possible on the components that last short. Then update those more often. Just a tip :-)

Vint Falken wrote a comment on April 26, 2007
MyAvatars 0.2

TY very much for the kind advise on how I should handle my electronics purchases. *Looks at her very old kickass Altec subwoofer* *does rolls eyes too*

Yes, adding features and fixing problems is important. Although I’d love to see the ‘fixing problems’ getting more priority then ‘adding features’. It woud be nice if they would keep those things seperated, as ‘adding features’ usually means ‘more problems to fix’. They could offer a version in which problems are fixed every week, and a version with added features once and so often AFTER it has been thoroughly tested on the beta grid? =)

Care to comment?