590 replies to this topic

[Cukeman]

On Mac, when I go to "View Map > Save to File (Mapmaker)" ZC crashes.
Sometimes it does make an image in my folder, but it is only 256x224.

What I said before isn't quite true.

ZQ DOES crash when I go to "View Map > Save to File (Mapmaker)"
but it successfully makes a full size map file in my ZC folder.

[aaa2]

I was looking through zscripts available functions in std.txt once again when my eye fell on this line:


const int SFT_*
* Screen Freeze Types, can be used to set or compare against Screen->Freeze

Then i looked at std.zh to find out what constants are possible for this and found that this was written:
//Screen Freeze Types
const int SFT_NONE = 0;
const int SFT_FREEZE = 1;
const int SFT_FREEZEFF = 2;

However much to my sadness i had to find that Screen does not have a variable called freeze(compiler complaining) while this is also consistent with zscript.txt i wonder why this is written about in std.txt and std.zh. Am i doing something wrong when trying to set the variable or was it planned to get implemented but just forgotten about? I am curious!

[Mero]

Game->GuyCount only works on screen 00.

[DarkFlameWolf]

Well Saffith, I might have come across a legit bug when converting Lost Isle to 2.5. The screen state carryovers in the Ice Palace (Svalbard Temple) on Horgrus Summit no longer work. You hit the switch, activate the trigger which in the Screen Data IS SET CORRECTLY to the proper screen that the screen state should carry over to, but none of the doors usually activated by those switches actually open or work anymore and after looking through the quest multiple times, I don't see what the issue is. Help?

[Moosh]

I think I've found a bug and something that probably isn't a bug but I think it should be fixed nonetheless regarding weapon types. It appears fire type weapons can't have their CSet and presumably other variables written to on the frame they're created. Boomerang type weapons can't have their CSet written to at all, which I think is kinda silly unless there's some deadly bug caused by changing a boomerang's CSet.

Edit: Small update on the boomerang bug (I'm very sure it's a bug now because of this), it seems if I write both the boomerang's CSet AND Original CSet values the color will change but not if either of them remains unset and the results are still rather bizarre. Here's a video showing the bug:

Edited by Moosh, 19 May 2012 - 04:17 PM.

[Orithan]

This is bizarre.
ZC will crash if a LWeapon goes off the left edge of the screen from Combo 0. I have confirmed this to happen with the Fire, Sword and Bombblast LWeapons.

[Moosh]

This is bizarre.
ZC will crash if a LWeapon goes off the left edge of the screen from Combo 0. I have confirmed this to happen with the Fire, Sword and Bombblast LWeapons.

Just tested this ingame and it doesn't crash. Or do you mean it has to use combo 0?

[Gleeok]

This is bizarre.
ZC will crash if a LWeapon goes off the left edge of the screen from Combo 0. I have confirmed this to happen with the Fire, Sword and Bombblast LWeapons.

Can you post the script that crashes?

[Orithan]

Can you post the script that crashes?

No scripts were involved. The crashes occur where a LWeapon goes off the left edge of the screen from Combo 0. I used the normal Sword, Candle flames and normal Bombs. I see LWeapons as any of Link's weapons, created by a script or not, as opposed to be Link's weapons that are only created by scripts.

Edited by Orin XD, 19 May 2012 - 09:13 PM.

[Ricky of Kokiri]

I don't know if anybody has had this problem, but when I try to load RC3 with a USB gamepad hooked up, ZC crashes on the load game screen. If I unplug the USB gamepad, it doesn't crash.

[MoscowModder]

I use a gamepad (a Logitech, if that matters) and it does not cause any crashes. What kind of gamepad, PC, and OS are you using?

[Cukeman]

So I had a global script that warps Link to a specific screen while his death animation takes place,
but now that my quest is in RC3, this script is ignored. Did something change to not let these
kinds of scripts work? This is a game breaking issue for my quest.

Argh! Another global script I had stopped working in RC3. This was a script that gave and took away item #1
every time link obtained or ran out of item #2

Have all global scripts been disabled for RC3???

Edited by Cukeman, 25 May 2012 - 07:13 PM.

[MoscowModder]

No, global scripts are working in RC3. That would be dumb.

[Gleeok]

Please create a new save file for RC3 and don't reuse old ones that use scripts!

Either that or recompile the scripts in RC3. I don't think that should matter though, as the bytecode should still all be valid.

[Cukeman]

Please create a new save file for RC3 and don't reuse old ones that use scripts!

Yeah, I brought a RC2.5 in-progress quest into RC3...
I'm not sure how to go about bringing my quest into RC3 without starting over though, hmm...

Either that or recompile the scripts in RC3. I don't think that should matter though, as the bytecode should still all be valid.

I guess it's worth trying a recompile before anything else.