What’s Happening With UZDoom?

[Enjay]

Just some random from myself about UZDoom: Some time ago, my buddy attempted to try UZDoom in action and he found it being very buggy and glitchy, and generally messy. I don't know details by myself since I mostly watch the GZDoom itself that I directly contribute sometimes.

I'd be interested to know what "some time ago" means. UZDoom hasn't even had an official release out for a month yet. Even the concept of UZDoom is only about 2 months old.

For my part, UZDoom 4.14.3 has been running very nicely, even with some very complex mods. It is, after all, mostly just GZDoom 4.14.2 with some bug fixes and a few additional tweaks.

Even the in-progress 5.0 builds haven't really given me any serious issues. They too can run very complex mods very nicely on my system.

Neither have come close to anything that I would describe as "very buggy and glitchy, and generally messy."

However, if your friend is finding bugs with it, it would be really useful if they reported them on the UZDoom GitHub page:
https://github.com/UZDoom/UZDoom/issues

[Wohlstand]

"some time ago"

I checked the conversation, there was some talks related to UZDoom around 7'th of December, and my buddy's conclusion at 13'th of December, the primary blame that code base of UZDoom uses several things especially music libraries from the old GZDoom (lack of recent updates related to MIDI synthesizers support that I contributed to ZMusic), and various bugs, and one of these bugs is the mouse controlling that is not properly calibrated. And ye, according to the video showcase he did in 13'th of December, it was UZDoom 4.14.3.

His explicit expression about the mouse bug (roughly translated from Russian):

A cool bug yeah I rated it

In such way it consumes sources of "Rusty legacy"
and now it's uniquely GZDoom 100% only GZDoom

[Enjay]

Has he reported these problems? If they still exist, it would be useful if your friend did so. If the devs don't know about the problems, they can't fix them.
There were some people reporting problems configuring things relating to sound, but it was more to do ini settings and file locations as I recall. Things did get sorted for them eventually without the need for changes to UZDoom itself. If there is a bigger issue (and it sounds like you might well be the person to know the details, if they relate to your contributions) then it would be valuable if they were reported.

Could the mouse thing be this one? https://github.com/UZDoom/UZDoom/issues/171

[Wohlstand]

I guess he didn't, he just tested it locally to build an opinion on the thing. The mouse problem he shown: just he starts playing Doom 2, and he used some mod with the fire gun, and in begining of Doom 2 game, he attempted to move mouse, and camera just crazily moves around very fast.

[Enjay]

Curious. I've not experienced that at all. If it was a common issue, someone else would have mentioned it by now too.
I wonder if it's related to the mod?
Again, if they want to, it would be useful if it was reported (complete with details about the mod and mouse/mouse drivers).

Is the video publicly available?

[Wohlstand]

Curious. I've not experienced that at all. If it was a common issue, someone else would have mentioned it by now too.
I wonder if it's related to the mod?
Again, if they want to, it would be useful if it was reported (complete with details about the mod and mouse/mouse drivers).

Is the video publicly available?

He sent a video, but first I'll ask for permission, and if grant approved, I'll share.

[Wohlstand]

Okay, here are mods that he used:
Link removed.
My buddy tells that It's need to unpack all the content of archive, mix it with the application and just run the application itself.

Then, type in console the "Give all" and hit the "6" two times, then it should appear a fire gun from the "Legacy of Rust" game.

The video of the bug:
https://disk.yandex.ru/i/Xf35DeRx7SBWeA

[R4L]

Okay, here are mods that he used:
Link removed.
My buddy tells that It's need to unpack all the content of archive, mix it with the application and just run the application itself.

Then, type in console the "Give all" and hit the "6" two times, then it should appear a fire gun from the "Legacy of Rust" game.

The video of the bug:
https://disk.yandex.ru/i/Xf35DeRx7SBWeA

@Wohlstand I removed your link because it contains Legacy of Rust and other IWADs. You cannot legally distribute these.

[Wohlstand]

@Wohlstand I removed your link because it contains Legacy of Rust and other IWADs. You cannot legally distribute these.

I'll ask my buddy to remove these iWADs and keep only mods. With a reference that these iWADs are required to be added too.

[Wohlstand]

Okay, now it's CLEAR archive (all illegal WADs removed).

https://disk.yandex.ru/d/Ozpz_ZPtiI-c2Q

I hope it's should be enough now.

So, the list of required IWADs to append with this:
- DOOM2.WAD from Doom2
- Legacy of Rust'ss WADs:
- id1.wad
- id1-res.wad
- id1-weap.wad

@R4L, let me know if any files also should be removed, I will remove immediately.

[Boondorl]

I'm sorry but I can't seem to be able to replicate this issue. I used id1-res and id1-weap with Doom2 like the original file list included (including id1 boots me into Legacy of Rust) in 4.14.3 and can't seem to get this to happen, regardless of whether autoaim is on or off. I suspect an issue this serious would've been reported a long time ago as the weapons have been in the engine since at least 4.14.2 and 4.14.3 was in RC for ~3 weeks and released for longer, so I'm not sure why this seems to only be happening to specific individuals. If anyone else could verify this happens that would be great (and preferably reported on the GitHub repo).

[Jay0]

also 4.14.3 does not have any changes from 4.14.2 with regards to zmusic or mouse movement handling, so it's really odd that 4.14.2 is fine for him compared to 4.14.3

[Enjay]

The video of the bug:
https://disk.yandex.ru/i/Xf35DeRx7SBWeA

I'm afraid I can't replicate that at all either. When I fire the incinerator, it behaves exactly as expected.

[Wohlstand]

The video of the bug:
https://disk.yandex.ru/i/Xf35DeRx7SBWeA

I'm afraid I can't replicate that at all either. When I fire the incinerator, it behaves exactly as expected.

Possibly that means it's exclusively Windows specific bug then. I am on Linux by myself, but that buddy uses Windows 10

[Enjay]

I'm on Windows 10 too - and I suspect the majority of users will be on Win10 or 11.
So, it could be Windows specific, but windows combined with something about your friend's mouse/drivers/setup.

I don't suppose your buddy has tried it again has he? Possibly with a totally clean ini (if he previously migrated his GZDoom one that is).