v16 compatibility & bug list (WIP)

Discussion of development and patch submission.
User avatar
leilei
Posts: 781
Joined: Fri 25 Apr, 2014 4:47 pm

Re: v16 compatibility & bug list (WIP)

Post by leilei » Tue 07 Apr, 2020 4:01 pm

Mystique focus but with the Powerdesk 4.12.013 driver instead, fixing some hangs

Code: Select all

Advanced/ZP Cyrix M II-266, 128MB, Matrox Mystique 4MB (Powerdesk 4;12;013), SB16, Win98SE:
Works:
Dark Rift demo
Dominant Species demo
Forsaken demo
Jane's WWII Fighters demo
Jedi Knight
Moto Racer demo
Moto Racer 2 demo
NFL Fever 2000 Trial
Outwars Trial
Urban Assault demo
Warbirds 2.01

Somewhat:
Croc demo (flickery)
Final Reality (2D test color corruption)
Incoming demo (game works,menu non-visible)
Jane's Longbow 2 Demo 2D screens don't render the white color, possibly real behavior)


Doesn't:
Recoil Demo (fatals with "Unknown texture format 4")
Sonic R (no menu graphics, blackscreen freeze on game load)
Ultimate R@ce Pro demo (Freezes after awhile ingame, Direct3d)

Joel_w
Posts: 3
Joined: Sat 16 Mar, 2019 3:33 pm

Re: v16 compatibility & bug list (WIP)

Post by Joel_w » Thu 09 Apr, 2020 3:51 pm

win2kgamer wrote:
Sat 04 Apr, 2020 3:52 pm

Anything in pcem.log? (On Windows it will be in the same directory as the main PCem executable, on Linux it will be in /home/$USERNAME/.pcem/logs)
Right now this is the only thing in pcem.log:

ILOAD DWGCTRL_ATYPE_RPL 0e000000 0e0c6009

But since I posted about the crash I've installed updated drivers and used the emulator for a bit. I'm not sure if the log has been updated after the crashes, but I haven't seen any crash after installing the new drivers either.

User avatar
SarahWalker
Site Admin
Posts: 1868
Joined: Thu 24 Apr, 2014 4:18 pm

Re: v16 compatibility & bug list (WIP)

Post by SarahWalker » Fri 10 Apr, 2020 6:50 pm

I'm throwing in the towel on the Mystique. I've spent the last couple of weeks trying to fix games that freeze, games that reboot, games that only display 1% of rendered frames, games that run absurdly slowly, etc etc. The Matrox D3D drivers appear to be ultra finicky, often deciding to stop servicing interrupts or stop sending any new commands when anything even slightly inaccurate occurs timing-wise. I think I'd need to write a proper timing model to get this working reliably, but as this would take weeks and I just want v16 to be done, I've marked it as DEVICE_NOT_WORKING in rev 1556, meaning the Mystique won't appear in release builds.

I'm not happy doing this, as this would have been the biggest feature for v16. But I just don't want to work on this any more right now.

User avatar
omarsis81
Posts: 838
Joined: Thu 17 Dec, 2015 6:20 pm

Re: v16 compatibility & bug list (WIP)

Post by omarsis81 » Fri 10 Apr, 2020 10:03 pm

Don't worry, we welcome v16 as it is!

User avatar
leilei
Posts: 781
Joined: Fri 25 Apr, 2014 4:47 pm

Re: v16 compatibility & bug list (WIP)

Post by leilei » Sat 11 Apr, 2020 12:18 am

Given there's also a lot of early D3D games that don't like the Mystique either (with real behavior exhibited when they go wrong, such as early games with fog) it's probably for the best. Could imagine the false PCem bug reports on how NFS3 and Lithtech games missing textures on it, etc... 1st gen 3D is always an unstable risk like that.

also I don't have a Mystique to crosscheck with, but do have a Productiva G100A which is pretty much a Mystique 220 with bilinear on RGB and a wrecked LOD bias.

User avatar
omarsis81
Posts: 838
Joined: Thu 17 Dec, 2015 6:20 pm

Re: v16 compatibility & bug list (WIP)

Post by omarsis81 » Sat 11 Apr, 2020 12:42 am

Is that Productiva G100A more compatible with games?

andr25352
Posts: 10
Joined: Sun 12 Feb, 2017 9:50 am

Re: v16 compatibility & bug list (WIP)

Post by andr25352 » Sat 11 Apr, 2020 10:13 am

