how do i make a doom tas

[Betelgeuse]

Bro how do i make a doom tas ik there are tutorials but they are so confusing can someone explain in detail or make a video on how to make a doom tas?

 

[Maribo]

Sorry, but this is probably the best tutorial you're going to find. For making TASes in Doom, these days you only really have the option of using XDRE or DSDA-Doom, both of which function differently and currently don't match up at all in terms of UI or fine points of what exactly you can do with the software. The closest thing to a write-up for DSDA-Doom is the build mode documentation that you can find here, and the XDRE guide I've linked is very long but written by someone who understands how it works and has an extensive history of TAS work. I would suggest reading it and then asking questions about specific things that you don't understand.

[almostmatt1]

Sorry that that XDRE guide is so wordy and indirect. I intended to be as unambiguous as possible but that absolutely came at the expense of it being way too long to get through, and it being quite inefficient to get usable information out of if you just want to get up and running. It isn't how I'd write it if I had to do it again, but it probably will still answer many questions you have.

The basics are this. TASes can be made by individually controlling every single input of every single frame of a demo, or they can be made by playing the game with slow motion and re-recording segments which is commonly done nowadays with DSDA-Dooms extremely valuable rewind button. Both XDRE and DSDA-Doom allow you to create a TAS frame-by-frame, but only DSDA-Doom allows you to make a demo using slowmo+segmenting. Building frame-by-frame gives you a LOT more control over what is going on, but is more time consuming and difficult to do well. The beginning of the XDRE guide has been edited to discuss some advantages and disadvantages of either program. 

I don't have enough experience with slowmo+segmenting or using DSDA-Doom to be much help but I've spent much more time TASing with XDRE than I have actually playing Doom, so if you decide that you would like to make a TAS with XDRE feel free to reach out any time with specific questions about what you want to accomplish and any issues you are experiencing and I'll do my best to help you out. :)

[Betelgeuse]

13 hours ago, almostmatt1 said:

Sorry that that XDRE guide is so wordy and indirect. I intended to be as unambiguous as possible but that absolutely came at the expense of it being way too long to get through, and it being quite inefficient to get usable information out of if you just want to get up and running. It isn't how I'd write it if I had to do it again, but it probably will still answer many questions you have.

The basics are this. TASes can be made by individually controlling every single input of every single frame of a demo, or they can be made by playing the game with slow motion and re-recording segments which is commonly done nowadays with DSDA-Dooms extremely valuable rewind button. Both XDRE and DSDA-Doom allow you to create a TAS frame-by-frame, but only DSDA-Doom allows you to make a demo using slowmo+segmenting. Building frame-by-frame gives you a LOT more control over what is going on, but is more time consuming and difficult to do well. The beginning of the XDRE guide has been edited to discuss some advantages and disadvantages of either program. 

I don't have enough experience with slowmo+segmenting or using DSDA-Doom to be much help but I've spent much more time TASing with XDRE than I have actually playing Doom, so if you decide that you would like to make a TAS with XDRE feel free to reach out any time with specific questions about what you want to accomplish and any issues you are experiencing and I'll do my best to help you out. :)

ty i definitely will.

[Betelgeuse]

15 hours ago, almostmatt1 said:

Sorry that that XDRE guide is so wordy and indirect. I intended to be as unambiguous as possible but that absolutely came at the expense of it being way too long to get through, and it being quite inefficient to get usable information out of if you just want to get up and running. It isn't how I'd write it if I had to do it again, but it probably will still answer many questions you have.

The basics are this. TASes can be made by individually controlling every single input of every single frame of a demo, or they can be made by playing the game with slow motion and re-recording segments which is commonly done nowadays with DSDA-Dooms extremely valuable rewind button. Both XDRE and DSDA-Doom allow you to create a TAS frame-by-frame, but only DSDA-Doom allows you to make a demo using slowmo+segmenting. Building frame-by-frame gives you a LOT more control over what is going on, but is more time consuming and difficult to do well. The beginning of the XDRE guide has been edited to discuss some advantages and disadvantages of either program. 

I don't have enough experience with slowmo+segmenting or using DSDA-Doom to be much help but I've spent much more time TASing with XDRE than I have actually playing Doom, so if you decide that you would like to make a TAS with XDRE feel free to reach out any time with specific questions about what you want to accomplish and any issues you are experiencing and I'll do my best to help you out. :)

can you tell me how to tas using xdre or dsda-doom in a simplified way?

 

Edited September 17, 2023 by Tarry111

[Betelgeuse]

16 hours ago, almostmatt1 said:

Sorry that that XDRE guide is so wordy and indirect. I intended to be as unambiguous as possible but that absolutely came at the expense of it being way too long to get through, and it being quite inefficient to get usable information out of if you just want to get up and running. It isn't how I'd write it if I had to do it again, but it probably will still answer many questions you have.

The basics are this. TASes can be made by individually controlling every single input of every single frame of a demo, or they can be made by playing the game with slow motion and re-recording segments which is commonly done nowadays with DSDA-Dooms extremely valuable rewind button. Both XDRE and DSDA-Doom allow you to create a TAS frame-by-frame, but only DSDA-Doom allows you to make a demo using slowmo+segmenting. Building frame-by-frame gives you a LOT more control over what is going on, but is more time consuming and difficult to do well. The beginning of the XDRE guide has been edited to discuss some advantages and disadvantages of either program. 

