After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 141807 - scratch TGA from 3DSMax6
scratch TGA from 3DSMax6
Status: RESOLVED DUPLICATE of bug 138178
Product: GIMP
Classification: Other
Component: Plugins
2.0.x
Other Windows
: Normal critical
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2004-05-04 09:24 UTC by Bendel Xavier
Modified: 2004-05-13 16:00 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Bendel Xavier 2004-05-04 09:24:32 UTC
Impossible to import .tga files rendered in 3DSMax6.
File>Open>tga file
The file in the window looks like scratches lines of colors.

Is there any configuration in plugins to import those files in The Gimp.
NB : I tried with "Maya 5 tga images", I had no problems; import is perfect.
Comment 1 tobias 2004-05-05 07:19:12 UTC
Please add a link to such a file.
Comment 2 Maurits Rijk 2004-05-07 08:09:47 UTC
Xavier: do you see any warnings/errors on the console while loading this file?
And please add either a link or an attachment to this report so we can
investigate this problem.
Comment 3 Bendel Xavier 2004-05-09 08:41:27 UTC
No, I have no message when I imported the file.

See the TGA files...
The image rendered with Max6 :
http://xavier.bendel.free.fr/bugzilla/SalonIm01_11m41s.tga

The image opened and resaved in The gimp :
http://xavier.bendel.free.fr/bugzilla/TheGimp_SalonIm01_11m41s.tga
Comment 4 Hans Breuer 2004-05-09 13:11:38 UTC
The image loads fine on Linux (and I could not download it on win32 cause my
browser thinks its a text file). Is's a common portability problem to
open/read/write binary files as text file (cause on *NIX there is no difference)
- but looking at The GIMP's tga plug-in it does not have this problem. 
So maybe some other program has done it wrong ?
Comment 5 Hans Breuer 2004-05-09 15:18:41 UTC
Some further investigation (starting from bugs FIXED, NOTGNOME) reveals some
probable problems in the build environment used to create the binary GIMP
distribution.

See:
https://sourceforge.net/tracker/index.php?func=detail&aid=863667&group_id=2435&atid=102435

Maybe there should be a prominent link somewhere on wgo or the windoze gimp
installer page to avoid wasting time while investigating duplicates like this ?

Thanks,
    Hans
Comment 6 Jernej Simoncic 2004-05-09 16:00:14 UTC
The installer released on 1st May (gimp-2.0.1-i586-setup-1.zip) should not have 
this problem.
Comment 7 weskaggs 2004-05-10 15:51:25 UTC
This is probably a duplicate of bug #139343 (which Hans figured out but didn't
reference.)
Comment 8 Bendel Xavier 2004-05-13 15:33:32 UTC
I have just installed gimp-2.0.1-i586-setup-1.
The problem is fixed.

THanx for all

Have fun!

gzavye
Comment 9 Sven Neumann 2004-05-13 16:00:23 UTC

*** This bug has been marked as a duplicate of 138178 ***