Come Get Some :)

[Alex.]

I have a Blu+ and shareware version. I replaced the file you said, but without any luck. Still, congratulations on the achievement, hopefully it won't be late until it will also run on the Blu+

 

[Vimacs]

try the grp from the shareware, nd/or try removeing the .dmo files from the .grp

 

[Alex.]

try the grp from the shareware, nd/or try removeing the .dmo files from the .grp

​

By using Game Extractor I found zero *.dmo files.

 

[Talyz]

Duke3D Zodiac

My NLU is broken, why I can't try it (I'm getting Jarska333's BLU+, though). Can anybody compar it to the Zodiac version.

Also, might be some interesting information for Woogal in this thread.

​

What do you think it was that reminded me to try porting this? . Haven't actually tried the Z version yet though.

​

I guessed so, but I wanted to point it out anyway. Did you use MetaView's source code?

 

[Quiest]

I have the right cons, I have the right cfg, I have the right grp (the same as Vimacs) but it still does not work.

Might be a BLU(+) problem now

 

[MIK]

it works *muhaaaa*

My Files
CRC Filename Size
98BE383F DEFS.CON 35.688 Bytes
2D021514 CDROM.INI 13 Bytes
94C5580E DUKE3D.CFG 4.693 Bytes
0E14908A DUKE3D.GRP 49.381.007 Bytes
C967DA38 GAME.CON 149.972 Bytes
14C89C80 USER.CON 43.471 Bytes

The Files are from Duke Nukem 3D Atomic For Winxp. Works on a nonflu GP with the cfg of Woogal.

 

[greven]

yeah i works, the problem is the .con, you were right.
COME GET SOME !!!

 

[Morgantium]

:huh: I have the original duke3D game, and duke it out in DC, but none of them are working on my Blu even with the con files and cfg that were posted earlier.

I wanna play Duke!

And the worsed of all I can't find my Atomic CD rom. Moved house twice since I last played it.

 

[Sonic-NKT]

i have a nlu and a blu+ and used one 64MB SMC
i have the cons which work (posted here) and the shareware wad.
It works great on the nlu
It doesnt work at all on the blu+ (restarts after 2 seconds or so)
so its a blu+ (dont know if normal blus work) problem.
i hope this gets fixed soon, cause its hard to play with my nlu in the evening

 

[Shikigami]

I'm beging you Woogal !!! make it playable on Blu and blu+ :mellow:

 

[Winterkid]

I hear you there. Appears the con files fixes all the non-BLU players, but BLU+ has problems.

I am still excited about the project though.

 

[dpoarch]

Yes! this is awesome. Got it working on my flu using the posted files by viamacs. good work woogal

 

[Morgantium]

Darn found my Atomic CD Rom, installed it and fired over the .grp from the atomic directory to my Blu and still no response. White screen and reset.
Please, please Woogal try to get the blu port for Duke working.

 

[woogal]

I can fix things if it works on a blu and the display is corrupt on a blu+, but it sounds like all blu and blu+ users can't even get to the screen init code so there's no display to fix. And I can't for the life of me think why there would be any difference that early on in the startup process between a blu and a flu or nlu. Let this be a valuable lesson to all you blu owners - my screen might be almost impossible to see, but when I can see it at least it's displaying something

I'll see what I can do. It might be as simple as dropping the gcc optimisation level down to 1. Using 3 I could get as far as the menu, and couldn't get the game running until I went down to 2. Maybe 1 will make it work on a blu, hopefully without slowing things down. If that doesn't work then I'm not sure how I can find the problem quickly as I don't have a blu.

 

[Franxis]

I can fix things if it works on a blu and the display is corrupt on a blu+, but it sounds like all blu and blu+ users can't even get to the screen init code so there's no display to fix. And I can't for the life of me think why there would be any difference that early on in the startup process between a blu and a flu or nlu. Let this be a valuable lesson to all you blu owners - my screen might be almost impossible to see, but when I can see it at least it's displaying something

I'll see what I can do. It might be as simple as dropping the gcc optimisation level down to 1. Using 3 I could get as far as the menu, and couldn't get the game running until I went down to 2. Maybe 1 will make it work on a blu, hopefully without slowing things down. If that doesn't work then I'm not sure how I can find the problem quickly as I don't have a blu.

​

Really extrange, compile with another version of GCC. Are you using 4.0.1 (DevKitARM r15)??? Please check 3.4.4 (DevKitARM r14). My MAME port does not run with 4.0.1 (devkitarm r15), but it runs ok with all previous versions.

Or maybe you could get a gp32 blu from a friend or...

 

[Franxis]

I'll see what I can do. It might be as simple as dropping the gcc optimisation level down to 1. Using 3 I could get as far as the menu, and couldn't get the game running until I went down to 2. Maybe 1 will make it work on a blu, hopefully without slowing things down. If that doesn't work then I'm not sure how I can find the problem quickly as I don't have a blu.

​

Maybe this is because size of executable is increased if you increase optimization level. I think Duke Nukem 3D should require a lot of memory.

 

[DaveC]

I can fix things if it works on a blu and the display is corrupt on a blu+, but it sounds like all blu and blu+ users can't even get to the screen init code so there's no display to fix. And I can't for the life of me think why there would be any difference that early on in the startup process between a blu and a flu or nlu. Let this be a valuable lesson to all you blu owners - my screen might be almost impossible to see, but when I can see it at least it's displaying something

I'll see what I can do. It might be as simple as dropping the gcc optimisation level down to 1. Using 3 I could get as far as the menu, and couldn't get the game running until I went down to 2. Maybe 1 will make it work on a blu, hopefully without slowing things down. If that doesn't work then I'm not sure how I can find the problem quickly as I don't have a blu.

​

It may be the firmware that is used. All BLUs use Euro FW (unless re-flashed). I have had things not work on a NLU that used Euro FW before too (BOR, Giana sisters). Hardware wise a BLU, NLU, FLU (not BLU+) all have the same hardware. I suspect it to be FW related.

 

[woogal]

Really extrange, compile with another version of GCC. Are you using 4.0.1 (DevKitARM r15)??? Please check 3.4.4 (DevKitARM r14). My MAME port does not run with 4.0.1 (devkitarm r15), but it runs ok with all previous versions.

​

I actually found the reverse was true with quake. GCC 4.0.1 (which I'm also using for duke) was much more stable than any 3.x version. Suprised me, but it was a nice suprise

 

[chris_r]

Does anyone know if its possible to remove unnecesary sounds or files from the grp because I dont have anywhere near enough space on my smc

 

[woogal]

New version has been uploaded (same place : http://gp32.sector808.org/duke3d.fxe ).

Should now work with shareware and other version 1.3 files without having to use the con files from the atomic version. There seems to be a little bug on the shareware version where the jetpack baddies never fly down, and if you shoot them the don't disappear. This doesn't happen on the atomic version. The files you need are - duke3d.cfg, duke3d.grp, game.con, user.con, defs.con. I think now you can actually play without any .con files and it will just use the ones within the grp, but I've not tested. It seems to be quite yerky outside sometimes, especially on the top of the building at the start of the first level. Going back to the menu and waiting for a few seconds can sometimes make it smooth again. Not sure what causes this.

I've also compiled this version with optimisation at level 1 as I mentioned earlier. This may or may not fix the blu problem. Give it a go and let me know if it works.