Zola25

^ I make that three questions . However, I am interested in the answers also.

Sadly there's no way to put the update functionality back on a par with Windows 7/8/8.1, but these steps will give you much more control and is how I've been managing updates since the Win 10 preview builds. 1. Fire up the local group policy editor. Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Windows Update. Open Configure Automatic Updates, set the policy to enabled. In the options box set "Configure automatic updating" to "2 - Notify for download and notify for install", then click "ok". This then means you will receive notifications, but it won't install updates without you pressing the update button. Note it may take a reboot or two for the policy to take effect. You'll know it's working if you go to the Windows update page of the settings app and at the top it says "Some settings are managed by your organisation", the message is due to group policy mainly being used to manage computers on domains. 2. Go into control panel (not settings) > system > advanced system settings >advanced > hardware > device installation settings. Set "Do you want to automatically download manufacturers apps etc" to "No". This will allow you to update, but windows update should then not replace any existing drivers. 3. For even finer control, google for "Windows 10 hide updates". See https://support.microsoft.com/en-us/kb/3073930 . This will allow you to install an MS hotfix that allows you to selectively disable any current updates including drivers before pressing the update button if you've completed step 1 above. Hope this helps.

TK has responded to my thread on the TW forums again, he's made an (almost) certain statement that there will be no further PC updates: Zola25, Thanks, but the game is over 7 years old, so there should be no reasonable expectation for a patch at this point. We'd love to be able to do more updates, but we simply do not have the resources to do them at the moment. If you need a clear "yes" or "no" answer instead of "maybe", then it has to be "no". That way, any update we do would be a bonus, and no one is disappointed if we never do another update. Thanks! Although this is disappointing it's hardly surprising, and at least we know where the series stands. ​Hopefully nVidia's next driver will help, which then leaves the lack of AI using countermeasures pods as the worst outstanding bug IMO.

Before taking any action I'd recommend disabling driver updates via Windows update - I've also had it swap out my NVidia driver for whichever one it fancies! Open system properties, select the hardware tab, then Device installation settings. If using Win 10 build 10586/1511 change the yes to a no. I'd then use Display driver uninstaller, and install the NVidia driver you wish to use with "perform clean install" checked.

Definitely worth trying a driver update. Intel iGPUs perform notoriously strangely in this game at times.

I've now tested 359.06 and for me (on Windows 10) these drives reduce the problem, but doesn't entirely eliminate it. As for TW/TK, I wish he'd come clean about whether he's abandoned the PC games or not. His responses seem to be very cryptic.

Thanks Stingray, I've been away on business for a couple of days so had not seen the response. I'll give the new drivers a go and report back.

Thanks Fubar, it's good to capture the drivers for those who only play SF2 as this at least gives them a workaround in the short term. As the discussion on the TW forum centred around Windows 10, I've created a new thread here http://bbs.thirdwire.com/phpBB/viewtopic.php?f=9&t=9754 and have clearly described that the issue happens on Windows 7 on which the SF2 series is supported. I hope TK will weigh in further on the matter......

This is quite worrying for the future of the series. I suspect I am in the same position as many others in that I need to run newer NVidia drivers for other games. I'll post a thread on the TW forums, not that I expect a response or even an acknowledgement.

It runs very much the same as on Windows 7 x64 I've found, i.e. almost perfectly but with a very occasional crash to desktop on mission exit. I'm now running SF2 in Windows 10 which has also been fine so far.

You can literally copy and paste the stock SF2 folders to wherever you like, you'll need to make new shortcuts but this will work. Assuming you use a mods folder, you can also move that to the d: drive. All you then need to do is find your options file, which defaults to %UserProfile%\Saved Games\Thirdwire\Strike Fighters 2\options.ini, then in this file under [Mods] change the directory location to point to your new mods folder.

You can also use the Thirdwire Auto installer which will download and install all the games, XPs and DLC that you have purchased.

Voted. All SF2 titles and XP's merged, but the only DLC I have is the campaign customiser.

I have to agree with the sentiments expressed above. Without the modding community the SF series would be an interesting distraction, but mods have transformed the game into something spectacular where pretty much any scenario can be fulfilled. It's like Birds of Prey, CFS, Fleet Defender, F-19, LOMAC and all the Jane's games of old rolled into one. It may not have the avionics fidelity of some of those titles, but what is there is sufficient to scratch my itch. TK provided may have provided the blank canvas, but this community provided the world class artists to flesh it out and for that I will be forever grateful. For me at least, the hard work and dedication of the modders has given me countless hours of entertainment since I accidently discovered the series 8 years ago.

Hi Eric, I can now answer my your question above. After playing around with a stock SF2 only install and walking through the patches, the last version I have that works as expected is July 2012. As soon as you patch to May 2013 or beyond, the behaviour when setting a StartTime changes.

No problem Eric, and yes I agree it used to work perfectly. On further testing I've found it will work as long as the start time range is not set later than 16:00 or earlier than 06:00. I've got a feeling this bug must have only been introduced in a recent patch. What is interesting is night capable aircraft can still have subsequent campaign missions start at any time, as far as I can see this bug only effects the very first mission in a campaign, so it not big a problem at all. If I thought TK would fix this I'd post a bug report on the TW forums, but given that he's aware of the external countermeasures bug Jul 2013 introduced I can't imagine we'd see a fix for this either.

I've had a little more time to look at this today and the bug actually appears to be global, and not just limited to naval campaigns. Any campaign with a start time set will start at 0600 regardless of the time in the campaign data file. This is the case for not only the SF2NA exe, but also with the plain old SF2 exe with no other mods. It would be interesting to see if someone who's install does not include SF2NA at all gets the same issue. For reference my base install is fully merged which was recently installed using the auto downloader: SF2 SF2V SF2E SF2I SF2NA Both expansion packs Campaign customiser July 2013 patch

I've been playing around, and I think I can shed some light on this. It seems that it only affects campaigns where NavalCampaign=TRUE. I've managed to trigger the same bug in all the terrains I've tried (Germany, ODS, Black Sea and Korea) with the exception of Iceland. I've got a feeling that if the start time is set for a naval campaign it's not working correctly, and perhaps is only working in Iceland due to the unusual latitude. What I can say for sure is it's not a problem specific to the ODS mod. For now I've commented out the start time in the affected campaigns, as I'd rather do that than lose the carrier groups personally.

The only issue with July 2013 I've seen are that AI aircraft don't release counter measures from external pods. They are still able to use built in CM though.

If other naval planes are showing up OK on the carriers, check the MinBaseSize you have set for the A-5

If it helps, I downloaded the 4th part twice as the first time the archive was reported as corrupt. That may have just been for me, but I guess it's possible that some other people also had to download it twice. I've not had a chance to play the campaigns yet, but very much looking forward to it - thanks to all involved

If you have an old custom FLIGHTENGINE.INI file it can cause this issue.

I suspect you are correct that the problem is due to differences between DX9 and DX10/11. Not sure this is the best solution, but running the game in DX9 mode would prove this. In your options.ini file change ForceDX9=FALSE to ForceDX9=TRUE. Edit - beaten by a Jedi Master By any chance, are you using Intel integrated graphics?