Problems with JDRP for Doom and jXCCP_123 for Hexen continue
All of the latest builds on my two computers (Win 7 64 bit, gtx680, i7 3770K and Win XP 32 bit, gtx560Ti, e6850) are still not compatible with the JDRP for Doom and jXCCP_123 for Hexen.
In Doom - in less than 1 minute of play it will freeze with the Windows error message “Doomsday.exe has stopped working” flashes on the screen. Usually striking any key will dump you back to the desktop. You may have to use Alt-Ctrl-Del and open the task manager then move its window out of the way to see this error message.
In Hexen – A “segmentation violation” will be displayed before the game can get started using the newest jXCCP_123.pk3. With the older jXCCP.pk3 it seems to be playable but some items to not seem to load e.g. rain, the clay pot in front of the player at the very opening screen of the first episode appears to be the original not the upgraded version.
Hopefully this will be easy to reproduce as everyone I have talked to that use these add-ons have had the same experience. However, none have an AMD cpu or video card, so I do not know if they will make a difference.
Heretic however seems to run just fine with jHeretic Resource Pack, JHRP-Garg.pk3 and JHRP.pk3.
The last build that runs all the games on the Doomsday engine on my machines including the add-ons that I am using (e.g. Rain & JXCCP_123.PK3 for Hexen and the JDRP for Doom) is build 857, for what that is worth. I am aware that eventually all of these kinds of problems will be addressed and if I can’t wait to play the Doomsday engine I will just load up Build 857 or one of the stable builds that works with these add-ons.
In Doom - in less than 1 minute of play it will freeze with the Windows error message “Doomsday.exe has stopped working” flashes on the screen. Usually striking any key will dump you back to the desktop. You may have to use Alt-Ctrl-Del and open the task manager then move its window out of the way to see this error message.
In Hexen – A “segmentation violation” will be displayed before the game can get started using the newest jXCCP_123.pk3. With the older jXCCP.pk3 it seems to be playable but some items to not seem to load e.g. rain, the clay pot in front of the player at the very opening screen of the first episode appears to be the original not the upgraded version.
Hopefully this will be easy to reproduce as everyone I have talked to that use these add-ons have had the same experience. However, none have an AMD cpu or video card, so I do not know if they will make a difference.
Heretic however seems to run just fine with jHeretic Resource Pack, JHRP-Garg.pk3 and JHRP.pk3.
The last build that runs all the games on the Doomsday engine on my machines including the add-ons that I am using (e.g. Rain & JXCCP_123.PK3 for Hexen and the JDRP for Doom) is build 857, for what that is worth. I am aware that eventually all of these kinds of problems will be addressed and if I can’t wait to play the Doomsday engine I will just load up Build 857 or one of the stable builds that works with these add-ons.
Comments
Even more recently, I was starting the first map of Alien Vendetta with candidate build #907 and when pressing the automap button, it just dimmed with no map showing, then as I was proceeding to play, it froze and crashed forcing me to bring up task manager to exit the game. I remember I had it paused for a long time by bringing up the menu with Esc since I was doing other things. So it seems to occur 1 minute into play if the play is active and it isn't paused in any way. Then I couldn't get it to run in the launcher. It said 'launching' but then the words 'launching...' disappeared it didn't launch, even after reinstalling the last stable build. So I had to delete the frontend to get it working again. Kind of a ridiculous amount of work. I better wait until the stable before downloading a new build. Hopefully the upcoming stable won't have this issue, or else I will have to remove frontend and reset my settings again.
When downgrading back to 1.10, it is necessary to use the "-reset" command line option as the persistent data created by the later 1.11 is not tolerated by 1.10. Starting with 1.11 this is not necessary any more however, for example if downgrading 1.12=>1.11 because the engine knows how to handle this particular error situation. (1.10 does not.)
I don't know if a proper Doosmday.out is generated to tell you the cause of the crash since it freezes with no error and I muct use the keys control+alt+delete to exit and then it says something like 'Doomsday.exe has stopped working', but here:
These crash every time:
* Cyberdemon attack
* Wolfenstein Nazi attack
* Shotgunner attack
* Lowering the minigun (from jdrp-packaged-20070404 with the animated lowering)
* Barrel explosion (the one from the jdrp 1.1 + "fixes" pack) (jdrp-packaged-20070404 barrels explode without crash)
These crash some times:
* Gibbing
* Trooper attack
* Mancubus death
There are probably some others, these are just what I've noticed.
EDIT: I have started build 917. After investigating the code further, I discovered yet more cases of hidden assumptions about the number of submodels present in rendered models or model definitions. Hopefully I have finally been able to locate all the issues...
EDIT: I successfully ran Hexen with jXCCP.pk3 (instead of the latest incompatible jXCCP_123.pk3) and the Doomsday.out had all the same errors as given below with jXCCP_123.pk3 EXCEPT for the undefined flags. Maybe that is the problem with jXCCP_123.pk3?
Also, too bad I can't just press a key to bring up the console now. Now I have to select the taskbar after going to options instead of pressing one key, not to mention that now if you want to go to the control panel, you have to take even more steps, but I can also just select joystick to more quickly get there.
Also, the texture overlapping problem still exists, but I did learn that I can delete the conflicting files in the texture pack PK3 after moving a copy over to another folder so I don't have to bother copying them under a jdoom folder since those commands in the custom options box are not doing anything.
On a side note, when typing in the post box on this forum as I'm doing now, the box isn't zoomed out enough to display the first character on the far left that I type and the scroll bar is only half visible on the right. Since the forum layout is a WIP, this is understandable.
Edit: Also, I notice that the automap does have a problem. It is stuck in the maximum zoom in position so the arrow appears massive. But I recall an automap arrow problem already being mentioned.
Shift + Esc is the shortcut to open the taskbar.
Post build 900, a second taskbar opening shortcut was added to Dday; the tidle key.
However, if you are upgrading from an earlier release, you need to manually add this second bind yourself:
Deng team plan to make Dday automatically update users configs with the second binding before stable release of 1.11.
I think the earlier gibbing issue was because of this. Imp has some fire particles spawned from it's hand which is submodel 1. And when it's gibbed, it's only got submodel 0.