Made more improvements to the ViRGE emulation - better subpixel correction removes most polygon gaps, fixed issues with mipmapping, and implemented dithering (though as ViRGE dithering is extremely poor this will be optional). Annoyingly, it's getting difficult to determine whether rendering issues ...

Because the forum was misconfigured. Seems to be working now - fingers crossed that it remains that way!

Please refer to my previous post on this subject.

Separate patches, please! Big patches are an utter nightmare to work with. Make my life easier, and your patches are more likely to be merged in!

viewtopic.php?f=3&t=5&sid=58140f6715a2b ... f78f3a088b

Context is fairly important when providing patches.

It's possible, but not very high priority for me.

Given the number of operating systems that PCem can run (this functionality would have to be written for all of them), this feature is unlikely. I'd instead recommend using a disk image utility to read/write files from hard disc images; I use WinImage, though there are several others around.

Next release should be towards the end of summer. I don't put out binaries of development versions.

Good, fix committed at rev 108.

Try adding to the top of win-joystick.cc.

What DirectX libraries are you using?

BTW, please don't double post to both this forum and VOGONS - I do read both.

Just added this, at rev 106.

Fixed the perspective issues (overflow), and the missing triangles by switching to emulating a ViRGE/DX as well as the original; I suspect the D3D drivers for the original chip are broken but don't own one to test.

Fixed the texture LOD issue, and implemented blending and more texture modes. Still some issues though - as can be seen below, Quake and Jedi Knight have texture issues and some missing triangles.

Since the Development forum is currently empty, I thought I'd start posting some screenshots of current developments. The first update is of the ViRGE S3D emulation, which has got to the point that some games can be (slowly!) played on it. Tomb Raider and Terminal Velocity (with affine texturing) wo...

I don't have a Radeon so this may be difficult to reproduce and fix. As a temporary workaround, try the attached config - it should allow the emulator to start in Direct3D mode.

That's a DirectDraw issue, indicating that the emulator couldn't create the required back buffers. What graphics card and drivers are you using?

I can't reproduce this. More information please - what setup within the emulator, what version of DOS, what GUS drivers are loaded, what else is loaded, etc.

No, it simply got lost in the mess that was the old thread.

It's a bug with hardware cursor emulation on interlaced modes.

I fixed the inverted mouse yesterday (see viewtopic.php?f=2&t=11&sid=978829afc068 ... 25b574de9e). You'll have to wait for a binary though, I don't publish binaries of development versions. I suspect someone else will make one at some point though.

Fixed on rev 100.

Please submit patches as output from git diff. When working on the emulator, please follow the coding style : * 8 character tabs * Braces should be on a new line * Try to avoid multiple statements on a single line unless it actually improves readability * Use spaces around keywords and operators oth...

When posting a bug report, please include as much of the following information as possible : * What the effect of the bug was (ie more than "doesn't work") * Description of the error, if any * What software was running on the emulator at the time * What OS was running on the emulator at th...