Zc 2.50 rc3

*Attn Windows users* After opening zc for the first time, close it and open up the config file (ag.cfg) and change these two lines: zq_win_proc_fix = 0, zc_win_proc_fix = 0. This will fix many crash problems that may occur.

Windows: http://www.mediafire.com/?wb4eywz2ma4gd2h
Linux: http://www.mediafire.com/?qnhy9s7cnkd19hu
Mac OS X (Intel only, compiled in 10.6.8 Snow Leopard): http://l.j-factor.com/zeldaclassic/ZC-250-rc3.tgz

Quests saved in RC3 will not work in older builds. They'll open, but they'll be badly corrupted.

HORRAY!!! I can finally play ZC in a big enough screen. Good work!

Nice! thanks :)

Sorry for the momentary delay. If something doesn't work right with the OS X build then do tell.

Is the 1600x1200 working? I think mine stays at 800x600 or something. 1280x960 is good.

Works here in Fullscreen.

Quote:

---

Originally Posted by Misopesaminos

Is the 1600x1200 working? I think mine stays at 800x600 or something. 1280x960 is good.

---

Is 1600x1200 not working right? It should be.

Maybe it's my computer...

Like I said, it definitely works here in Fullscreen mode. I checked my monitors OSD to see what mode it was running in and it reported back it was running at 1600x1200.

It seems 1600x1200 does indeed not work on Windows 8 Consumer Preview, it does however work under Windows 7.

Anybody having trouble with Windows 8 Consumer Preview, do the following:
Open the Zelda Classic folder.
Right click zelda-w.exe and click Properties.
Click the compatibility tab.
Check "Reduced Color Mode" and set it to "8-bit (256) color."

Sorry but is Build 1497 downloadable ??? now that I got it to stop crashing in window mode it runs real slow!!

Quote:

---

Reverted a change that hurt the game's framerate on many systems. ( Saffith, 2012-03-08 07:19:46 )

---

thanks!!

Nasty!

Upon attempting to run Zelda Classic, I get the error

Code:

---

./zelda-l: error while loading shared libraries: libXpm.so.4: cannot open shared object file: No such file or directory

---

I am running 64 bit Arch Linux
I do have libxpm installed, and it does have libXpm.so.4 under /usr/lib/libXpm.so.4

Quote:

---

Originally Posted by Nastytang

Sorry but is Build 1497 downloadable ??? now that I got it to stop crashing in window mode it runs real slow!!

---

No, it's not. The change that was referring to was a ways back; if you didn't have the same problem in RC2, that's not what was fixed.

Quote:

---

Originally Posted by mraof

Upon attempting to run Zelda Classic, I get the error

Code:

---

./zelda-l: error while loading shared libraries: libXpm.so.4: cannot open shared object file: No such file or directory

---

I am running 64 bit Arch Linux
I do have libxpm installed, and it does have libXpm.so.4 under /usr/lib/libXpm.so.4

---

Do you have 32-bit libraries installed?

Yes, some, but I do not believe I have a 32 bit version of libXpm installed

Edit: I installed lib32-libxpm and now it works, thank you for the help

nice going guys zelda classic crashes upon pushing any button.

Problem signature:
Problem Event Name: APPCRASH
Application Name: zelda-w.exe
Application Version: 0.0.0.0
Application Timestamp: 4f4aad0d
Fault Module Name: StackHash_0a9e
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: ffff0851
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789


Dunno if that'd be useful at all.


Win7 64 Pro. Used z-launcher, tried setting 1280x960.

open up ag.cfg and change these two lines:
zq_win_proc_fix = 0;
zc_win_proc_fix = 0;

then you can enjoy it not crashing in all its glory.

they're not in there, where do I put 'em?

in the [zquest] and [zeldadx] sections respectively.

I'm trying to play this on my Mac. I've played it before and it worked fine, but now it suddenly won't let me hit any direction but Up. =\

I've tried re-downloading it, but that didn't work. I tried setting the controls, that didn't work. I tried using a joystick, and it crashed. -_-

Any ideas? I'm on OS X 10.6.8 Snow Leopard.

EDIT: Deleted all files and re-installed it, and now Down is the only working direction on the menu, but Link walks Up/Left automatically. -_-

I had my first experience playing a version other than 1.90 today. I am generally testing forward compatibility of the quests I have made and am making and I noticed a few things that don't seem right.

-general choppiness. it seems this thing is a bit weighed down with code within code. I have watched a lot of videos of newer games and I always thought the frantic and spastic execution of moves was inherent in the video software, but I now believe it is just the program itself. it isn't fluid like 1.90 was.

-I reach up much better than I reach down (and pick the...) and hitting enemies has changed A LOT. guys two tiles above are easy to hit with the sword, but guys one tile below are hard to hit with the sword. this can be seen as a feature, sure, but as an automatic conversion it changes the gameplay by default a bit too much. in what i believe is a related issue, one of the sections of HowHigh is unreachable in 2.5(3) because it required the player to place a bomb downward and hit a combo that destroyed a house. I suspect it was two tiles down and can no longer be reached. these types of changes may even be "fixes," but they break old workarounds to problems that may not have appeared to be problems.

-octorock shots got through objects. they used to bounce to gone upon hitting trees and rocks and the likes, but now they keep going until they hit the hero or the edge of the screen. I figure there is a way to fix this stuff, but I also think every effort to adhere to the rules that the quest was written for should be made so quests are forward compatible but play as they did in previous versions. the way enemies act has changed; even if the changes are for the better, it can ruin compatibility when they default to actions different than they used to. I hope that makes sense.

I'm sure I will see more that I will question, but my major point is that I think 2.5x should recognize which build a quest was made in and treat it accordingly whenever possible so old quests don't become impossible to complete. thanks for reading this and wish me luck with learning to use these newer versions.