Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Kaiser

Doom64 EX 2.0a (Feedback Build) - Updated 3-12-11

Recommended Posts

Kaiser said:

Also, its suppose to fade out whenever a current game session is done. I just never realized it because it fails to fade out in a N64 emulator. I had to watch some videos on youtube that had gameplay footage on the actual N64 just to see if theres anything that I missed.

I could hook up my N64 to my gamebridge and stream it for you if you want. :P

Share this post


Link to post
footman said:

I could hook up my N64 to my gamebridge and stream it for you if you want. :P


How's the quality? Reason why I ask is because one of the things that I really need to get right is the fog distances which are ALL wrong on ALL emulators. I need to look at the N64 version and do a very close side-by-side comparison.

Share this post


Link to post
Kaiser said:

How's the quality? Reason why I ask is because one of the things that I really need to get right is the fog distances which are ALL wrong on ALL emulators. I need to look at the N64 version and do a very close side-by-side comparison.

Pretty decent actually. There's some motion blur, but it's pretty minor.

Share this post


Link to post

I noticed in 20a when playing in 16:9 with a resolution of 1280x720 the sides of the screen are glitchy, though it was ok in 1.4

20a


1.4

Share this post


Link to post

http://dl.dropbox.com/u/18609/Kex_Engine.zip

16:9 aspect ratio are supported and resolutions for 1600 x #### are in. For the password bug that Footman mentioned, the order in which the weapons are stored in the code were changed around; what this means is that there may be some potential bugs involving the weapons. I think I fixed all the bugs that were affected by this change (like starting a new game with a shotgun with 0 shells for example). The key bindings for the weapons will need to be re-binded due to this change.

Share this post


Link to post

The status bar's messed up.



I'm using the version that was just posted, on a computer with integrated Intel Graphics Media Accelerator 950.

Share this post


Link to post

Already aware of it; its caused by texture padding. Setting 'Texture Fit' under the Misc menu to Scaled will fix it for now but Scaled tends to cause some images to look blurry.

Share this post


Link to post

Thanks for adding support for 16:9! :)

I noticed on map 26 "Hardcore" the Arachnotron's teleport into each other and get stuck, don't think it happens with the mancubi though

Share this post


Link to post

When attempting to bind new keys to the fist/chainsaw and shotgun/ssg commands, I get this lovely image when it asks me to press a key for it:
http://i5.photobucket.com/albums/y181/steel_ph/stuff/KexBind.png

Binding does work fine though.

And while we're on the subject of binds, any binding to semicolon gets erased after exiting the game.

EDIT: Passwords given by the game itself are considered invalid. Nor will it take passwords given by the N64 version, oddly enough.

Password from D64EX:
CGYK QBXR SY2? J5KB

Password from N64:
C63? TGN1 TSNZ PSKB

Both function fine when input into the N64 version.

Share this post


Link to post
Kaiser said:

Both N64 and PC versions seems to be rejecting those passwords..

Yea, I typo'd the N64 one. Don't remember what it was. As for the PC password I got it mixed up with a much older pass I had lying around. I'll grab some fresh ones.

EDIT: Okay now passwords given be either game work on both. I have no idea what was going on there.

Share this post


Link to post
Mechadon said:

An easy way to test this is to switch to a different weapon. While it's still scrolling on/off the screen, pause the game.

Mechadon said:

I noticed in MAP03 that the Caco's could trip one of the teleporter line actions even though they are supposed to be blocked by a lowered ceiling. I guess it has something to do with the way flying monsters interact with solid objects


Both issues fixed. The Caco triggering the teleport line was a something I missed on my end. Apparently, Midway added a few checks for floating things and collision with linedefs. You could get this to happen in Vanilla Doom but not in the original Doom64 game :)

http://dl.dropbox.com/u/18609/Kex_Engine.zip

Share this post


Link to post

Crash in Hectic. I had just grabbed the supercharge and was about to exit the level when I quicksaved:

DOOM64 caused an Access Violation Exception (0xc0000005)
in module DOOM64.EXE at 0023:00427ac2.

