590 replies to this topic

[Saffith]

Hm, I'm still not seeing it... Might be some weirdness with the path or filename.
What's the name of the file? Does it make a difference if you move it into the ZC application directory?

[Cukeman]

Hm, I'm still not seeing it... Might be some weirdness with the path or filename.
What's the name of the file? Does it make a difference if you move it into the ZC application directory?

It looks like it's working fine now. I went and moved my files into the ZC folder for RC3
(I guess before I was trying to run them from the ZC folder for 2.5)

Edited by Cukeman, 28 February 2012 - 07:21 PM.

[Colossal]

OK, well that sucks. It looks like it's crashing somewhere in the allegro event handling code. I don't know why. The fix for this is not fun so it's getting deferred to post 2.5. win_fix is now 0 by default and will always log a warning message at startup if it is enabled by the user or accidentally set somehow.

Thanks for testing it though. I'll try and get a bugfix version out soon.

I found this in Allegro.log after a crash on exit with zc_win_proc_fix = 1

CODE

Armageddon Games web site: http://www.armageddongames.com
Zelda Classic web site: http://www.zeldaclassic.com
Zelda Classic wiki: http://www.shardstorm.com/ZCwiki/
AllegroProc().... ...returned ok, .
AllegroProc().... ...returned ok, .
AllegroProc().... ...returned ok, .
AllegroProc().... AllegroProc().... ...returned ok, .
...returned ok, .
AllegroProc().... ...returned ok, .
AllegroProc().... ...returned ok, .
AllegroProc().... ...returned ok, .
AllegroProc().... AllegroProc().... ...returned ok, .
AllegroProc().... ...returned ok, .
AllegroProc().... ...returned ok, .
AllegroProc().... ...returned ok, .
AllegroProc().... ...returned ok, .
AllegroProc().... ...returned ok, .
AllegroProc().... ...returned ok, .
AllegroProc().... AllegroProc().... ...returned ok, .
...returned ok, .
AllegroProc().... ...returned ok, .
error: HWND != hWnd. WTFBBQ?!?
AllegroProc().... ...returned ok, .
...returned ok, .

EDIT: RC3.1 seems to crash on exit less often than RC3, at least for me.

Edited by Colossal, 28 February 2012 - 08:55 PM.

[Gleeok]

That actually looks like the random and rarely seen still "at exit" crash which is unrelated. That one is still a mystery for me too since it's very rare and only happens in RELEASE configurations for me.

[Cukeman]

When I opened up my .qst file made in RC 2.50 I got a message that my enemy data was corrupted.
All I'd done was change sensitive warps to stair. Don't know if this might be related to filepaths

[Saffith]

You mean you saved the quest in RC3 and then opened it in RC2.5, right? That's going to mess up more than just enemy data.

[Moosh]

I notice that clicking the flag button now takes you to the flag menu, eliminating the handy scroll wheel shortcut I was accustomed to...could you maybe at least make this toggleable?

[Cukeman]

Boomerang blocks block Link's boomerang, but not enemy boomerangs.
Is this a bug, or is that the way it was designed to work?

Edited by Cukeman, 29 February 2012 - 04:16 AM.

[cavthena]

In the Edit Message String window you can now bookmark Messages by creating a string beginning with two hyphens.
Has anyone been able to get this working?

[Xenix]

I hope I'm not bothering you guys by asking this, but is there any possibility of at least one scripted LWeapon being affected by gravity? This would be very greatly appreciated as one script my group is using relies on that and Zepinho is having to try to find a workaround and write lots of extra code and this would make things so much simpler. I just need one of them to be affected by gravity.

[Moosh]

I hope I'm not bothering you guys by asking this, but is there any possibility of at least one scripted LWeapon being affected by gravity? This would be very greatly appreciated as one script my group is using relies on that and Zepinho is having to try to find a workaround and write lots of extra code and this would make things so much simpler. I just need one of them to be affected by gravity.

I believe you can do this with ghost.zh.

[Saffith]

I notice that clicking the flag button now takes you to the flag menu, eliminating the handy scroll wheel shortcut I was accustomed to...could you maybe at least make this toggleable?

Probably not, honestly.

Boomerang blocks block Link's boomerang, but not enemy boomerangs.
Is this a bug, or is that the way it was designed to work?

That's a bug. Should be pretty easy to fix.

In the Edit Message String window you can now bookmark Messages by creating a string beginning with two hyphens.
Has anyone been able to get this working?

Hm, yeah, that doesn't seem to be working... Another thing I'll have to look into.

I hope I'm not bothering you guys by asking this, but is there any possibility of at least one scripted LWeapon being affected by gravity? This would be very greatly appreciated as one script my group is using relies on that and Zepinho is having to try to find a workaround and write lots of extra code and this would make things so much simpler. I just need one of them to be affected by gravity.

Here:

Code

CODE

import "std.zh"

const int FALLING_LWEAPON_ID=31;
const float LWEAPON_GRAVITY=0.16;
const float LWEAPON_TERMINAL_VELOCITY=3.2;
const int IDX_LWEAPON_GRAVITY=15;

void DoFallingLWeapon(lweapon wpn)
{
    if(wpn->ID!=FALLING_LWEAPON_ID)
        return;
    
    if(IsSideview())
    {
        if(OnSidePlatform(wpn->X, wpn->Y))
            wpn->Misc[IDX_LWEAPON_GRAVITY]=0;
        else
        {
            wpn->Y+=wpn->Misc[IDX_LWEAPON_GRAVITY];
            if(OnSidePlatform(wpn->X, wpn->Y))
            {
                wpn->Y=Floor(wpn->Y/8)*8;
                wpn->Misc[IDX_LWEAPON_GRAVITY]=0;
            }
            else
                wpn->Misc[IDX_LWEAPON_GRAVITY]=Min(wpn->Misc[IDX_LWEAPON_GRAVITY]+LWEAPON_GRAVITY, LWEAPON_TERMINAL_VELOCITY);
        }
    }
    else
    {
        if(wpn->Z<=0)
            wpn->Misc[IDX_LWEAPON_GRAVITY]=0;
        else
        {
            wpn->Z=Max(0, wpn->Z+wpn->Misc[IDX_LWEAPON_GRAVITY]);
            wpn->Misc[IDX_LWEAPON_GRAVITY]=Max(wpn->Misc[IDX_LWEAPON_GRAVITY]-LWEAPON_GRAVITY, -LWEAPON_TERMINAL_VELOCITY);
        }
    }
}


global script FallingLWeaponScript
{
    void run()
    {
        lweapon wpn;
        
        while(true)
        {
            for(int i=1; i<=Screen->NumLWeapons(); i++)
            {
                wpn=Screen->LoadLWeapon(i);
                DoFallingLWeapon(wpn);
            }
            
            Waitframe();
        }
    }
}

[Anthus]

At the moment, it's not possible. It might not be hard to add; I'll look into it.
Set zc_win_proc_fix and zq_win_proc_fix to 0 in ag.cfg. If that doesn't help, try setting disable_direct_updating to 0.

Actually, it isn't doing it anymore. It only did it the first few times I ran the programs. Strange.

[Eurysilas]

Still no fullscreen support in the Mac client. What logs do you require?

[Saffith]

allegro.log from after it crashes may help, but if there's any terminal output, that would probably be better.

Higher resolution handling has changed now. Does it make a difference if you set resx and resy in ag.cfg to match your screen resolution?