Opening Cutscene messed up in timing (hardcoded issue?)

Status
Not open for further replies.

glaber

Emblem Radar Ready
(Apparently the real issue is how badly the old SRB2 intro was actually coded)

While porting a mod to 2.1, I discovered that the settings for Pic1Duration don't always work anymore, this is especially noticeable with SRB2's old April fools intro (That is used in the mod)

at first I thought the text space was messing it up now, but after experimenting with timing, I don't know what's going on.

now just in case, I do have how the entire thing was set up
Code:
CUTSCENE 1
NUMSCENES 21
SCENE 1
NUMBEROFPICS = 1
TEXTXPOS = 0
TEXTYPOS = 144
PIC1NAME = OLDCUT35
PIC1XCOORD = 0
PIC1YCOORD = 0
PIC1DURATION = 140
SCENETEXT =               
                     #
SCENE 2
NUMBEROFPICS = 1
TEXTXPOS = 0
TEXTYPOS = 144
MUSICSLOT = 1035
PIC1NAME = OLDCUT01
PIC1XCOORD = 96
PIC1YCOORD = 0
PIC1DURATION = 35
SCENETEXT =               
                     #
SCENE 3
NUMBEROFPICS = 1
TEXTXPOS = 84
TEXTYPOS = 144
PIC1NAME = OLDCUT02
PIC1XCOORD = 96
PIC1YCOORD = 0
PIC1DURATION = 70
SCENETEXT = The planet Mobius...
#
SCENE 4
NUMBEROFPICS = 1
TEXTXPOS = 0
TEXTYPOS = 144
PIC1NAME = OLDCUT03
PIC1XCOORD = 96
PIC1YCOORD = 0
PIC1DURATION = 1
SCENETEXT =         
                     #
SCENE 5
NUMBEROFPICS = 1
TEXTXPOS = 96
TEXTYPOS = 144
PIC1NAME = OLDCUT04
PIC1XCOORD = 96
PIC1YCOORD = 0
PIC1DURATION = 126
SCENETEXT = Over the past two
 months has been
       peaceful.#
SCENE 6
NUMBEROFPICS = 8
TEXTXPOS = 92
TEXTYPOS = 136
PIC1NAME = OLDCUT05
PIC1XCOORD = 96
PIC1YCOORD = 0
PIC1DURATION = 14
PIC2NAME = OLDCUT06
PIC2XCOORD = 96
PIC2YCOORD = 0
PIC2DURATION = 5
PIC3NAME = OLDCUT07
PIC3XCOORD = 96
PIC3YCOORD = 0
PIC3DURATION = 5
PIC4NAME = OLDCUT08
PIC4XCOORD = 96
PIC4YCOORD = 0
PIC4DURATION = 5
PIC5NAME = OLDCUT09
PIC5XCOORD = 96
PIC5YCOORD = 0
PIC5DURATION = 5
PIC6NAME = OLDCUT10
PIC6XCOORD = 96
PIC6YCOORD = 0
PIC6DURATION = 5
PIC7NAME = OLDCUT11
PIC7XCOORD = 96
PIC7YCOORD = 0
PIC7DURATION = 5
PIC8NAME = OLDCUT12
PIC8XCOORD = 96
PIC8YCOORD = 0
PIC8DURATION = 105
SCENETEXT =    Until the Black
     Asteroid was
heading for Mobius...#
SCENE 7
NUMBEROFPICS = 1
TEXTXPOS = 92
TEXTYPOS = 136
PIC1NAME = OLDCUT13
PIC1XCOORD = 96
PIC1YCOORD = 0
PIC1DURATION = 105
SCENETEXT =    ..but why is it
heading for Mobius?#
SCENE 8
NUMBEROFPICS = 1
TEXTXPOS = 0
TEXTYPOS = 136
PIC1NAME = OLDCUT14
PIC1XCOORD = 96
PIC1YCOORD = 0
PIC1DURATION = 1
SCENETEXT =                
                     #
SCENE 9
NUMBEROFPICS = 1
TEXTXPOS = 80
TEXTYPOS = 136
PIC1NAME = OLDCUT15
PIC1XCOORD = 96
PIC1YCOORD = 0
PIC1DURATION = 84
SCENETEXT = The answer is inside...
#
SCENE 10
NUMBEROFPICS = 1
TEXTXPOS = 112
TEXTYPOS = 136
PIC1NAME = OLDCUT16
PIC1XCOORD = 96
PIC1YCOORD = 0
PIC1DURATION = 210
SCENETEXT = The answer is
Dr. Robotnik!#
SCENE 11
NUMBEROFPICS = 1
TEXTXPOS = 94
TEXTYPOS = 136
PIC1NAME = OLDCUT17
PIC1XCOORD = 96
PIC1YCOORD = 0
PIC1DURATION = 175
SCENETEXT =    Only one person
on Mobius can save
    the world from
 being destroyed.#
SCENE 12
NUMBEROFPICS = 1
TEXTXPOS = 112
TEXTYPOS = 136
PIC1NAME = OLDCUT18
PIC1XCOORD = 96
PIC1YCOORD = 0
PIC1DURATION = 280
SCENETEXT = One hedgehog,
   namely...               
                     #
SCENE 13
NUMBEROFPICS = 1
TEXTXPOS = 112
TEXTYPOS = 136
PIC1NAME = OLDCUT36
PIC1XCOORD = 0
PIC1YCOORD = 0
PIC1DURATION = 210
SCENETEXT =                
                     #
