T2K and VLM emulator: updated 12/2/07 to version 0.06b
Well, ordinarily I would, but sadly I think it's a toolchain problem based on the digging into it I've done so far...
I'll leave the GP2X build now (that little jingle they've added to the bootloader is starting to get on my tits) and do the x86 Linux build next. Who knows, maybe I'll find something to blame on you in there?
I'll leave the GP2X build now (that little jingle they've added to the bootloader is starting to get on my tits) and do the x86 Linux build next. Who knows, maybe I'll find something to blame on you in there?
"I am a very considerate person. If I want to go out all night on my miniature golf course and shoot lizards, well, no reason to keep the neighbours awake..."
You might not want the next build then. That will really scare you, I've found some enthusiasm for upping the compatibility a bit and there's been quite a few significant rewrites in the core
.
Compatibility is miles up though. Not that anything else is playable yet mind, but most ROMS will start and make a passable fist of running the game.
Compatibility is miles up though. Not that anything else is playable yet mind, but most ROMS will start and make a passable fist of running the game.
Bring it on! Your code doesn't scare me! 
Didn't manage to get any more done to the GP2X build yesterday as I was out literally all day, but I've just done a smidge more just now.
It seems that the segfaults were down to the amount of BSS used (I suspected they might be as they moved to a different part of the code whenever I put some debug fprintf's in). So I replaced the obvious two large things-allocated-in-BSS with some mallocs and now it doesn't segfault, which seems to prove my theory. It doesn't work mind, so I've still got further work to do...
I'll see if I can bang out an x86 Linux version this evening.
Didn't manage to get any more done to the GP2X build yesterday as I was out literally all day, but I've just done a smidge more just now.
It seems that the segfaults were down to the amount of BSS used (I suspected they might be as they moved to a different part of the code whenever I put some debug fprintf's in). So I replaced the obvious two large things-allocated-in-BSS with some mallocs and now it doesn't segfault, which seems to prove my theory. It doesn't work mind, so I've still got further work to do...
I'll see if I can bang out an x86 Linux version this evening.
"I am a very considerate person. If I want to go out all night on my miniature golf course and shoot lizards, well, no reason to keep the neighbours awake..."
And here was you saying you wouldn't mind me BSS'ing a 24 meg block
.
You need to be very careful how you change those to pointers. There are dozens of sizeof(rom) and similar things knocking about you will need to fix. They have mostly gone away in the next version though because of the aforementioned 24 meg block option.
You need to be very careful how you change those to pointers. There are dozens of sizeof(rom) and similar things knocking about you will need to fix. They have mostly gone away in the next version though because of the aforementioned 24 meg block option.
Yeah... Well, now it appears I was talking out of my arse.Dio wrote:And here was you saying you wouldn't mind me BSS'ing a 24 meg block.
A 24 meg block should be fine as long as it's malloc'ed.
It should be fine in BSS, but I think the bods who've done the GP2X firmware have somehow bollocksed up the Linux ELF loader. I'm sure it should fail gracefully at the very least instead of fucking up and running your program anyway with sections overlapping and extending out of the task space. Perhaps they didn't know what some of the config options did? Actually, I should probably ask about that on one of the GP2X forums...
I'll have a good trawl through and look for them.Dio wrote:You need to be very careful how you change those to pointers. There are dozens of sizeof(rom) and similar things knocking about you will need to fix.
That's looking like quite an appealing change. Should make things simpler on the 68000 emulation front as well, and I doubt any machine that can reasonably be expected to run your emulator is going to have problems finding a free block of memory that size.Dio wrote:They have mostly gone away in the next version though because of the aforementioned 24 meg block option.
"I am a very considerate person. If I want to go out all night on my miniature golf course and shoot lizards, well, no reason to keep the neighbours awake..."
It's still a 24M BSS segment at the moment mind. I'll look at making sure it's malloc-able by the time it's ready to go out the door.Firefox wrote:That's looking like quite an appealing change. Should make things simpler on the 68000 emulation front as well, and I doubt any machine that can reasonably be expected to run your emulator is going to have problems finding a free block of memory that size.
Well, don't go to any trouble on my account.Dio wrote:It's still a 24M BSS segment at the moment mind. I'll look at making sure it's malloc-able by the time it's ready to go out the door.Firefox wrote:That's looking like quite an appealing change. Should make things simpler on the 68000 emulation front as well, and I doubt any machine that can reasonably be expected to run your emulator is going to have problems finding a free block of memory that size.
Hmmm, I've just gone through and fixed all of the sizeof(rom)'s and sizeof(ram)'s and now I'm back to a segfault but in a fixed place.
Actually, it's no wonder it sat there doing nothing when I'd quickly replaced the BSS declarations with mallocs as my shell code was loading all of two bytes from the ROM image before starting the emulator. Hoisted by my own sizeof()s!
"I am a very considerate person. If I want to go out all night on my miniature golf course and shoot lizards, well, no reason to keep the neighbours awake..."
I've been playing on v0.05 for a bit ... it's lightning fast, but it still lags every so often.
Is this out of the ordinary, seeing as my laptop is a:
P4 2.8 GHz
512MB DDR RAM
nVidia GeForce FX 5200 Go
Finally, how does the "mouse as spinner" option work? I enabled it, but it just makes the ship move uncontrollably. I'm sure I'm missing something fairly obvious here.
SiN
Is this out of the ordinary, seeing as my laptop is a:
P4 2.8 GHz
512MB DDR RAM
nVidia GeForce FX 5200 Go
Finally, how does the "mouse as spinner" option work? I enabled it, but it just makes the ship move uncontrollably. I'm sure I'm missing something fairly obvious here.
SiN
From the title screen, press X to go to the game select screen. Press 'O' and the options screen appears; then press 'P' and an extra option will appear "Controller type". Go into that menu and select 'P1 Rotary".SiN wrote:Finally, how does the "mouse as spinner" option work? I enabled it, but it just makes the ship move uncontrollably. I'm sure I'm missing something fairly obvious here.
It's not much fun on a mouse (I've found). It just about works on a spinner but I've not spent the time calibrating it that it really needs.
As to the pauses, if your machine goes away to do something else then you'll get a single pause of a second or two just like any other game.
- Kelloggs
- Baaaaa!

- Posts: 1859
- Joined: Wed Jun 22, 2005 11:38 pm 0
- XBL Gamertag: TheAntiKelloggs
- Location: Widnes or Altrincham. Take your pick.
I've found what I think could be a bug in the 0.05 Wintel code, but I can't remember how the Jag does it, and it's at home and I'm not: between levels, does yon breathy woman say "Superzapper Recharge" every time? I'm only getting it coming off a Warp Bonus level, not in between regular levels.
If this is how the Jaguar did it, please ignore me, but I don't remember it being quite so quiet...
If this is how the Jaguar did it, please ignore me, but I don't remember it being quite so quiet...


