Everything to do with our favourite pastime! Reviews, recommendations, sells/swaps, problems etc. Whether they are on the latest consoles, arcade or retro classics. It's not the winning or losing, we came to play!
I was looking at the code for the Linux version on Sunday and it's a bit of a mess in places. I'll do another version starting again with your 0.05 sources. I'll do a neater job now I understand how it works.
So D2k runs on it now then...?
In other news: Bloody hell, the 68000 instruction encoding is a right nightmare, isn't it?
"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..."
D2K runs, and looks tolerably good, but the game logic is rather screwed up and I've no idea where to go to fix it. Not a high priority project right now.
Not even a hint of slowdown that I noticed. Awesome work!
P.S. You bastard! I was supposed to be in bed half an hour ago!
"even had I suspected then the truly horrifying suffering and amazing loss of life that would be caused by our well-meaning enterprise... I'd have done it anyway. Only more so." Lagertron for Android It's Robotron at the pub! My stuff
Do you know how much I hate dialog boxes and DirectInput???
I'll add it to the list. You were one of the people plagued by F1 hangs before, weren't you?
I knew that would fix it. Crappy nvidia drivers. Then again, what I was doing (reinitialising D3D from inside a wndproc, which then also caused it to initialise itself again without shutting the first partially complete initialisation down) was not very legal.
Dio wrote:Do you know how much I hate dialog boxes and DirectInput???
I'll add it to the list. You were one of the people plagued by F1 hangs before, weren't you?
I knew that would fix it. Crappy nvidia drivers. Then again, what I was doing (reinitialising D3D from inside a wndproc, which then also caused it to initialise itself again without shutting the first partially complete initialisation down) was not very legal.
Yeah, but I've also updated the drivers since then (I think).
Hmm.. Every since I got my PC back from my brother, it's come up with 'failed to clear back buffer' on versions .3, .4 & the new release.. any idea what he might've done to my pc? (Athlon 1.7g, nvidia geforce4 mx420, 256mb ram running XP)
Bollocks. I thought I'd completely cleared that problem on this version. It certainly should be fixed on Radeon 7500 and I thought I'd fixed it on all DX7 cards.
If I can turn up a GF4MX I'll see what I can do. That said, don't have an AGP debug target any more so it might be tricky .
Dio wrote:Bollocks. I thought I'd completely cleared that problem on this version. It certainly should be fixed on Radeon 7500 and I thought I'd fixed it on all DX7 cards.
If I can turn up a GF4MX I'll see what I can do. That said, don't have an AGP debug target any more so it might be tricky .
'Tis strange, as the previous versions used to work on the swame pc.. I'll have a fiddle with my options and see if I can sort it.. Out of interest, what does the 'unable to clear buffer' actually mean, to an idiot like myself?
guythp wrote: 'Tis strange, as the previous versions used to work on the swame pc.. I'll have a fiddle with my options and see if I can sort it.. Out of interest, what does the 'unable to clear buffer' actually mean, to an idiot like myself?
It's failed a D3D stretchrect call. In the old version, this was on DX7 ATI cards, that exported 0 for stretchrectfiltercaps when I was always selecting POINT. If I had to guess wildly, I'd say your card is exporting 0, but expecting POINT anyway. If you know what the D3D caps viewer is, then you could look it up for me, but if you don't, you can't.
guythp wrote: 'Tis strange, as the previous versions used to work on the swame pc.. I'll have a fiddle with my options and see if I can sort it.. Out of interest, what does the 'unable to clear buffer' actually mean, to an idiot like myself?
It's failed a D3D stretchrect call. In the old version, this was on DX7 ATI cards, that exported 0 for stretchrectfiltercaps when I was always selecting POINT. If I had to guess wildly, I'd say your card is exporting 0, but expecting POINT anyway. If you know what the D3D caps viewer is, then you could look it up for me, but if you don't, you can't.
Nope, tried a quick google on failed D3D but looked blankly at the screen with my tongue poking out..
I've downloaded the new DirectX to no avail, so I'm gonna get the newest drivers for my gfx card. Failing that, I'll update everything. Should that not work, I'll just wait until I'm back in my house and get get up to the atic to get me jag out.. Emulation's chuffing great, but you can't (as they say) beat the real thing