Can't jump properly (Fedora 18 build of latest svn)

ulatekh

#1 Posted 11 June 2013 - 11:39 AM

Hello all! I have Duke Nukem 3D working on my Fedora Core 18 machine, using dosbox, and was glad to find the EDuke32 project -- it offered much better resolution options, as well as vastly improved graphics! (And that's without the HRP...just turning on Polymer is a big upgrade!)

I've found one blocking problem, though...I can't jump! Duke seems to come back to earth too quickly to make jumping worthwhile.

I was able to partially work around it by modifing line 4878 of source/player.c -- where it divided by 12, I now divide by 5. This lets me jump onto the ledge from the box in the early part of E1L1, but I just found I can't jump into the air-vent just inside the strip club in E1L2, and I doubt hacking numbers like this is the right solution anyway. Can anyone suggest what I should try next?

Other than that, it appears to work flawlessly.

I'm running Fedora Core 18, i686 version, on an old Athlon 64 4200, i.e. a dual-core running at 4420.84 bogomips. I'm building the latest version of EDuke32 (i.e. from Subversion) by simply typing "make" without any changes.

TerminX

el fundador

#2 Posted 11 June 2013 - 11:46 AM

What the heck? Post a video or something.

Jimmy

Let's go Brandon!

#3 Posted 11 June 2013 - 11:58 AM

You can't jump into the vent from the ground. You have to jump from that nearby table.

Plagman

Former VP of Media Operations

#4 Posted 11 June 2013 - 04:22 PM

Also, are you talking about the RPG ledge in E1L1 or the sloped building side? You can't jump directly to the RPG ledge from the crate either, you have to jump to the sloped one and then to the RPG ledge.

ulatekh

#5 Posted 11 June 2013 - 05:17 PM

I'm talking about the vent just inside the front door of the strip club, the one that leads to the bathroom. And I'm talking about the sloping ledge, not the RPG ledge.
I _have_ played this game before, you know. :-)
And keep in mind that it works fine when playing the standard Duke Nukem 3D from a dosbox.

I'll go make a video.

Plagman

Former VP of Media Operations

#6 Posted 11 June 2013 - 05:26 PM

Yeah, it's good to just make sure; sometimes people who haven't played the game in a long time get confused. I remember someone posting about the game speed being too fast, but Duke really runs and shoots that fast.

One of the first things I would try in your situation is to try building with -m32 to see if that's possibly an obscure x86_64 memory bug?

EDIT: Nevermind, you did mention this was on i686. Huh. Maybe try pinning it to one core with taskset? Could be timing-related.

ulatekh

#7 Posted 11 June 2013 - 06:11 PM

OK, here's a video.

And taskset (i.e. "taskset -c 0 ./eduke32 -grp ~/.dosbox/drive_c/DUKE3D/DUKE3D.GRP") had no effect on the jumping issue.

TerminX

el fundador

#8 Posted 11 June 2013 - 06:32 PM

Post your eduke32.log, please. That's really weird. Please also paste the output of gcc -v.

ulatekh

#9 Posted 11 June 2013 - 06:38 PM

The requested info is now posted here.
Thanks for taking the time to look into this!

BTW, my gcc is the standard one from the Fedora Core 18 repos.

Hendricks266

Weaponized Autism

#10 Posted 11 June 2013 - 07:20 PM

Try:

./eduke32 -gamegrp ~/.dosbox/drive_c/DUKE3D/DUKE3D.GRP

Hendricks266

Weaponized Autism

#11 Posted 11 June 2013 - 07:31 PM

Here are my dev notes:

ulatekh definitely has a clean install of the shareware.
The CONs are in fact from v1.3D.
The GRP is the shareware v1.3D GRP. When I asked ulatekh to symlink the GRP to the CWD, it showed up as "Duke Nukem 3D Shareware 1.3D" in the startup window.

The culprit in my mind is that the gravitational constant is different between v1.3D and v1.4+, and the game says the CONs are v1.4+ when they are definitely v1.3D. I thought that having EDuke32 properly detect the GRP as the main game GRP would trigger the shareware flag, but it did not.

(This is how I know the CONs are v1.3D:)

GAME.CON: In state `blimphitstate':
GAME.CON:157: warning: expected action, found define.

LeoD

Duke4.net topic/3513

#12 Posted 11 June 2013 - 08:01 PM

Bug confirmed on Windows. Introduced in r3803 - more shits than giggles. :lol:

inspirationforbirthcontrol

#13 Posted 12 June 2013 - 07:34 PM

I just built the most recent release from source and jumping doesn't seem to work. I can only jump like a half inch into the air for some reason.

This isn't as big of a problem, but I'm also having issues with fullscreen mode. The screen is blank in fullscreen for some reason. I can only run in a window, but I can't seem to get my cursor back without quitting the application. This is annoying because the window starts up in like the corner and it would be nice to be able to hit alt+tab or something and center the window on the screen. My environment is Fedora 18 and I'm using gnome if that makes a difference.