----- Original Message ----- From: Aley Keprt <[EMAIL PROTECTED]> To: <[email protected]> Sent: Tuesday, November 16, 1999 4:34 PM Subject: Re: Wincoupe
> I know that this question is not addressed to me, but I must say something. > When I set "frameskip none" it falls down to 25 fps. I have Pentium 3. Fair enough. > > I use Pentium 3/450 and Windows 2000 rc 2. > Here is the table. It shows some interesting numbers, there are probably > some > weird bugs (in SimCoupe). Yes, there are definitely some weird bugs in SimCoupe. But I thought we were talking about WinCoupe? (As far as I remember, you were the last person to change SimCoupe source :) > The "table" shows how the framerate changes when i set "frameskip" and > "accurate mode 3". > mode 3 on --- 175fps with "skip auto" --- 142fps with "skip none" > mode 3 off --- 50fps with "skip auto" --- 25fps with "skip none" Which window mode? (1x1? 2x2? 3x3?) What color depth? etc > > 1. I though "skip none" should be the fastest. I can see "skip auto" is > faster. A bug? A bug in your logic, perhaps. When frameskip is set to 'none' it doesn't skip frames. (Hence 'Frameskip None'). In other words it tries to redraw the screen every frame. When frameskip is set to 'auto' it will automatically skip frames. (Hence 'Frameskip Auto'). In other words, it will NOT try to redraw the screen every frame. In other words, for some frames, it will ignore redrawing the screen for that frame. This means it does less work therefore quicker emulation therefore more frames per second. However, that really only applies if Sync To 50Hz is disabled. If Sync To 50Hz is enabled, FrameSkip Auto should never drop below 50Hz! I have a question for you, because those fps counts look suspicious. Are you using 'Sync to 50Hz enabled' or have you disabled it? (See what fps you can reach with 'Sync to 50Hz' turned off, and the four combinations you have tried above. Also see what fps you get with 'Sync to 50Hz' turned on, and the four combinations you have tried above) And are you using 1x1 mode or 2x2 mode or 3x3 mode? And what is your current desktop resolution and color depth? And what is the make / model of your video card? And what version drivers are you using? And you do realise that the operating system you are running is a Beta version (what with it being unreleased n'all). Try again with Win95 or Win98 and very recent drivers. > 2. Mode 3 off should generate 320x240 picture --> i.e. faster. But it is > slower. A bug? Disabling 'accurate mode 3' will only generate a 320x240 picture if you're running WinCoupe full screen (But if you're running WinCoupe full screen how are you measuring the fps??) To be honest, from those timings it actually looks to me a little like you've actually disabled 50Hz synchronisation instead of enabling accurate mode 3! But I admit, they do look a little odd. Furnish us all with the complete details of what you tested and how. > Also, these all I've get with "frameskip auto". When "Frameskip none" > and "mode 3 on" I get 130fps (less than "frameskip auto" No you don't. You just already said that with Frameskip none and mode 3 on you get 142 fps. Which is it? 142fps or 130fps? (It's an farily large difference, the fps shouldn't fluctuate that much I don't think) > Well, menu has no shortcuts. I want at least Alt+Space to enter the menu. How about these for shortcuts: Press ALT to enter the menu. Even works for full screen. Press 'F' for File menu, 'C' for CPU menu, 'V' for Video menu, 'S' for Sound menu, 'H' for Help menu. The only menu that doesn't have a shortcut in this way is 'Hardware' but you could use ALT-H-LeftCursor or ALT-S-RightCursor. Options on the menu even have shortcuts ... Bonus! F6 to disable sync to 50Hz, F7 to cycle Frameskip modes, F5 to cycle window mag modes, ... Admittedly ALT+SPACE is currently not detected by WinCoupe (Si?) > Dirty lines are too complicated? It's because you've probably did too > optimised > video code. I can imagine your sources. :-))) I haven't seen Si's source code for WinCoupe. However, your comment sounds a little insulting. I think the point is though that putting dirty update code back into WinCoupe is essentially more trouble than its worth at this stage. Especially since memory writes now seem to be quicker without it! > Mame uses dirty rectangles (the thing you call "dirty lines") and it > benefits from > it. You're right, that it can slow the whole emulator. But how much? A > little bit. Question: How can an emulator 'benefit' from using a dirty rectangle update scheme if it slows the whole emulator down? (Or have I missed the point again?) saasound.dll development is temporarily on hold whilst I try to get my head round a new high-quality mode. Latest version is still 2.01 D a v e
