(GZDoom)(Solved) Enemy, weapon, and pickup sprites invisible

[shotgunfacelift]

Hello,
When running Doom or Doom II in GZDoom, the enemy, weapon, and pickup sprites are not appearing. I have attached a link for a video that shows the issue. Does anyone know how to fix this?
Also, the video quality is complete garbage, I know that. I didn't feel like waiting for a long export. It rendered kinda wrong, too.
https://youtu.be/fQBIycwlDYM

[Caligari87]

Gonna need a lot more info:

- GZDoom version (don't just say "latest")? Hardware or Software renderer? Graphics card? Operating System? Are your drivers up-to-date?

- Mods loaded? (including skins folder or autoload) Did you modify your IWADs? Please post your startup log.

- When did it stop working or when was the last time it worked? What did you last do?

[shotgunfacelift]

Gonna need a lot more info:

- GZDoom version (don't just say "latest")? Hardware or Software renderer? Graphics card? Operating System? Are your drivers up-to-date?

- Mods loaded? (including skins folder or autoload) Did you modify your IWADs? Please post your startup log.

- When did it stop working or when was the last time it worked? What did you last do?

Thanks for the response!
-Tested on 2 versions - 2.2.0 and 3.1.0/Software renderer/Radeon HD 6770M/Windows 7 Professional/Yes, all drivers are up to date
-No mods loaded/IWAD not modified/Check below
-The last time it worked was on my old Dell laptop with Intel graphics. I just tried it for the first time on my new laptop. The last thing I did was copy the files from my old computer to the new one.
Startup log:

---

Code: Select all

Log started: Fri Aug 25 12:37:03 2017

M_LoadDefaults: Load system defaults.
Using program directory for storage
W_Init: Init WADfiles.
 adding C:/(doom directory)/gzdoom.pk3, 620 lumps
 adding ./doom.wad, 2306 lumps
I_Init: Setting up machine state.
CPU speed: 2195 MHz
CPU Vendor ID: GenuineIntel
  Name: Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz
  Family 6, Model 42, Stepping 7
  Features: MMX SSE SSE2 SSE3 SSSE3 SSE4.1 SSE4.2
I_InitSound: Initializing FMOD
FMOD Sound System, copyright © Firelight Technologies Pty, Ltd., 1994-2009.
Loaded FMOD version 4.44.61
V_Init: allocate screen.
S_Init: Setting up sound.
ST_Init: Init startup screen.
Checking cmd-line parameters...
S_InitData: Load sound definitions.
G_ParseMapInfo: Load map definitions.
Texman.Init: Init texture manager.
ParseTeamInfo: Load team definitions.
LoadActors: Load actor definitions.
DECORATE parsing took 29.27 ms
R_Init: Init Doom refresh subsystem.
DecalLibrary: Load decals.
M_Init: Init menus.
P_Init: Init Playloop state.
ParseSBarInfo: Loading default status bar definition.
ParseSBarInfo: Loading custom status bar definition.
D_CheckNetGame: Checking network game status.
player 1 of 1 (1 nodes)
I_InitInput
I_StartupMouse
I_StartupKeyboard
I_StartupXInput
I_StartupRawPS2
I_StartupDirectInputJoystick
GL_VENDOR: ATI Technologies Inc.
GL_RENDERER: Radeon (TM) HD 6770M
GL_VERSION: 4.1.11013 Core Profile Context (Core profile)
GL_SHADING_LANGUAGE_VERSION: 4.10
GL_EXTENSIONS: GL_AMDX_debug_output GL_AMDX_vertex_shader_tessellator GL_AMD_conservative_depth GL_AMD_debug_output GL_AMD_depth_clamp_separate GL_AMD_draw_buffers_blend GL_AMD_multi_draw_indirect GL_AMD_name_gen_delete GL_AMD_performance_monitor GL_AMD_pinned_memory GL_AMD_sample_positions GL_AMD_seamless_cubemap_per_texture GL_AMD_shader_stencil_export GL_AMD_shader_trace GL_AMD_texture_cube_map_array GL_AMD_texture_texture4 GL_AMD_transform_feedback3_lines_triangles GL_AMD_vertex_shader_tessellator GL_ARB_ES2_compatibility GL_ARB_blend_func_extended GL_ARB_color_buffer_float GL_ARB_compatibility GL_ARB_copy_buffer GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_draw_buffers GL_ARB_draw_buffers_blend GL_ARB_draw_elements_base_vertex GL_ARB_draw_indirect GL_ARB_draw_instanced GL_ARB_explicit_attrib_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4 GL_ARB_get_program_binary GL_ARB_gpu_shader5 GL_ARB_gpu_shader_fp64 GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_instanced_arrays GL_ARB_map_buffer_range GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_pixel_buffer_object GL_ARB_point_sprite GL_ARB_provoking_vertex GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_separate_shader_objects GL_ARB_shader_bit_encoding GL_ARB_shader_objects GL_ARB_shader_precision GL_ARB_shader_stencil_export GL_ARB_shader_subroutine GL_ARB_shader_texture_lod GL_ARB_shadow GL_ARB_shadow_ambient GL_ARB_sync GL_ARB_tessellation_shader GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_compression GL_ARB_texture_compression_bptc GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_cube_map_array GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_gather GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_lod GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_rgb10_a2ui GL_ARB_texture_snorm GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_attrib_64bit GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_ATI_draw_buffers GL_ATI_envmap_bumpmap GL_ATI_fragment_shader GL_ATI_meminfo GL_ATI_separate_stencil GL_ATI_texture_compression_3dc GL_ATI_texture_env_combine3 GL_ATI_texture_float GL_ATI_texture_mirror_once GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_copy_buffer GL_EXT_copy_texture GL_EXT_direct_state_access GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_draw_range_elements GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_provoking_vertex GL_EXT_shader_image_load_store GL_EXT_shadow_funcs GL_EXT_stencil_wrap GL_EXT_subtexture GL_EXT_texgen_reflection GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_buffer_object GL_EXT_texture_compression_bptc GL_EXT_texture_compression_latc GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_add GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_rectangle GL_EXT_texture_sRGB GL_EXT_texture_shared_exponent GL_EXT_texture_snorm GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_transform_feedback GL_EXT_vertex_array_bgra GL_EXT_vertex_attrib_64bit GL_IBM_texture_mirrored_repeat GL_KTX_buffer_region GL_NV_blend_square GL_NV_conditional_render GL_NV_copy_depth_to_color GL_NV_explicit_multisample GL_NV_float_buffer GL_NV_half_float GL_NV_texgen_reflection GL_NV_texture_barrier GL_SGIS_generate_mipmap GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod GL_SUN_multi_draw_arrays GL_WIN_swap_hint WGL_EXT_swap_control
Max. texture size: 16384
Max. texture units: 16
Max. varying: 128
Max. uniform block size: 65536
Uniform block alignment: 256
Resolution: 1920 x 1080

<------------------------------->

e1m1 - Hangar

[Caligari87]

Just as a quick troubleshoot, in case this is related to a configuration setting: Move your "gzdoom-username.ini" file somewhere else, and run the game again. GZDoom should generate a new "default" configuration, see if the problem still occurs then. If it's fixed, that means something in your old config was causing the problem. At that point I'd recommend re-doing your key bindings and stuff on the new config so the problem setting doesn't get re-introduced.

[shotgunfacelift]

Move your "gzdoom-username.ini" file somewhere else, and run the game again.

It created a new default config, but the sprites are still missing. Doom II has the same problem.

[phantombeta]

Try running it in OpenGL, just to be sure. if it doesn't show the sprites either, then it's either a problem with your copy of the IWADs, or your copy of GZDoom.
(In that log, GZDoom says your GPU supports OpenGL 4.1 Core Profile. That means it can definitely run GZDoom's OpenGL renderer. Should run with a playable framerate, too, I think.)

EDIT: Wait, that video doesn't seem to have y-shearing... Did you enable the poly renderer? If not, then you're using hardware rendering, not software. (I'm saying this because if the poly renderer isn't enabled, then software rendering is done with the old Doom/Carmack renderer, which has y-shearing when looking up/down and can't look straight up or down)
You also say you tested it in 2.2.0. Did you enable software rendering with vid_renderer 0 in that?

[shotgunfacelift]

Try running it in OpenGL, just to be sure. if it doesn't show the sprites either, then it's either a problem with your copy of the IWADs, or your copy of GZDoom.
(In that log, GZDoom says your GPU supports OpenGL 4.1 Core Profile. That means it can definitely run GZDoom's OpenGL renderer. Should run with a playable framerate, too, I think.)

EDIT: Wait, that video doesn't seem to have y-shearing... Did you enable the poly renderer? If not, then you're using hardware rendering, not software. (I'm saying this because if the poly renderer isn't enabled, then software rendering is done with the old Doom/Carmack renderer, which has y-shearing when looking up/down and can't look straight up or down)
You also say you tested it in 2.2.0. Did you enable software rendering with vid_renderer 0 in that?

2.2.0 is the original one I tested it with, it's the version in the video I posted. 3.1.0 is the current latest version, I just downloaded it today to see if it would fix the issue.
In 3.1.0, there is an option to switch from OpenGL (Accelerated) to the hardware renderer, and that seemed to fix it. Vid_renderer 0 in 2.2.0 seems to fix it as well. This seems to be an OpenGL issue, so is there any way I can get it working without having to use the hardware renderer?

Edit: Also, when using mods on the hardware renderer, this happened:

[phantombeta]

In 3.1.0, there is an option to switch from OpenGL (Accelerated) to the hardware renderer, and that seemed to fix it. Vid_renderer 0 in 2.2.0 seems to fix it as well. This seems to be an OpenGL issue, so is there any way I can get it working without having to use the hardware renderer?

Uhhh... This sentence doesn't make much sense. The options are "Hardware (OpenGL)" and "Software (Doom)". The former is hardware rendering with OpenGL, and the latter is software rendering using the CPU.
Anyway. Make 100% sure your GPU drivers are up to date. Since you say this computer is new, it will probably have outdated drivers.

Also, get it to happen again and click "Save Report to Disk...". After that, post the report here. That screenshot is useless, as it gives no useful information.

[shotgunfacelift]

Uhhh... This sentence doesn't make much sense. The options are "Hardware (OpenGL)" and "Software (Doom)". The former is hardware rendering with OpenGL, and the latter is software rendering using the CPU.
Anyway. Make 100% sure your GPU drivers are up to date. Since you say this computer is new, it will probably have outdated drivers.

Also, get it to happen again and click "Save Report to Disk...". After that, post the report here. That screenshot is useless, as it gives no useful information.

Sorry that my sentence didn't make sense, I meant software renderer. When I say the laptop is "new" I mean it's from 2012 and I bought it used. I just installed the latest drivers onto a fresh install of Windows. I know that the screenshot is useless as is, I wanted to show that using the software renderer produces issues with some mods. I looked at the crash report, and it seems to be an issue on the mod's end, as lots of the different ammo/weapon types seemed to be causing errors. My point was that on my old computer, I never got these issues when using OpenGL.

[phantombeta]

Ah. Well, there's something seriously wrong here. It shouldn't be doing this with hardware rendering. Sounds like there's something weird going on.
Hmm... Just to be sure, go to the "Display Options" menu (Options>Display Options) and change the "Notebook switchable GPU" option. (It's in the bottom of the menu)
(Even if your laptop doesn't have a switchable GPU, I'd say it's better to check just in case.)

[shotgunfacelift]

Ah. Well, there's something seriously wrong here. It shouldn't be doing this with hardware rendering. Sounds like there's something weird going on.
Hmm... Just to be sure, go to the "Display Options" menu (Options>Display Options) and change the "Notebook switchable GPU" option. (It's in the bottom of the menu)
(Even if your laptop doesn't have a switchable GPU, I'd say it's better to check just in case.)

That didn't seem to fix it on 3.1.0. Is there any fix specifically for 2.2.0? I'd prefer to use that version.

[phantombeta]

Why would you prefer to use 2.2.0?
That's VERY outdated. Quite a few mods are using new features that were only introduced in or after 2.3.0. There's also no real reason to use it, really.

Also, I'm not even sure what your problem is, really. There's no way it could be a bug in GZDoom, it seems like something's wrong with your GPU. (Specially since it happens in 2.2.0 too. It'd have been fixed before if it were a bug in GZDoom)

[Graf Zahl]

Of course there is no fix for 2.2.0. It was superseded by 2.3, which was superseded by 2.4 which again was superseded by 3.1.
This isn't Windows where 4 major versions get maintained in parallel. If a bug gets fixed, it will get fixed for the latest one, not some older release.

[shotgunfacelift]

Why would you prefer to use 2.2.0? That's very outdated. Quite a few mods are using new features that were only introduced in or after 2.3.0. There's also no real reason to use it, really.

I noticed that in 3.1.0 the audio sounds different, and the menu text doesn't highlight when the mouse is over it. The audio issue seems to be because there is no "sound system" option in the MIDI device list on 3.1.0.

[shotgunfacelift]

Of course there is no fix for 2.2.0. It was superseded by 2.3, which was superseded by 2.4 which again was superseded by 3.1.
This isn't Windows where 4 major versions get maintained in parallel. If a bug gets fixed, it will get fixed for the latest one, not some older release.

This is a bug that I've encountered only on this specific laptop. And so far, none of the fixes for 3.1.0 on the OpenGL renderer seem to work for me.