Opening Vega Strike image files
Moderator: pyramid
-
- Explorer
- Posts: 9
- Joined: Wed Nov 28, 2007 4:32 am
Opening Vega Strike image files
One would think that this would be fairly straight forward put would seem that everything but Vega Strike believes that the image files that VS comes with are either corrupt or damaged. Is there some esoteric method of opening say, confedPri.png in Gimp? Is there a plugin I'm missing? Similar problems with the splash scream .jpgs. Thoughts?
-
- The Shepherd
- Posts: 5841
- Joined: Fri May 13, 2005 8:37 pm
- Location: Ottawa
- Contact:
As it says on the front page one of the new features of the beta is that the textures are compressed to dds format and yes there is a plug-in for theGIMP and one for photoshop as well there is a link to the plug-in in this thread http://vegastrike.sourceforge.net/forum ... hp?t=10003 if you have problems just post
Enjoy the Choice
Enjoy the Choice
my box::HP Envy i5-6400 @2Q70GHzx4 8 Gb ram/1 Tb(Win10 64)/3 Tb Mint 19.2/GTX745 4Gb acer S243HL K222HQL
Q8200/Asus P5QDLX/8 Gb ram/WD 2Tb 2-500 G HD/GF GT640 2Gb Mint 17.3 64 bit Win 10 32 bit acer and Lenovo ideapad 320-15ARB Win 10/Mint 19.2
Q8200/Asus P5QDLX/8 Gb ram/WD 2Tb 2-500 G HD/GF GT640 2Gb Mint 17.3 64 bit Win 10 32 bit acer and Lenovo ideapad 320-15ARB Win 10/Mint 19.2
-
- Explorer
- Posts: 9
- Joined: Wed Nov 28, 2007 4:32 am
-
- The Shepherd
- Posts: 5841
- Joined: Fri May 13, 2005 8:37 pm
- Location: Ottawa
- Contact:
No problem homer moments are good for the ego
Enjoy the Choice
Enjoy the Choice
my box::HP Envy i5-6400 @2Q70GHzx4 8 Gb ram/1 Tb(Win10 64)/3 Tb Mint 19.2/GTX745 4Gb acer S243HL K222HQL
Q8200/Asus P5QDLX/8 Gb ram/WD 2Tb 2-500 G HD/GF GT640 2Gb Mint 17.3 64 bit Win 10 32 bit acer and Lenovo ideapad 320-15ARB Win 10/Mint 19.2
Q8200/Asus P5QDLX/8 Gb ram/WD 2Tb 2-500 G HD/GF GT640 2Gb Mint 17.3 64 bit Win 10 32 bit acer and Lenovo ideapad 320-15ARB Win 10/Mint 19.2
-
- Developer
- Posts: 2150
- Joined: Mon Apr 23, 2007 1:17 am
- Location: Pennsylvania
- Contact:
most of the problems with opening images in VS has to do with lazily programmed applications just looking at the extension of the file to determine the type. Applications should not depend on the filename to verify type. In addition to the lack of the correct reader plugin.
Also, there is a definite lack of time on our part in renaming image files to reflect their real format, or at least to a pseudo extension, like .vsg (vs graphic). I'd really like to see all the .jpg and .png files renamed, since they are misleading. Doing so requires a lot of data editing though, since many many files reference images explicitly.
Also, there is a definite lack of time on our part in renaming image files to reflect their real format, or at least to a pseudo extension, like .vsg (vs graphic). I'd really like to see all the .jpg and .png files renamed, since they are misleading. Doing so requires a lot of data editing though, since many many files reference images explicitly.