118 replies to this topic

[FireSeraphim]

Here is the contents to the Allegro.log file on my end.

Spoiler

 

ZQuest v2.50 Beta (Build 31)
Allocating tunes buffer (16.00k/16.00k)... OK
Allocating map buffer (435.63k/451.63k)... OK
Allocating combo buffer (5.98k/457.60k)... OK
Allocating string buffer (680.00k/1.11M)... OK
Allocating door combo buffer (159.50k/1.27M)... OK
Allocating dmap buffer (234.00k/1.50M)... OK
Allocating combo buffer (1.62M/3.11M)... OK
Allocating color data buffer (314.11k/3.42M)... OK
Allocating tile buffer (8.50M/11.92M)... OK
Allocating tile grab buffer (511.88k/20.42M)... OK
Allocating trash buffer (97.66k/20.51M)... OK
Allocating item buffer (31.12k/20.54M)... OK
Allocating weapon buffer (2.50k/20.54M)... OK
Allocating guy buffer (70.00k/20.61M)... OK
Allocating combo class buffer (33.30k/20.65M)... OK
Allocating combo undo buffer (1.62M/22.26M)... OK
Allocating new tile undo buffer (511.88k/22.76M)... OK
Resetting new tile buffer...OK
Allocating file path buffers (14.00k/22.77M)... OK
Initializing Allegro... OK
Loading data files:
Fonts.Dat...OK
ZQuest.Dat...OK
QST.Dat...OK
SFX.Dat...OK
OK
Initializing sound driver... OK
Overlays not supported

[Saffith]

That happens if you try to run ZQuest at a size too big to fit on the screen. Most likely it's set to use the 2.50 interface scaled up.

[Gleeok]

[] It's actually the size of the hardware surface overlay. ...but then why does DevCaps return with the DDCAPS_OVERLAY bit set to zero only for ZQuest?

[edit] @FireSeraphim: Are you setting the compat w/ win7; run as admin; etc. settings when opening Zquest? Maybe also running with ZCLauncher, or running in windowed mode? If none of these work can you copy over your ag.cfg from your 2.50.2 folder and try it again?

[Timelord]

Here is the contents to the Allegro.log file on my end.

Spoiler

 

ZQuest v2.50 Beta (Build 31)
Allocating tunes buffer (16.00k/16.00k)... OK
Allocating map buffer (435.63k/451.63k)... OK
Allocating combo buffer (5.98k/457.60k)... OK
Allocating string buffer (680.00k/1.11M)... OK
Allocating door combo buffer (159.50k/1.27M)... OK
Allocating dmap buffer (234.00k/1.50M)... OK
Allocating combo buffer (1.62M/3.11M)... OK
Allocating color data buffer (314.11k/3.42M)... OK
Allocating tile buffer (8.50M/11.92M)... OK
Allocating tile grab buffer (511.88k/20.42M)... OK
Allocating trash buffer (97.66k/20.51M)... OK
Allocating item buffer (31.12k/20.54M)... OK
Allocating weapon buffer (2.50k/20.54M)... OK
Allocating guy buffer (70.00k/20.61M)... OK
Allocating combo class buffer (33.30k/20.65M)... OK
Allocating combo undo buffer (1.62M/22.26M)... OK
Allocating new tile undo buffer (511.88k/22.76M)... OK
Resetting new tile buffer...OK
Allocating file path buffers (14.00k/22.77M)... OK
Initializing Allegro... OK
Loading data files:
Fonts.Dat...OK
ZQuest.Dat...OK
QST.Dat...OK
SFX.Dat...OK
OK
Initializing sound driver... OK
Overlays not supported

 

 

Oops. I need to see your ag.cfg file too. What are your display resolution settings?

 

That happens if you try to run ZQuest at a size too big to fit on the screen. Most likely it's set to use the 2.50 interface scaled up.

 

I suppose that is one possible reason.

 

It's a bug in allegro DX code. It's actually the size of the hardware surface overlay. ...but then why does DevCaps return with that bit set to zero only for ZQuest?

Well, you wanted to upgrade to allegro 4.4 ZoriaRPG... Be careful what you wish for, you might just get it.


[edit] Are you setting the compat w/ win7; run as admin; etc. settings when opening Zquest? Maybe also running with ZCLauncher, or running in windowed mode?

 

4.4 is a critical update, and it should have been done seven years ago. Running libs that are years out of date makes it bloody impossible to fix most of the issues that we have. None of these programmes should default to opening in fullscreen. If he used my ag.cfg file, then it would open as 'large, windowed, direct updating on'. There might be some missing settings that should be in there.

 

