290 replies to this topic

[grayswandir]

Pardon my ignorance but I am not sure how to make ZC larger in window mode, the only thing I see in ZCLauncher is screen resolution. It seems like setting the window mode to a larger size would be my solution as the game does play in window mode. Thank you for your help

If that's the only thing you see, why didn't you, you know, try it?

[SyrianBallaS]

You could try modify the ag.cfg file to specify a resolution not predefined already.

 

You have to make sure the aspect ratio is 4:3 though or it'll look funky.

 

Go here for a list of resolutions.

Edited by SyrianBallaS, 18 February 2016 - 04:06 PM.

[Mister Snooze]

You could try modify the ag.cfg file to specify a resolution not predefined already.

 

You have to make sure the aspect ratio is 4:3 though or it'll look funky.

 

Go here for a list of resolutions.

I tried all the screen resolutions in ZCLauncher, that did not work. What program do I use to open the ag.cfg file

[Orithan]

Use Notepad or a similar program like Notepad++ to open ag.cfg

Edited by Orithan, 18 February 2016 - 05:29 PM.

[Mister Snooze]

If that's the only thing you see, why didn't you, you know, try it?

Yeah, cause i am really smart hehe

[SyrianBallaS]

Edited this to match the one I made on AGN

 

Normally this wouldn't be considered a bug, but granted the lag is so horrible in 1st quest there has to be something wrong with the code.

The problem only occurs for me for resolutions above 240p even though I have a pretty decent computer.

 

Here are the specs:

 

 

Also  another issue which is most definitely a bug.

(zlaunch-l:15290): GLib-CRITICAL **: Source ID 57 was not found when attempting to remove it

(zlaunch-l:15290): GLib-CRITICAL **: Source ID 56 was not found when attempting to remove it

 

The PIDs don't matter but the same GLib-CRITICAL appears every single time I exit zlaunch-l.

Edited by SyrianBallaS, 19 February 2016 - 01:36 AM.

[Mister Snooze]

You could try modify the ag.cfg file to specify a resolution not predefined already.

 

You have to make sure the aspect ratio is 4:3 though or it'll look funky.

 

Go here for a list of resolutions.

Thank you for you response! I have tried the following predefined resolutions in ag.cfg, to no avail. I still have the same problem.  Am I the only one out here with Windows 10 Pro that is trying to play these games?

 

640X480

768X480

854X480

800X600

960x680

1024X576

[SyrianBallaS]

I'm using Windows 8.1 Pro and it works fine, I don't know about Win10. I heard it's pretty buggy.

[Timelord]

[...] Am I the only one out here with Windows 10 Pro that is trying to play these games?
[...]

Yes.

On a more serious note, we might need to do some special configs or a special launcher for these newer Windows versions; unless updating Allegro actually works.

Edited by ZoriaRPG, 22 February 2016 - 10:19 PM.

[Mister Snooze]

Yes.

On a more serious note, we might need to do some special configs or a special launcher for these newer Windows versions; unless updating Allegro actually works.

I remember that happened when Windows 7 first came out. I guess it is to be expected,

 

As to Windows 10 Pro being buggy, I have not had that experience. ( re: Syrian''s response -I'm using Windows 8.1 Pro and it works fine, I don't know about Win10. I heard it's pretty buggy.)

Edited by Mister Snooze, 23 February 2016 - 12:04 PM.

[Mister Snooze]

The allegro log states

 

set gfx mode successful at -2 8bpp 1280 x 960 

 

(the numbers are one of many tries)

but I still have the same problem

a little more knowledge might be useful

[Orithan]

The Map button is bugged. While it is pressed (on DMaps that don't use the default spacebar map), Link can not move NorthWest or SouthEast. The corresponding keys (Up Left and Down Right respectively) still register as being pressed, but Link can not move in either of those two directions.

[Timelord]

The Map button is bugged. While it is pressed (on DMaps that don't use the default spacebar map), Link can not move NorthWest or SouthEast. The corresponding keys (Up Left and Down Right respectively) still register as being pressed, but Link can not move in either of those two directions.

 

Right, so, if I understand this:

 

If you have map display with space disabled, and the player holds down the map button, Link can move up, down, left, right, up+right, and down+left, but not up+left or down+right.

 

Please confirm that this is correct, and clarify:

Did you test this with both the keyboard, and controllers?

This only affects diagonal movement?

[Saffith]

That sort of thing has always been a keyboard issue in the past. Most keyboards can't handle certain key combinations, and something not working with one or two diagonal directions is very common. I'm not seeing the same thing myself, so I'm inclined to think that's the case here.
You say the keys still register, though? That's unusual. How are you determining that?

[Orithan]

Edit: The whole thing appears to be a keyboard issue and incompatibility with pressing the Space bar and UpLeft or DownRight keys at the same time. I mapped the Map key to somewhere different and those two directions are now working.

 

I haven't tested using a controller/joypad yet, but as far as I know it only affects Diagonal Walking. This was tested across multiple quests.

 

That sort of thing has always been a keyboard issue in the past. Most keyboards can't handle certain key combinations, and something not working with one or two diagonal directions is very common. I'm not seeing the same thing myself, so I'm inclined to think that's the case here.
You say the keys still register, though? That's unusual. How are you determining that?

 

It appears that the inputs don't register after all if the Traces were also placed in the Map key conditional. I put the trace checking thing outside the condition for if the map key is pressed by mistake. Now that the traces were inside the map key conditional, they weren't returning unless I pressed one of the directions and then the other one of the directions.

When outside of the Map key conditional, the traces were returning if I held the Map Key and UpLeft or DownRight.

Edited by Orithan, 08 March 2016 - 03:38 PM.