TSHPI Error: Unknown Pixel Format

I get this error msg whenever i try to open/view the extracted fsh file from the players.viv file.
What am i doing wrong?

I get this error msg whenever i try to open/view the extracted fsh file from the players.viv file.
What am i doing wrong?

I am guessing that you are not using version 1.0.0.

The latest version recognizes all known EA graphic pixel formats. If you do have version 1.0.0 then I would be very interested in finding out how you got that error.

My bad, i was using the old version
ok i feel like an idiot now....

My bad, i was using the old version

Not a problem. Glad to hear you are taken care of now 8)

Remember, there is no such thing as a stupid question. Just stupid people that ask them [just kidding]

Hehe....silly Joe and his silly thread... You were so convinced that you had the right version too...awww...

Brien,
How come when you open a player bhed it comes out 16 Bpp...i know you mentioned it in another thread but i don't understand what the point of it being converted to 16 Bpp when you have to convert it to 24 anyway. And it's quality isn't as good as the fshtool.

And How come when you extract the bhed image from a player.viv at 16 bpp it turns out too much over to the left?

It's no hastle converting to 24 Bpp. Just some little questions.

How come when you open a player bhed it comes out 16 Bpp...i know you mentioned it in another thread but i don't understand what the point of it being converted to 16 Bpp when you have to convert it to 24 anyway. And it's quality isn't as good as the fshtool.

The image is NOT a 24 bit image. FshTool converts the image to 24 bits. DirectX DXT1 and DXT3 image ARE 16 bits per pixel. 5 bits red, 6 bits green, 5 bits blue. EAGE displays the image in the correct BPP format. FSHTool converts the image to 24 Bpp. Many graphic programs can not handle images in formats other than 8 BPP or 24 BPP. So, I am guessing the author of FSHTool chose to convert his images to 24 Bpp so it would be compatible with more programs.

And How come when you extract the bhed image from a player.viv at 16 bpp it turns out too much over to the left?

I extracted Andre Miller using FSHTool. I then opened the Miller fsh and the FSHTool bmp in EAGraph. Both images appeared to have the same origin (i.e., the EAGraph image was no farther to the left). The tip of Miller's nose was NOT in the middle of either image.

It's no hastle converting to 24 Bpp. Just some little questions.

I am confused why you would want to convert the 16 bit image to 24 bits. Just open, extract, open, use import wizard, and you are done. If you were to use FSHTool to import a 24 bit image, FSHTool would have to reduce the colors to 16 BPP to store it as a DXTC image.

Please, I am not trying to be negative about FSHTool. Its a great app. The only misconception is that "because it saves images in 24 bits" then FSHTool is correct and EAGE is wrong. As a statement of FACT... DXT1 and DXT3 compressed images are in 16 BPP.

I am confused why you would want to convert the 16 bit image to 24 bits.

I don't know if this happens to anybody else, but as i said before, when i extract the .bmp as 16 bpp it appears to far to the left. When i convert it to 24 Bpp and extract the .bmp again it looks fine. I don't know why this happens. maybe i'm doing something wrong...but it happened to me with the 2k1 version too.

Also, When i extract the .bmp from a .fsh with the fshtool...the qulity looks better as apposed to using the EAGE. Does it do this on purpose?

I don't know if this happens to anybody else, but as i said before, when i extract the .bmp as 16 bpp it appears to far to the left. When i convert it to 24 Bpp and extract the .bmp again it looks fine. I don't know why this happens. maybe i'm doing something wrong...but it happened to me with the 2k1 version too.

So when you say "extract" what you must mean is "save as". In EAGraph extract just makes a 1:1 copy of the EA bits and saves it to a file. So, when you extract a fsh, it is saved to file as a fsh, not a bmp. So, you are saying there is a problem with the way the fsh is saved as a bmp. There could be a bug there, I will test it out. Thanks for the lead.

Also, When i extract the .bmp from a .fsh with the fshtool...the qulity looks better as apposed to using the EAGE. Does it do this on purpose?

It could be this problem is related to the one above. My problem was your use of the word "extract". In reality, even FSHTool just reads the fsh and "saves it as" a 24 bpp bitmap.

I was going to release ver 1.0.1 today, but i think I will check this out first.

Thanks again.

well, i could show you the difference between fsh files opened with fshtool and ones with eage... and it is noticable



the first one from the left is eage's, the second is opened with fshtool. the difference is noticable (especially on the neck part), colors arent that smooth etc...

anyhow, if the quality could remain the same... that'd be great.

Thank you Tony-x.

I will look into it more. The new version 1.0.1 will have slightly better quality in presentation than 1.0.0

I see the quality problems. However, I can not reproduce the "too far left" problem reported by Barn-Z. I save the file as a bmp and then reopen it, it appears just like the original.

And How come when you extract the bhed image from a player.viv at 16 bpp it turns out too much over to the left?

However, I can not reproduce the "too far left" problem reported by Barn-Z. I save the file as a bmp and then reopen it, it appears just like the original.

I am getting this problem too (with Live 2000). I opened a player's .fsh file and save the face as a .bmp. Then when I open it in Paint Shop Pro and the player's face is too far to the left. It looks fine if I open the .bmp in EAGE. And when I import it back into the .fsh file it is now too far to the left when I look at it in EAGE.

daChiller

It sounds like there is difference in byte alignment between the way the EAGE creates a bmp and the way that Photoshop reads them. This is definitely not fixed in the latest version of EAGE.

EAGE now creates 24 bit bitmaps just like fshtool. Maybe this problem will mysteriously disappear!