I don't have enough experience with slowmo+segmenting or using DSDA-Doom to be much help but I've spent much more time TASing with XDRE than I have actually playing Doom, so if you decide that you would like to make a TAS with XDRE feel free to reach out any time with specific questions about what you want to accomplish and any issues you are experiencing and I'll do my best to help you out. :)

btw xdre is not working, when i drag doom.wad into xdre.exe nothing is happening, any idea why?

[Guff dotD]

21 minutes ago, Tarry111 said:

btw xdre is not working, when i drag doom.wad into xdre.exe nothing is happening, any idea why?

Because it's not GZDoom.

 

[Betelgeuse]

6 minutes ago, Guff dotD said:

Because it's not GZDoom.

 

ohh ok so what do i do

Edited September 17, 2023 by Tarry111

[Guff dotD]

I really don't know anything about Tas'ing in Doom (so take everything I say with a healthy dose of salt), but I would assume that getting it [XDRE] to run may be more complex than dragging-and-dropping an IWAD on top.

 

 

[Betelgeuse]

I HAVE FIGURED IT OUT, i was using xdre 2.21 which wasnt working but xdre 2.20 is!

[Betelgeuse]

but i did a demo and when i try to open it it says "couldn't open demo, figure that out yourself"

[Firedust]

ask bloodite krypto

[almostmatt1]

Could you please tell me if you're using a pwad or just doom.wad, what map you want to make a TAS for, and what category you want to do? Like UV-Speed/No Monsters/UV Max etc. The more information the better.

Also, just so you know when you make a demo with XDRE and try to play that demo using a source port, it will only work with vanilla-compatible source ports. This means it will work with DSDA-Doom, PrBoom+, Crispy Doom, Chocolate Doom etc, but not source ports like GZDoom, Zandronum etc. If you're not confident you know what the difference is, just grab DSDA-Doom from here and I'll show you what to do once you have a demo to play.

[Betelgeuse]

18 hours ago, almostmatt1 said:

Could you please tell me if you're using a pwad or just doom.wad, what map you want to make a TAS for, and what category you want to do? Like UV-Speed/No Monsters/UV Max etc. The more information the better.

Also, just so you know when you make a demo with XDRE and try to play that demo using a source port, it will only work with vanilla-compatible source ports. This means it will work with DSDA-Doom, PrBoom+, Crispy Doom, Chocolate Doom etc, but not source ports like GZDoom, Zandronum etc. If you're not confident you know what the difference is, just grab DSDA-Doom from here and I'll show you what to do once you have a demo to play.

i am using doom.wad to speedrun e1m2 uv-speed. Then when i am done i got my .lmp file. i wanted to open it using xdre but it said "couldn't open demo, figure that out yourself"

[RockyGaming4725]

18 hours ago, Tarry111 said:

i am using doom.wad to speedrun e1m2 uv-speed. Then when i am done i got my .lmp file. i wanted to open it using xdre but it said "couldn't open demo, figure that out yourself"

That error is thrown when xdre couldn’t properly load the demo (which shouldn’t really ever happen). Vague message for sure, but basically it means that something about the demo is causing xdre to freak out. This could be an unknown complevel or unknown demo structure. (For example, recording a demo in dsda doom with -dsdademo, which allows for the capture of freelook inputs among other things).

What source port did you use to record your e1m2 demo? If you want to send the demo over I could take a look and see what’s causing xdre to throw an error.

Also, if you wish, you can grab an updated version of XDRE over here.

Edited September 19, 2023 by RockyGaming4725

[Betelgeuse]

21 hours ago, RockyGaming4725 said:

That error is thrown when xdre couldn’t properly load the demo (which shouldn’t really ever happen). Vague message for sure, but basically it means that something about the demo is causing xdre to freak out. This could be an unknown complevel or unknown demo structure. (For example, recording a demo in dsda doom with -dsdademo, which allows for the capture of freelook inputs among other things).

What source port did you use to record your e1m2 demo? If you want to send the demo over I could take a look and see what’s causing xdre to throw an error.

Also, if you wish, you can grab an updated version of XDRE over here.

i am using woof source port

[Shepardus]

Did you specify a complevel when recording the demo? If not, you probably recorded it in MBF21 compatibility, which XDRE doesn't support.

[Betelgeuse]

Guys ty but i no longer need help in it, i am no longer interested in xdre and its features. Thank you all for your time

[Redneckerz]

2 hours ago, Tarry111 said:

Guys ty but i no longer need help in it, i am no longer interested in xdre and its features. Thank you all for your time

I love it when users have short term interests in things and let people try to help you only for you to abandon it.

[Shepardus]

1 hour ago, Redneckerz said:

I love it when users have short term interests in things and let people try to help you only for you to abandon it.

"I was interested until I realized it takes more than 15 minutes of effort"

[Betelgeuse]

2 hours ago, Redneckerz said:

I love it when users have short term interests in things and let people try to help you only for you to abandon it.

So? Got a problem with that? You could do that too yk.. everyone does

[Betelgeuse]

Guys just please excuse anything i say, i am still new here and still learning to adapt.

[baja blast rd.]

16 minutes ago, Tarry111 said:

So? Got a problem with that? You could do that too yk.. everyone does

 

This is definitely an attitude to avoid because the only people I can think of who shamelessly wasted others' time are now banned. 

 

At least Maribo's and almostmatt's replies will be helpful in the future to someone who uses the search function.

[Betelgeuse]

I know in the past i used to just be dumb and ask questions about something and then just abandon it right away.

But yk how a human brain can be. 

From now on when i want to ask a question I'll just be serious and fully focused on that topic.

[Betelgeuse]

Just excuse me please