It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like:Chrome,Firefox,Internet Explorer orOpera

×
So I'm playing Duke 3D using eDuke32 and I have Windows 7 (64-bit).
At the end of each episode after the cinematic the screen that explains the plot is not present it's just a black screen, I wait a little while but it doesn't appear.

I searched through the forum but couldn't find anyone else with this problem.
Any ideas?
This question / problem has been solved by Waltoriousimage
For me, I had to hit a key to make it appear. The cinematic would finish and nothing would happen until a hit something.
avatar
Waltorious: For me, I had to hit a key to make it appear. The cinematic would finish and nothing would happen until a hit something.
Yeah I hit a key and the cinematic ends, then there's just a black screen, if I wait nothing happens, if I hit a key I get to the screen showing time, kills, secrets found etc.
avatar
almodovien: Yeah I hit a key and the cinematic ends, then there's just a black screen, if I wait nothing happens, if I hit a key I get to the screen showing time, kills, secrets found etc.
That's exactly what happens to me.... are you saying there should be another screen explaining the plot? That would go a long way to explaining why I was confused as to how the episodes connected to one another.

I noticed that in the first episode, I could hit a "help" key (I think it was F1) and it would display the "story" screen, maybe you can do that in other episodes and get the story screen that way?


EDIT: Youtube confirms that there should be some screens with text explaining the story, but I didn't get them with eDuke32 either. I've already finished the game so I can't go back and check, but maybe hitting F1 in different episodes will show you that screen. I don't know how to get it to show normally.
Post edited March 30, 2011 by Waltorious
Tried pressing F1, all other Fkeys, but nothing happened. Eventually I was taken to the level statistics screen.
avatar
almodovien: Tried pressing F1, all other Fkeys, but nothing happened. Eventually I was taken to the level statistics screen.
I meant, try pressing F1 once you start the next episode. When you're actually playing the first level of the next episode. I think it recalls the story screen for you. It certainly works in episode 1... it has the same effect as viewing the "help" option from the game's main menu. I don't know how this works in the other episodes, but hopefully it brings up the story motivation screen that was first showed at the end of the previous episode.

So this wouldn't be a full fix but it would let you see what you missed.
Nope, doesn't work.
avatar
almodovien: Nope, doesn't work.
That sucks. Unfortunately I don't know how to fix it then. I had already finished the game when I found out I'd been missing these screens so I just got caught up by checking Youtube. Anyone else know how to get eDuke32 to display the end-chapter story screens (after the cutscenes)? We're just getting a black screen.
No idea if this will be of any use but you never know. Some sort of command that you can run to trigger the end of episode sequence. Details here:

http://wiki.eduke32.com/wiki/Endofgame
How should I enter that? Just type it like a cheat code or into the console or is there anything else I need to do first?

Anyway, those endscreens aren't terribly important, I checked them all on youtube and who said Duke Nukem needs a story? it's just about blowing things up ;-)
But it DOES BUG ME!
avatar
almodovien: How should I enter that? Just type it like a cheat code or into the console or is there anything else I need to do first?

Anyway, those endscreens aren't terribly important, I checked them all on youtube and who said Duke Nukem needs a story? it's just about blowing things up ;-)
But it DOES BUG ME!
Well, I'd have thought it was a console command but I've just tried it and it's not a valid command for eDuke32. However, I don't have the latest version so there is a possibility that it is something new, but to be honest, having re-read that link I'm more leaning towards that being an original game console command and not a command for the eDuke32 engine.

Maybe send the author of eDuke32 an email explaining the issue will lead to it getting fixed?
In another thread, someone suggested changing the renderer in eDuke32 to Software 8-bit. Apparently the other renderers cause the end-of-chapter screen to appear blank.

I've already finished the game, can someone else test this out?
avatar
Waltorious: In another thread, someone suggested changing the renderer in eDuke32 to Software 8-bit. Apparently the other renderers cause the end-of-chapter screen to appear blank.

I've already finished the game, can someone else test this out?
Yeah, that would work. The problem happens because I started implementing a Polymost/Polymer version of the fading effect the 8-bit renderer uses all over the place for screen transitions and never finished it. It'll probably be commented out in an upcoming build until I have time to finish it.
avatar
Waltorious: In another thread, someone suggested changing the renderer in eDuke32 to Software 8-bit. Apparently the other renderers cause the end-of-chapter screen to appear blank.

I've already finished the game, can someone else test this out?
avatar
TerminX: Yeah, that would work. The problem happens because I started implementing a Polymost/Polymer version of the fading effect the 8-bit renderer uses all over the place for screen transitions and never finished it. It'll probably be commented out in an upcoming build until I have time to finish it.
Hey TerminX. Good to know you are aware of the problem and that you do intend to finish it. :)
avatar
Waltorious: In another thread, someone suggested changing the renderer in eDuke32 to Software 8-bit. Apparently the other renderers cause the end-of-chapter screen to appear blank.

I've already finished the game, can someone else test this out?
avatar
TerminX: Yeah, that would work. The problem happens because I started implementing a Polymost/Polymer version of the fading effect the 8-bit renderer uses all over the place for screen transitions and never finished it. It'll probably be commented out in an upcoming build until I have time to finish it.
Gonna try this out. Haven't got my own computer now though so I'll have to wait until it gets back (repairs).
Didn't check this thread for a long time since I had already finished Duke3D.