[Szasz]

Hello Hard-Lighters

My only goal was to play at native resolution otherwise I would be happy with the GOG retail, which btw works as it should. So I decided to go with Freespace open.
The problem is that I have a black screen while running fsopen and I can't help it.

I followed these instructions yesterday for installing: http://www.hard-light.net/wiki/index.php/Installing_FreeSpace_2_Open
Chose wxLauncher and build 3.7.0 for the first time. Set up 1920*1080 for resolution enabled 3Dshockwaves, FXAA and missile lighting.
Running the game produced a black screen but I heard the voices and music of the game in the background, it responded to keyboard and mouse as well there was just nothing to see. (I played FS2 a lot, so I remembered the menu structure).
Tried to turn every option off and lower the resolution and then the Launcher5.5 and an earlier build (3.6.18) to no avail.

I decided to remove everything and clean the registry.
Today I went through the process again with a small difference: leave every option at its default. The game ran and there was picture. Once. Then higher resolution was set, nothing else and there is no picture again. Even if I set the resolution back to its default.
Plus I get a "failed enumadaptermodes in updateantialiaslist" fatal error every time I start the launcher (doesn't matter which one) which did not happen for the first run in both installment.
There is a similar thread for the latter matter, but there is no solution there, just some bashing how old comp the guy has: http://www.hard-light.net/forums/index.php?topic=39224.0

My specs are:
OS: Win 8.1 x64
CPU: i7 3630QM
GPU: Intel HD 4000 + GeForce GTX660M
RAM: 8GB
(There is blank screen with either video adapter.)

I am clueless.
Please share your ideas with me, anything you have.

[niffiwan]

Please post your fs2_open.log file.  Instructions on how to do this can be found in this post.

[Szasz]

Please post your fs2_open.log file.  Instructions on how to do this can be found in this post.

Here it is.
There was nothing wrong with windowed mode, so I included the log about a fullscreen approach, too.
EDIT: I entered the main hall in both cases.
EDIT: But the issue remains with fullscreen_window.

[attachment deleted by an evil time traveler]

[Axem]

Just moving this to the support forum.

[niffiwan]

The log you posted was running with the Intel video card.  Unfortunately intel cards can have some problems with FSO.  Have you tried forcing FSO to use your nvidia card instead? If you have and it still didn't work, could you please post a log from running with the nvidia card?

[Szasz]

The log you posted was running with the Intel video card.  Unfortunately intel cards can have some problems with FSO.  Have you tried forcing FSO to use your nvidia card instead? If you have and it still didn't work, could you please post a log from running with the nvidia card?

It works on the nvidia card apart from the antialising error message meaning there is no blank screen. I might did not try to run it before because I already got scared by the error message.
Please find the log file attached.

I wish there was a borderless window option like in Total Annihilation or a way to choose custom resolution so it would fit my screen with the borders and make it possible to play with the integrated graphics. (Due to power consumption and heat efficiency. Plus the dedicated card is kind of an overkill for this game.)

[attachment deleted by an evil time traveler]

[niffiwan]

I wish there was a borderless window option like in Total Annihilation or a way to choose custom resolution so it would fit my screen with the borders and make it possible to play with the integrated graphics. (Due to power consumption and heat efficiency. Plus the dedicated card is kind of an overkill for this game.)

There is!   (at least I'm pretty sure that's what this is, it's only available on Windows and I run with Linux)

Try setting this in the launcher;  Advanced Setting -> Dev Tool -> Fullscreen Window

[General Battuta]

-fullscreen_window in the custom flags field should give you a borderless window. You can set custom resolution with the -res flag.

[Szasz]

The -fullscreen_window switch stil leaves me with a blank screen.
Good to know the -res flag.
Thanks guys.

[Szasz]

Does anybody know why I'm getting an excessive screen tearing using the dedicated graphics card regardless of nvidia driver settings? (either 'application controlled' or 'forced on' vsync)
Shouldn't be it on by default unless I use the -disable_vsync switch? I'm asking because I became skeptic due to the -fxaa switch not making any difference.
Tearing does not occur with the integrated graphics.

[General Battuta]

FXAA only works if you have postprocessing enabled. It should be pretty noticeable, unless something broke it.

[Szasz]

FXAA only works if you have postprocessing enabled. It should be pretty noticeable, unless something broke it.

Thanks.
It does not seem to work with postprocessing on either.

[pecenipicek]

Does anybody know why I'm getting an excessive screen tearing using the dedicated graphics card regardless of nvidia driver settings? (either 'application controlled' or 'forced on' vsync)
Shouldn't be it on by default unless I use the -disable_vsync switch? I'm asking because I became skeptic due to the -fxaa switch not making any difference.
Tearing does not occur with the integrated graphics.

because of the way optimus works. ( Intelgrated + nvidia "dedicated" = optimus on laptops these days. and its annoying as all hell )

[Szasz]

because of the way optimus works. ( Intelgrated + nvidia "dedicated" = optimus on laptops these days. and its annoying as all hell )

It is. Almost exclusively with old games. Freelancer for example. And Linux.

-fullscreen_window in the custom flags field should give you a borderless window. You can set custom resolution with the -res flag.

Looks like -res itself creates a borderless window.
What's funny about it is that the screen will be blank if I put the native resolution there. If any less, even with only one pixel like 1920x1079, it's fine.
What the hell?
(It dies on alt+tab though.)