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
What is Debug Beacon Line Width (again)? | 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

What is Debug Beacon Line Width (again)?

July 24, 2007 4:42 pm

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

Puzzled over Debug Beacon Line WidthOk, I’m still puzzled over this: what exactly is or does ‘debug beacon line width’ in the Graphics tab of the Second Life preferences menu? We’re three months later and I still do not know. =(

So, a dollar (ah well, 350 L$) for anybody that can clearly explain to me what ‘debug beacon line width’ does in the comments of this blogpost or by trackback. If after 7 days there is no useful reply, the 350L$ will go to the most creative answer*. And I’ll give you 500L$ instead of 350 Linden Dollars if you can also tell me what the Bump Mapped & Cloth checkbox is for. Maybe Nicholaz?

If this is of any help at all:

Debug: With software, to detect, locate, and correct logical or syntactical errors in a computer program. With hardware, to detect, locate, and correct a malfunction or to fix an inoperable system. The term troubleshoot is more commonly used in hardware contexts – especially if the problem is suspected to be a major one.

Beacon1: A snippet of code placed in an ad, on a Web page, or in an email which helps measure whether the ad, page or email was delivered to the browser and to track actions in general. Also known as a clear GIF or pixel tag.

Beacon2: On a FDDI network, a special frame generated and passed along when a node detects a problem.

Width: In general English usage, length (symbols: l, L) is but one particular instance of distance – an object’s length is how long the object is – but in the physical sciences and engineering, the word length is in some contexts used synonymously with “distance”. Height is vertical distance; width (or breadth) is a lateral distance; an object’s width is less than its length.

* ‘Clear explanation’ and ‘creative answer’ values for each comment/answer are decided upon by sole discretion of Vint Falken.

6 Responses to “What is Debug Beacon Line Width (again)?”

Claryssa Schmidt wrote a comment on July 24, 2007
MyAvatars 0.2

Go into the View menu of your client, and you should see a “Beacons” menu item with a sub-menu. From that sub-menu, pick “Scripted Objects”. Many objects (any objects containing scripts) will now have red lines coming from them, and in the center of these objects will be a little box.

Now play with the “Debug Beacon Line Width” setting. These lines and boxes should get thicker as you turn it up and thinner as you turn it down.

There’s also beacons for physical objects (green), sound sources (yellow), and particle sources (blue). The sub-menu also has a convenient way to hide particles.

Francz Kuhn wrote a comment on July 24, 2007
MyAvatars 0.2

My shot at the Bump Mapping Thingy:
As far as I can fathom, Bump Mappping is what makes oranges look like oranges (with its little bumpy dimples) and not just like little orange plastic beach balls (all smooth and perfect).
Well that’s as far as I can tell from
http://en.wikipedia.org/wiki/Bump_mapping
I can’t test the theory in “real” SL coz I us an (unsupported) (non-Pro)MacBook with (unsupported) Intel card. :-/

Francz Kuhn wrote a comment on July 24, 2007
MyAvatars 0.2

/me hears constant voices in empty head saying, “bump map… CLOTH.. avi… ?”

OK, so what does Bump Mapping have to do with Cloth and Avis?

More clues from
http://secondlife.com/app/help/technical/preferences.php:

“Avatar Rendering:
Normal causes avatars to be displayed normally without special detail.
Bump Mapped causes avatars to be displayed with additional detail (wrinkles in clothing, etc.)
Bump Mapped & Cloth causes avatars to be displayed with additional detail. Hair and loose clothing will shift with the wind.”

Sounds fun but…. does its really work in “real” SL life? Inword help page suggests that it might actually be broken (or was):
http://secondlife.com/app/help/avatar/appearancemode.php:

“If your graphics card supports it, your clothes and hair can wave in the wind. To turn this on, go to Edit menu > Preferences > Graphics tab and set Avatar Rendering to Bump Mapped & Cloth. Relog and fly around and see if you can see the difference: it’s particularly noticeable with long, poofy skirts and hairstyles.
• If you’re wondering what “Bump Mapped” means, it relates to the “Wrinkles” sliders at the bottom of some clothes. Unfortunately, it’s been broken for awhile, so it won’t currently (April 2006) have any effect.”

/me is more confused about Bump Mapped and Cloth than before. :-/

Claryssa Schmidt wrote a comment on July 24, 2007
MyAvatars 0.2

Here’s a clearer explanation: Debug beacons are markers you can use to locate various types of objects. These consist of a wireframe box with axis lines going through it. “Debug Beacon Line Width” determines the thickness of the box and the axis lines.

(the above comment describes how to enable debug beacons)

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

Aha. Thank you. I think I start to understand. It’s a useless button until you actually turn the feature on in the client menu? *is going to experiment in-world*

MyAvatars 0.2

[…] I finally have an answer to the ‘What does Debug Beacon Line Width?‘ question (thank you, Claryssa Schmidt), I started using it for snapshotting. Somehow I feel […]

Care to comment?