[0.8.0_beta-152-g5b6aa372e] Shadow Warrior Bugs

Forum rules
Please don't bump threads here if you have a problem - it will often be forgotten about if you do. Instead, make a new thread here.

Post a reply

Smilies
:D :) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :geek: :ugeek: :!: :?: :idea: :arrow: :| :mrgreen: :3: :wub: >:( :blergh:
View more smilies
BBCode is OFF
Smilies are ON
Topic review
   

Expand view Topic review: [0.8.0_beta-152-g5b6aa372e] Shadow Warrior Bugs

Re: [0.8.0_beta-152-g5b6aa372e] Shadow Warrior Bugs

by Graf Zahl » Sun Feb 28, 2021 10:52 am

This wasn't Build, this was just some unexpected use of interpolation variables.
The ultimate cause of the error was that the old variable was written out to a save game while the new one wasn't, because none of the other games needed it.

Re: [0.8.0_beta-152-g5b6aa372e] Shadow Warrior Bugs

by Xtyfe » Sun Feb 28, 2021 10:44 am

Graf Zahl wrote:That's the same effect from the other savegame for the first map of the original game.
From looking at the code I have a suspicion - the door movement code uses the old interpolation coordinates inappropriately - but that stuff got refactored recently so this may have some side effects.

It's perfectly reproducable if you save while the door is open. Once the game is reloaded it starts to get mad.
Will be a bit tricky to fix because the change is rather extensive.
Was it really that simple to break? Of course it was! This is build I guess. :roll:
Glad it wasn't too complicated to track down.

Re: [0.8.0_beta-152-g5b6aa372e] Shadow Warrior Bugs

by Graf Zahl » Sun Feb 28, 2021 5:39 am

Fixed the door bug so this can be closed now.

Re: [0.8.0_beta-152-g5b6aa372e] Shadow Warrior Bugs

by Graf Zahl » Sun Feb 28, 2021 4:41 am

That's the same effect from the other savegame for the first map of the original game.
From looking at the code I have a suspicion - the door movement code uses the old interpolation coordinates inappropriately - but that stuff got refactored recently so this may have some side effects.

It's perfectly reproducable if you save while the door is open. Once the game is reloaded it starts to get mad.
Will be a bit tricky to fix because the change is rather extensive.

Re: [0.8.0_beta-152-g5b6aa372e] Shadow Warrior Bugs

by markanini » Sun Feb 28, 2021 3:24 am

Forgot to log in...

Re: [0.8.0_beta-152-g5b6aa372e] Shadow Warrior Bugs

by Guest » Sat Feb 27, 2021 3:26 pm

Bugs being solved by a fresh install sounds familiar.
@Xtyfe can you tell me a specific spot and steps leading to repeated triggers? Assuming I have a bugged install I will try to reproduce it.

And I think I might have a bugged install because In Twin Dragons first map doors are opening and closing multiple times after being opened for the first time. I'm not 100% sure but I don't remember that happening in v0.7. On a different note I tried a user map recently which had a repeating gong sound. I assumed a map error but now I wonder if it's related to this report.
In the mean time here's a save from the TD map1 gong room with the suspicious doors: https://filebin.net/hl5ml2t8qom24gxl

Re: [0.8.0_beta-152-g5b6aa372e] Shadow Warrior Bugs

by Graf Zahl » Fri Feb 26, 2021 1:59 pm

Xtyfe wrote: The duct tape holding the build engine together seems to be peeling off a bit for me :D
That's why "Raze" isn't called "Build"... :twisted:

Re: [0.8.0_beta-152-g5b6aa372e] Shadow Warrior Bugs

by Xtyfe » Fri Feb 26, 2021 1:32 pm

That is a really good question, but I don't exactly have an answer. From my perspective, I simply started playing Twin Dragon and Wanton Destruction in Raze and these things just started happening consistently.
I don't know if it's my play environment, the choices I made during play, my inputs from my mouse and keyboard. What's weirder for me is the fact that I somehow made it stop today while I was trying to get it to trigger for a saved game. I don't know how I made that happen either.

The duct tape holding the build engine together seems to be peeling off a bit for me :D

Re: [0.8.0_beta-152-g5b6aa372e] Shadow Warrior Bugs

by Graf Zahl » Fri Feb 26, 2021 1:09 pm

Whyt did you do to trigger this?

Re: [0.8.0_beta-152-g5b6aa372e] Shadow Warrior Bugs

by Xtyfe » Fri Feb 26, 2021 12:26 pm

Scratch that, I do have an old save that still produces the issue. This is the first level of regular Shadow Warrior
Attachments
save0004.dsave
(128.85 KiB) Downloaded 29 times

Re: [0.8.0_beta-152-g5b6aa372e] Shadow Warrior Bugs

by Xtyfe » Fri Feb 26, 2021 12:15 pm

Well, this is embarrassing. I was able to reproduce the issue again in regular Shadow Warrior, on the first level even. I then went to test on the DOS version but did not experience the problem.

When I went back to Raze to make a save game, I could no longer reproduce the issue. I thought for a moment how this could be possible and I wondered if playing in DOS somehow fixed this, as absurd as it sounds. I tried a fresh install and only played the game in Raze and still could not reproduce the issue. I even reinstalled Raze fresh again and I still could not do it.

At this point, I'm not sure how I managed to manifest this but it seems like it was entirely on my end. if I see this happen again though, I will make a new post with a savegame.

Re: [0.8.0_beta-152-g5b6aa372e] Shadow Warrior Bugs

by Graf Zahl » Fri Feb 26, 2021 11:59 am

The crash on the credits screen is fixed.

Re: [0.8.0_beta-152-g5b6aa372e] Shadow Warrior Bugs

by Graf Zahl » Fri Feb 26, 2021 11:35 am

A video would not help much as it cannot be debugged. A savegame right in the problem spot is always more helpful.

Re: [0.8.0_beta-152-g5b6aa372e] Shadow Warrior Bugs

by sinisterseed » Fri Feb 26, 2021 11:14 am

Indeed, that would be very useful. A short video would be even better to have some actual footage of it, but fair enough.

I tried to break some maps earlier today and I could not do it, so we're quite curious to see what you're experiencing.

Re: [0.8.0_beta-152-g5b6aa372e] Shadow Warrior Bugs

by Graf Zahl » Fri Feb 26, 2021 11:03 am

Xtyfe wrote:As far as the trigger line issue, as far as I have witnessed, it happens in ALL levels of each mission pack. Always with doors, but never lifts or explosive walls and so on. In Doom, triggers for shooting a sector open and open manually were separated by different line actions. I don't know if this is different in the Build engine or Shadow Warrior but both line actions seem to trigger this bug. Once it has been triggered, I as the player can't retrigger it again. For example, I can't open a door manually myself after this issue has been triggered, I'd have to wait for the door to open or close on its own. I have not tested this in regular Shadow Warrior in either DOS or Raze, but I did very briefly test one level in Twin Dragon in DOS and could not reproduce the issue. I'll play regular Shadow Warrior in DOS and Raze and I'll see if I can find the issue again.
The trigger system in the Build games is very different from Doom and also very different from each other. I wouldn't even know where to start with this, as the game code is virtually unchanged from the parent ports, and if there had been differences between VoidSW and SWP I probably would have noticed.

Can you please try to make a savegame in a spot where you think the game misbehaves? I do not mean the gong thing but the door thing you mention here.

Top