To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.colorOpen lugnet.color in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Color / 1148
Subject: 
Not wanting to start rumors, but
Newsgroups: 
lugnet.color
Date: 
Mon, 4 Jul 2005 11:43:11 GMT
Highlighted: 
(details)
Viewed: 
2014 times
  
"Heiner" from 1000steine mentioned in the discussion that the
Sandcrawler([TM] or whatever) sports a different kind/hue of tan.

Can anybody confirm/deny this? Or is this just an additional colour
instead of a replacement? Or ist this a mistake on Heiners side?

LEGO has been dumb enought to pull such a stunt before and shown how
little they care for their customers - and I don't want to be bitten
again in the middle of a large-scale project. So I thought I'd ask
before I spend my money on a few tenthousand bricks in a colour that may
or may not be available in a few months...

concerned, Christian


Subject: 
Re: Not wanting to start rumors, but
Newsgroups: 
lugnet.color
Date: 
Mon, 4 Jul 2005 19:39:04 GMT
Viewed: 
2043 times
  
In lugnet.color, Christian Treczoks wrote:
"Heiner" from 1000steine mentioned in the discussion that the
Sandcrawler([TM] or whatever) sports a different kind/hue of tan.

Can anybody confirm/deny this? Or is this just an additional colour
instead of a replacement? Or ist this a mistake on Heiners side?

LEGO has been dumb enought to pull such a stunt before and shown how
little they care for their customers - and I don't want to be bitten
again in the middle of a large-scale project. So I thought I'd ask
before I spend my money on a few tenthousand bricks in a colour that may
or may not be available in a few months...

concerned, Christian

More likely a new color. Or probably Cool Yellow.
Tan, known inside TLG as Beige, has been locked.
See here: <http://news.lugnet.com/lego/?n=2605>
I shure hope TLG is smart enuff to not pull off such a silly trick again.

scott Frischmann.


Subject: 
Re: Not wanting to start rumors, but
Newsgroups: 
lugnet.color
Date: 
Tue, 5 Jul 2005 12:35:58 GMT
Highlighted: 
(details)
Viewed: 
2017 times
  
Scott Frischmann wrote:

> More likely a new color. Or probably Cool Yellow.
I thought they already had more than enough surplus colours?

Tan, known inside TLG as Beige, has been locked.
See here: <http://news.lugnet.com/lego/?n=2605>
Well, several people tried to get Jake or whomever at Lego to confirm
that the mentioned "Beige" is indeed 'our' "Tan" or the official LEGO
"Colour 5 Brick Yellow", to no avail so far. Just have a look at the
replies to that posting.

> I shure hope TLG is smart enuff to not pull off such a silly trick
> again.
I would not bet my A** on that, or even 2 cents.

Yours, Christian


Subject: 
Re: Not wanting to start rumors, but
Newsgroups: 
lugnet.color
Date: 
Wed, 6 Jul 2005 13:35:26 GMT
Viewed: 
2067 times
  
In lugnet.color, Christian Treczoks wrote:
"Heiner" from 1000steine mentioned in the discussion that the
Sandcrawler([TM] or whatever) sports a different kind/hue of tan.

Can anybody confirm/deny this? Or is this just an additional colour
instead of a replacement? Or ist this a mistake on Heiners side?

LEGO has been dumb enought to pull such a stunt before and shown how
little they care for their customers - and I don't want to be bitten
again in the middle of a large-scale project. So I thought I'd ask
before I spend my money on a few tenthousand bricks in a colour that may
or may not be available in a few months...

I've checked on this, and, as always, no - this is not a new color. There has
been no change in this color.

If you have a brick that seems to be a different color, please contact me
offline and I can arrange to get your "odd" brick to the QA department to ensure
there wasn't a problem with a production run somewhere.

