Anyone tried StrikeFighters 2 with Windows 10?

[stuntman]

great, thank you!

[Richo]

I did not get my Logitech Extreme 3D PRO to work and could not get drivers.  That was the only issue I had with Win10.  However that is the only type of joystick I have.  So I have now went back to Win7.  All my other Logitech gaming hardware worked fine when I got the driver's.  I may have to wait till I can get some Win10 driver's for the Logitech Extreme 3D PRO.

[+russouk2004]

win 10...?....im impressed...so far everything runs smoother than 7

Edited August 13, 2015 by russouk2004

[eightlein]

What compatability mode is it running in?

[saisran]

I did not get my Logitech Extreme 3D PRO to work and could not get drivers.  That was the only issue I had with Win10.  However that is the only type of joystick I have.  So I have now went back to Win7.  All my other Logitech gaming hardware worked fine when I got the driver's.  I may have to wait till I can get some Win10 driver's for the Logitech Extreme 3D PRO.

I also have a 3d pro and so far no problem. Logitech Profiler is up and running. Try to r

[Richo]

I also have a 3d pro and so far no problem. Logitech Profiler is up and running. Try to r

I did try to reload drivers.  I went to Logitech web site and they did not have drivers for win10.

However I did get drivers for my G13, G710+ and G9X.  They worked very well.  If I have to change compatability mode how do you do that? 

[Spinners]

I've gone from W8.1 to W10 on my laptop and I'm less than impressed but going from W7 to W10 on my desktop has been a much happier experience. @ Richo - I can't help with your compatability mode query but I'm using a Logitech Extreme 3D Pro joystick in W10 with no problems with SF2.

[+MigBuster]

I did try to reload drivers.  I went to Logitech web site and they did not have drivers for win10.

However I did get drivers for my G13, G710+ and G9X.  They worked very well.  If I have to change compatability mode how do you do that? 

 

Generally you right click on the shortcut or exe file for a program, then select properties -> Compatibility tab

[stuntman]

Turns out I have visual artifacts (flickering, textures tearing, dds textures not working) playing sf2 with windows 10. After a few tests, it comes from my modded flightengine.ini; Which i modded for a longer viewing distance. Any DetailMeshSize parameter set over 12 creates these artifacts. Do you guys observed this? Do you have any idea how to fix this? (I set this parameter at 16 when i was using windows 7, and everything was fine).

[+Menrva]

I have no such problems, have you tried updating your video drivers?  There should be new ones available by both ATI and nVidia.  I have an old GeForce video card, the guys at nVidia were kind enough to make some updated drivers for it and other older cards.

[stuntman]

It seems I've just fixed the problem. It looks like the culprits were the latest Nvidia drivers 355.60 (which I installed a couple days ago). Reverting back to 353.62 fixed it so far.

Edited August 16, 2015 by stuntman

[+Viper63a]

Ok, I ran into the same issue with nVidia. I just came on here to report that, but it looks like Stuntman, et al, already did. The new nVidia driver causes intermittent graphics issues...My jet fragments and I am flying around with bit of my plane in an "exploded view"...parts all over the place.

 

Other issue, I reported it as a minor issue, now it is becoming a major pain...Windows 10 is not consistently assigning my CH flight controllers. Ie, FighterStick device 1, throttle device 2, pedal device 3. In Windows 7, this never changed. In Windows 10, it assigns them however they want. Ie. My Fighterstick and ProThrottles (and or ProPedal) assignments changes. So my controller assignment goes out the window every couple of days. Has anyone else seen this with multiple controller set ups?

 

If I can't find a solution for this, I will have to go back to Windows 7....I am not about to reconfigure my buttons on all my games every couple of days...

 

=V=

Edited August 19, 2015 by viper63a

[Geary]

viper63a,

 

  I'm having the same problem with my CH Products; Figherstick, Pro Throttle and Pro Pedals.

 

  I've saved a working copy of the default.ini file and when Windows 10 screws up the one in an install I copy the saved file into the controls folder.

 

  Doesn't always work but it's a start.

 

  Hope CH Hangar comes up with a fix soon.

[+Viper63a]

Hey Geary,

 

Good to know it's just not me (not that misery loves company, lol). I tried backing up the config file...but, no joy there.

 

I just read some posts in the CH Hangar that CH is working on it. But I'm not sure if that is wishful thinking or a CH issue to start with, more of Windows 10 not caring what order USB devices are configured...just my guess. Maybe CH will release a wrapper interface or some thing. Hope they fix this soon, mainly before my "backout to Windows 7" time runs out. Thinks it a month and then you're stuck...

 

