Search the Community
Showing results for tags 'win10'.
Found 13 results
-
Not sure if this has been posted here already, but it seems that recent Win10 Redstone 3 builds (internal name for the next big Win10 update, due to be released in Fall 2017) are rendering 3rd party addons unusable due to changes in OneCore which is an essential part of Win10 (its part of the "Windows Everywhere" strategy allowing all Microsoft hardware platforms to use the same OS core, Desktop, Mobile and Xbox). This seems to affect pop up window handling of 3rd party addons for P3D/FSX. AFAIK. Redstone3 is currently only being rolled out to fast ring insider members but it might soon be extended to slow ring participants. Its currently unclear if those issues are due to a bug or an intentional change within OneCore. If its the latter then brace yourself as this would mean that many addons will require an update once the new Win10 build will be rolled out to end users. So if your sim recently started to act funny, ranging from "error creating child window", CTDs after loading scenario (PMDG 747), chaseplane and ezdok no longer working, erratic behavior of FSLabs A320 and being unable to open any add on windows like FSUIPC, GSX and everything else that sits under the addon tab in P3D, then welcome to my world....you are likely a member of Win10 insider preview. Looks like opting out of insider preview will require a complete reinstall of Win10, so i might sit this one out. I just hope its not going to be a permanent change that will require all addons with pop up windows to be updated. -
Hi, all, I'm a newbie to this forum. I've been building a cockpit over the past several months and am now building a new PC to run it. These are my specs: Intel Core i5-6600k 3.5GHz Cryorig H7 49 CFM cooler MSI Z170A Krait Gaming 3X motherboard MSI GeForce GT 710 MSI GeForce GTX950 2GB G.Skill Ripjaws V Series DDR4 16GB Crucial MX300 535GB SSD DIYPC S280-W case EVGA 100-B1-0500-KR 500W power supply I have been running MS-FSX Gold Edition w/Acceleration on Windows 7 with these add-ons: Orbx-FTX: Global BASE Orbx-FTX:VECTOR REX4 Texture Direct w/ REX Soft Clouds My Questions are: Do I stick with Windows 7 or move to Windows 10? Do I stick with FSX or is there an advantage to switching to FSX-SE? Any other 3rd party plugins I should consider? Any and all advice or thoughts welcome! Thank you kindly! Dave -
I've installed Win 10 along with Fs9 on two laptops and 7 months later this still isn't fixed. The bug when you are in full screen and you it the alt key to bring up the menu and the whole screen goes dark, if you want to to get to the menu you have to go to windowed mode first. Well this just won't do. Especially if youre running FSNavigator. Win 10 basically breaks Fs9. Any fixes for thia? I'm going to cross post this in the FS9 so hope that's ok. I need to find an answer to this.
-
Hi folks, I know this might not be the right place to ask this question..... I have searched and can't find a solution. I am trying to install a livery, manually in the cfg file,[notepad] when I try to save, I get an error, like I don't have permission... I am using W10, and P3Dv3 Thanks, Jerry Friz
-
All LINDA users are advised that no compatibility testing with Windows 10 has been carried out with the new Windows 10 release with any of the compatible flight simulators (FSX, FSX-SE or P3D). I have no intention to change my working or development systems until the new operating systems is proven to operate flawlessly with my setup and development tools. However, if LINDA users have or plan to cross to the dark side, please report your experience and success/failures here. There is nothing I will be able to assist but it will help others.
-
Hi, I have a Xbox One Controller connected via BlueTooth that I am trying to use to control Chase Plane. Chase Plane picks up the button assignments from the controller no problem. My issue is that certain buttons on the controller are sending commands to P3D, even though I cannot find any of them assigned in the P3D controller menu. For example, the "Change View" button on the controller activates the "End Scenario" menu in P3d. The A or "Select" button actives the brakes. I have also tried using FSUIPC to intercept the controller commands and assign them to either a NULL command, a keyboard command, or a FS command. However, no luck; the default controller/P3D behaviour persists. I've tried searching through the various WIN10 settings menus, but have not come across anything that is mapping the Xbox controller commands to something else. Any thoughts on how I can remove the default behaviour of the controller and the commands it is passing to P3D? Thanks, Tom
-
My windows got updated yesterday. I noticed that windows wanted me to update when I shut it down last night. Today I notice several irregularities: - My Majestic dash 8 isn't starting in a cold and dark config. Instead it starts on battery, and none of the switches do anything except move from one position to another when I manipulate them. FMC dont come on, and the radio stacks dont turn on. Turning the battery off doesnt do anything. Restarting the sim doesnt help. - Prepar3d v4.1 just hangs when I shut it down. It's window dissapear, but its on the taskbar showing as active. It's been 5 minutes now, and it still hasnt gone away. - My windows task bar shows up in the top of the screen instead of the bottom where I want it when I first boot up the system. I get alot of app crash messages when initially coming into the desktop. Subsequent startups during the day leaves the taskbar in its normal position in the bottom, and I get no app crash messages. I am using Nvidia surround on 3 screens btw. GFX driver is updated along with geforce experience. These are just three of the most glaring issues I had because of this update. Anyone else noticing any not normal things with their pc/sims?
-
Hello, for some reason I'm not getting any response from the ATC. Also during startup I get following error : Which is odd because as you can see I in fact do have English installed and set as default (I have my native language pack installed as well but that should not be a problem since it's not default, right? ) : But for some reason I do not get any response from the ATC at all. I'm using the text "SayIt" interface as I don't have mic setup, plus I don't really want to be talking to my computer, text interface is fine :-) Also the test in config does not work. The voice tests work fine, I even get ATIS response when I tune in ATIS on radio (P2ATC set to handle ATIS) but no response from any actual controllers : I'm flying IXEG 733 which uses a lot of custom systems so just to make sure it's not blocked by battery and so on I set P2ATC to ignore those : Any ideas pls ? PS: My flight plan seems fine. It's validated and filed. Also I'm using LKTB Gnd to try to get the clearance as there is no dedicated clearance frequency but that is not the issue - I tried them all, I get response from none. PS2: I also tried running the P2ATC as administrator and also in Win7 compatibility mode (just in case). No luck.
-
After upgrading my laptop to Win10 and a SSD, I decided to give FSX-SE another try, applying NickN's Bible from the start (FSX-MS is not an option, since I removed the DVD drive). However, when I tried installing Real Trim (https://github.com/nmeier/fscode/wiki/Realtrim), I find it's not available in the Add-ons menu. FSUIPC shows no issue at all. Has anybody been able to run Real Trim in Windows 10 and FSX-SE? For reference, Steam is installed in C:\Steam, where C:\ is the SSD. -
Hi. The program LINDA v3.0.5 causes an error: Unexpected Kernel Mode Trap. The error comes when I want to save a flight, the key is the "Ü". The Ü key is the default assignment for saving flights. So, I start the P3D and press the Ü key. Without further notice the P3D passed with a BlueScreen. It only helps to restart the computer. The error has come since I upgraded to P3D v4.3 and FSUIPC 5.1.3.2 and the error is reproducible. My system Windows 10 64-bit P3D v4.3 FSUIPC 5.1.3.2 LINDA 3.0.5 Currently I have disabled LINDA and I am wondering if I will do without LINDA altogether. Does anyone have similar problems or even a solution?
-
I’ve just had a catastrophic graphics event that seemingly randomly causes a totally black screen (that sometimes switches to a weird pinkish) and the only way to get out of it is to hard reset the PC. As a result, I have totally uninstalled all FSX related software, purged and clean installed the latest NVIDIA driver and done a windows scan for missing or corrupt files. All to no avail, now even with just basic FSX installed flying the trike around Friday Harbour with the high settings for my machine, it still happens. SO… Maybe this is the push to go to Windows 10. A few questions: 1. Is it definitive that the RealityXP GNS430 will not work in FSX-BOXED in WIN10? 2. If not, I’m thinking of going to FSX-SE. I purchased it a while back in a $5 sale day. Will my add-ons below (except RXPGNS) work in FSX-SE on WIN10? I know PE is OK. 3. Instead of the RXPGNS how about the MindStar 430/530. Is that functionally as good as the RXP? I know I’d have to have the subscription to RealNav data for updated databases. 4. I’ve ordered a 2nd SSD to use as a clone for future catastrophic events. Is Acronis the clone software tool of choice? Thanks for any insights. Bruce FSX boxed DX9 with Acceleration, WIN 8.1 64bit Z97 PRO-GAMER, i7-4790K @4.0GHz, GTX 970 4GB, 16GB DDR3 1600 SDRAM, 500GB SSD, 1TB HDD Add-ons: REX4 TD w/SC, ASN, PilotEdge Client, Carenado PA-28A, Carenado Phenom 100, Aerosoft F14X, RealityXP GNS430/530 Scenery: LatinVFR KSNA & KSAN, SIM720 KCRQ, MSE California South 2X, MSE KLAX / KSAN Ultra Res
-
So today after creating a new .cfg file and having everything work good... or so I thought... this popped up after my crash. I have no idea what it could be since all the drivers are up to date. Any help would be greatly appreciated. Thanks in advance!!! Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: XAudio2_6.dll, version: 9.28.1886.0, time stamp: 0x4b6b0791 Exception code: 0xc0000005 Fault offset: 0x0002cbef Faulting process id: 0x1c90 Faulting application start time: 0x01d0584630a72017 Faulting application path: C:\FSX\Microsoft Flight Simulator X\fsx.exe Faulting module path: C:\WINDOWS\SYSTEM32\XAudio2_6.dll Report Id: bc74dd36-c456-11e4-be9d-902b3457650f Faulting package full name: Faulting package-relative application ID:
-
Reported on the BBC News website today, form an orderly queue all you Windows 10 sufferers: Payout of $10,000 for Windows 10 updateMicrosoft has agreed to pay a Californian woman $10,000 (£7,500) after an automatic Windows 10 update left her computer unusable. Teri Goldstein said her Windows 7 computer had automatically tried to update itself to Windows 10 without her permission. She said the update had made her machine unstable, leaving her unable to use it to run her business. Microsoft said it had dropped its appeal to save on legal costs. Microsoft has been aggressively pushing the latest version of its widely used operating system, which is currently available as a free download for computers running Windows 7 and 8. However, many people have chosen not to upgrade, because they are running old hardware, have software that does not run on Windows 10, are concerned over the software's tracking features, or simply do not want it. In February, the company bundled Windows 10 in with its security updates and made it a "recommended update", which meant it was automatically downloaded and installed unless blocked by the user. Some people accused the company of trying to "trick" customers into installing the update. The Seattle Times reported that Ms Goldstein's computer had "slowed to a crawl" after the update, and Microsoft customer support had not fixed the problem. "I had never heard of Windows 10. Nobody ever asked me if I wanted to update," she told the newspaper.
- 36 replies
-
- 2
-
-
- windows 10
- win10
- (and 1 more)
