jmarso

That was one of the first things I tried. I've used that method to make other older games run 'unstretched' with black bars to either side of my screen. Oddly enough, with SF2, the game causes the reduced screen res to vanish and go back to full stretched widescreen. However, I do appear to have a 'fix' by the method I described above. I haven't played around with it that much since messing with it a week or so ago, but I'll probably do more in the next few days.

Think I might have got it working. By turning off compatibility mode and keeping 'disable fullscreen optimizations' turned on, coupled with Nyghtfall's fix. The loading screens and so on are still stretched, but the graphics in game seem normal. If I change a control setting or what not it goes back to being stretched, but I can fix that by exiting the game and reloading after making my changes. I'll have to play around with it some more to see if it is well and truly working correctly, but I think it may be. I was starting to think I was just going to have to give this game up entirely.

WIN10 here also.

Tried the above- no joy. Anything particular in the properties of your executeable?

I've got an AGON 3440x1440 curved monitor, and no matter what I've tried, I cannot get the game to either 1) have a normal (non-stretched) look in widescreen, or 2) launch in a lower resolution without automatically reverting to full widescreen and being stretchy. Things I've tried: 1. Changing the monitor resolution and setting the game option settings to match 2. Changing the game option settings by themselves 3. Editing the .ini file in the options folder in concert with 1 and 2 above, manually trying different aspect ratios, including 2.370370. (Game menu doesn't offer 21:9 on its own, only 16:9 and 16:10) 4. Editing the properties of the .exe file for 'run as admin', 'disable fullscreen optimizations', 'Windows 7 compatibility mode'. 5. Various combinations of the above 4 things. No matter which I try, when I start the game, it comes up in full widescreen, stretched out, even if the options say it should be in a different resolution. Something somewhere is getting overridden when the game boots, and I don't know what. Anyone have any experience with this any success at making it work? Thanks.

View File SF2_Norway_1986_v2.0 (Excerpt from README file) This mission pack is designed to coincide with / complement Eburger68’s North Cape campaign. It is essentially the same scenario as the ‘Fighting Withdrawal’ campaign, told a slightly different way, with a twist and a new pack of single player missions designed to have some ‘story continuity’ to them. Part I is an eight-mission pack in which you are assigned to VF-84 as an F-14A (82) pilot in Carrier Air Wing EIGHT, in September of 1986. When the war begins and the Nimitz battle group begins its fighting withdrawal, you are going to have your hands full fighting off hordes of Soviet bombers and aiding your Norwegian allies every way you can. Part II is a ten-mission pack in which you are assigned to VA-86 as an A-7E pilot in Carrier Air Wing EIGHT. When the war begins and the Nimitz battle group begins its fighting withdrawal, the two A-7E squadrons are detached temporarily to land bases in Norway to press the fight against the Soviet invaders in the north. Two of the missions are transits, with eight combat missions in between. Disclaimer: the weather in these missions isn't nearly as good as in the screenshots. ;) Submitter jmarso Submitted 08/20/2019 Category User Made Missions

It's not a terrain, it's an entire campaign mod that includes the needed terrain. Here ya go:

Mission List: 1. North Storm Rising: On the eve of war, join up with the rest of the squadron and reposition to Batsfjord. 2. Kickoff: Lead a division of four to the FEBA and engage tanks, SAMS, and enemy aircraft trying to kill you. WWIII has begun! 3. Interdiction: Lead a section to destroy a Soviet troopship headed for Vadso, escorted by two missile corvettes. 4. The Siege of Kirkenes: Another tankbusting mission in the FEBA, as you try to help blunt the rapid Soviet advance. 5. The Parthian Shot: Participate in a multi-axis deck strike against the Soviet Kiev battle group transiting to the north of Norway. 6. Falling Back: Displace to Lakselv before your base at Batsfjord is overrun. Hit the enemy and scout his advance as you go. 7. Behind Enemy Lines: Lead a section to sink a pair of Soviet tankers threatening to dock in Burygoyne and shorten the enemy's supply chain. 8. Breaking the Chains: Strike enemy supply lines just behind the FEBA, in inclement weather. 9. Hunted: Evade a lone enemy ace hunting you and your wingman in poor weather as you try to accomplish your CAS mission. 10. We Shall Return: Accompany the remnants of the two-squadron detachment back to the USS Nimitz as the battle group leaves the theater. If you like to turn on the autopilot during your transits, hit F12 and watch the action going on elsewhere, these missions have a lot to offer! (Just don't stay away for too long, or you might get plinked!)

View File Norway_1986.7z Excerpt from README File: Setting In this ten-mission pack, you are assigned to VA-86 as an A-7E pilot in Carrier Air Wing EIGHT, in September of 1986. When WWIII begins and the Nimitz battle group begins its fighting withdrawal from Norwegian waters, the two A-7E squadrons are detached temporarily to land bases in Norway to press the fight against the Soviet invaders in the north. This mission set is designed to coincide with / complement Eburger86’s North Cape campaign. It is essentially the same scenario as the ‘Fighting Withdrawal’ campaign, told a slightly different way, with a twist and a new pack of single player missions designed to have some ‘story continuity’ to them. Requires Eburger86's North Cape user made campaign mod. This is actually Part II of a two part release. Like the SW movies, they are being made out of order. :p Submitter jmarso Submitted 08/04/2019 Category User Made Missions

Replayed this campaign recently and enjoyed it. (Taking a break from DCS) Ran into an issue with the Kola campaign, one I encountered in the past, and I'm not sure if it's a known issue or not. Fighting Withdrawal and Return to Norway work fine. In the Kola campaign, however, everytime I start the campaign and fly a mission (generally a strike mission), I get a CTD when the first weapon hits a target. I've tried it in the campaign, and in single missions up there in the White Sea and the around the Kola P. and the same thing happens. Any idea what is going on here?

...And works good, lasts a long time! Thanks again!