[can't fix][0.9.5] Texture error in Legacy-specific WAD

Bugs that have been resolved.

Moderator: Graf Zahl

Locked
User avatar
MartinHowe
Posts: 154
Joined: Tue Aug 30, 2005 22:07
Location: East Suffolk (UK)

[can't fix][0.9.5] Texture error in Legacy-specific WAD

Post by MartinHowe »

Playing Aphrodite.wad with Legacy works fine, but with GZDoom 0.9.5 the result is:
Log started: Mon Sep 12 11:44:17 2005

adding gzdoom.wad (140 lumps)
adding ./doom2.wad (2919 lumps)
adding aphrodit.wad (22 lumps)
CPU Speed: 2595.571662 MHz
CPU Vendor ID: GenuineIntel
Name: Intel(R) Pentium(R) 4 CPU 2.60GHz 4 CPU 2.60GHz
Family 15, Model 2, Stepping 7
Features: MMX SSE SSE2
I_InitSound: Initializing FMOD
Setting DirectSound output succeeded
Setting driver 0 succeeded
Initialization succeeded
GL_VENDOR: ATI Technologies Inc.
GL_RENDERER: MOBILITY RADEON 7500 DDR x86/SSE2
GL_VERSION: 1.3.1010 WinXP Release
GL_EXTENSIONS: GL_ARB_multitexture GL_EXT_texture_env_add GL_EXT_compiled_vertex_array GL_S3_s3tc GL_ARB_occlusion_query GL_ARB_texture_border_clamp GL_ARB_texture_compression GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_mirrored_repeat GL_ARB_transpose_matrix GL_ARB_vertex_blend GL_ARB_vertex_buffer_object GL_ARB_window_pos GL_ATI_envmap_bumpmap GL_ATI_map_object_buffer GL_ATI_texture_env_combine3 GL_ATI_texture_mirror_once GL_ATI_vertex_array_object GL_ATI_vertex_streams GL_ATIX_texture_env_combine3 GL_ATIX_texture_env_route GL_EXT_abgr GL_EXT_bgra GL_EXT_clip_volume_hint GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_multi_draw_arrays GL_EXT_packed_pixels GL_EXT_point_parameters GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_specular_color GL_EXT_stencil_wrap GL_EXT_texgen_reflection GL_EXT_texture3D GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_rectangle GL_EXT_vertex_array GL_HP_occlusion_test GL_NV_blend_square GL_NV_occlusion_query GL_NV_texgen_reflection GL_SGI_color_matrix GL_SGIS_generate_mipmap GL_SGIS_multitexture GL_SGIS_texture_border_clamp GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod GL_SUN_multi_draw_arrays GL_WIN_swap_hint WGL_EXT_extensions_string WGL_EXT_swap_control
Resolution: 1280 x 1024
Init DOOM refresh subsystem.

**** DIED WITH FATAL ERROR:
Bad texture directory
User avatar
Graf Zahl
GZDoom Developer
GZDoom Developer
Posts: 7148
Joined: Wed Jul 20, 2005 9:48
Location: Germany
Contact:

Post by Graf Zahl »

The WAD is buggy and the error is justified. But I have no idea why it has to be fatal. Only Randy knows.
User avatar
MartinHowe
Posts: 154
Joined: Tue Aug 30, 2005 22:07
Location: East Suffolk (UK)

Post by MartinHowe »

So presumably, anyone playing it all the way through with Legacy will eventually encounter some sort of error along the way. I assume it's fatal in order to prevent having to handle the discovery of an error later on, but as stated, only Randy knows for sure.

What is actually wrong with that texture list anyway?
User avatar
Graf Zahl
GZDoom Developer
GZDoom Developer
Posts: 7148
Joined: Wed Jul 20, 2005 9:48
Location: Germany
Contact:

Post by Graf Zahl »

At least the first 2 textures in it are broken. The error says that some texture points to data beyond the end of the TEXTURE1 lump.
User avatar
Graf Zahl
GZDoom Developer
GZDoom Developer
Posts: 7148
Joined: Wed Jul 20, 2005 9:48
Location: Germany
Contact:

Post by Graf Zahl »

Unfortunately this problem is unfixable. ZDoom can't determine whether this TEXTURE1 lump is in Doom or Strife format due to the empty textures.

ZDoom prohibits empty texture definitions for a good reason.
User avatar
MartinHowe
Posts: 154
Joined: Tue Aug 30, 2005 22:07
Location: East Suffolk (UK)

Post by MartinHowe »

Hmm. And Legacy loads it as well. Another reason to ditch it :)

Thanks!
Locked

Return to “Closed Bugs”