Also, did you hear the rumors that MS may try to control what you have on your PC? A Genuine Check that disables stuff they think is pirated? I don't have anything pirated (least not that I am aware of)....but that has me concerned...What if they determine Falcon BMS is pirated? etc etc etc...

 

=V=

Edited August 19, 2015 by viper63a

[+EricJ]

So far works fine still, no real issues on my end.

 

I saw that article on Facebook but didn't read it, and good luck though (Steam does a good job I think) but yeah that'd be interesting if it does work though.

Edited August 19, 2015 by EricJ

[Geary]

No doubt about it, Windows 10 is buggy, but I think in time many of the bugs will be fixed.

 

I'm trying setting my default.ini to read only.  I'll see how that works.

 

Already got messages from software companies popping up on my computer asking if their software is genuine. Thanks Microsoft. Figured this 'FREE' new operating system has some ulterior motives.

 

I can always reload Windows 7 if I want, but I'll stick with 10 for a while and see where it leads.

 

I'm also running SF1 on Windows 10.  It loads game and missions alright but crashes half the time exiting missions.  Don't know if that will ever get fixed.

[+Viper63a]

OK...so  changed the order of my devices (where the devices are plugged in the back of the computer) until FighterStick is Device 1, ProThrottle is Device 2, and ProPedal is Device 3....will see if this helps. This didn't matter in Win7...but will see if Win 10 scrambles them again.

[bubu]

Ok this is related to Win 10 since DirectX12 is installed with it... but now my graphics don't work as well, getting tile breaks, slow frame rates when dropping bombs, etc. Since the software itself last had a TK update in July 2013 I wonder if THAT has something to do with it... mysterious since I am running a GTX NVida 900-series graphics card (brand new)...

[+MigBuster]

Issues with CH Manager;

 

well it works okay for me and luckily I had put on BMS & DCS before SF2 because it worked fine in both.

 

SF2 was not recognising any CH commands even though they were listed in default.ini. I had to manually remap them in game, but they have stuck since.

 

Whether they need to be run as admin in win 7 compatibility mode.

[+Viper63a]

I manually reset all the controls in game last night...went to sleep, woke up today and booted up the PC...my fighterstick and my throttle switched again...

 

:(

[+Viper63a]

Issues with CH Manager;

 

well it works okay for me and luckily I had put on BMS & DCS before SF2 because it worked fine in both.

 

SF2 was not recognising any CH commands even though they were listed in default.ini. I had to manually remap them in game, but they have stuck since.

 

Whether they need to be run as admin in win 7 compatibility mode.

 

Uninstalled CH Manager. Re-plugged in CH devices...will run without the manager and see what happens.

 

=V=.

[saisran]

For most windows 10 related issue the usual fix is to download the latest drivers off manufacturers site. If your lucky they might have released a new win10 compatible driver. Uninstall the affected drivers. Reboot and install new drivers. If that doesnt work. Uninstall and reinstall using compatibility mode

[+MigBuster]

CH Manager 4.55 is the latest and one to use - quite old now.

 

Run the SF2 games as admin and change compatibility modes (in shortcut properties)  - they might not be getting access to write the control changes properly.

[531Ghost]

Running CM v4.55 under Win 10 and CM is running just fine on my Toshiba Laptop.  Keys test in CM v4.55 after the .map is downloaded presses the appropriate keys that are programmed.  That said, Win 10 knocked out my mouse pad and mouse buttons on the laptop.  Had to plug in a mouse.   AND, when I go to install SFP2 onto the laptop, after supplying my email address and code SFP2 doesn't seem to be able to connect to the interwebs to verify, even though, I AM connected.  UGH.

 

Keys:

 

Fresh update to Windows.

Uninstall/Remove all CM

Unplug CH Devices

Re-install CM

Wait for install to finish

Re-plug CH Devices

Wait for devices to install

Calibrate devices.

Edited August 21, 2015 by 531Ghost

[+Fubar512]

Running CM v4.55 under Win 10 and CM is running just fine on my Toshiba Laptop.  Keys test in CM v4.55 after the .map is downloaded presses the appropriate keys that are programmed.  That said, Win 10 knocked out my mouse pad and mouse buttons on the laptop.  Had to plug in a mouse.   AND, when I go to install SFP2 onto the laptop, after supplying my email address and code SFP2 doesn't seem to be able to connect to the interwebs to verify, even though, I AM connected.  UGH.

 

Keys:

 

Fresh update to Windows.

Uninstall/Remove all CM

Unplug CH Devices

Re-install CM

Wait for install to finish

Re-plug CH Devices

Wait for devices to install

Calibrate devices.

 

Thanks Ken, You Da Man.