Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.
Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).
I was playing around in Coldstone, and my JPG graphics seemed to be causing problems. I'm really annoyed at first, but then I say, "Eh, I'll use pict graphics." They are invisible. Then I notice that the extension is .pict instead of .pct. I change, and they are still invisible. Ok, then, PNGs. I try my PNG. I can see!!! Only problem is, its about 5 times too large. I open graphics converter, checked its size, made sure magnification was normal. I saved again, and what do you know IT STILL DIDN'T WORK. At this point CS is making me very very angry and I feel like shooting it, not to mention another problem where whenever I pick up a certain tome*, it quits. I will try BMP for graphics, but I am getting annoyed. So any ideas on this?
*The tome is near the same place as the graphic
EDIT: Solved tome problem: the tome was in the "normal" layer, not "back" only problem is, the now you can't see it. How stupid. I'd add it to the bug list, but there has been no indication that Beenox even reads that list, so I'll wait till there is. Also, BMPs worked, don't know why the others didn't
------------------ CI-I@()s (url="http://"http://www.evula.org/cha0s/")The Homepage of Cha0s(/url)
(This message has been edited by CI-Ia0s (edited 02-08-2003).)
the manual states JPG, .BMP is a destructive format, avoid using.
Your pict files may have a resolution over 72dpi even 72.001dpi is unacceptable, 72 dpi is the mazimum number of pixels that can fit within a square inch, your png imaes may have a dpi that is 5 times larger than 72 therefore CGE may have scaled them up.
Changing the extension is not an issue, it only will/may be an issue when running an uncompiled/pc version
Magnification has no effect on images outside of viewing.
No matter what format you use CGE will in effect turn them into PNGs upon the compilation into a data file, this is listed just before the chart warning you about destructive formats.
in short ...hue man air oar.
------------------
(url="http://"http://www.geocities.com/ellrx/index.html")eLL' softWare: "eLL'_e_vated" :Last updated 01.28.03(/url)
(url="http://"http://tntphoenix.vze.com")TNT Phoenix: Independant TNT Basic User WebBoard(/url)
(url="http://"http://ellrx.vze.com")eLL comm.Pound : eLL' softWare webBoard..."the quickest way to catch an eLL'."(/url)
Quote
Originally posted by CI-Ia0s: **I was playing around in Coldstone, and my JPG graphics seemed to be causing problems. I'm really annoyed at first, but then I say, "Eh, I'll use pict graphics." They are invisible. Then I notice that the extension is .pict instead of .pct. I change, and they are still invisible. Ok, then, PNGs. I try my PNG. I can see!!! **
Only .pct and .png files work with coldstone. Just to make shure, are you just changing the .pict to .pct or do you accually re-save it as the new file type. You need to re-save it as the new file type not change the end.
I try my PNG. I can see!!! Only problem is, its about 5 times too large. I open graphics converter, checked its size, made sure magnification was normal. I saved again, and what do you know IT STILL DIDN'T WORK. (/B)
Are you using the .png as a tile or a layer?
------------------ Thanks, GrahamVH graham@vhpublications.com Coldstone Developer
** Only .pct and .png files work with coldstone. Just to make shure, are you just changing the .pict to .pct or do you accually re-save it as the new file type. You need to re-save it as the new file type not change the end. ** False. There is no difference all you need do is drop the 'i'. the file type which is pict, remains the same, the only thng that will change is the creator code 8BIM - photoshop ttxt- simpletext/system GKON- graphic converter which has no bearing on the image because it is standard.
** Are you using the .png as a tile or a layer? ** unless your png graphics contain white there will be little effect. About 20 minutes ago i layed down an entire array of semitransparent pngs in the ground layer, the only noticeable effect is that the blaack matte which all games are rendered above bleeeds through.
side note: failure to place an entire layer ground tiles even if they are simply blaack just like the matte, will cause smooth transparencies to be nulled out.
however simply saving, as GrahamVH stated will not solve problems associated with the parent file;
for example photoshop v5, saves png grapics darker, shifting the value to a lower percentile. attempting to save save as save a copy as will not solve the problem. The image will still be drawn dark. The solution (there are more than one but...) you must open the file in Graphic converter, select all, copy, and choose new picture from clipboard (apple+j). Save the file which wil be named 'from clipboard' with the proper extension/file type from the drop down list (checking off the 'set type from extension' box, saves you time and allows you to simply type .png). You now have a perfect translation.
While the details may vary from app to app the principal remains the same, the application will tend to include more than the actual content.
Maybe the PICT/PNG problem is my fault, however, I'd like to note:
BMP is not listed as destructive, just big. Yes, it added about .1 MB to my file, but I don't care. It works, and it looks good. And, since my plugin is small, it won't hurt any downloads too badly.
EDIT: I see that this is a point of interpretation. The manual says to use PICT or PNG for a non-destructive format instead. They could mean that BMP is destructive, or they may just be saying, "It isn't destructive, but it is HUGE."
pg. 87: "The standard Windows raw image format. Not recommended since it uses alot of disk space. You should use PCT or PNG for a non-destructive format instead."
The last sentence labels it as destructive...it needn't be clapped out a syllable at a time.
----->>>
"It isn't destructive, but it is HUGE."
simple Fallacy.
THe literary counterpart/device; 'WIlling Suspension of Disbelief'
Originally posted by ellrx: **The last sentence labels it as destructive...it needn't be clapped out a syllable at a time. **
Ahem, time for an English lesson from Celchu.
From the manual, pg. 87: ** "The standard Windows raw image format. Not recommended since it uses alot of disk space. You should use PCT or PNG for a non-destructive format instead." **
Let me use an analogy here:
"Internet Explorer is standard Windows software. Not recommended since it supports an evil company. You should use Netscape or Mozilla for a web browser instead."
Now, since you have experience with browsers you know that Explorer is, in fact, a browser. However, in the case of graphics formats and ColdStone, you do not have that experience, and so come to the conclusion that BMP is destructive.
As support for this, why would the manual list the reason for avoiding it as "it uses alot of disk space" when "it screws over your game" would be a much better deterent?
Also, please cease using those debate fallacy definitions. They annoy me enough on debate boards, and let's not turn this place into a debate board. Chill, this attitude of yours is creating a hostile environment. Instead of assuming that your interpretation of a guideline is correct (at least in an elusive situation like this), try it for yourself. After all, chaos reported sucess using BMPs.
Chaos, as to your original question, I repeat Graham's question: Are you using the .png as a tile or a layer? This would be the most likely cause.
edit: Ben, I'm now tied with your post count, at long last. Better try to keep up.
------------------ A tomb now suffices for him for whom the world was not enough.
(This message has been edited by Celchu (edited 02-08-2003).)
To the point:
definition: ** the root of destruction is destroy. Quoted from the american heritage dictionary, electronic edition 3:
de0stroy (dž-stroi2) v. de0stroyed, de0stroy0ing, de0stroys. —tr. 1. To ruin completely; spoil. 2. To tear down or break up; demolish. 3. To do away with; put an end to. 4. To kill. 5. To subdue or defeat completely; crush. 6. To render useless or ineffective. —intr. To be destructive; cause destruction. ** the application: BitMaP format is a versatile, sharp crsytal clear format, which allows graphics to be easily reproduced, without significant loss of detail, similar to the metal master records used in CD duplication. However it does so at the expense of memory, more specifically RAM. In addition it leaves vestiges or footprints. It is referred to in many texts as raw, meaning there is intentionally little or no compression scheme/algorithim/encoding involved with it. In a sense it is 'digital Analog'.
CGE no matter how much memory you allot to it still has definite processing limits. It will shut down certain resources in order to continue running a game...ie; sound,music,static graphics and most readily animation. Many of you have or will experience this.
A format that intentionally gathers as much Memory as possible at the expense of the; platform, device, system,program,application which is running it " " and....surrenders itself wholey to all 6 definitions.
The rebuttle to the syllable break down; de- to make the opposite of, invert a process struct- linked to the word structure -ive prone to a type of action
as to your suggestion of trying it for myself, i present you with a tried and true, equation over an analogy:
more memory docile, more memory volatile.
(DIAL TONE)
(url="http://"http://www.geocities.com/ellrx/index.html")eLL' softWare.(/url)
I'm not hostile i'm just accurate. But by all means, please...feel free to take pot shots at my education/learning, go on the first gram's free wink.