Can't save my DDS files

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Download and install 18 Wheels of Steel: American Long Haul.
2. Rename the file "base" in the game folder to "base.zip" (change the 
extension).
3. Extract the contents of this file, keeping it's directory structure.
4. Navigate the new directory structure to any model you like that has a DDS 
file.
5. Open the DDS file.
6. Save a copy of the DDS file.

(I included a copy of one of these super advanced files that is at least five 
years old for you to enjoy playing with.  Bet you have the same problems with 
it, since, you know, this is such new and advanced technology.)

Also, I can not see all the layers of the DDS file.
1. Download and install Compressionator by AMD.
2. Open the DDS file that does not save in GIMP.
3. Check the file properties.  You will find it has THREE layers.  Gimp reports 
only ONE layer.

What is the expected output? What do you see instead?
Expected:  Saves a copy of the DDS file.
Instead:  It complains that the file is not the kind of DDS file this is 
designed to work with.  In other words, the DDS add on does not work with DDS 
files.

What version of the product are you using? On what operating system?
Gimp 2.6 with the most recent DDS add-on.  I just installed the program in 
hopes it would be able to edit these files, but apparently it can not.

Operating system is Windows XP Pro SP3.

Please provide any additional information below.
Apparently none of the free applications can convert these files in to full, 
multi-layer images and convert them back.  In the process, all the free 
utilities lose at least one of the layers, resulting in the edited textures 
coming out black.

It seems, as mentioned above, the "DDS editing" applications only load the 
alpha and the texture.  The third layer is apparently ignored, although AMD's 
"The Compressionator 1.50" reports that there are in fact THREE layers, not TWO.

I want to change the texture layer.  But nothing seems able to handle the 
images properly.

This is particularly trying because this game is AT LEAST five years old, and 
the technology it's using could be ten years old or more.

It's unusual for the open source community to lag behind the technology so 
much.  You guys had ready support for SATA drives and can support most NICs 
without any problems, long before MicroSoft caught up.  So this is proving a 
little unexpected.

Original issue reported on code.google.com by leks_tra...@yahoo.com on 2 Mar 2012 at 5:41

Attachments:

• plain.dds

[GoogleCodeExporter]

Marking as WontFix.  I had no trouble with the attached file.  Next time 
instead of being a dick, make a clean bug report and leave your politics at the 
door.  I maintain this plugin with my spare time, which I have little of.  No 
one is forcing you to use this software and it costed you nothing to obtain.  
The source code is available to everyone.  If you would like to help out, by 
all means, have at it.  Be a little more respectful next time.

Original comment by ski...@gmail.com on 26 Jun 2012 at 7:12

• Changed state: WontFix

[GoogleCodeExporter]

"Be more respectful next time." �Do yourself a favor. �Load the texture in 18 
Wheels of Steel: American Long Haul. �Betcha' it's all black.

Aren't you guys so nice? �I remember the Debian groups saying "If you don't 
know how to build your own computer using a microscope, a needle, and a wafer 
of silicon, then you should not be using computers." �Good to know you guys 
have the same attitude.

It's even better to know how your view is that since the encyclopedic source 
code that is generally poorly written to be as difficult to read as possible 
happens to be available for me to read it. �You know the variable 'a' can be 
anything, right? �And when you name a variable gaslkli that isn't terribly 
informative, either. �If you're going to keep your software open source, keep 
the variable names meaningful, so we can tell what they are. �And while your at 
it, name all the functions descriptively. �Naming a function funcgarlic doesn't 
tell me anything about what it does.

I saved the files. �I saved several files, with or without changes. �And the 
program drew them all as black. �Which meant the files were not saved in a 
format for the program to read them. �Which tells me you did not fix it, 
because it still does it. �And you did not test the file fully, either. �If you 
had, you would have discovered that what I described, which was quite detailed 
(loading it in to gimp, saving it without modification, and then loading the 
game) resulted in the texture being destroyed. �Not that you guys care, after 
all. �After all, I'M the disrespectful one here.

Furthermore, without any idea why the software isn't saving a file that is used 
by a program, even without changing it, causes the file to be unable to read in 
the game, how am I supposed to fix the code? �Maybe you can explain what the 
software that the file's being modified for is doing differently so we can fix 
it!

Have fun standing on your high horse. �I hope you, with your "all knowing" 
attitude, discover that your grounds are faulty in your house - the hard way.

"I save the file. �I load it. �It works." �No, it doesn't. �Because the TARGET 
PROGRAM does not load the file correctly after GIMP's FUCKED IT UP.

Original comment by leks_tra...@yahoo.com on 27 Jun 2012 at 2:37

[GoogleCodeExporter]

Downloading a game that runs on a platform I do not own is not doing myself a 
favor. I'm not going to jump through hoops over this. Help me to help you.  You 
obviously own the game already.  All the tools are in your hands to help 
diagnose the issue.  Instead you spend 95% of your "reports" flaming me and my 
work.  Which I did for free with MY spare time.  It's not my problem if you 
don't understand the code.  Other contributors have had no trouble submitting 
patches to fix issues or add new feature.  Your skill level with the C language 
is not my problem.  No, you are a dick, plain and simple.  I'm willing to wager 
you don't work very well with others so I'm not going to hold my breath in 
hopes than you can be more constructive on this issue.  Good day sir.

Original comment by ski...@gmail.com on 27 Jun 2012 at 2:56