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:
Couldn't get the issue with the flashing lights to occur.


Me neither... I think it has to do with Akira98's hardware setup.

Nevertheless, nice job fixing some of the problems with the save games!
I finally was able to move on, minus one small curiosity.

I'm perfectly fine on MAP04, everything is nice, and then I decide to load up a previous save game (in Hectic), the game loads up perfectly.
Then I decide to go back via savegame to MAP01, and I get this:

Error - P_UnArchiveMobjs: Mobj read is inconsistent
Then I run again, load that MAP01 save, everything is nice, then I load up the Hectic save, and I get the same thing.
Third chance: Loaded my MAP04 save, all is fine, then I load up the MAP01 save, and it crashes.
If I load between Hectic and MAP04, there's no problem at all.
Basically I can resume it up to:
MAP04  -> Hectic  = OK
MAP04  -> MAP01  = NG
Hectic -> MAP01  = NG
Hectic -> MAP04  = OK
MAP01  -> MAP04  = NG
MAP01  -> Hectic = NG
I'll upload my saves when I have a chance.
Also, what is up with Hectic's BG?

Share this post


Link to post

Skies aren't affected by looking up/down. Didn't really support that since the original didn't have looking. Could probably do something about that in the future but thats considered low priority compared to the other stuff that needs to be addressed.

Also, is the savegame on map01 from an older version?

Share this post


Link to post

Kaiser said:
Skies aren't affected by looking up/down. Didn't really support that since the original didn't have looking. Could probably do something about that in the future but thats considered low priority compared to the other stuff that needs to be addressed.

I knew you were going to say that, but nevertheless it felt kind of awkward seeing that flame going up and down with me.
Trust me that I agree with you, you shouldn't be able to look up and down (but I think I grew too accustomed to looking up and down in other engines).

Kaiser also said:
Also, is the savegame on map01 from an older version?

Nope, as always when you release a new version, I erase everything from the directory minus the Doom 64 ROM (thus I have to restart my game, but this goes towards the advancement of the engine).
Here's the savegame pack http://ifile.it/woj73b6. Hope it helps you in any way.

