Resolution

[Grief Tyrant]

I picked the wrong resolution the 1st time, now it won't let me change. The bar in wich i can change it is completely blank. Uninstalling and then reinstalling wont work. Any idea's?

[Smiling Spectre]

Try to set compatibility mode (XP SP3) for configure program?

[Space Coward]

Go to the actual file location (Right-click the game from Steam > Properties > Open File Location) and run SettingsApplication.exe. It'll probably pop up an error saying your drivers are out of date, just click okay and keep going (it can't properly recognize modern drivers because they're entirely different from the drivers that were around back in 2003).

I recommend going into your GPU drivers and making up a resolution for whatever you have in 4:3. For example, on a 1080p montior, 1440x1080@60 looks quite nice. 1920x1440@60 is awesome on an Nvidia or AMD card that can support DSR/VSR.

Also, does Steam really not ask you about the Settings application? The uPlay version has two options on startup.

[Smiling Spectre]

Originally posted by Moss:

Also, does Steam really not ask you about the Settings application? The uPlay version has two options on startup.

It starts named SettingsApplication.exe each time instead. Forementioned "bar for change resolution" is here - not in game. But it's obviously doesn't work for Fladdervogel. I believe, compatibility can fix it.

[Space Coward]

Originally posted by Smiling Spectre:

Originally posted by Moss:

Also, does Steam really not ask you about the Settings application? The uPlay version has two options on startup.

It starts named SettingsApplication.exe each time instead. Forementioned "bar for change resolution" is here - not in game. But it's obviously doesn't work for Fladdervogel. I believe, compatibility can fix it.

So, there are two launch options? Interesting. I'll presume it's just not showing up properly for him.

At the very least, that means the Steam version does have the launcher included, so this can probably be fixed. I only just managed to get it all working myself recently, and I posted on another thread with the compatibility options I used to fix the awful framerate/slowdown.

[Smiling Spectre]

I see slight misunderstanding. :)

Originally posted by Smiling Spectre:

It starts named SettingsApplication.exe each time instead. Forementioned "bar for change resolution" is here - not in game. But it's obviously doesn't work for Fladdervogel. I believe, compatibility can fix it.

Originally posted by Moss:

So, there are two launch options? Interesting. I'll presume it's just not showing up properly for him.

There is only _one_ option for Steam by default (I think. Maybe I am wrong). And it's starting settings exe that will allow you to start the game.

There are still the same 2 exes in the game folder (settings and bge.exe), and you can run the game directly, if you want.

I only just managed to get it all working myself recently, and I posted on another thread with the compatibility options I used to fix the awful framerate/slowdown.

Ha, I told it countless times, so it will not harm to repeat: enable everything in "Advanced" options and pull to the left the Anti-Aliasing bar afterwards. :)

(And I still recomments Idarion's wide-screen fix for widescreen monitors).

[Space Coward]

I actually did try all options, and it didn't fix everything. That's why I had to actually experiment around with it. There are some options that might actually break the game even more depending on your setup. :\

[Smiling Spectre]

Originally posted by Moss:

There are some options that might actually break the game even more depending on your setup. :\

Oh, really? Ok, it seems, I need to study your research more. *going to the neighbour thread*

[Space Coward]

Originally posted by Smiling Spectre:

Originally posted by Moss:

There are some options that might actually break the game even more depending on your setup. :\

Oh, really? Ok, it seems, I need to study your research more. *going to the neighbour thread*

It could be my monitor. Basically, the game would desync from audio on certain settings or the framerate would variably tank whenever particle effects were on screen (of course, the opening cutscene was horrible as a result).

[Smiling Spectre]

Originally posted by Moss:

It could be my monitor. Basically, the game would desync from audio on certain settings or the framerate would variably tank whenever particle effects were on screen (of course, the opening cutscene was horrible as a result).

I checked your settings. Unfortunately, I haven't game at hand right now, but by memory, you _have_ all additional options enabled. Had you disable anything, except AA?

And to going into details, I went into research when, after upgrade to Win10, Idarion's fix suddenly stopped to work. After some experimenting and consulting with Idarion himself, I discovered several important points:

1. AA in game heavily broken on "full" setting. Actually, anything except full works, but as it have no significant influence to the gameplay, it's simpler to disable it in game altogether.

2. Disabled HW vertex processing responsible to horrible framerate. Unfortunately, enabling it results to polygon glitches here and there (most obvious is interface edges and tree in the initial cutscene).

3. Some combination of SSE, mipmap, fastflip and mipmap autogen fixes the glitches, but I wasn't able to determine which. Fortunately, simple enabling _all_ of them works. :)

But yes, I have "standard" 60Hz monitor, so I cannot test your conclusions about 144Hz.

[Space Coward]

I noticed the tree clipping in the intro, as well as the clear outline in the ground where a meteor was supposed to land, but figured it was just a minor Ubisoft mistake. Are you saying that'll get worse? And yeah, AA on any setting other than off entirely caused desync. I'm using an AMD R7 360 at the moment, by the way.

Anyway, I guess I'll get back to bashing my head against dgVoodoo to see if there's a way around the HW Vertex glitches.

[Smiling Spectre]

Originally posted by Moss:

I noticed the tree clipping in the intro, as well as the clear outline in the ground where a meteor was supposed to land, but figured it was just a minor Ubisoft mistake. Are you saying that'll get worse?

It's drivers glitch that must not be here - and on my NVidia it isn't, _if_ I enable every possible additional setting - and disable AA. Did you try this?

P.S. Just for record: actually I enabled and put _everything_ on max, disabling only AA. Maybe it matters.