Come Get Some :)


i think sound effects make the 1st person shooters great, not the music. All the first person shooters on the Jag didn't have music and Doom was excellent and AVP is still one of my favs of all time and it really gave the game the mood of actually walking around the cooridors, if you were running around you would not have music around you all the time. :p
 
Um probably pointless for me to post this but it doesn't work on my BLU either :( I have used all the correct con & cfg files adn tried it with the shareware and atomic versions.

This is awesome work though and should be commended. If you can get it working properly on BLUS with sound I shall be the happiest little mungbean who ever lived :)
 
Sorry to keep you waiting guys. Not had as much time to work on this as I thought I would. I think I've discovered another issue that may be linked to the blu instability and that is compressing with spiv's b2fxec. I've been playing around with the code a little, and a compressed fxe will sometimes crash randomly for no apparent reason, but an uncompressed fxe will work fine.

So, here finally is a version that may (or may not) work on a blu (if it works on a blu+ it will probably have that white bar thing). Because I've dropped the image cache down to 1 meg it means that things take a little longer to load. You will now have to wait around 20 seconds with a white screen, followed by 9 seconds of a black screen, then you will (might) see the first logo. After that things won't be too bad and the only real delay should be level loading.

http://gp32.sector808.org/duke3db.fxe (don't bother downloading if the last version worked fine for you - this has no new features and is just a blu test)

Sound is being worked on (leaving the music for now as it's not as important), but when the sound stuff was originally ported to sdl it looks like they used a very nasty hack which makes it very unstable on the gp32. So far I can hear sounds on the opening animation, but it crashes before I even get to the menu.
 
Woogal i think a good solution to all is post a package with all needed files. I mean the .cons and the shareware .grp. Because i am thinking a lot of ppl, me include, so confusing with all post about the files.

Go to try the new .fxe
 
woogal posted on Oct 3 2005 at 08:30 PM said:
So, here finally is a version that may (or may not) work on a blu (if it works on a blu+ it will probably have that white bar thing). Because I've dropped the image cache down to 1 meg it means that things take a little longer to load. You will now have to wait around 20 seconds with a white screen, followed by 9 seconds of a black screen, then you will (might) see the first logo. After that things won't be too bad and the only real delay should be level loading.

http://gp32.sector808.org/duke3db.fxe (don't bother downloading if the last version worked fine for you - this has no new features and is just a blu test)

Sound is being worked on (leaving the music for now as it's not as important), but when the sound stuff was originally ported to sdl it looks like they used a very nasty hack which makes it very unstable on the gp32. So far I can hear sounds on the opening animation, but it crashes before I even get to the menu.


Taking longer to load is fine. If it doesn't work then it wouldn't matter how fast it loads :p
 
Last edited by a moderator:
still reboots my blu+ like the older releases, nothing changed for me.
Argh i want to duke on my blu... :(
 
Yes, i get a rebooot and now the load time get more time, sure because the size of the fxe.

Greetings
 
mgiht it be an smc size issue?


I recall there being one of them for a certain port one time
 
hmm no i dont think so.. i have a nlu and a blu+ and the game is on the same smc.
anyway i have 2x64MB
 
I've just tried the latest version, with the files given in this thread, in the geepee emulator using a smc image with my BLU firmware. GeePee crashed out (not the duke3D crashing, the actual emulator crashed).
 
Hmmm, ok, back to the drawing board :(

GP40 posted on Oct 4 2005 at 04:07 PM said:
I've just tried the latest version, with the files given in this thread, in the geepee emulator using a smc image with my BLU firmware. GeePee crashed out (not the duke3D crashing, the actual emulator crashed).
Crashing is the one thing geepee does really well ;). Doesn't prove anything unfortunatly as even very basic programs can sometimes cause geepee to crash.
 
Last edited by a moderator:
Woogal why don't you put a button wait after each init part of the code, so people can work out exactly where the crash is?
 
Because that would completely defeat the point of deliberately causing it to crash so I can con a free blu out of someone... er.. bugger, where's that edit button..

But seriously, yeah you're right. I think displaying the current position and pausing is the only option left (and I was so sure that last version would fix things :(). There's so many places it could be crashing though that I think I'll release a version with rough break points, then keep releasing further versions refining each time until I track it down.
 
Woogal, one of my friends has a FLU version and he tell to me the load of the port it gets over 20 seconds with white screen. In the case of my BLU that happends only during 3 or 4 seconds.

My friend told to me the BLU hardware has some new feature about the control of energy it can eat. I hope that things can help to you in some...

Regards ... RST
 
Back
Top