Two9A

Sure, if it can get from the title screen to the game itself, it'll all run fine. Nothing comes up because all the blocks are drawn onto the second background, and I only draw one background right now. The GPU is on the back burner right now, but don't worry. It'll be back.

Oh believe me, it's gonna be a long time before games actually start working. And I don't have a GBA or a DS, so I have no legal reason to own backup ROMs. If you wanna test some, then please do; be aware that I make no guarantees for the safety of your computer, house or sanity.

Yer know, I've never seen the point in skinning for applications like that. I use a plain audio player with no skins, but a heck of a lot of features (which is more important ) Hell, if you want to make it skinnable, go right ahead; the code's out there. You weren't wide of the mark, sir; just about spot on. User interface issues don't tend to plague me so much as a broken GPU.

It's great to see that you're interested in what's going on here, mate. It helps me to see what I do being commented and improved on by other people. As regards first.bin, it's weird. Sometimes it runs on some boxes, and then it'll crash on the same boxes. And for some, it simply refuses to run. I'm guessing there's a certain memory blockage somewhere that I'm just not catching.

Yep; the LDM tests aren't in the ROM yet, so that's why those screens show up blank. And my Thumb ALU is broken beyond belief, has been for a long time. I don't understand this one. Everything shuts down fine, then the application jumps to some random place where there's obviously no code. Makes absolutely no sense, and warrants detailed investigation. Another weird one. I thought I was catching the instance when the command line is a full path, and not adding anything to it. Obviously this isn't the case.

A log.txt is created, but you'd be surprised where it goes. I honestly don't have a clue where Windows would put it. From this, I have learned one thing: Don't trust Windows to give you the path to your exe when you ask for the current directory. Instead, ask for the path to the exe Should be all fixed now. Download it and try it out.

It's good to see that people are excited by the prospect of this stuff actually working. Could be a while before it is, of course, but I don't mind that at all. By those, I'm guessing you mean X/Y. There's a slight issue with those.. Nintendo decided not to map them into the standard Keys register, but on the second CPU. Why, I have no clue; the general concensus is that it's a strange decision. Hence, it could be some time before those work. (If you mean the touchscreen, that has the same root issue, being mapped onto the sub CPU.) Er, I can't actually.. remember. Whatever they are, they should be the same as VBA's defaults. I really should do something about that key-input dialog box sometime.

Right, I can see there's gonna be issues with OpenGL and everyone's computers. I'll add some kinda fallback to GDI if OpenGL init fails, I think; that should cover everyone. I'm about to investigate the issue with the dragging of the file; should work fine though

Ok, that's not what I was expecting, to be honest. I was hoping it'd be a problem with OpenGL; at least I've verified that to occur. Looks like a CPU core issue, but that can't be right, since it runs fine here. Now I'm confused

Let's not discourage anything here. If you wanna help out by running stuff, kevin, go right ahead. The more, the merrier when it comes to this. Of course, it'd be nicer if someone wanted to write a GPU for me..

Actually, it would help a little if you could throw up the log.txt; grab the newest Zip, and see how that does.

I've received this error from another source, so I know it does happen on a fair few boxen. Why it happens exactly, I have no clue; the error message should mean the DLL has been unloaded from memory and won't be referenced again, and yet it is being referenced again. That's a brand new one on me, I'm afraid, and I can't reproduce it here. I'll have to hope that resolves itself. Yeah, there's a reason behind that. I can't get the OpenGL resizing constants right without a magic number that only applies to the original window size; if you resize, you'll get a small region where the texture won't reach. I can fill it in black if you like. Thanks for the help; much appreciated.

Significant progression will occur in tandem across both cores. Since they share a CPU and almost everything else right now, there's no reason for the tandem not to continue.

Because the "good" one, which wasn't so good in the first place, went all wonky and then died. Being on a slow box will eventually be incentive for me to write that dynarec, so don't worry. All will be well. There may be issues with OpenGL and selecting a texture context; I know at least one person who got back to me on that. Problem is, it shouldn't crash, just bail out. I dunno what's going on there.

There is of course, one problem. I don't have that much RAM here; before long, I'll be heading into the realms of using swap space to run the emulator. And that's when things get dog slow.

It seems that I KEEP running out of VRAM. I pushed the allocation up to 128k the other day, and I've just had to push up to 256k. I'll be in the megs before long. Should be all good now

Did ya press F4? Sometimes, I mod the INI file, and I leave LoadAndRun at 0 in the final package. Yeah, the Thumb ALU is really broken right now. I'm gonna do some work on replacing it with some assembly in the near future. Mm-hm; I've been told this is the case. It's great

After a short investigation, I am forced to agree with you. My drive is riddled with PariteB. Hope you didn't get infected too hard; I should be clean now. I can only hope the few others who downloaded are ok, and don't hate me.

You know, I was just talking about this with someone. We came to the conclusion that collaboration on projects of this kind would be bad; there'd be a lot of discussion and not much happening. Friendly competition is a much better way to get results; I just have to make sure it doesn't turn into a full-blown fight

Ok, maybe there was a period of about an hour when it was all broke, but should be fine now. You seem to be getting luck with the downloading of broken code

I've covered this in the past. I honestly don't mind someone making all the money they like out of my emulator; since it is released under the BSD licence, nothing prevents them from doing so, just as long as they maintain the copyright notice. Last time I checked, the guy had done so. I only have one complaint; I really wish he would update. I get all sorts of email from people saying v0.0.1a doesn't load anything; I've known this for months now. $edit: Maybe I should say "she would update", since Kai says xAix is female.

Insanity and madness. I wasn't expecting output, especially with the screen being the wrong size, in the wrong place in memory, with the wrong modes. But this is good! And I have a sneaky suspicion that the rest of the screen is only missing because there's only code for one background in gpu.c; this might be motivation to crack on with finishing up on the GPU. Yeah, I wouldn't recommend running GBA games through the DS dll (or vice versa, either). There probably isn't a way to totally exclude the possibility of it happening, though.

Either you check the page a heck of a lot, or you just hit lucky to catch me between putting the news post up and hacking the new archive Makefile.Well done That is far too clever an idea for me to come up with. I was gonna have maybe two options on the File menu (Load GBA, Load DS), but that's nice. I'll have to look into it.

To be perfectly honest, I don't think it's possible to compare the two. I've been working on producing an accurate core and neglecting the graphics a little, whereas Firefly's been getting 3D output and neglecting the core a little. Having said that, Firefly has previous in this area, so I'd expect him to be further ahead in total than I am right now. I might have to start putting a DS memory map together, see if I can catch up.

Well, not quite. I got bored, and added the original non-affiliation message to the About box. Grab the latest zip, have fun.