[Gorilla]

Gorilla, on 03 December 2022 - 12:16 AM, said:

Sorry to be tardy to the party gentlemen, but has any one of you einstein-types made the level editor work yet? I dont know jack from jill but if I could figure a way to cook up a level of my own and load it into the game i'd be more than willing to try and learn the old magic.

Sorry for the double post, I answered my own question - the heaven sent kingly fellows remaking Duke4 have fixed us up a nice little slice to try out. It's more than enough to answer my question. If anyone else somehow has missed out on this dopalicious new development, look no further than right here

Now.... if anyone has any footage of them working around and showing off all the wonderful features....THAT'D be a treat

EDIT 3 - okay I also found just that and in case anyone else is a dipshit like myself but is also interested, viola

[MusicallyInspired]

[Ninety-Six]

I'm very curious about the story they're building. It seems like they're going with the original concept of it being a parasite, before the DN3D aliens were brought in. Which is an odd choice since by the 2001 version the aliens were back.

I did see a few Pig Cops in the trailer but that doesn't necessarily mean anything. Those guys show up in every game whether it's the DN3D aliens or mutants or whatever.

[JohnBlade]

MusicallyInspired, on 17 December 2022 - 09:10 PM, said:

Amazing work!

So what is going to happen on 21st December? Do we get to try some sort of beta?

[Mr. Tibbs]

[DisgustedGrunt]

MusicallyInspired, on 17 December 2022 - 09:10 PM, said:

First slice is out
https://www.moddb.co...-first-slice-10

[MusicallyInspired]

Hope everyone enjoys our hard work on the First Slice over the past several months! It's in a much more stable state than the initial leak and the playability of the levels is just incredible. There's still a bit of residual jank though so beware of that. I'm really excited to continue working on it next year after the holidays!

I'm also putting together some of the new music I wrote for it and will be uploading it to YouTube and for download some time today.

Also, a disclaimer on the current release from the team in relation to said jank:

Quote

Alt-tabbing is broken and we're lookin at it soon! we recommend playing in windowed if you need to multi-task. also, make sure your directory has no spaces or non-english characters in it!

[Outtagum]

Duke's face looks like it got the Mickey Rourke treatment.

[fofo.rider]

Thx !

[JohnBlade]

MusicallyInspired, on 21 December 2022 - 12:31 PM, said:

Hope everyone enjoys our hard work on the First Slice over the past several months! It's in a much more stable state than the initial leak and the playability of the levels is just incredible. There's still a bit of residual jank though so beware of that. I'm really excited to continue working on it next year after the holidays!

I'm also putting together some of the new music I wrote for it and will be uploading it to YouTube and for download some time today.

Also, a disclaimer on the current release from the team in relation to said jank:

Thank you so much for this release and big kudos to the rest of the team - it turned out much better than I could ever hope for.

I noticed couple of bugs including in the renderer - where is the best place to report those bugs?
I'm happy to report them on regular basis.

I can't join your discord though - it forces me to verify via a phone number with my current Internet service provider.

Btw is there a better way to take screenshots rather than the integrated system using F10 key? It freezes the whole game for like 5 seconds and generates couple of megabytes bmp file...

[MusicallyInspired]

I'm not really sure. The Discord is currently the best place but if that's out of the question then I guess post it here. Or maybe just DM me and I'll pass it along.

If you're on Win10 try Win+Shift+S and select "Window Snip" at the top to capture the entire window. Or press Win+PrintScreen and it'll take a fullscreen shot and save it to the clipboard. You can also just press PrintScreen if you're on something earlier than Win10.

[MusicallyInspired]

Realized I never dropped this here yet. And since this forum can't handle YT playlist embeds, here's just a link to the playlist and an embed for the first track:
https://www.youtube....Sbqs2GRvINxuzem

[Malgon]

Just finished listening to Rooftop and it's really great work! Going through the rest of the playlist now. Keep up the good work!

[The Albino Ape]

Not Duke related but the 1995 build of Prey just leaked...