There is a reason this is a Beta release and not a Gamma release. )

 

The default ag.cfg file probably needs clean-up. This is the one that is in the ZIP:

 

[zquest]
mouse_scroll = 0
invalid_static = 0
tile_protection = 1
showinfo = 0
show_grid = 0
grid_color = 15
snapshot_format = 3
save_paths = 1
cycle_on = 1
vsync = 1
showfps = 0
combo_brush = 0
brush_position = 0
float_brush = 0
open_last_quest = 0
show_misalignments = 0
scale = 1
scale_large = 1
fullscreen = 0
showffscripts = 1
showsquares = 1
animation_on = 1
auto_backup_retention = 2
auto_save_interval = 6
auto_save_retention = 2
uncompressed_auto_saves = 1
overwrite_prevention = 0
import_map_bias = 0
keyboard_repeat_delay = 300
keyboard_repeat_rate = 80
zqmusic_bufsz = 64
small = 0
rulesetdialog = 1
enable_tooltips = 1
layer_mask = 65535
normal_duplicate_action = 2
horizontal_duplicate_action = 0
vertical_duplicate_action = 0
both_duplicate_action = 0
leech_update = 500
leech_update_tiles = 1
only_check_new_tiles_for_duplicates = 0
gui_colorset = 0
command01 = 0
command02 = 0
command03 = 0
command04 = 0
command05 = 0
command06 = 0
command07 = 0
command08 = 0
fps = 60
frameskip = 0
force_exit = 0
zq_win_proc_fix = 0
beta_warning = t~z#~~F~

[graphics]
disable_direct_updating = 1

[zeldadx]
joystick_index = 0
js_stick_1_x_stick = 0
js_stick_1_x_axis = 0
js_stick_1_x_offset = 0
js_stick_1_y_stick = 0
js_stick_1_y_axis = 1
js_stick_1_y_offset = 0
js_stick_2_x_stick = 1
js_stick_2_x_axis = 0
js_stick_2_x_offset = 0
js_stick_2_y_stick = 1
js_stick_2_y_axis = 1
js_stick_2_y_offset = 0
analog_movement = 0
key_a = 24
key_b = 26
key_s = 67
key_l = 1
key_r = 19
key_p = 75
key_ex1 = 17
key_ex2 = 23
key_ex3 = 5
key_ex4 = 18
key_up = 84
key_down = 85
key_left = 82
key_right = 83
btn_a = 2
btn_b = 1
btn_s = 10
btn_m = 9
btn_l = 5
btn_r = 6
btn_p = 12
btn_ex1 = 7
btn_ex2 = 8
btn_ex3 = 4
btn_ex4 = 3
btn_up = 13
btn_down = 14
btn_left = 15
btn_right = 16
digi = 248
midi = 255
sfx = 248
emusic = 248
pan = 1
zcmusic_bufsz = 64
volkeys = 0
vsync = 0
throttlefps = 1
translayers = 1
snapshot_format = 3
name_entry_mode = 0
showfps = 0
fastquit = 0
clicktofreeze = 1
title = 2
scanlines = 0
load_last = 12
ss_enable = 1
ss_after = 14
ss_speed = 2
ss_density = 3
heart_beep = 1
gui_colorset = 0
use_sfx_dat = 0
frame_rest_suggest = 1
force_exit = 0
debug_console = 0
zc_win_proc_fix = 0
use_dwm_flush = 0
midi_patch_fix = 0
save_indicator = 0

[zelda-graphics]
resx = 640
resy = 480
fullscreen = 0
fps = 60
native = 1

[zquest-graphics]
resx = 800
resy = 600
fullscreen = 0
fps = 60
native = 1

[zelda-sfx]
volume = 248
pan = 1

[romview-graphics]
resx = 320
resy = 240
fullscreen = 0
native = 1
fps = 60
 

 

If anyone wants to tailor a config file that should go in the dist, I'll change it out.

 

Once I dig out one of my iBuffalo controllers, I will also check on that.

Edited by ZoriaRPG, 16 July 2017 - 07:41 PM.

[Saffith]

Why include any ag.cfg at all? We never did before.

[Nightmare]

Revenge 2, Demo 1.84, and U3Q work..  I haven't got to total detail, still have to get further into them to test all tech.

 

New Quest V 1.84 is NOT working, and there's not much mention of it in allegro,log.  All quests pre-1.84 official release seem not to work.

 

-James

Edited by Nightmare, 16 July 2017 - 08:41 PM.

