steven84 posted on Sep 12 2004 at 04:52 PM said:had duke 3D been ported over yet for GP32? -should be more challangeing to port than wolf3D etc
But if you do that the smc will be many time rewritten, so it will not last so long I supposesteven84 posted on Sep 12 2004 at 06:52 PM said:you could try the old windows trick - convert free space into virtual memory , the atomic version of duke 3d was about 60-70mb to install (im sure using v memory direct from the card rather than usb would be faster)
Well, you might probably have some swap then... but apart from the fact that swap memory is a lot slower than standard memory (which would slow duke3d down as hell IMO), you'd have the OS overhead of linux, which would slow it all down to one barely usable mess.Wolfsclaw posted on Sep 12 2004 at 06:21 PM said:maybe when we can use extern HDDs over gp32linux... because they are so fast, stuff can be read from the hdd and be as fast as RAM.
No. it wouldn't. As far as I remember, the transfer rates for Smart Media Cards are between 250kb/s and 300kb/s - about a fourth of the USB1.1 transfer rate.steven84 posted on SEP 12 2004.06:52 OM said:you could try the old windows trick - convert free space into virtual memory , the atomic version of duke 3d was about 60-70mb to install (im sure using v memory direct from the card rather than usb would be faster)
From what I've seen of the engine, it is the most unholy hack imaginable. I wouldn't touch it if you paid me.Squidge posted on Sep 12 2004 at 06:45 PM said:I've looked at porting Duke Nukem 3D, but it contains a sizable chunk of intel assembler, which would need rewriting. It's questionable whether rewriting it in C would be fast enough, so it may have to rewritten in ARM assembly.
That would be awesome squidge! I'm sure you'd do Duke justice Hope they give you the source.Squidge posted on Sep 13 2004 at 06:59 AM said:Actually I believe it uses a similar amount of floating point as Quake does, so expect it to run just as fast. I've looked at the C source code, and it looks like they started from an empty file, and patched it until they got Duke3D. Not very nice to read at all.
Mind you, the BOR source code wasn't that pretty either, and that wasn't too difficult to port.
Hmm... Can't find the authors email address, so dropped a few requests in forums where the PocketPC version is being discussed, and we'll see if the source surfaces somewhere. I believe the license requires the source code to be available for any port.
Agreeed and than someone might take it off you once your stuck or give u some helpHooka posted on Sep 14 2004 at 07:18 AM said:I'd really like to take a look at it (I know, I'm not a coder but an interviewer) but I'd give it my best try and trying with lots of failure is better than not trying at all!
There are a lot of things I'd like to take a look at and try and get working, but I'm always confused by the sheer number of files, let alone anything else. Open one and I've not got a clue where it fits in, and often what its supposed to do (I'm not what you'd call *good* at C yet lol).Hooka posted on Sep 14 2004 at 07:18 AM said:I'd really like to take a look at it (I know, I'm not a coder but an interviewer) but I'd give it my best try and trying with lots of failure is better than not trying at all!