SCENE 14
NUMBEROFPICS = 8
TEXTXPOS = 0
TEXTYPOS = 144
PIC1NAME = OLDCUT19
PIC1XCOORD = 96
PIC1YCOORD = 0
PIC1DURATION = 35
PIC2NAME = OLDCUT20
PIC2XCOORD = 96
PIC2YCOORD = 0
PIC2DURATION = 5
PIC3NAME = OLDCUT21
PIC3XCOORD = 96
PIC3YCOORD = 0
PIC3DURATION = 5
PIC4NAME = OLDCUT22
PIC4XCOORD = 96
PIC4YCOORD = 0
PIC4DURATION = 5
PIC5NAME = OLDCUT23
PIC5XCOORD = 96
PIC5YCOORD = 0
PIC5DURATION = 5
PIC6NAME = OLDCUT24
PIC6XCOORD = 96
PIC6YCOORD = 0
PIC6DURATION = 5
PIC7NAME = OLDCUT25
PIC7XCOORD = 96
PIC7YCOORD = 0
PIC7DURATION = 5
PIC8NAME = OLDCUT26
PIC8XCOORD = 96
PIC8YCOORD = 0
PIC8DURATION = 5
SCENETEXT =                
                     #
SCENE 15
NUMBEROFPICS = 6
TEXTXPOS = 0
TEXTYPOS = 144
PIC1NAME = OLDCUT27
PIC1XCOORD = 96
PIC1YCOORD = 0
PIC1DURATION = 70
PIC2NAME = OLDCUT28
PIC2XCOORD = 96
PIC2YCOORD = 0
PIC2DURATION = 7
PIC3NAME = OLDCUT27
PIC3XCOORD = 96
PIC3YCOORD = 0
PIC3DURATION = 7
PIC4NAME = OLDCUT28
PIC4XCOORD = 96
PIC4YCOORD = 0
PIC4DURATION = 7
PIC5NAME = OLDCUT27
PIC5XCOORD = 96
PIC5YCOORD = 0
PIC5DURATION = 7
PIC6NAME = OLDCUT29
PIC6XCOORD = 96
PIC6YCOORD = 0
PIC6DURATION = 35
SCENETEXT =                
                     #
SCENE 16
NUMBEROFPICS = 1
TEXTXPOS = 0
TEXTYPOS = 144
PIC1NAME = OLDCUT30
PIC1XCOORD = 96
PIC1YCOORD = 0
PIC1DURATION = 1
SCENETEXT =                
                     #
SCENE 17
NUMBEROFPICS = 1
TEXTXPOS = 0
TEXTYPOS = 144
PIC1NAME = OLDCUT31
PIC1XCOORD = 96
PIC1YCOORD = 0
PIC1DURATION = 70
SCENETEXT =                
                     #
SCENE 18
NUMBEROFPICS = 1
TEXTXPOS = 0
TEXTYPOS = 144
PIC1NAME = OLDCUT32
PIC1XCOORD = 96
PIC1YCOORD = 0
PIC1DURATION = 35
SCENETEXT =                
                     #
SCENE 19
NUMBEROFPICS = 1
TEXTXPOS = 0
TEXTYPOS = 144
PIC1NAME = OLDCUT33
PIC1XCOORD = 96
PIC1YCOORD = 0
PIC1DURATION = 14
SCENETEXT =                
                     #
SCENE 20
NUMBEROFPICS = 1
TEXTXPOS = 0
TEXTYPOS = 144
PIC1NAME = OLDCUT34
PIC1XCOORD = 96
PIC1YCOORD = 0
PIC1DURATION = 210
SCENETEXT =                
                     #
SCENE 21
NUMBEROFPICS = 1
TEXTXPOS = 0
TEXTYPOS = 144
PIC1NAME = OLDCUT33
PIC1XCOORD = 96
PIC1YCOORD = 0
PIC1DURATION = 70
SCENETEXT =                
                     #
The trouble seems to be either the scene(s) goes faster than specified, or slower when told to have a duration of 1
 
Last edited:
ok it's been about a month and still no way to fix this yet.

So maybe it would be best to show what's happening.
This video will show what actually happens when I try to use the old April fool opening as the actual opening.
http://youtu.be/2FoXbweYpIs

Note, the video can't recieve comments because my YT account doesn't have Google+ linked
 
Last edited:
Well I ported my the walls of the void maps from 2.0, which had cutscenes, and they all work fine. The reason why the durations for that cutscene which you showed is either too fast or too slow is because the durations you showed make it so. A duration of 100 is around 5 seconds, a duration of 200 is about 15 seconds. For quick transitions, I use a duration of 10 or 50. I can't give specific information about what duration which scene will be, but if you keep the 100 = 5 seconds rule in your head and experiment a bit with it, you might find the answers to what the durations for each scene should be.
 
In fact, the duration is in "tics"
35 tics = 1 second.
Making a duration of 10 tics is... less than 1 second, this explain why it goes too fast.
 
Yea, I figured this out earlier. Hard to believe that this was how the original SRB2 opening was SOCed.

Anyway, I'm in the process of fixing it now.
 
It's not a choice of the creator; 35 was the max FPS of Doom, and you cannot just decide whenever or not to use tics. I believe you can just put [# of seconds]*TICRATE as a way to get around not using tics.

EDIT: Ninja'd
 
well some scenes don't even last a second, but I shouldn't have a problem with repairs from this point, hopefully.

Just have to get help fixing some other stuff. (Will make another topic for that.)
 
Status
Not open for further replies.

Who is viewing this thread (Total: 0, Members: 0, Guests: 0)

Back
Top