[DarkDragon]

Why include any ag.cfg at all? We never did before.

 

Agreed, assuming that the default is to start windowed (fullscreen is a huge gamble on modern OSes)

[FireSeraphim]

Here's my ag.config for 2.53

Spoiler

[zeldadx]
joystick_index = 0
js_stick_1_x_stick = 0
js_stick_1_x_axis = 0
js_stick_1_x_offset = 0
js_stick_1_y_stick = 0
js_stick_1_y_axis = 1
js_stick_1_y_offset = 0
js_stick_2_x_stick = 1
js_stick_2_x_axis = 0
js_stick_2_x_offset = 0
js_stick_2_y_stick = 1
js_stick_2_y_axis = 1
js_stick_2_y_offset = 0
analog_movement = 1
key_a = 119
key_b = 117
key_s = 67
key_l = 26
key_r = 24
key_p = 75
key_ex1 = 17
key_ex2 = 23
key_ex3 = 1
key_ex4 = 19
key_up = 84
key_down = 85
key_left = 82
key_right = 83
btn_a = 2
btn_b = 4
btn_s = 8
btn_m = 9
btn_l = 5
btn_r = 6
btn_p = 8
btn_ex1 = 3
btn_ex2 = 1
btn_ex3 = 0
btn_ex4 = 0
btn_up = 13
btn_down = 14
btn_left = 15
btn_right = 16
digi = 248
midi = 255
sfx = 248
emusic = 248
pan = 1
zcmusic_bufsz = 64
volkeys = 0
vsync = 0
throttlefps = 1
translayers = 1
snapshot_format = 3
name_entry_mode = 0
showfps = 0
fastquit = 0
clicktofreeze = 1
title = 2
resx = 640
resy = 480
scanlines = 0
load_last = 1
win_qst_dir = C:\Program Files 2\Zelda Classic\ZC 2.53\
ss_enable = 1
ss_after = 14
ss_speed = 2
ss_density = 3
heart_beep = 1
gui_colorset = 0
use_sfx_dat = 1
fullscreen = 1
doublebuffer = 1
triplebuffer = 0
color_depth = 8
frame_rest_suggest = 1
force_exit = 0
debug_console = 0
zc_win_proc_fix = 0
use_dwm_flush = 0
midi_patch_fix = 0
save_indicator = 0

[graphics]
disable_direct_updating = 1

[DarkDragon]

It doesn't look like you have a [zquest] section, I guess because ZQuest has never successfully loaded up and saved its settings...

 

Did you try launching ZQuest in windowed mode at minimum resolution (320 x 240) in the launcher? (And if that doesn't work, in fullscreen mode)?

[Timelord]

The launcher settings for this, are:

 

Interface: Classic

Scale: 1x

Revenge 2, Demo 1.84, and U3Q work..  I haven't got to total detail, still have to get further into them to test all tech.

 

New Quest V 1.84 is NOT working, and there's not much mention of it in allegro,log.  All quests pre-1.84 official release seem not to work.

 

-James

 

Did 'New Quest V184' work in 2.50.2?

[Nightmare]

Zoria, critical bug:

 

I was playing Revenge 2, and when I went for the Fire Boomerang, picked up the Mushroom, and the guy came back when I left the cave.

 

I imagine this is pretty bad (compatibility with 1.90)

 

-James

[FireSeraphim]

Another bug I discovered: The ALTTP Styled room lighting used in Quest 744 is still glitched in 2.53

[Timelord]

Another bug I discovered: The ALTTP Styled room lighting used in Quest 744 is still glitched in 2.53

Screenshot, please.

Zoria, critical bug:
 
I was playing Revenge 2, and when I went for the Fire Boomerang, picked up the Mushroom, and the guy came back when I left the cave.
 
I imagine this is pretty bad (compatibility with 1.90)
 
-James

James, please check these two issues in 2.50.2. I need to know if these are issues that we never knew about before, or if they are new, introduced in 2.53. I suspect this is a quest rule that is not being set, or something odd. I'll need to check the quests.

Are you testing this stuff with, or without cheats?

[Avaro]

You know what's happening Zoria. xD It's the bitmap offset fix.

[Timelord]

You know what's happening Zoria. xD It's the bitmap offset fix.

I thought so, but the post was not entirely clear if it is a new issue. I'll go in and re-apply the fix when I have some time.

I'll add both default behaviour for old quests, plus a QR so that quests saved in 2.53 do not need to reconfigure their scripts.

Edited by ZoriaRPG, 17 July 2017 - 10:30 AM.