https://archive.org/details/prey-1195/

[JohnBlade]

MusicallyInspired, on 23 December 2022 - 10:23 AM, said:

I'm not really sure. The Discord is currently the best place but if that's out of the question then I guess post it here. Or maybe just DM me and I'll pass it along.

If you're on Win10 try Win+Shift+S and select "Window Snip" at the top to capture the entire window. Or press Win+PrintScreen and it'll take a fullscreen shot and save it to the clipboard. You can also just press PrintScreen if you're on something earlier than Win10.

Would you mind if I asked admins to setup a section for your mod in "Free hosted forums" and just report it there? I'm quite sure others would follow. 1 bug = 1 topic

[MusicallyInspired]

JohnBlade, on 26 December 2022 - 04:11 AM, said:

Would you mind if I asked admins to setup a section for your mod in "Free hosted forums" and just report it there? I'm quite sure others would follow. 1 bug = 1 topic

No, I don't think that's really appropriate. The rest of the mod leads are not even on this forum which means I'd probably be the one maintaining it and I don't want to do that lol. I've got enough to do.

[Malgon]

Seeing all the recent releases of Prey 1995, Duke Nukem Endangered Species, and the DNF 1996 prototype, it seems there's more chance than ever of the later, more complete version of DNF being released as well. I'm guessing this is something that is an ongoing discussion for the DNF restoration team in the event of this happening (and probably was discussed before work on the project even began), and that there's a plan to easily allow the team to transition to the later version? It'd be a shame to lose any of the hard work completed so far, although I'm sure there would be ways to utilise it somehow and therefore minimise the losses.

[JohnBlade]

MusicallyInspired, on 26 December 2022 - 05:17 PM, said:

No, I don't think that's really appropriate. The rest of the mod leads are not even on this forum which means I'd probably be the one maintaining it and I don't want to do that lol. I've got enough to do.

How about posting it here? https://gitlab.com/D...mirror/-/issues

Is it your repository? Or where do you share your work? If you do not wish to post it publicly feel free to PM me I would like to help this project somehow.

[MusicallyInspired]

We aren't going to be updating that repository on a regular basis so posting issues there would be pointless. Development is all private. Also a lot of the issues we're already aware of. The renderer especially is unfinished in a multitude of ways and is still being worked on. I'd say sit tight for now. When the time comes for another release we'll see what we can do about playtesting though. But that won't be for a while.

[JohnBlade]

MusicallyInspired, on 29 December 2022 - 11:14 PM, said:

We aren't going to be updating that repository on a regular basis so posting issues there would be pointless. Development is all private. Also a lot of the issues we're already aware of. The renderer especially is unfinished in a multitude of ways and is still being worked on. I'd say sit tight for now. When the time comes for another release we'll see what we can do about playtesting though. But that won't be for a while.

OK fair enough - when you are looking for more testers happy to help out - just PM me here.

Thanks again for great Xmas present

[MusicallyInspired]

Well look at that. I wake up to find this:

Quote

We now have a proper Issue Board for logging bugs you run into. https://gitlab.com/t...ic-issues-board

Please read the Readme on the front page for proper issue format. any issues without proper formatting or labels will be deleted

[protivakid]

I've tried the leak from Archive.org and moddb yet I can't get it to work on my Windows XP rig. P4 3.4 HT, Radeon X1800.

When the game first boots I get an Entry Point Not Found Error for "QueryFullProcessImageNameW" in KERNEL32.dll that I can click OK to which brings me to the menu.


When I go to select a level however the game crashes with a "exception_int_divide_by_zero" error from UnCanvas.cpp.


Anyone else experience this? Google came up dry.

[protivakid]

Ok, so none of the pre-built builds seemed to work for me, however I followed the instructions in the archive to manually build under Windows XP and now am able to run the game.

Two issues, the menu looks like this, not sure if this is an issue others have had?