Error occurred at 2/3/2011 12:49:36.
C:\DOOM\Ports\Doom64 EX\2.0\DOOM64.EXE, run by Dragonsbrethren.
Operating system: 6.1.7600
2 processors, type 586.
33% memory in use.
2559 MB physical memory.
1703 MB physical memory free.
0 MB page file.
3340 MB paging file free.
2048 MB user address space.
1819 MB user address space free.
Access violation at 07d742f4. The memory could not be written.

Context:
EDI:    0x00000000  ESI: 0x009b4671  EAX:   0x045956a0
EBX:    0x00000000  ECX: 0x07d742a0  EDX:   0x045956a0
EIP:    0x00427ac2  EBP: 0x0018fcb0  SegCs: 0x00000023
EFlags: 0x00010246  ESP: 0x0018fcb0  SegSs: 0x0000002b

Bytes at CS:EIP:
89 51 54 5d c3 55 8b ec 51 e8 4e 00 00 00 25 ff 

Stack:
0x0018fcb0: 0018fcd8 0042a788 045956a0 00429c00 ......B..VY...B.
0x0018fcc0: 045956a0 007b74e0 00000000 00000100 .VY..t{.........
0x0018fcd0: 00000300 007b74e0 0018fce0 00428d25 .....t{.....%.B.
0x0018fce0: 0018fcec 0040a4ee 007b99a0 0018fcf8 ......@...{.....
0x0018fcf0: 0040a3f2 00000003 0018fd04 00404e5f ..@........._N@.
0x0018fd00: 00000002 0018fd0c 004054b2 0018fd14 .........T@.....
0x0018fd10: 0040db68 0018fd48 0040daeb 00000001 h.@.H.....@.....
0x0018fd20: 0018fd84 00000000 009b4671 00000000 ........qF......
0x0018fd30: 0018fd24 0018f884 0018ff78 004d897e $.......x...~.M.
0x0018fd40: 004d9598 00000000 0018fd74 0044fa1c ..M.....t.....D.
0x0018fd50: 00000001 0018fd84 4d4f4f44 00003436 ........DOOM64..
0x0018fd60: 0018fd58 0018fd58 00000006 00000001 X...X...........
0x0018fd70: 0018fd58 0018feec 0044fe14 00000001 X.........D.....
0x0018fd80: 0018fd84 0018fd8d 00000000 5c3a4322 ............"C:\
0x0018fd90: 4d4f4f44 726f505c 445c7374 366d6f6f DOOM\Ports\Doom6
0x0018fda0: 58452034 302e325c 4f4f445c 2e34364d 4 EX\2.0\DOOM64.
0x0018fdb0: 00455845 00440020 00000000 009b4671 EXE. .D.....qF..
0x0018fdc0: 0018fd84 0018fd8c 0000002a 74b90000 ........*......t
0x0018fdd0: 75b42940 0018fd84 0018fd8c 445c3a43 @).u........C:\D
0x0018fde0: 5c4d4f4f 74726f50 6f445c73 34366d6f OOM\Ports\Doom64
0x0018fdf0: 5c584520 00302e32 4d4f4f44 452e3436  EX\2.0.DOOM64.E
0x0018fe00: 00004558 00c38d72 00c38d70 00000000 XE..r...p.......
0x0018fe10: 000000a4 77e8de86 00000000 009d6188 .......w.....a..
0x0018fe20: 009b00c4 0018fd5c 000003cc 00000000 ....\...........
0x0018fe30: 010003dd 0018fe50 75aaa53a 00000000 ....P...:..u....
0x0018fe40: 009b4671 0018fe5c 75aaa55c 0018fecc qF..\...\..u....
0x0018fe50: 0018fe6c 75aaf637 00000000 75b42bd0 l...7..u.....+.u
0x0018fe60: 00c31a38 00c307d0 00000001 0018fe84 8...............
0x0018fe70: 75aaf61a 00000000 00000020 00000000 ...u.... .......
0x0018fe80: 00000004 0018fea0 75ab2d6a 00000020 ........j-.u ...
0x0018fe90: 00c38d78 00000000 00000002 00000027 x...........'...
0x0018fea0: 0018fed8 75ab2cd6 00000000 00c38d7c .....,.u....|...
0x0018feb0: 00c38da7 0018fed4 00000000 00000000 ................
0x0018fec0: 00000000 000000a4 0000009c 00000027 ............'...
0x0018fed0: 00000000 009b4671 00000000 004d8c59 ....qF......Y.M.
0x0018fee0: 00000001 0000001b 009b4648 0018ff88 ........HF......
0x0018fef0: 004d8cc3 00400000 00000000 009b4671 ..M...@.....qF..
0x0018ff00: 00000001 00000000 00000000 7efde000 ...............~
0x0018ff10: 00000000 009b4671 00c38d78 00000000 ....qF..x.......
0x0018ff20: 00000000 00c31c60 00000001 00000044 ....`.......D...
0x0018ff30: 009cd920 009cd6d0 009d0f38 00000000  .......8.......
0x0018ff40: 00000000 00000000 00000000 00000000 ................
0x0018ff50: 00000000 00000000 00000401 00000001 ................
0x0018ff60: 00000000 00000000 00010001 00000000 ................
0x0018ff70: 0018ff04 00000000 0018ffc4 004d897e ............~.M.
0x0018ff80: 004dbd88 00000000 0018ff94 75d73677 ..M.........w6.u
0x0018ff90: 7efde000 0018ffd4 77e99d42 7efde000 ...~....B..w...~
0x0018ffa0: 7736668d 00000000 00000000 7efde000 .f6w...........~
0x0018ffb0: 00000000 00000000 00000000 0018ffa0 ................
0x0018ffc0: 00000000 ffffffff 77ed03dd 00c65ac9 ...........w.Z..
0x0018ffd0: 00000000 0018ffec 77e99d15 004d8b8f ...........w..M.
0x0018ffe0: 7efde000 00000000 00000000 00000000 ...~............
0x0018fff0: 00000000 004d8b8f 7efde000 00000000 ......M....~....


===== [end of CRASHLOG.TXT] =====
dkk.slickproductions.org/files/doom/doom64ex/map32crash.zip

Share this post


Link to post

Whenever I open it, a messages pops up that says "This application has failed to start because MSVCR71.dll was not found." I've already made the IWAD, and I'm playing on a 2 year old Toshiba with Vista. Do you know what the problem is/how to fix this? It's not in the bugs text.

Share this post


Link to post

If you're missing MSVCR71.dll, you will need to download it from dll-files.com and place it into C:\Windows\System32 - Doom64EX might still complain about a missing DLL, but the best strategy here is to go to dll-files.com and download each one it complains about and stick it into your System32 folder until the program runs.

Amazingly, this is even the approved solution for the problem at Microsoft's own support website.

Share this post


Link to post

It doesn't look like this has been reported but when I play the latest beta in fullscreen using a widescreen resolution, the top and right borders of the screen contain random imagery, usually based on what I've last played using hardware acceleration.

it looks a bit like this

Share this post


Link to post
InsanityBringer said:

It doesn't look like this has been reported but when I play the latest beta in fullscreen using a widescreen resolution, the top and right borders of the screen contain random imagery, usually based on what I've last played using hardware acceleration.

it looks a bit like this


I have the same issue with a 16:10 1440x900 screen resolution. But the screen was centred and the left and right sides have that same random imagery.

Share this post


Link to post
InsanityBringer said:

It doesn't look like this has been reported but when I play the latest beta in fullscreen using a widescreen resolution, the top and right borders of the screen contain random imagery, usually based on what I've last played using hardware acceleration.

it looks a bit like this


What resolution you're running at?

Share this post


Link to post

Out of curiosity, does your monitor autosize the resolution whenever you're in fullscreen mode? Starting to suspect that your monitor is trying to auto-fit the resolution of the game to match its ratio but at the same time, Doom64ex also adjusts the viewport width and height when 16:9/16:10 is enabled.

Share this post


Link to post

As far as I'm aware my monitor tries to do no autoscaling (for the purposes of aspect-ratio correction) by itself, and the information option in the on-screen menu usually matches the resolution I have set (In the case of Doom 64 EX though, it lists 1680x1050 as the resolution). I think my video driver does autosizing, but disabling that had no effect.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×