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

×
Greetings,

After years (!) spent reading the manual, I have finally been playing F117. But I am running into two issues.

First, and this may be the most crucial one, the landing. Figuring where to land is tricky enough (the visual limitations of the game and the clutter of its terrain representation makes it quite hard), but I almost systematically die at the end of the runway. The ILS is pretty lousy, and my best efforts, I am landing about 1/3 in and the time to figure which key is the break one, I am already well into the decor.
I am suspecting the manual is a bit off (it's 70%=300knots tipped me off something may be off), and that I should land much slower than 200 knots, but it is tough to judge. Any tip? Should I resort to the terrible "easy landing" or even worse, "no crashes" option?

Second, while I am mastering the other options, I can't quite figure cluster bombing.
My first try worked perfectly, although I released the bomb way before the red line became a dot. Now that I respect this dot policy, I systematically aim off and destroy innocent villages, and I must say I am barely surprised: it looks like the line becomes a dot right when you are on top of the target.
So, despite what the manual says, are you supposed to guesstimate when to release in advance (in the good old fashioned arc way) — and in this case, any tip for when to release the load — or am I doing it wrong?

Thanks in advance.
This question / problem has been solved by Strijkboutimage
avatar
Danster:
Hi,
Not sure, but it does sound like you're running dosbox with too high cycles, try lowering it (CTRL+F11), I think 3000 to 5000 cycles should be about right for this game.
That's absolutely right: I was running the game at 7500 or 10000, depending on my mood, and the jerky behaviours got fixed by lowering the cycle count. It also made the enemy much more aggressive (before, they felt absolutely lethargic!).
The downside is that the framerate is suffering heavily, of course.
In any case, thank you.
Your framerate may improve by using a different renderer in the Graphic Mode setup utility. It defaults to surface, you may have better performance using one of the hardware renderers.

Example: in the Zork graphic adventures, I was having issues with panning scenes.Particularly, earlier in Return to Zork, when walking up the stairs in the light house, it would take a few seconds for it to load the next screen, tearing the whole time it was trying. Switching to DirectDraw had little improvement, but using OpenGL resolved the issue entirely, and it now plays out exactly as intended.

So, checking those out may get you the proper control of a low cycle count with a decent framerate. If not, I know there's a lot more manual settings in the .conf file to play with that can help. If you do find a combination of settings that resolves everything, don't forget to tell GOG so they can test it and add it in as the default!
F-117A always ran at a slow framerate, dont worry too much about it.