The best solution when things like this come up is to contact Consumer Service
(http://www.lego.com/service). They can arrange replacement parts and facilitate
getting the questionable bricks to QA.


Jake
---
Jake McKee
Community Liaison
LEGO Community Team


Subject: 
Re: Not wanting to start rumors, but
Newsgroups: 
lugnet.color
Date: 
Wed, 6 Jul 2005 16:54:51 GMT
Highlighted: 
(details)
Viewed: 
2129 times
  
In lugnet.color, Christian Treczoks wrote:
Scott Frischmann wrote:

More likely a new color. Or probably Cool Yellow.
I thought they already had more than enough surplus colours?

Tan, known inside TLG as Beige, has been locked.
See here: <http://news.lugnet.com/lego/?n=2605>
Well, several people tried to get Jake or whomever at Lego to confirm
that the mentioned "Beige" is indeed 'our' "Tan" or the official LEGO
"Colour 5 Brick Yellow", to no avail so far. Just have a look at the
replies to that posting.

We recently had a chance to compare our color list with LEGO's official one, and
these colors were absolutely verified by LEGO as correct translations:

#   Peeron   Lego
==================================
1   White    White
5   Tan      Brick Yellow/Beige
18  Flesh    Nougat
21  Red      Bright Red
23  Blue     Bright Blue
24  Yellow   Bright Yellow
26  Black    Black
28  Green    Dark Green
29  MdGreen  Medium Green
40  Clear    Transparent \(new\)
41  TrRed    Transparent Red
42  TrLtBlue Transparent Light Blue/Transparent Dove Blue
43  TrBlue   Transparent Blue
44  TrYellow Transparent Yellow
48  TrGreen  Transparent Green
102 MdBlue   Medium Blue
106 Orange   Bright Orange
192 RedBrown Reddish Brown
194 MdStone  Stone Grey
199 DkStone  Dark Stone Grey
208 LtStone  Light Stone Grey
283 LtFlesh  Light Nougat

We will try to verify the rest, but finding sample pieces for them is not always
easy.

I'll also update the Color List with this information
(http://www.peeron.com/inv/colors/)

Hope that helps!

Dan


Subject: 
Re: Not wanting to start rumors, but
Newsgroups: 
lugnet.color
Date: 
Wed, 6 Jul 2005 17:57:58 GMT
Viewed: 
2103 times
  
Dan Boger wrote:
We recently had a chance to compare our color list with LEGO's official one, and
these colors were absolutely verified by LEGO as correct translations:

#   Peeron   Lego
==================================
1   White    White
5   Tan      Brick Yellow/Beige
18  Flesh    Nougat
21  Red      Bright Red
23  Blue     Bright Blue
24  Yellow   Bright Yellow
26  Black    Black
28  Green    Dark Green
29  MdGreen  Medium Green
40  Clear    Transparent \(new\)
41  TrRed    Transparent Red
42  TrLtBlue Transparent Light Blue/Transparent Dove Blue
43  TrBlue   Transparent Blue
44  TrYellow Transparent Yellow
48  TrGreen  Transparent Green
102 MdBlue   Medium Blue
106 Orange   Bright Orange
192 RedBrown Reddish Brown
194 MdStone  Stone Grey
199 DkStone  Dark Stone Grey
208 LtStone  Light Stone Grey
283 LtFlesh  Light Nougat

We will try to verify the rest, but finding sample pieces for them is not always
easy.

I'll also update the Color List with this information
(http://www.peeron.com/inv/colors/)

Hope that helps!
Thank you very much, Dan! This list of confirmed colours is what quite a
lot of people were waiting for. Let's hope the rest of the list will
come soon.

The thing that strikes me as quite amazing is that colours are stamped
as "Universal" when they are that hard to find or rare.

Oh, and I would have preferred to have the colours 2, 25 and 27 in that
list, of course ;-)

It lightens my heart that I can continue with the project as planned - I
already ordered 1700 tan jumper plates today for a start...

Yours, Christian


Subject: 
Re: Not wanting to start rumors, but
Newsgroups: 
lugnet.color
Date: 
Wed, 6 Jul 2005 18:04:42 GMT
Viewed: 
2083 times
  
Jake McKee wrote:
I've checked on this, and, as always, no - this is not a new color. There has
been no change in this color.
That is good news indeed. So I already ordered 1700 jumper plates in tan
and hope they mach the other bricks in the model ;-)

If you have a brick that seems to be a different color, please contact me
offline and I can arrange to get your "odd" brick to the QA department to ensure
there wasn't a problem with a production run somewhere.
I'll forward that to Heiner (I did not buy that Sandcrawler, too much
new brown in it).

