![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Hi(gh)!
On 03.11.2012 21:13, Anthony D. Baye wrote:
> overlay a grime texture
...not to forget bread crumbs, potato chip/crisp splinters, coffee
crusts, scalp and beard hairs making their way into the keyboard over time!
See you in Khyberspace!
Yadgar
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On 11/2/2012 10:26 PM, John VanSickle wrote:
> I'm scheming a scene which is going to have a bunch of computers at
> desks, and here's the keyboard.
>
> The chief problem with this model is that it contains 2152 scene-level
> objects. There are ways to lower this, but that'll take some work.
>
> (It won't animate, either, but I'm not planning an shots where that will
> be an issue.)
>
> (And I'm sure some of you would prefer a different color.)
To answer some of the questions:
* Yes, the key board base should have a cut-out area around the keys. I
was getting to the point where I wanted to post something.
* The texturing is done with object patterns based on text objects.
That way the detail is there at any magnification.
* Why, yes, there are no OS keys. That is deliberate.
* I was thinking of texturing the F13-F15 keys with the usual text like
the keyboard I'm typing this on, but I got lazy there. It's not hard to
change. I might also make a full row of function keys, going to F20.
* I might replace the caps lock key with something else. It will
probably be security-related because the intended scene is a military
command-and-control center.
* The final version will use meshes for the keys to cut down on the
object count (each key contains 21 CSG primitives). It will also
support animating the keys so that they move when pressed.
Regards,
John
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
> Hi(gh)!
>
> On 03.11.2012 21:13, Anthony D. Baye wrote:
>
>> overlay a grime texture
>
> ...not to forget bread crumbs, potato chip/crisp splinters, coffee
> crusts, scalp and beard hairs making their way into the keyboard over time!
>
LOL! Very true indeed.
Thomas
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On 3-11-2012 23:22, clipka wrote:
> Am 03.11.2012 22:33, schrieb Jaime Vives Piqueres:
>> On 03/11/12 21:13, Anthony D. Baye wrote:
>>> That's odd... I haven't seen a two-row enter key in years. they're
>>> usually on REALLY OLD computers that don't have the windows and menu
>>> keys to the right of the spacebar.
>>
>> Must be a Spanish thing... every keyboard around here has a tall but
>> space for a key as important as enter, so it's expanded to the row above.
>
> German keyboards, too, typically have a tall Enter key; in addition,
> they also a very narrow left shift key, to make room for yet another key.
>
> I do prefer the tall Enter key.
And so do Dutch keyboards ;-)
In fact, that is probably the European version.
Thomas
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
> On 11/2/2012 10:26 PM, John VanSickle wrote:
>> I'm scheming a scene which is going to have a bunch of computers at
>> desks, and here's the keyboard.
>>
>> The chief problem with this model is that it contains 2152 scene-level
>> objects. There are ways to lower this, but that'll take some work.
>>
>> (It won't animate, either, but I'm not planning an shots where that will
>> be an issue.)
>>
>> (And I'm sure some of you would prefer a different color.)
>
> To answer some of the questions:
>
> * Yes, the key board base should have a cut-out area around the keys. I
> was getting to the point where I wanted to post something.
>
> * The texturing is done with object patterns based on text objects. That
> way the detail is there at any magnification.
Just use a scale statement.
>
> * Why, yes, there are no OS keys. That is deliberate.
>
> * I was thinking of texturing the F13-F15 keys with the usual text like
> the keyboard I'm typing this on, but I got lazy there. It's not hard to
> change. I might also make a full row of function keys, going to F20.
That would make it a "special purpose" keyboard... If that's the case,
why don't you go overboard and make TWO rows of 20, or more, Fn keys? :P
>
> * I might replace the caps lock key with something else. It will
> probably be security-related because the intended scene is a military
> command-and-control center.
Something like a "Launch" key...?
>
> * The final version will use meshes for the keys to cut down on the
> object count (each key contains 21 CSG primitives). It will also
> support animating the keys so that they move when pressed.
>
> Regards,
> John
Using a mesh for the generic key would greatly help here.
Another possibility would be to use a height field with a water level
used to cut off the bottom part.
You could create an image of all the keys' marking and apply it to an
union of meshes composing the complete keyboard. This should support
some animation as the keys movment is parallel to the axis of the image map.
Alain
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
From: Jörg 'Yadgar' Bleimann
Subject: Re: One Small Problem... (169kbbu)
Date: 5 Nov 2012 11:32:47
Message: <5097ea2f@news.povray.org>
|
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Hi(gh)!
On 04.11.2012 02:51, John VanSickle wrote:
> * Yes, the key board base should have a cut-out area around the keys. I
> was getting to the point where I wanted to post something.
>
> * The texturing is done with object patterns based on text objects. That
> way the detail is there at any magnification.
>
> * Why, yes, there are no OS keys. That is deliberate.
>
> * I was thinking of texturing the F13-F15 keys with the usual text like
> the keyboard I'm typing this on, but I got lazy there. It's not hard to
> change. I might also make a full row of function keys, going to F20.
>
> * I might replace the caps lock key with something else. It will
> probably be security-related because the intended scene is a military
> command-and-control center.
>
> * The final version will use meshes for the keys to cut down on the
> object count (each key contains 21 CSG primitives). It will also support
> animating the keys so that they move when pressed.
What about making it a contribution to the object library on
www.povray.org? POVers who like to build huge, consistent worlds would
be grateful about that...
See you in Khyberspace!
Yadgar
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
John VanSickle <evi### [at] KOSHER hotmail com> wrote:
> * Why, yes, there are no OS keys. That is deliberate.
>
> [snip]
>
> * [snip] the intended scene is a military
> command-and-control center.
I understand! ;-)
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On Sat, 03 Nov 2012 09:22:16 +0100, Jaime Vives Piqueres wrote:
> BTW, I think I've not seen a one-row enter key on the last 20
> years...
> but as clipka said, the labeling is "awsome rolex" material.
My HP media keyboard has a one-row enter key - it looks almost identical
to this image, but with rounded corners (I smell an Apple lawsuit against
HP for it <g>).
Seriously, though, great image. :)
Jim
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |