I've noticed an issue quite some time ago under WinXP but it seems it wan not caused by my setup as i first thought. b17 and newest b18 still have this issue under Win7 x64 too.
Here's what happens. Display settings: "Render both pixel lines" is checked and "DirectX stretch" is not checked -> both pixel lines are NOT rendered. Checking or unchecking "Render both pixel lines" has no effect, only 1 pixel line is rendered. Also, "Half-size display" is NOT checked.
Is this a bug or something to do with my setup after all? I'm using an HP laptop (pavilion dv7) if this means something.
Do you have PAL emulation on? That will render alternate lines a darker colour.
Ah, yes! That was it. Many thanks man. :)
I don't really like DirectX stretch. OK, it's nice to be able to stretch the screen to whatever size you like but i hate the blur it has. I guess there's nothing you can do about it, right? It's a DirectX thing, isn't it?
Yes, DirectX does some anti-aliasing with the normal rescaling which may make things look a little blurry.
The other problem I have is that my display is not in widescreen any more when I have fullscreen mode on.
Quote from: Darren on 15:50, 17 August 12
The other problem I have is that my display is not in widescreen any more when I have fullscreen mode on.
I guess it's because the CPC only has a 4:3 display...
So entering fullscreen with WinApe (F10) will turn your screenmode into a 16:9 or 16:10 screenmode but with CPC image in 4:3.
Re-entering windowed mode should turn back to your desktop's screenmode.
When I load something into the B drive on Winape it loads in fine, but when I try to "cat" drive B it shows it all out of sync and funny and changes colour. I do not have any problem with drive A.
Quote from: Darren on 13:24, 19 August 12
When I load something into the B drive on Winape it loads in fine, but when I try to "cat" drive B it shows it all out of sync and funny and changes colour. I do not have any problem with drive A.
You need to remove the PARADOS ROM to be able to CAT the B: drive (from memory)... replace it with AMSDOS.
(but there's probably a less drastic solution...)
Thanks :D . I will try this, although if anyone else does know of a less drastic solution then please feel free to add.
I replaced PARADOS with AMSDOS (on bank 7) but the Winape did not load in at all :o .
Works for me... check your BASIC ROM. I sometimes find it disappears when playing around with PARADOS/AMSDOS.
Thanks. My lower bank was empty, but have now put OS6128 in and all seems fine.
Quote from: tastefulmrship on 16:56, 19 August 12
check your BASIC ROM. I sometimes find it disappears when playing around with PARADOS/AMSDOS.
huh, is this a bug?
I've found that sometimes WinAPE behaves a bit strangely (the CPC won't boot, suggesting lack of proper ROM) when toying with ROMs. Quite a few times I've had to just delete the ini file and start anew, but I have never managed to pinpoint where and when that happens. But it's a very small thing.
Some DOS do not work (in ROM), f.e. xddos. I dunno why.