When I try to run any emulated machine with sound device "Sound Blaster PCI 128", PCem crashes just after the initial beep of the bios.
I get this message in the terminal:

Code: Select all

Menu item not found: 1403
Menu item not found: 1404
Menu item not found: 1403
Menu item not found: 1404
*** buffer overflow detected ***: ./pcem terminated
Aborted (core dumped)
Tested on Linux Mint 19.3.
Only happens when compiled with gcc and with optimizations enabled. When using Clang this doesn't happen.

ZoltanTheHun
Posts: 6
Joined: Sun 19 Feb, 2017 9:57 pm

Re: v16 compatibility & bug list (WIP)

Post by ZoltanTheHun » Sat 11 Apr, 2020 11:50 am

I am so glad for all your work Sarah. This emulator is one of my favourite projects on the net. If the Mystique is not part of the release, so be it, I am sure most of us understand.

User avatar
leilei
Posts: 781
Joined: Fri 25 Apr, 2014 4:47 pm

Re: v16 compatibility & bug list (WIP)

Post by leilei » Sun 12 Apr, 2020 8:12 pm

Tested a bunch. Miss the Mystique already :(
So far the bugs seen here are old bugs and not new regressions which I hoped to look for. Should probably up my variety of games as I don't have enough racing here...

Code: Select all

FIC VA-503+, Mobile Pentium MMX 300, 256MB, S3 ViRGE DX 4mb, Voodoo2 12MB, SBAWE32, Win98SE, :
* = MS-DOS Mode boot required as Win9X shouldn't work with it
Works:
3-Demon
Abuse
Alien vs. Predator
Bart's Fun House*
Big Red Racing
Blood
Blood 2
Breakfree
California Games*
Chessmaster 2100
Chex Quest
Crossbow 
Dark Forces
Death Rally
Descent
Descent 2
Deus Ex
Doom
Duke Nukem 2
Duke Nukem 3D
Dune 2
DXBall 2
Elder Scrolls: Arena
Elfland
Frogger (1997)
GLQuake
Half-Life (1.0.0.9)
Heretic 2
Hexen95
Hi-Octane
Magic Carpet
Master of Orion
Mechwarrior 2 (DOS)
Mechwarrior 3
Metal Gear Solid
Need For Speed High Stakes
Nerf Arena Blast
Nomad
One Must Fall 2097 (1.0)*
Oregon Trail (DOS)
Out of This World (aka Another World) *
Powerslave (aka Exhumed)
Prince of Persia 2
Puyo Puyo Tsuu (DOS)*
Quake
Raptor
Red Alert 2
Rise of the Triad
Simcity 2000 (DOS 1.0)
Star Control
Star Control 3
Star Trek Voyager Elite Force
Stunts (aka 4D Sports Driving)
The Fortress of Dr. Radiaki
Turok Dinosaur Hunter
Unreal Tournament
Warcraft
Warcraft 2
Williams Arcade Classics
Worms Armageddon
Virtual Reality Studio (aka 3D Construction Kit)
Zeliard

Shadow Warrior

Somewhat:
Gunmetal (Glide fatals Bad CMDFIFO0 bb07a0b8, software fine)
MDK2 (Fades broken)
Spectre VR (DOS version: Keyboard issues with menu under DOS, fine under Windows 98)
Starsiege Tribes (flickery polys in Glide)
The Labyrinth (Broken on Voodoo2)

Broken:

User avatar
SarahWalker
Site Admin
Posts: 1868
Joined: Thu 24 Apr, 2014 4:18 pm

Re: v16 compatibility & bug list (WIP)

Post by SarahWalker » Mon 13 Apr, 2020 8:07 am

leilei wrote:
Sun 12 Apr, 2020 8:12 pm
Tested a bunch. Miss the Mystique already :(
Tell me about it :(

Anyway, _finally_ brought the list in the first post up to date. No showstoppers so far...

Greatpsycho
Posts: 137
Joined: Tue 22 Mar, 2016 10:03 am
Location: Korea
Contact:

Re: v16 compatibility & bug list (WIP)

Post by Greatpsycho » Wed 15 Apr, 2020 6:41 am

SarahWalker wrote:
Fri 10 Apr, 2020 6:50 pm
I'm throwing in the towel on the Mystique. I've spent the last couple of weeks trying to fix games that freeze, games that reboot, games that only display 1% of rendered frames, games that run absurdly slowly, etc etc. The Matrox D3D drivers appear to be ultra finicky, often deciding to stop servicing interrupts or stop sending any new commands when anything even slightly inaccurate occurs timing-wise. I think I'd need to write a proper timing model to get this working reliably, but as this would take weeks and I just want v16 to be done, I've marked it as DEVICE_NOT_WORKING in rev 1556, meaning the Mystique won't appear in release builds.

I'm not happy doing this, as this would have been the biggest feature for v16. But I just don't want to work on this any more right now.
That's bad news. If so, Please review other pending patches before releasing version 16.

Greatpsycho
Posts: 137
Joined: Tue 22 Mar, 2016 10:03 am
Location: Korea
Contact:

Re: v16 compatibility & bug list (WIP)

Post by Greatpsycho » Fri 17 Apr, 2020 7:45 am

I found that 486+ machine with Dynamic recompiler enabled cause the following problems.

1. Machines doesn't work properly on CentOS 64-bit version host.
2. Turbo Debugger 286 included in Borland C++ 2.0 or 3.x crashes.

200mmx
Posts: 6
Joined: Fri 20 Mar, 2020 8:51 am

Re: v16 compatibility & bug list (WIP)

Post by 200mmx » Mon 20 Apr, 2020 6:39 am

In PCem v16, the "About" tab displays PCem v14.

User avatar
Neville
Posts: 39
Joined: Tue 02 Aug, 2016 1:43 pm

Re: v16 compatibility & bug list (WIP)

Post by Neville » Tue 21 Apr, 2020 3:59 pm

As already mentioned [url=https://pcem-emulator.co.uk/phpBB3/viewtopic.php?f=2&t=3461]in this thread[/url], The System 16 Emulator somehow stopped working on v16.

Not that many people probably use it, but it could be an indicative of something not working right.

On the other hand, now Lotus: The Ultimate Challenge now works with the dynamic recompiler on :D

Siggy12
Posts: 33
Joined: Sat 21 Jul, 2018 6:04 pm

Re: v16 compatibility & bug list (WIP)

Post by Siggy12 » Tue 21 Apr, 2020 7:05 pm

for me is impossible in v16 exit fullscreen with CTRL+ALT+PAG-DOWN
v14 and v15 exit fullscreen perfectly, in v16 I have to use ALT+TAB don't know why,
if there is any log that I can provide I'll do it.

Agorima
Posts: 4
Joined: Mon 07 Oct, 2019 3:39 pm

Re: v16 compatibility & bug list (WIP)

Post by Agorima » Tue 21 Apr, 2020 8:25 pm

Siggy12 wrote:
Tue 21 Apr, 2020 7:05 pm
for me is impossible in v16 exit fullscreen with CTRL+ALT+PAG-DOWN
v14 and v15 exit fullscreen perfectly, in v16 I have to use ALT+TAB don't know why,
if there is any log that I can provide I'll do it.
I upgraded PCem from v15 to v16 by overwriting the older version in the same folder, the keyboard combination CTRL-ALT-PAG DOWN is working just fine.

User avatar
omarsis81
Posts: 838
Joined: Thu 17 Dec, 2015 6:20 pm

Re: v16 compatibility & bug list (WIP)

Post by omarsis81 » Tue 21 Apr, 2020 9:09 pm

Agorima wrote:
Tue 21 Apr, 2020 8:25 pm
Siggy12 wrote:
Tue 21 Apr, 2020 7:05 pm
for me is impossible in v16 exit fullscreen with CTRL+ALT+PAG-DOWN
v14 and v15 exit fullscreen perfectly, in v16 I have to use ALT+TAB don't know why,
if there is any log that I can provide I'll do it.
I upgraded PCem from v15 to v16 by overwriting the older version in the same folder, the keyboard combination CTRL-ALT-PAG DOWN is working just fine.
What OS are you using?

Agorima
Posts: 4
Joined: Mon 07 Oct, 2019 3:39 pm

Re: v16 compatibility & bug list (WIP)

Post by Agorima » Tue 21 Apr, 2020 10:43 pm

omarsis81 wrote:
Tue 21 Apr, 2020 9:09 pm
Agorima wrote:
Tue 21 Apr, 2020 8:25 pm
Siggy12 wrote:
Tue 21 Apr, 2020 7:05 pm
for me is impossible in v16 exit fullscreen with CTRL+ALT+PAG-DOWN
v14 and v15 exit fullscreen perfectly, in v16 I have to use ALT+TAB don't know why,
if there is any log that I can provide I'll do it.
I upgraded PCem from v15 to v16 by overwriting the older version in the same folder, the keyboard combination CTRL-ALT-PAG DOWN is working just fine.
What OS are you using?
Windows 10 Home x64 (version 2004)

Siggy12
Posts: 33
Joined: Sat 21 Jul, 2018 6:04 pm

Re: v16 compatibility & bug list (WIP)

Post by Siggy12 » Thu 23 Apr, 2020 8:10 pm

omarsis81 wrote:
Tue 21 Apr, 2020 9:09 pm
Agorima wrote:
Tue 21 Apr, 2020 8:25 pm
Siggy12 wrote:
Tue 21 Apr, 2020 7:05 pm
for me is impossible in v16 exit fullscreen with CTRL+ALT+PAG-DOWN
v14 and v15 exit fullscreen perfectly, in v16 I have to use ALT+TAB don't know why,
if there is any log that I can provide I'll do it.
I upgraded PCem from v15 to v16 by overwriting the older version in the same folder, the keyboard combination CTRL-ALT-PAG DOWN is working just fine.
What OS are you using?
I'm using Windows 10 too 1803 version.

User avatar
te_lanus
Posts: 130
Joined: Tue 28 Jul, 2015 4:47 am

Re: v16 compatibility & bug list (WIP)

Post by te_lanus » Mon 04 May, 2020 9:37 am

Been playing around the last few days:

Code: Select all

Award 286 clone 286/8 vga

MS-Dos 3.30
MS-Dos 6.2

Deathtrack
Arkanoid
Arkanoid 2 - Revenge of Doh
________________________________________
Award 286 clone 286/20 vga

Grand Prix Unlimited
________________________________________
AMI 286 clone 286/8 vga

MS-Dos 5.0
Compaq DOS 3.31
DR-Dos 6.0

Test Drive III
Simcity 1.07
Hard Drivin II

Neverlock
ViewMAX
________________________________________
AMI 386DX clone i386DX/33 Tseng ET4000AX 

V2_OS V0.60x (Joosts Y2K-Demo)
V2_OS V0.52b
________________________________________
Award SiS 496/497, i486DX2/66, ATI Graphics Pro Turbo (Mach64 GX)

Microsoft Encarta 97 (Windows NT SP1)
________________________________________
Award SiS 496/497, i486DX2/66, S3 ViRGE/DX

Windows 95 c (OEM version)

All Windows 95:
Diablo 
Diablo Hellfire
Microsoft Golf 1
Earthworm Jim
Midtown Madness (runs but is slow and choppy. Needs a Pentium)

Errors:
Midtown Madness: When PCem is running in a window, the screen is squished horizontally  (when PCem isn't fullscreen)
________________________________________, 
AMI WinBIOS 486, i486DX/33, S3 ViRGE/DX

MS-DOS 5.0

MAME 0.6
Rage 0.9
Nesticle 0.3

Errors:
MAME does have graphical errors with WOW (Wizard of Wor) But not sure if it's a mame issue or pcem

Fishworldwar
Posts: 1
Joined: Fri 01 May, 2020 2:54 am

Re: v16 compatibility & bug list (WIP)

Post by Fishworldwar » Wed 13 May, 2020 2:20 am

I tested 3 early builds of Windows and here are the results:
Windows 3.1 Beta Build 43e (No issues)
Windows Chicago Builds 58s (No issues) and 116 (requires hard reset and fail-safe boot to work correctly after installation and startup)

win2kgamer
Posts: 56
Joined: Sun 09 Nov, 2014 12:24 am

Re: v16 compatibility & bug list (WIP)

Post by win2kgamer » Sat 23 May, 2020 4:53 am

Tested my collection of Windows Chicago betas using the following configuration:
Machine: AMI 486 clone
CPU: i486DX2/66, Recompiler off
RAM: 8MB
Video: Tseng ET4000AX
Sound: Sound Blaster 16
HDD controller: Adaptec AHA-1542C
FDDs: 1x3.5" 1.44M (A) + 1x1.2MB 1.2M (B)
CD-ROM: PCemCD 4x
Mouse: Microsoft 2-button serial

As none of these systems came on bootable CDs (and didn't include CD-capable boot floppies as far as I can find), I used a retail Windows 98 boot floppy to partition, format and begin the install.

Builds tested (all are working well enough to install and boot to the desktop, didn't test deeply beyond that):

Code: Select all

- 58s
- 73f
- 73g
- 81
- 90c
- 99
- 116
- 122
- 189
- 216
- 224
- 267
- 275
- 314
- 324
- 331
- 337
- 345
- 347
- 405
- 431
- 440
- 462
- 468
- 484
- 490

Post Reply