The best solution when things like this come up is to contact Consumer Service
(http://www.lego.com/service). They can arrange replacement parts and facilitate
getting the questionable bricks to QA.
Erm, not wanting to be picky, but just like they did with the knight
bus? Initially, nobody knew, and then, suddenly, its perfectly within
the quality limits and no reason whatsoever to return a botched product...

Yes, I know I sound horribly negative again, but it just comes with the
topic and how it has been handeled in the past.

Yours, Christian


Subject: 
Re: Not wanting to start rumors, but
Newsgroups: 
lugnet.color
Date: 
Thu, 7 Jul 2005 05:44:20 GMT
Viewed: 
2030 times
  
Jake,

Does this mean we can ship back all our Knight's Bus purple and receive ONE SINGLE
PURPLE color back in return?  I only have maybe 2-5 of the set, but it sure would be
nice if the purple was consistent.  "Within acceptable tolerances" they are NOT.


Jake McKee wrote:

If you have a brick that seems to be a different color, please contact me
offline and I can arrange to get your "odd" brick to the QA department to ensure
there wasn't a problem with a production run somewhere.

The best solution when things like this come up is to contact Consumer Service
(http://www.lego.com/service). They can arrange replacement parts and facilitate
getting the questionable bricks to QA.

--
Tom Stangl
*http://www.vfaq.com/
*DSM Visual FAQ home
*http://www.vfaq.net/
*Prius Visual FAQ Home


Subject: 
Re: Not wanting to start rumors, but
Newsgroups: 
lugnet.color
Date: 
Thu, 7 Jul 2005 12:49:41 GMT
Viewed: 
2243 times
  
In lugnet.color, Christian Treczoks wrote:

The best solution when things like this come up is to contact Consumer Service
(http://www.lego.com/service). They can arrange replacement parts and facilitate
getting the questionable bricks to QA.
Erm, not wanting to be picky, but just like they did with the knight
bus? Initially, nobody knew, and then, suddenly, its perfectly within
the quality limits and no reason whatsoever to return a botched product...

Yes, I know I sound horribly negative again, but it just comes with the
topic and how it has been handeled in the past.

What do you mean "nobody knew"? Our production folks and quality folks were well
aware of the issue by the time the AFOLs (and me) brought it up to them. It's
just that when it was brought to *me*, I didn't know about it. In a company of
thousands, I'm simply not able to keep up with absolutely every issue, project,
problem, and situation. My task isn't to know every single thing happening in
the company, it's to be able to find out what's happening.

That may sometimes give the impression that "the company" doesn't know anything,
but that's simply not true. The reality is that not ever colleague can keep up
with all the projects that every other colleague is working on. A big part of my
week is dedicated to sharing the activitites and achievements of the AFOL
community and the Community Development with the rest of the company, and there
are still people who I don't reach. That's just the nature of having any
organization the size of our company. Heck, that's the situation in an
organization the size of 2+ :)

Jake
---
Jake McKee
Community Liaison
LEGO Community Team


Subject: 
Re: Not wanting to start rumors, but
Newsgroups: 
lugnet.color
Date: 
Thu, 7 Jul 2005 14:38:48 GMT
Viewed: 
2079 times
  
Jake McKee wrote:
What do you mean "nobody knew"? Our production folks and quality folks were well
aware of the issue by the time the AFOLs (and me) brought it up to them.
Does this mean that (significant parts of) LEGO were fully aware of the
colour problems of the Knight Bus when they shipped them?

Usually, the AFOLdom is quite early when it comes to noticing problems,
and this particular issue popped up in Germany before the bus was even
shipped (Nürnberg Toy Fair!).

It's
just that when it was brought to *me*, I didn't know about it. In a company of
thousands, I'm simply not able to keep up with absolutely every issue, project,
problem, and situation. My task isn't to know every single thing happening in
the company, it's to be able to find out what's happening.
Thats quite acceptable - nobody can expect more than that. But I was not
talking of you, I was talking of those nice ladies answering the phones
to handle customer service issues. Production knew, QA knew, so why did
they not brief Customer Service on this potential issue? I mean, this
question is not to irate or mock you - I just consider it wise to brief
the front line people when, where and why to expect "enemy fire" from
the customer side...

That may sometimes give the impression that "the company" doesn't know anything,
but that's simply not true. The reality is that not ever colleague can keep up
with all the projects that every other colleague is working on. A big part of my
week is dedicated to sharing the activitites and achievements of the AFOL
community and the Community Development with the rest of the company, and there
are still people who I don't reach. That's just the nature of having any
organization the size of our company. Heck, that's the situation in an
organization the size of 2+ :)
I bet there is a lot of knowledge in your company. And quite a lot is
propably buried deep in some peoples mind, and if you can help banging a
few heads to come up with the knowledge for the best of all, that's just
great.

A big problem with this "the company does not know" though, is that
there is only a small part of any company communicating with the
outside. If this part is in the know, it can make a quite wonderful
impression. If these people a) get briefed early enough on potential
problems and b) have a fast path to information inside their company,
but also across the service department, it makes the whole company look
intelligent and well informed.

Ahh, the wonders of communication :-)

Yours, Christian


©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR