It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Community
Outcastchanging to a viable resolution?(78 posts)(78 posts)
(78 posts)
Pages:
1
2
3
4
5
6
This is my favourite topic
Posted April 23, 2010
I guess if you are able to get rid of the black borders, it shouldn't be a problem getting it to look like that. Either the 4:3 image could be stretched over the whole screen, or you use "cinemascope" to get it to be 16:9, even though then part of the screen will just be cropped. I'm sure either of the two was done in that picture.
Posted April 24, 2010
Well the aspect ratio looks correct so I don't think it's been stretched, and Cinemascope isn't actually widescreen, it's just 4:3 that renders the top and bottom of the screen as black bars. If you're using it and try to access a menu, the menu actually goes into the black space.
Posted April 24, 2010
avatar
Syrion: ... Either the 4:3 image could be stretched over the whole screen...

And how would you do that? It seems I can't get it stretched. It's just tiny window with huge black borders on every side of my screen.
Posted April 24, 2010
avatar
sethsez: Well the aspect ratio looks correct so I don't think it's been stretched, and Cinemascope isn't actually widescreen, it's just 4:3 that renders the top and bottom of the screen as black bars. If you're using it and try to access a menu, the menu actually goes into the black space.

Oh, I see. I just gave it a try, and while you're right, at least the normal HUD is not inside the black bars. So, maybe whoever took that photo of Outcast running in widescreen was really able to play it like that and just had to bear with the menu being cut off a bit.
Judging from how problematic it already is to get the game to run without black borders, and how 640x480 seems to be the only "non-standard" resolution that can be used, while even that doesn't work flawlessly, I can't imagine that it's possible to run Outcast with a proper widescreen resolution without problems.
avatar
Loengard: And how would you do that? It seems I can't get it stretched. It's just tiny window with huge black borders on every side of my screen.

Using one of the methods mentioned in this thread. Apparently it doesn't work for everyone, but I got the game to run in 512x384 without any black borders, thus enabling my display to stretch the image to fullscreen.
Though, as sethsez said, if you have a widescreen monitor and the image gets stretched to fullscreen, it should look rather distorted.
Posted April 24, 2010
Here is my way to fix my problems with the game:
1st. - I can't play in Full Screen, cause my graphic card doesn't support the resolution 512x384.
2nd. - The music is jumping all the time ...
Solution: (works fin for me)
Download this little program:
[url=]http://outcastii.free.fr/FTP/loaderp_eng.zip[/url]
Put it in the Outcast folder and start it. Sett the resolution to 512x384 and load the game. You shoud have fullscreen now.
To deal with the music issue, lower the soundcard hardware acceleration to minimum. Don't turn it of, dn't set it to medium. It must be "minimum". You can change the the hardware acceleration with "dxdiag" ...
The game should be working then ...
Direx
Posted April 24, 2010
avatar
direx: ...
Download this little program:
[url=]http://outcastii.free.fr/FTP/loaderp_eng.zip[/url]
Put it in the Outcast folder and start it. Sett the resolution to 512x384 and load the game. You shoud have fullscreen now.
---

well it;s not full screen but it's better than native launcher.
my native laptop res is 1440x900 but i launch this custom launcher in 640x480 forced (compability mode)
Attachments:
outcast.jpg (26 Kb)
Posted April 24, 2010
avatar
direx: ...
Download this little program:
[url=]http://outcastii.free.fr/FTP/loaderp_eng.zip[/url]
Put it in the Outcast folder and start it. Sett the resolution to 512x384 and load the game. You shoud have fullscreen now.
---
avatar
GingeR13: well it;s not full screen but it's better than native launcher.
my native laptop res is 1440x900 but i launch this custom launcher in 640x480 forced (compability mode)

You should set it to 512x384. If I set it to 640x480 - the game crashes ... Look at the picture below ...
Direx
Attachments:
oc1-2010-04-24-1.jpg (128 Kb)
Posted April 25, 2010
avatar
GingeR13: well it;s not full screen but it's better than native launcher.
my native laptop res is 1440x900 but i launch this custom launcher in 640x480 forced (compability mode)
avatar
direx: You should set it to 512x384. If I set it to 640x480 - the game crashes ... Look at the picture below ...
Direx

the game in custom launcher [LoaderP_eng.exe] is set to 512x384. but in propertis for LoaderP_eng.exe i choose 'run in 640x480'.
still - i can't get outcast in fullscreen :/ or with blank spaces on the sides
Posted April 25, 2010
avatar
Sweetz: With nVidia drivers, you do this by going the Custom Resolution Utility (Change resolution -> Add Resolutions -> Create Custom Resolution). When you get the create window, it should be defaulted to setting that match your native resolution. Expand then timing section, then choose Manual. Don't touch anything else in the timing section , then go back up to the top and enter 512x384 then test/accept. This may or may not work, it can be finicky. This should make 512x384 a custom resolution that is scaled to and output at your native resolution.

I can't seem to get the manual timing to stick. Everytime I change it then test/save, when I check the settings again it's back to automatic. This is before I even close the window
Posted April 25, 2010
avatar
Whooosh: I can't seem to get the manual timing to stick. Everytime I change it then test/save, when I check the settings again it's back to automatic. This is before I even close the window

Don't worry about that. If the test runs successfully, then that resolution is good. It changes on my system too. Once the resolution is tested it's "locked-in" to the timings that worked regardless of what it says in the window.
Posted April 30, 2010
I dont' know if this has been suggested but I own an nVidia Card and I did this:
Before installing the driver I edited NV4_DISP.INF
There is a part called [nv_commonDisplayModes_addreg] with a single line starting with HKR,, NV_Modes...
Scrolling slightly to the right, there are thre comming resultions 640x480 800x600 and 1024x768.
Now, what I did was adding 512x384 (and 640x400 - which is great when you use 2xSAI in DOSBox) .
Now my card can use a resolution of 512x384. No black borders. It seems to use some hardware-scaling that smoothes the edges a little bit.
Posted May 02, 2010
None of the suggested fixes that don't include patches work for me, why's that?
My monitor doesn't seem to be compatible with 512x384 so I can't use Sweetz' method.
Meh.
Faildose 7 - 64bit.
EDIT:
I'm running the game fullscreen now without any problems, no crashes whatsoever, I just started LAUNCHER.EXE and disabled 'Framed' and loaded my game.
Surely it couldn't be that simple... I'm gonna try and see if I can find what I actually did.
Post edited May 02, 2010 by Masklin2
Posted May 02, 2010
avatar
Masklin2: I'm running the game fullscreen now without any problems, no crashes whatsoever, I just started LAUNCHER.EXE and disabled 'Framed' and loaded my game.
Surely it couldn't be that simple... I'm gonna try and see if I can find what I actually did.

I think as long as the "Framed" option is enabled, the game will always run it with a black border, no matter how you change the resolution settings.
From what I understand, Outcast has no problem with actually running in fullscreen 512x384. But, since most modern displays/graphics cards don't support that resolution by default, Outcast automatically switches to the "Framed" mode at the first start.
Posted May 06, 2010
You don't have to use custom loaders or deal with write protection to tweak the Outcast.ini settings. All you need to do is bypass the loader entirely by running oc1.exe with the word "game" on its command line. If you run it this way, Outcast.ini won't be overwritten.
The easiest way to do this (at least in Windows XP) is by:
- making a shortcut on the desktop to OC1.EXE, which can be found in the directory where you installed Outcast
- opening the Properties dialog for the shortcut (right click the shortcut, then select Properties)
- adding a space and the word "game" (without the quotes) at the end of the "target" textbox (where the path to OC1.EXE is)
- double clicking the shortcut whenever you want to start the game
This will skip the intro movie and start the game from the very beginning, so to continue with a previously saved game you'll have to skip (or watch) the first cutscene and then load your savegame from the in-game menu.
Posted May 09, 2010
avatar
Hexchild: You don't have to use custom loaders or deal with write protection to tweak the Outcast.ini settings. All you need to do is bypass the loader entirely by running oc1.exe with the word "game" on its command line. If you run it this way, Outcast.ini won't be overwritten.
The easiest way to do this (at least in Windows XP) is by:
- making a shortcut on the desktop to OC1.EXE, which can be found in the directory where you installed Outcast
- opening the Properties dialog for the shortcut (right click the shortcut, then select Properties)
- adding a space and the word "game" (without the quotes) at the end of the "target" textbox (where the path to OC1.EXE is)
- double clicking the shortcut whenever you want to start the game
This will skip the intro movie and start the game from the very beginning, so to continue with a previously saved game you'll have to skip (or watch) the first cutscene and then load your savegame from the in-game menu.

This gives me a direct draw error?
EDIT: Also my game is yet again blackbordered, and I didn't really do anything, so I'm rather confused at the moment... this is such a mess.
Post edited May 09, 2010 by Masklin2
Pages:
1
2
3
4
5
6
This is my favourite topic
Community
Outcastchanging to a viable resolution?(78 posts)(78 posts)
(78 posts)