I might be saying this as I never stated it before (but I'm not having any graphic glitches so far), my video card is an ATi Radeon X700.

Share this post


Link to post

Any chance of a better selection of screen resolutions? Having to rearrange my desktop (I have a dual monitor setup) due to the resolution change is really bugging me. I can get it to run at 1920x1080 by forcing the resolution via the console/config file but it stretches it to 16x9 instead of either running it at the correct aspect ratio natively or running it within a pillarboxed window.

In addition I might as well request that you change the fullscreen implementation from the old-fashioned way to the more modern "full-screen window" way that a lot of games and apps are using nowadays.

Share this post


Link to post
Swiss_Cheeseman said:

In addition I might as well request that you change the fullscreen implementation from the old-fashioned way to the more modern "full-screen window" way that a lot of games and apps are using nowadays.


Out of curiosity, what is the modern method? Never knew there was a difference in how older games handled fullscreen mode.

Share this post


Link to post

There's some odd behavior involving freelook, which has been easier to find with the crosshair. More screenshot spam...


All these shots were taken when aiming below the default height. In the upper area (the first screenshot), the shots were appearing below the crosshair. In the area just below, and keeping the same view angle, the shots were appearing above the crosshair. Aiming above the default height is also affected.

If you turn autoaim off, you end of firing at whatever height you were looking at, regardless of where you're looking at now.


The odd light glitch in the crusher room has been fixed with the most recent version. Not sure exactly what happened there.

Lost souls can kill each other through infighting. Now that I think about it, I actually don't know if this is normal behavior or not. =P

You can activate the automap from the pause menu.

Music never restarts when loading a savegame from the same map you are on, but it does loading from the menu. Happens every savegame I've tried.

With the pain elemental on MAP06, more often than not couldn't spawn lost souls correctly. It happens regardless of whether or not the N64 collision is being used. The pain elemental would either spawn them inside something, killing both lost souls, or spawn them inside each other, which would cause the infighting problem as they try to attack me.

I've included the save file with the pain elemental in question, so it can be easily reproduced: http://files.drdteam.org/index.php/files/get/K3MtuThPTl/painelementalglitch.zip

Share this post


Link to post
Swiss_Cheeseman said:

I believe the method used is making a borderless window the size of the desktop. XBMC has options for both, it's possible to toggle between the two modes.

Pretty much. The upcoming Doomsday 1.9.0-beta6.10 release has a similar option. This method is particularly useful for multi-display setups.

Share this post


Link to post
Akira_98 said:

There's some odd behavior involving freelook, which has been easier to find with the crosshair. More screenshot spam...

All these shots were taken when aiming below the default height. In the upper area (the first screenshot), the shots were appearing below the crosshair. In the area just below, and keeping the same view angle, the shots were appearing above the crosshair. Aiming above the default height is also affected.


That is mostly a d64ex 'feature'. I say feature because its the best I could do to fake bullet puffs hitting the floor and ceiling. Doom never really supported proper collision detection for ray-trace shots and Eternity's implementation to fake this was only good enough for software. I basically had to write my own method to support my engine. Its not exactly perfect and I knew that there was going to be some precision issues. Its REALLY bad in wide open spaces like in No Escape or Eye of the Storm. Sadly I am limited by lack of arithmetic skills.

This only affects where the bullet puffs are spawned though and not the actual ray-trace of your line of sight.


Edit:
Password system and autoaim option fixed
http://dl.dropbox.com/u/18609/Kex_Engine.zip

Share this post


Link to post

Hey Kaiser, little trivia question. I see this wiki edit and I think it'd be more accurate to say "RECT (MOTH in the Absolution TC)", wouldn't it?

Share this post


Link to post

To make things confusing, the sprites are named as MOTH in the TC, but is actually named as RECT in the original so its more accurate to go with that. Though the wiki itself should probably be updated with additional information sometime in the future. Also some information still pertains to the TC version so it needs to be updated anyways.

Share this post


Link to post
Akira_98 said:

Lost souls can kill each other through infighting. Now that I think about it, I actually don't know if this is normal behavior or not. =P

With the pain elemental on MAP06, more often than not couldn't spawn lost souls correctly. It happens regardless of whether or not the N64 collision is being used. The pain elemental would either spawn them inside something, killing both lost souls, or spawn them inside each other, which would cause the infighting problem as they try to attack me.


Confirmed to be normal behavior. Tested this on the N64 version and the pain elemental had the same trouble spitting out the lost souls. Lost souls will also infight each other.

Share this post


Link to post

Yet another bug with passwords: Any password that gives you a backpack will quadruple your max ammo count, as opposed to simply doubling it.

Share this post


Link to post
footman said:

Yet another bug with passwords: Any password that gives you a backpack will quadruple your max ammo count, as opposed to simply doubling it.


rofl. I'll have a looksie. Can you provide that password?

Share this post


Link to post

Pretty much any password that includes the Backpack will do it, such as the cheat password or any of the fully loaded passwords Ledmeister has on his site.

EDIT: For the hell of it, here's a non-fully loaded password that does it: LX91 CVX4 7D84 RF7Z

Share this post


Link to post
Mechadon said:

- If you die near a wall and press use, the player will still make the grunting noise just like he would if he were alive. Of course directly after that the game fades out to restart the level. I just found this one out by accident and I don't think it's anything major. I didn't check to see if switches could still be pressed though.


I just confirmed that this DOES happen on the original N64 version. Not sure if I should add a compatibility fix or whatnot.

Share this post


Link to post

It is sort of weird but I don't suppose it's really a horrible sort of bug. I never did check to see if you could press switches though. That might be a little more worrisome but still not something game-breaking bad.

Share this post


Link to post
Mechadon said:

It is sort of weird but I don't suppose it's really a horrible sort of bug. I never did check to see if you could press switches though. That might be a little more worrisome but still not something game-breaking bad.


If you didn't take the chance to find it, it would remain unknown.
Nevertheless, I think it doesn't breaks a single thing (gameplay wise) thus a compatibility fix it's not that important or need any priority.

For now, I tested the last release. It seems to work really nice.
The "P_UnArchiveMobjs: Mobj read is inconsistent" save game error still occurs (detailed info in a previous post).
Also, it seems save games from last version work in this release.

I had something to say about the fullscreen techniques but I need to research more about the programming side to properly explain what I want.

Share this post


Link to post
Tamhvm said:

The "P_UnArchiveMobjs: Mobj read is inconsistent" save game


It seems like you're the only one getting this now unless others can verify that its occurring for them to. Without any way to reproduce this on my end, this will be very non-trivial to fix. I've already reviewed your savegame files and according to the hex editor, everything is in place and loads fine on my end.

Share this post


Link to post

I still have the savegame issue. Sometime tomorrow I can check again on a totally different machine. Since it's only affecting a couple people, here is: Specs (Chapter 2):

OS: Windows XP Professional SP3
HD: Samsung SP1604N
CPU: 2.20 GHz AMD Athlon XP 3200+
1 GB RAM
Sound Blaster Live! 24-bit

Can't think of anything else that can help in this regard.

Share this post


Link to post

"P_UnArchiveMobjs: Mobj read is inconsistent" still occurs on and off when I save/load.
Last time was on Map13.
Seems that it's more likely to occur when there are more mobs on screen... though this is an uneducated guess.
Will upload the savegame when it happens again.

Edit: played some more - the Mobj-error occurs basically at random.
The save game works, then out of the blue, the error occurs.
Restart the prog and loading the save game works for a few times - and so on.

1 crash so far - http://www.mediafire.com/?lxxerjhn9fx40k8

Share this post


Link to post

I haven't had a chance to play this again for a while, but I'll mess around with saves/loads again soon. I'll try and see if a player can press switches when he's dead as well.

Share this post


Link to post

I tried on a different machine, and I'm still getting the savegame error, where I cannot load a save on any level other than the one the save was made on. Savegames:http://files.drdteam.org/index.php/files/get/QZgI2mqB9Y/newsaves.zip

Here is the machine's specs:
Windows 7 Home 64-bit
AMD Athlon II X4 360 2.8 GHz CPU
4 GB RAM
Realtek HD Audio
Video is some craptastic on-board, which refuse to give me any details, other than "RS880".

Share this post


Link to post
Kaiser said:

Added yet another possible fix:
http://dl.dropbox.com/u/18609/Kex_Engine.zip

In this thread it turns out that certain file reading/writing routines may have contributed to the mobj inconsistencies when reading savegame files. Though I will need testers to give this another shot. Should be able to use the existing savegame files.

Sir Kaiser, I think you've got your own testing army here.
I can confirm, the savegame error still occurs (using the old savegames).
One surefire way to test it, in my case: Load my first savegame (named BEFOREH). You can walk, do whatever, minus exit the map. Load the second savegame (named HECTIC1) [NOTE: You could load any other savegame]. The error occurs.
Same in the inverse: Load any other-than-first savegame. Go around, play, and when you're ready load the first savegame. The error occurs.
You can load freely between the other-than-first savegames. I don't know what the difference is in that first savegame, maybe mobs or something, as _bruce_ said.

P.S. I saw the other thread and well, that's awesomely interesting. But I have to agree with andrewj. There are some high-level functions to abstract-ize the low-level calls. It's really unnecessary and cumbersome to say the least. Also, that tidbit about INT 21 is hilarious. I can't really figure what method/function to utilize to properly determine a file's length, beyond fstat.

Share this post


Link to post

Try this one: http://dl.dropbox.com/u/18609/Kex_Engine.zip

You'll HAVE to re-save this time. Basically I think it could be the padding issue. If this doesn't work then I'll have to implement a thorough logging system just for this.

Whats really annoying is that I can NEVER get any error to occur on my end. I really don't know whats going on.

Share this post


Link to post

Unfortunately, I'm still experiencing the same save bug from...well, the whole time. I started fresh, removed everything before testing.

Also, I have a bug that I had believed was just my ears or speakers until I tested it with good headphones. Occasionally the music will only play from the left speaker. I've only tested it on my Sound Blaster Live! 24-bit.

Anyways, I have a tiny piece of good news. The autoaim bug (where the aiming would get stuck, but not the view) is a confirmed fix on my end. Another confirmed fix on my end: intermission screen while set to 'padded'. Older verify, didn't realize it needed it still. Bonus: It even works flawlessly on my Nvidia Riva TNT2 M64 (Basically the only thing).

Share this post


Link to post
Akira_98 said:

Unfortunately, I'm still experiencing the same save bug from...well, the whole time. I started fresh, removed everything before testing.


Upload the savegame file once again and provide detailed repro steps. From launching game up to the crash.

If I can't fix this then I will either:
a. Release the next official build with this bug present
b. Don't release the next official build until this is fixed

This is starting to become a lost cause on my end due to being unable to reproduce the crash. Unless I redesign the entire savegame system, this will probably never get fixed.

Though next time if anyone gets this crash, post what operating system you're using.

Share this post


Link to post

Saves: http://www.megaupload.com/?d=5WFB4TOH
Sorry for the Megaupload, DRDTeam Fileshare doesn't want to cooperate at the moment.
Save "A": At the end of map01.
Save "B": At the beginning of map02.

Repro 1:
1. Launch Doom64.exe. (Or use the launcher, irrelevant)
2. Start a new game (any difficulty, again irrelevant)
3. Attempt to load savegame "B".
Crashes for me here. (Loading savegame from map02 while at map01)

Repro 2:
1. Launch Doom64.exe. (Same as last time)
2. Load "B" from the title screen menu. (This will work for me. All savegames work from title screen menu.)
3. Once "B" loads, attempt to load savegame "A".
Crashes for me here as well. (Loading savegame from map01 while at map02)

It's the same as before. Loading a savegame from the map it was saved on, or the title screen results in a successful load. Loading a savegame from any map other than the one it was created on results in a crash.

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
×