December 24, 201510 yr I certainly did not 'pay' to get Windows 10, nor did millions of other folk. Now yet you haven't. The first rule of dealing with a tech company: Any company that offers you a free product really wants to make you the product. I don't need to worry about rolling back to Win 7... it's already running just peachy on my computers. I do have access to a Win 10 computer (Surface Pro 3 that my wife's employer gave her) and I'll just say I'm not overwhelmed. It's just another OS (not that that's bad), and I'll "limp" along on my "old" Win 7, thanks anyway. Greg
December 24, 201510 yr Commercial Member Windows 10 rocks!! Don't delay - update today, fix all your bad drivers and live the dream. Regards jja Jim Allen[email protected]SkyPilot Software home of FSXAssist / P3DAssist
December 24, 201510 yr Hello planenut...It seems you have virtually the same set up as me. I am lucky enough to have two p3dv3 licences and did a trial run on my new windows 10 laptop before upgrading my main dedicated simulation PC. My conclusion is... go for it. My laptop works great and doesn`t miss a beat and I have now upgraded my windows 8 pro PC to windows 10. Everything is working fine. A few of things I would add are below. 1 If you decide on a disc clean up after you upgrade, then do not remove your old version of windows until you are satisfied 2. I have read on the windows 10 forums that Microsoft intend to migrate everyone over to windows 10 in the new year. 3. Saitek now have beta drivers out for all the Saitek controllers except the throttle quadrant. Mine works fine however in windows 10 4. Use the spad drivers for your saitek panels and they will work great as well 5. If you have a DX12 capable graphics card, in the long term P3Dv3 may be upgraded to use it which will improve your graphics as well. Sorry for the long post.. but having gone through the same descision .. I hope this helps.. Regards...Rob PS Merry Christmas
December 24, 201510 yr I'm going to stay with Windows 7 for the time being. A certain game I've been wanting to check out is going to be DX12 only, so I might have to upgrade. Luckily, that gives MS a year to iron out the issues in Windows 10. Jeff Thomson
December 24, 201510 yr Commercial Member The nice thing about Win 10 is that it is an Evergreen technology - IOW always current. Microsoft DEVs are really happy about this new trend. Be Agile. jja Jim Allen[email protected]SkyPilot Software home of FSXAssist / P3DAssist
January 4, 201610 yr Here's my issue so far when I upgraded last night to Win 10 from Win 7 1. I'm running Nvidia surround video. That had to be reconfigured. 2. Opus FSX would not start permission problems...so I granted "everyone" full control of my Program (x86)\Microsoft Games folder 3. My current issue is that if I change the date/time in FSX...FSX Crashes...I think it's another permission problem...I will research this week. Other than that VOXATC works...CH Yoke and rudder pedals still there. However, Win 10 removes some applications that are no longer compatible. So far the two it removed was not FSX related...more chip set related. -realkewl
January 11, 201610 yr Where do I start ? Being in IT myself I firmly believe that the old adage of "if it ain't broke don't fix it" DOES NOT APPLY. Because software and operating systems move on, and unless you MAKE THE EFFORT to keep up, you end up with software that isn't supported on the OS you're using. I learnt this lesson trying to fix DOS systems for (stubborn) clients running it in Windows ... yes really. However that doesn't mean the move to W10 is smooth. I have an old 32 bit running ASN connected P-2-P to my 64bit running FSX:SE. There are issues with W10 and the way it handles Homegroups, which I still need to get to the bottom of, so if you're using a P-2-P and want to upgrade to W10; BEWARE ! I'm flying FSX:SE without too many issues, and by continuing to fix configuration details my knowledge of W10 increases ...... much the same as when I upgraded to Vista/Win7 from XP One important piece of advice I can give though is that "things" do seem to run smoother if you use the Microsoft Account details to login onto the PC rather that a Local Account.
Create an account or sign in to comment