Aces High Bulletin Board

General Forums => Custom Skins => Topic started by: DarkNet on February 21, 2007, 11:00:12 AM

Title: F4U version1
Post by: DarkNet on February 21, 2007, 11:00:12 AM

I haven't made any specifics to what planes I am working on but here is a prev of what I got..(http://www.linuxjet.com/pics/AH/f4u1.jpg)
(http://www.linuxjet.com/pics/AH/f4u2.jpg)
(http://www.linuxjet.com/pics/AH/f4u3.jpg)
(http://www.linuxjet.com/pics/AH/f4u4.jpg)

THX - UPdated

Title: F4U version1
Post by: Krusty on February 21, 2007, 11:31:50 AM

Nothing shows up. It hangs on "4 items remaining" and lists a bitmap it's trying to load.

I think you need to convert them to JPEGs, otherwise they're going to be 4MB each.

EDIT: After a very long time they showed up

Title: F4U version1
Post by: Sketch on February 21, 2007, 03:46:07 PM

They showed up in about 4 seconds for me...  they look nice so far.

Title: F4U version1
Post by: Krusty on February 21, 2007, 06:53:12 PM

My ISP must be flaking out then.

The real question is "Which plane you going to skin?"

Title: F4U version1
Post by: DarkNet on February 22, 2007, 11:49:43 AM

I'm up for suggestions...  I just wanted to get the paneling up to par before dove into that...
I don't want to work on anything thats already being done or step on anyones toes...

Title: F4U version1
Post by: Saxman on February 22, 2007, 12:16:38 PM

Looks like a 1D, so you're pretty safe from me. :D

Title: F4U version1
Post by: Krusty on February 22, 2007, 12:47:51 PM

Usually you do it the other way around (decide on the skin then begin work)!!

Title: F4U version1
Post by: Saxman on February 22, 2007, 02:53:01 PM

Could be he was just setting himself up a generic template first that he can adapt for the individual skins. That's what I did.

Title: Re: F4U version1
Post by: DarkNet on March 07, 2007, 08:24:13 PM

(http://www.linuxjet.com/images/AH/f4u1.jpg)
(http://www.linuxjet.com/images/AH/f4u2.jpg)
(http://www.linuxjet.com/images/AH/f4u3.jpg)
(http://www.linuxjet.com/images/AH/f4u4.jpg)

changes image host location