Menrva

Rends, do not touch the terrain .ini (the GermanyCE.ini for instance). The Longitude and Latitude of the stock terrain are correct, so restore them to default. The values I changed are those of the EnvironmentSystem.ini (which is in the Flight folder) that comes with Stary's mod. The first values in that .ini are the following: [EnvironmentSystem] UpdateRate=60.0 InclinationAngle=60 Latitude=0.0 I just changed them to this: [EnvironmentSystem] UpdateRate=60.0 InclinationAngle=23.5 Latitude=34.0 It seems to work for me. Report if it works or not. Bye!

Hi Stary! I noticed that with SARCASM 1.5, while playing missions set during winter, on some terrains set with their correct longitude and latitude we have night instead of daylight. I noticed you changed this values in the .ini: [EnvironmentSystem] UpdateRate=60.0 InclinationAngle=60 Latitude=0.0 I restored the stock default values and now night during daylight hours is gone. I hope this proves useful in case you are planning an update of your awesome mod.

Nice finding, jeanba! Mine one is at 0.1, the default value. I'm wondering what else these values change regarding the flight dynamics, apart from reducing the bouncing. However, as Wrench said, some planes do need new flight models since they were not updated to SF2 standards.

Have you tried playing with FM difficulty set to normal? See if it improves the bouncing problem when using a modded terrain. Also try to fly with stock unmodded planes and see if the problem occurs too. I hope it helps.

I once had this problem in my modded install: I removed the flightengine.ini in the flight folder and it worked mostly. I don't know the reason of this and since i needed a modded flightengine.ini (to allow better draw distance of trees and buildings) I extracted the original one with thirdwire utilities, i made the changes I wanted and it worked, no planes bouncing and exploding, or at least some that did it before now do not explode anymore. (However I also think it may be terrain related, but sometimes even with stock unmodded terrains the problem occurred).

.

Thanks a million for the link, SupGen. Your menu mod makes the original WOE menu work perfectly in sf2. The one in WOV is pretty different, as it uses different bitmaps for buttons. I guess i have no choice but to convert all those .bmp files into .tga with alpha channels to make them work.

Is it possible to make WOV menu screens (with the exception of the main menu) work flawlessly in SF2? I already tried to mess around with the various .ini of the screens but with no success, since some functions miss or words are not in their correct position or properly scaled. Thanks in advance.

I think it has something to do with the FlightEngine.ini. The one included in a mod (don't remember which) made my game crash. Now I use these following settings, and the game runs on Unlimited even with my crappy GeForce 310. [GraphicsSettings] ZBufferDepth=24 MaxVertexCount=16384 MaxIndexCount=98303 MaxTextureCount=16384 MaxModelType=4096 MaxMeshPerScene=4096 MaxModelPerScene=2048 MaxLightPerScene=512 AspectRatio=1.333333 MinPixelSize=1.0

Thank you very much for fixing all other export functions. I'm eager to create new planning maps for my WIP Red Sea terrain.

I'm glad Stary's back. Amazing tileset, as always!

A very useful tool indeed. Many thanks, gerwin.

Thank you Erik and everyone else involved in updating this wonderful site. It's such a pity that there were some complainers: clearly they have no idea how great the people of this community are.

Nice findings. I just hope TK releases another patch fixing at least one of those issues. Actually, I already noticed the first bug while pressing another key, probably F4... well, the one that lets you see all the aircraft, friendly and enemy.

That's strange. I remember my WOE install did work on Win7 x64, but only after installing the last patch. Of course, the SF2 series is far more Win Vista/7 friendly, but the october 2008 patch should make your game work correctly. Try to update your video and audio drivers, as well as directx.

Amazing photos! Sure they wasted a lot of ammo for a single Charlie.

I'm back. Damn, Wrench is right: the removal of the flightengine.ini does work for me, but only to an extent. In my mod even stock aircraft bounce a lot, especially the Harriers, even though before the removal of that file they crashed as soon as I started the mission on the runway. After hours of research, trial and error, I came to the conclusion that neither the data.ini of the aircraft nor the .inis of the terrains are involved directly: I've tried to remove the modified .inis of both modded stock aircraft and terrains, forcing the game to use the original ones, but nothing has improved. One thing is sure: the patch TK released ruins most mods, but the stock game works as intended. I apologize if my English isn't all that clear. After all, here in Italy nobody speaks English, apart from teachers, who sometimes don't even know what they're actually trying to say!

I created an account years ago just to download mods from CombatAce, so i feel a bit guilty to post something so late now. I've just found what may be causing the issue: I played my heavily modded SF2 and noticed that the F-14 had the same issue on both the stock and my modded Desert terrain. Then I played the same mission of the Desert Fury campaign on a completely stock SF2 and it didn't have the issue. After checking all .ini files in my modded SF2 I tried to remove the FlightEngine.ini and all aircraft soon worked correctly as usual. I hope it helps. P.S. Still I have no idea which parameter in the FlightEngine causes this.

.