590 replies to this topic

[ShadowTiger]

Any word on whether zq_win_proc_fix=0 fixes crashes?

Actually ZQuest has been behaving quite nicely with it set to 0. I did have an odd little crash that was actually somewhat consistent, though I've no idea what caused it. When I was fixing bugs in the DoY Quest file, sometimes when I would open up the Tiles Page, it would immediately freeze then crash. There aren't really any specific conditions on which it would happen, though it started on a screen I had made a new palette for. Started on Map 63, Screen 79 of the DoY Quest file. (I guess you don't need the password for it? ) Merely being on that screen causes the Tiles Page to crash sometimes. No rationality, but when it does crash and I boot it back up again, opening the tiles page again still crashes it, every time. Only if I don't do something else though.

Also, while you're in there, see how long it takes for any string dialog to load. Pretty long. 600+ strings in there.

[Gleeok]

Any word on whether zq_win_proc_fix=0 fixes crashes?

The answer to this is pretty much yes. I may try at some point to update our version of allegro to 4.4, which has mostly low-level fixes and not so many API changes. I believe this might help on windows at least, though it's unlikely to be a good move right now. Maybe after 2.5 gets tagged?

One crash I am unable to reproduce is a rogue crash in the constant folding parser. (still investigating this) I also believe that the tiles crashes reported earlier should not happen anymore.

Merely being on that screen causes the Tiles Page to crash sometimes. No rationality, but when it does crash and I boot it back up again, opening the tiles page again still crashes it, every time. Only if I don't do something else though.

ST: Is the tile the cursor would appear on when entering the tile pages blank? If I send you an early RC4 can you confirm this has been fixed?

[ShadowTiger]

ST: Is the tile the cursor would appear on when entering the tile pages blank? If I send you an early RC4 can you confirm this has been fixed?

That's ... wow. I don't even know how to answer that question. Does the answer to this possibly default to tile #0? Isn't that never blank? I.e. it has the heart gauge and rupee and bomb minitile information on it?

Or are you referring to me finding a tile through seeing what tile a combo points to, that happens to be on tiles page 0? It's not that, no. I just hit "t" to go to the tiles page, and then it immediately freezes for a second (Not more than one or two.) then crashes.

I wouldn't really have a way of knowing what tile the cursor initially appears on, because it crashes. Are you saying that it's somehow possible that the cursor would appear outside of the scope of the first tiles page despite being on the first tiles page? Because that's pretty neat. Ignore me, I'm dumb.


But to send me an Early RC4 would mean that I would have to reproduce the conditions of the crash. I would have to be able to tell whether or not I would be in the conditions that had caused the previous crash, which I can't do now. I'll certainly be glad to give it a shot of course.

[Gleeok]

Or are you referring to me finding a tile through seeing what tile a combo points to, that happens to be on tiles page 0? It's not that, no. I just hit "t" to go to the tiles page, and then it immediately freezes for a second (Not more than one or two.) then crashes.

I just tested this with the current revision 1507 and am unable to get a crash. Map 63, screen 79. I believe this should be fixed already though:

* Fixed a bug where a crash can occur while using the 'grab' option in the tile pages, or possibly any other place in the tile page where memset is used on potentially unallocated memory. ( Gleeok, 2012-04-28 05:04:36 )

I don't know how close we are to a RC4 right now. It might be a good idea to get it out just for all the major fixes. (like crashes)

[ShadowTiger]

OH SNAP actually you're right, I had been grabbing from things. Hence why I was in the tiles page so much. You're good. ;-p Okay, crash fixed then. Thank you.

[kurt91]

I'm trying out JoyToKey, and a modded PSP as a game controller, on ZC for the first time. It's crashing every time I start the program, but only when I have JtK and the PSP plugged in. If I turn all that stuff off and take the PSP out, then ZC runs normally.

I've been running a Super NES emulator with this setup, and everything works fine, so the issue has to be coming up from ZC's end. Any idea how to fix this?

[MoscowModder]

You don't need JoyToKey - ZC has gamepad support built in.

[Xenix]

I'm trying out JoyToKey, and a modded PSP as a game controller, on ZC for the first time. It's crashing every time I start the program, but only when I have JtK and the PSP plugged in. If I turn all that stuff off and take the PSP out, then ZC runs normally.

I've been running a Super NES emulator with this setup, and everything works fine, so the issue has to be coming up from ZC's end. Any idea how to fix this?

Dude, just use Fusa Game Pad. It will make it a game pad without all the extra hardware and software.
http://foosa.do.am/n...3/2010-01-03-23

[Saffith]

BUG: So has anyone ever tried to save and import a subscreen (.zss) file? ZQuest doesn't seem to recognize it as a compatible valid filetype, despite it being in the same folder as ZQuest's executable. (Everything is all in the same folder.)

Maybe we should just remove that. .sub works, and I don't see why we need two ways of doing the same thing.

Ok, so I've noticed that if you step of a combo that's been changed to a direct warp with a script (may have to be on the frame after it's changed, IDK) it warps you to the screen you're currently on. Might wanna get that checked out...

Can you make a demo quest or a script that will reproduce that reliably? I'm not having much luck with it.

I've been running a Super NES emulator with this setup, and everything works fine, so the issue has to be coming up from ZC's end. Any idea how to fix this?

Do you have zc_win_proc_fix=0 set? Gleeok mentioned problems with input specifically, so that seems likely to be the problem.

[Mero]

Hey Saffith did you ever get around to fixing Link->PressMap?

[Saffith]

Its done, I just haven't committed it yet.

[Mero]

Found another zscript bug. Game->GetScreenFlags map argument is based off 0 instead of 1.

And I assume the same apply to the above too, it's done just not committed yet?

[kurt91]

Dude, just use Fusa Game Pad. It will make it a game pad without all the extra hardware and software.

That's what I'm using. I didn't know ZC had gamepad support, so I was trying to use JoyToKey to map out the buttons, like I've been doing for the emulators I've been running it with.

Do you have zc_win_proc_fix=0 set? Gleeok mentioned problems with input specifically, so that seems likely to be the problem.

Next time I get a chance to borrow the PSP again, I'll give it a try without JtK, and see if it still crashes. I don't want to mess with the settings it's already at just yet. It works just fine as long as I use the keyboard for input.

[Cukeman]

possible bug with flickering shadows: http://www.purezc.co...&...st&p=783718

[Omega]

zc_win_proc_fix=0 Has got rid of window mode crashes for me and a friend who uses windows 7 and vista.