Yeah...I already read your post in the other topic 😀 But currently D3D makes the assumption that the monitor is 4:3. I'll have to check the code...

I wonder if anyone has tools for OpenGL-programming on windows. I'd love to query ATI's extensions to see if OpenGL on windows could be accelerated. On Linux, ATI OpenGL speed is good now (with my current changes). I'm also using 1280x800/fullfixed.

@swaaye: I found the problem. D3D is doing only integer scaling when fullfixed is on in order to avoid blurring pixels on LCD monitors. If the fullfixed resolution is 1280x800 and game res is 640x480 it will scale 2x in the x direction and only 1x in the y since 2x480 > 800. What would you prefer anyway? Having only 640x480 image with black bars around? Fullscreen image 1280x800 (w/ wrong aspect ratio), or ~1064x800 image with correct ar, some black bars and somehwat blurred pixels??

@`Moe`: What exactly do you need? There's a tool that shows you the supported extension - GLview, or you could just search through atioglxx.dll with a hexeditor 😁. But I think the code should be the same as in linux, set pointers, getprocaddress, etc...

the sdlmain.cpp of dosbox has some extension checks in it as well
it are 2 lines of code or so.
quite simple.

you basicly get a char* to a list in which all extensions are listed.
print it and you are done.

Aah, gulikoza, that's exaclty what I had in mind! Thanks!

gulikoza wrote:

@swaaye: I found the problem. D3D is doing only integer scaling when fullfixed is on in order to avoid blurring pixels on LCD monitors. If the fullfixed resolution is 1280x800 and game res is 640x480 it will scale 2x in the x direction and only 1x in the y since 2x480 > 800. What would you prefer anyway? Having only 640x480 image with black bars around? Fullscreen image 1280x800 (w/ wrong aspect ratio), or ~1064x800 image with correct ar, some black bars and somehwat blurred pixels??

I'd be ok with full 1280x800. Otherwise 1064x800 sounds ideal. Is there a way to make both an option, to make it stretch to full no matter what? Isn't that what aspect should do?

BTW, I don't THINK I posted with this question on the other forum.... Sorry about seeming that way tho!

Where is this direct3d output option documented? I hadn't heard of it until I read this thread just now! Any other features I should know about? I see from the CVS changelog that the config system has been overhauled - I hope someone documents that so we can help test it.

hmmm....yeah...must have been someone else then...but I do remember reading about tie fighter problem 😁
I already thought of using aspect option, but aspect= is in used in render.cpp, it does not get to D3D unfortunately. I'd need to change the structs to pass it on to D3D...

@HunterZ: Direct3D is my patch, it can be found on my page, it's not part of the official cvs. It goes around sdl, directly to DirectX and even has some support to use pixelshaders for scalers.

Ah, thanks. I figured it must have been a patch after looking in the unpatched source to see if there were any output modes not listed in the default dosbox.conf.

Sorry to hijack the thread, but:
- is the version of the coreswitch patch on your site the same one you use in your CVS builds?
- is there info somewhere on how to integrate the latest Munt CVS the way you're doing it?

1. Yes. Although it will not apply ATM because of the recent changes in cvs. I'll update it along with D3D when I sort this stuff.

2. There's some info in this thread.

There it is...the new build is up. The changes in the fullscreen scaling (D3D) are as follows:
- aspect=false, will do only integer scaling to avoid as much blurring on LCD as possible (as discussed in the other thread), fixed a bug when it would only scale in one direction
- aspect=true, will try to scale as close to 4:3 as possible. Should be useful on widescreen displays if you want the correct aspect ratio

@swaaye: I don't have any widescreen lcds here, so test this and see if it works for you 😁

Gulikoza, I gave the new build a try and it looks good! There is still a problem with TIE @ high res in-flight 640x480 where aspect has no effect on the aspect (heh). However, while TIE is in 320x200 the aspect=true does force proper aspect ratio. But hey, it works a ton better than before. No super-squished TIE! Full screen 1280x800 with D3D in use. Nice work.

I noticed another bug in the build where if you have core=normal set in the conf file, DOSBOX will say it's in Simple core mode when you start it up. Setting core to dynamic however will show dynamic when you start DOSBOX.

damn copy/pasting 😜. I've fixed the coreswitch patch now & recompiled 😁

As for Tie Fighter...hmm...it should be working. I tested TF in high-res as well. Are you saying that no matter what aspect= is set to, picture is the same size? How does it look (borders, fullscreen?)?

Ok. It was my fault 😀 I hadn't turned on fullfixed=true, so my LCD was interpolating from the game's default res's. However, there is still one issue.

When aspect=true everything is working fine. 320x200 and 640x480 are scaled to full height at 4:3, so there are black bars on the sides.

When aspect=false 320x200 is full 1280x800. However, 640x480 is not resized at all, staying 640x480 in the center of the screen.

I turned off LCD resize so I could see all of this btw.

That's a feature not a bug 😁. The theory is to scale only integrally (x1, x2, x3...), there's a whole thread here in case you missed it. This way in your case a 320x200 image can be scaled x4 to 1280x800 (w/ wrong AR of 1.6:1, but that's why aspect=false 😉). 640x480 can be scaled x2 in x-direction (to 1280) and only x1 in y (since 2x480 > 800). That's what happened before, now I added checks if AR is waaay off. So the biggest factor to scale a 640x480 to 1280x800 is times 1 - leave it as it is. btw: lcd resize should not matter since in all cases when fullfixed=true, lcd will be switched to that resolution, the black borders will be drawn.
This has now become quite complicated, but I guess it should work for most cases when the game does not use some strange resolutions (psycho pinball anyone? 😁). The CRTs should always display a nice picture, since you don't need fullfixed and just use native res.

ahhh. ok. I am now in complete and total understanding 😀