Messages

Thanks, Tuomas!

[AGS]

AGS: it's a fact, girls don't masturbate.

5th annual show yet it's 10 years old? How does that work?

It only takes place every two years? My guess.

EDIT: Oh wait, does annual strictly mean "yearly"? If that's the case, ignore this post.

A tornado made danceable in locrian...

YES!!

Thanks guys. I had already tampered with various config-files in the ps-directory, but that didn't help, tried to let ps create new ones (didn't help) and there were no log-files.


Now I have gone to the Settings and Documents folder for Photoshop and deleted those default files and now it works!

But honestly, Photoshop is programmed extremely weakly if hitting ctrl+q while it loads and messes with those default files (I guess) corrupts those files and really - in a way - trashes your copy of the program. Also, that it doesn't give you an error or creates a log-file telling you what's wrong is ridiculously bad - especially considering the image and price for the tool. That's a joke.

Thanks a lot, lot, lot!

Hmm... Reinstalling is not an option. I legally have Photoshop 5 LE, but I needed some functions for .tif-files for an important project and couldn't afford Photoshop 7 at all (which is still what I'm using *hint*). I hope you can understand this and not think of me as a dirty thief for all eternity...

I still don't believe it's RAM, because how could it just make one single program quit on startup? That seems very illogical too me, first of all, it would freeze the computer and not quit a single program - or am I misunderstand something here? And, as I said, it started doing this in the exact same moment I discovered that ctrl+q-shortcut, and now it quits in a very same way.

A further hint: it always quits while displaying: "initializing color preferences" in the splash-window. Don't know if that's really the cause, because it might just be the last line before really starting up etc., but that's the last thing I can read. A millisecond after displaying that line, it just vanishes.

Any help is immensely appreciated! I really need .tif-files with alpha-channels, and I don't know any other way of getting those without Photoshop (not even ImageReady can do that, which - as I said - still works). A project depends on this.

Very nice.

One thing that always bothers/bothered me: the blue back walls. First they were all the same color, now the back wall is darker than the left and right one. Turn that around. Give the darker shade to the left and rigth wall and the lighter one to the back wall. This is the way it would look like with the window being there.

You could also make the left window wall the darkest, make the back wall brighter and then make the right wall the brightest. Test it out how far you want to go with "realistical" shading.

Hmm... I don't know... My RAM messing with only Photoshop? Because I do CPU intense stuff with it just fine (like audio recordings etc).

EDIT: And about the RAM-thought: it worked perfectly even today. I really set it off by pressing that button twice (or it was really, really bad timing).

I will try to reinstall.

@Krishmuc: sure, that might be usable, but imagine creating a new file entering dimensions etc., then wanting to select all (CTRL+A) but by accident hitting one row above A -> Q. Bam, it exits. And this is what happened to me and there was no box asking for confirmation for some reason.

Technical help needed again, sorry guys.

This is really strange, I have used PS 7 since years and it always worked fine.

Today I start it up, accidentally hit CTRL+Q and it just disappears (I checked, it quit really quickly, the task was gone as well in the task-manager, so it was really gone, not just minimized etc), I find that strange, am not really sure what happened, so I start it up again, wait until it's started up completely (after the splash-screen disappears etc) and hit CTRL+Q again and it really works again. PS quits.

Allright, no problem. But whenever I try to start it now, it quits instantly while the splash-screen is still showing. Can't access the program at all. ImageReady still works, but when I try to jump from IR to PS, it says "Can't jump to PS because it doesn't respond".

What is up with that? I find it heavily strange to have such an instant-quit hotkey in the first place, but how can it ruin the program in that way?

I already tried a restart, didn't change a thing.

Style is good, but that's hard to judge without knowing more about your game/taking a loot at in-game screen-shots.

Fonts are good, but maybe try to anti-alias the edges (manually or automatically). They do work as they are, though.

Can't say anything about the name without knowing more about the project.

Another point of critic: I would make the New, Load and Quit buttons (ie. the font) smaller. They seem a little big.

Ah, okay. I didn't realize you could press twice. I though you had to hold it down - this way the rocket activates too, but too early to reach the other side. Just finished the demo, was nice, although it could use a little bit more polishing (at more levels of course).

Oh, I see. It just took sooo long. In that case, a loading message is a must.

EDIT: 1st level was easy, 2nd one seems impossible?

Doesn't load for me. That stick-man comes up, title appears fades out and that's it. I tried it through richt-clicking and skipping etc. but won't work.

Second time after cleaning the dust, it didn't do it. Now, the third time, it didn't either. Maybe it DID help...

Thanks so far to everybody, I'll let you know if the problem resurfaces.

Hehe, that doesn't exactly make it much better...

Thanks, though. This surely won't be the last Jam nor my last render.

Darn it. I wanted to enter with this:

It's rendered in Cinema 4d, but still an isometric sprite, very usable in a game with 15 colors + bgd color. Six or seven hours of work... Oh well, might use it in a high-color version for another game...

Nice, added you!

I dusted the computer out, but it didn't seem to help. It reseted itself again just afterwards (only one time, not three, through - but that might've been just luck as well).

I also took a look at the capacitors. There were four and they all had something on top of them, that looked like hard, brownish glue, on some it was more, on some it was just a little drip. Does that really mean they are blown? If so, when all four are blown, the computer shouldn't work anymore at all, should it? Because it still works...

Thanks for the help so far.

EDIT: When it reseted, it always comes up with a screen telling me that "Windows could not be started properly" and allows me to choose to boot up in safe-mode or in normal-mode etc. but also says "Ignore this screen if the computer was shut off because of a power outage etc." I guess, that's normal, because it looks like a power outage (which is why my first thought was the power cable). Also, Windows wants to check the drive consistency in this blueish xp-screen. I did it once a few days ago, and everything was fine. Now I just skip it. Though I'd mention that, too.

Okay, thanks for the help so far, guys. I will take a look at my motherboard as soon as possible. One question though: if a cap would be blown, wouldn't the computer reset either always or while in use? My machine ONLY does it when booting. How does that fit together? Or is it still possible that a faulty cap only sometimes AND only in a certain phase (ie. while booting) causes the computer to reset?

Well, since several weeks now, my computer resets itself while booting. I start it, it loads windows and then usually resets. Starts again, most of the times resets few seconds later again, and usually the third time it works. First it wasn't as bad (reseted once, then worked okay), but since six or seven days now, it needs up to three resets. One time, it even froze while the windows xp-logo was displayed with that little loading-bar underneath it with those three blue rectangles going through. Two times now, it switched completely off and I couldn't turn it on without switching the power-switch on the back of the computer off, waiting 30 seconds or something and switching it on again.

I did a virus check and nothing turned up, I have a good firewall installed in both the router and the computer and pretty good protection, so I kinda doubt it's a virus. In fact, I somehow doubt it's software related at all. The computer is kinda dusty, because I let it run with one of the sides removed, I should probably clean it out, but on the other hand, how would that cause the machine to shut off only while starting up (same applies to the cooler, I first thought it might be the fan not working, but then, why would it only not work at startup - after windows has finally started up, my computer works for hours without problems). The power connection seemed a little loose as well, but again, why would it only be loose at startup and not later on?

Anybody have the same problems?

Thanks for your help.