And second issue, the game seems to be missing objects. For example, in this screenshot the game knows there's a shower head there, but doesn't actually render it. has anyone else experienced this? The videos online seem to show a much more stable experience than my own.

[Green]

protivakid, on 18 April 2024 - 12:16 PM, said:

Ok, so none of the pre-built builds seemed to work for me, however I followed the instructions in the archive to manually build under Windows XP and now am able to run the game.

Two issues, the menu looks like this, not sure if this is an issue others have had?



And second issue, the game seems to be missing objects. For example, in this screenshot the game knows there's a shower head there, but doesn't actually render it. has anyone else experienced this? The videos online seem to show a much more stable experience than my own.

This happens due to the game falling back to the software renderer, typically it occurs when running in windowed mode.

To remedy this go to your \Players\(YourProfileNameHere)\ directory in your Duke Nukem Forever folder and modify the following line in the DukeForever.ini file under [Engine.Engine]:

Quote

WindowedRenderDevice=SoftDrv.SoftwareRenderDevice

to

Quote

WindowedRenderDevice=D3DDrv.D3DRenderDevice

Ensure the GameRenderDevice and RenderDevice lines are also set to D3DDrv.D3DRenderDevice, and you should be good to go. The .ini files in the profiles are generated from default.ini in \system\ and as such another method to achieve the same result is making the above change in the default.ini prior to running the game for the first time and creating a profile.

[protivakid]

Green, on 18 April 2024 - 03:59 PM, said:

This happens due to the game falling back to the software renderer, typically it occurs when running in windowed mode.

To remedy this go to your \Players\(YourProfileNameHere)\ directory in your Duke Nukem Forever folder and modify the following line in the DukeForever.ini file under [Engine.Engine]:


to



Ensure the GameRenderDevice and RenderDevice lines are also set to D3DDrv.D3DRenderDevice, and you should be good to go. The .ini files in the profiles are generated from default.ini in \system\ and as such another method to achieve the same result is making the above change in the default.ini prior to running the game for the first time and creating a profile.

First off, I really appreciate you taking the time to reply. I double checked this and unfortunately those values are already set so that's not my issue. I am using an X1800 with an ATI driver from 2006 on the XP rig so I'm wondering if it's simply "too new" for 2001 Duke. The game only detects my card as a "D3D device" instead of its actual name, and to even see it I have to click into the extra devices radio button.

[protivakid]

protivakid, on 18 April 2024 - 05:02 PM, said:

First off, I really appreciate you taking the time to reply. I double checked this and unfortunately those values are already set so that's not my issue. I am using an X1800 with an ATI driver from 2006 on the XP rig so I'm wondering if it's simply "too new" for 2001 Duke. The game only detects my card as a "D3D device" instead of its actual name, and to even see it I have to click into the extra devices radio button.

Still working on this issue. Have another XP Athlon rig with a GeForce2 MX100. The October build did the exact same thing as my X1800 P4 machine, and the setup doesn't see my video device either. The odd thing is when using the August build the game does properly detect my card on this 2nd machine. Using Nvidia drivers dated 2006 so again wondering if this is leading to my problem. On the Athlon rig the game did work fine directly from Archive.org without me having to compile it so progress I guess?

Also tried both the Duke Nukem Forever Restoration Project 0.2.1 (Duke It Out Patch) & Duke Nukem Forever Restoration Project Standalone (First-Slice Demo), yet both complain about not being a "valid Win32 application". The notes talked about running on original hardware but my guess is these were compiled for 64-bit only.

[protivakid]

Just sharing that I did FINALLY get this working on both older XP rigs of mine. The solution ended up being the deletion of d3d8.dll, d3d8.on12.dll, & d3d8.wine.dll in the system folder. After that the game ran fine with all models now shown. Hope this helps someone else.

[protivakid]

Another question. On my GeForce2 MX100 XP machine the visuals show as expected, however on my ATI X800 XP machine, when I run out of ammo and default to the boot, this is what I see... Any ideas? There are other artifacts that take over the screen at times as well on the ATI card machine.