Come Get Some :)

[A600]

A suggestion: upload a fxe with the overclock disabled.

 

[Vimacs]

it isnt overclockd....
learn to read...

 

[woogal]

Anything less than 133mhz isn't overclocking, and duke runs at 132mhz

 

[A600]

Anything less than 133mhz isn't overclocking, and duke runs at 132mhz

​

I think those 132 Mhz are the problem. 132 isn't a standard overclock speed. Furthermore, you said 156 was slower.

it isnt overclockd....
learn to read...

We'll see who is the "smart guy" here. :angry:

 

[Vimacs]

132 is the standart speed, most software uses it...

 

[woogal]

I think those 132 Mhz are the problem. 132 isn't a standard overclock speed. Furthermore, you said 156 was slower.

​

The settings I'm using are 132000000,0x3a011,3 which I've used for anything I've ever done that runs at 132mhz. Usually when you see something on the gp32 that says it's 133mhz it's actually using those settings. I don't think there's a single gp32 in existence that won't run with those clock settings. Oh, and there's no such thing as a standard clock speed .

 

[aapje89]

Anything less than 133mhz isn't overclocking, and duke runs at 132mhz

​

I think those 132 Mhz are the problem. 132 isn't a standard overclock speed. Furthermore, you said 156 was slower.

it isnt overclockd....
learn to read...

We'll see who is the "smart guy" here. :angry:

​

OMG rtfm man!

 

[barnesy]

It seems I can get the game to launch OK using the atomic edition .GRP and .CONs, and either my own or Woogal's .CFG file. But when I start a game in any episode, I just get the first frame (so the crashing ship just hovers in the air n the first episode). Nothing moves, but the menus continue to work. Anyone else had (and hopefully overcome!) that problem? It's so tantalisingly close!

 

[Cyclops]

Anything less than 133mhz isn't overclocking, and duke runs at 132mhz

​

I think those 132 Mhz are the problem. 132 isn't a standard overclock speed. Furthermore, you said 156 was slower.

it isnt overclockd....
learn to read...

We'll see who is the "smart guy" here. :angry:

​

OMG rtfm man!

​

Be nice

 

[DaveC]

So it's getting to the gfx init? Didn't think it got that far in only a few seconds, but that still doesn't explain why it doesn't work on a normal blu. Can't create a blu+ version just yet as it means recompiling chui's SDL lib with the blu+ stuff enabled (it's in there, but you have to enable it then compile a blu+ version) and I can't get it to compile with the version of gcc I'm using. I think chui might have used an older version that isn't as strict with certain bits of code. I've just sent chui an email asking if he can compile a blu+ sdl version for me.

​

On my BLU the screen just goes white for a few seconds, flickers for a second like it is loading something, then resets. I never get anything close to an image on the screen. This is the first time I have heard of something running on a NLU and not a BLU.

Ihope this can be fixed, it sucks not being able to try it even if it has no sound.

 

[Shikigami]

+1 DaveC

 

[gp32rich]

Here's something wierd :/

I have a working install, then last night .. it doesn't load.

Hmm. Maybe my not-so-freshly-charged batteries don't like 133Mhz?
I try Castaway, that's fine. So I reset, try Duke .. Oh! Now it works! :S :huh:

 

[craigix]

This happened once with doom, was a compiler setting. Some of you may remember doom not working with some gp32's, i think it was version 7 or 8.

I had to stop using -o3

Then mysteriously it just went away by itself after a few code updates and -o3 was working again, then randomly it would come back.

Rob then went up a GCC and the mystery was never solved. I think we all need closure now with it happening with duke

 

[Angel]

all i know is it works great on my FLU. Thanks Woogal.

 

[GP40]

Dont work on my BLU :/

Is there anyone with a BLU that has a FLU that does load Duke3D?

If so this might be a good test:-

1. Complie an smc image using the smc maker.
2. Try running Duke3D with the FLU firmware.
3. Try running it with the BLU firmware.

If it runs on the FLU but not on the BLU, it'll show it is the BLU firmware

EDIT: of course I mean anyone with both a BLU and FLU, not anyone who owns a BLU and the BLU owns the FLU :lol:

 

[DRK]

I dont think that its the FW, i have the newest EU FW on my flu and this FW is also for BLU GPs.

 

[Quiest]

Dont work on my BLU :/

Is there anyone with a BLU that has a FLU that does load Duke3D?

If so this might be a good test:-

1. Complie an smc image using the smc maker.
2. Try running Duke3D with the FLU firmware.
3. Try running it with the BLU firmware.

If it runs on the FLU but not on the BLU, it'll show it is the BLU firmware

EDIT: of course I mean anyone with both a BLU and FLU, not anyone who owns a BLU and the BLU owns the FLU :lol:

​

Read carefully and you will notice that someone already mentioned that it`s not running on his BLU(+?) but on his FLU(NLU?) with the same smc.

 

[Angel]

i got an old version of Aquafishs mf booting into whatever supplied European firmware came with it and it works fine on my FLU.

YAFL ROCKS!!!

 

[GP40]

Dont work on my BLU :/

Is there anyone with a BLU that has a FLU that does load Duke3D?

If so this might be a good test:-

1. Complie an smc image using the smc maker.
2. Try running Duke3D with the FLU firmware.
3. Try running it with the BLU firmware.

If it runs on the FLU but not on the BLU, it'll show it is the BLU firmware

EDIT: of course I mean anyone with both a BLU and FLU, not anyone who owns a BLU and the BLU owns the FLU :lol:

​

Read carefully and you will notice that someone already mentioned that it`s not running on his BLU(+?) but on his FLU(NLU?) with the same smc.

​

Dohhhhhh!!!!! I missed out a big chunk of what I meant :wacko:

I meant to say try it with the different firmwares in the geepee32 emulator. That should tell you if its the BLU firmware or the hardware, and you would be able to see the register content etc

 

[rst]

Ok, but really this is the first time some program work in FLU and not in BLU ???

Really strange...

Greetings ... RST