-
Please see the most recent updates in the "Where did the .com name go?" thread. Posts number 16 and 17.
I'm so tired....
- Thread starter Cees Donker
- Start date
I've only read a few lines in this thread (sorry if anything is a repeat). But a couple of points:
a) Development is brutal on any sim installation and crashes are cumulative; each one can cause corruptions that beget more crashes. You want the cleanest base sim possible, and to keep it that way. When I was developing regularly, I had every installed file needed to run the sim 'just the way I like' in a never-been-CTD'd sate backed up on an external HDD. About every 1-2 weeks, I would wipe and restore. I still use this method of file management (but only restore every couple of months), and it's really limited the number of CTD's. I had 3 CTD's in the last 10 or so flights, and thought it was really unusual....turns out it was the GPU kicking the bucket.
b) Get an PCI SSD that can house Windows and the simulator (on separate partitions). The file sizes in FSX/P3D are enormous, and no single purchase has done so much to improve frame rates/stutters etc. I bought one on a Black Friday deal last year, and it was reasonably affordable.
c) No firm opinions on Windows 10 (not the anniversary edition) other than it's what I run and haven't seen any significant de-stabilizing issues.
a) Development is brutal on any sim installation and crashes are cumulative; each one can cause corruptions that beget more crashes. You want the cleanest base sim possible, and to keep it that way. When I was developing regularly, I had every installed file needed to run the sim 'just the way I like' in a never-been-CTD'd sate backed up on an external HDD. About every 1-2 weeks, I would wipe and restore. I still use this method of file management (but only restore every couple of months), and it's really limited the number of CTD's. I had 3 CTD's in the last 10 or so flights, and thought it was really unusual....turns out it was the GPU kicking the bucket.
b) Get an PCI SSD that can house Windows and the simulator (on separate partitions). The file sizes in FSX/P3D are enormous, and no single purchase has done so much to improve frame rates/stutters etc. I bought one on a Black Friday deal last year, and it was reasonably affordable.
c) No firm opinions on Windows 10 (not the anniversary edition) other than it's what I run and haven't seen any significant de-stabilizing issues.
gman5250
Charter Member
Interesting thoughts John.
One observation. I've installed every revision of P3D since 2.0 was first released. I maintain a dedicated SSD for the sim, and only the sim. The "finicky" nature of P3D has been a constant since the beginning. I rarely update P3D, usually doing a clean install to make sure my R&D has not translated from previous version to the newest revision.
My observation has been that the sim FSX, FSX/SE and especially P3D does not like any disturbances i.e. things multi tasking in a multi-core processor, while it the sim is operating.
Case in point. I often open my internet browser (Microsoft Edge) while P3D is booting. Usually there is no issue, but many times if I drag a menu, or click a mouse button, that action translates to a mouse drag across the live Prepar3D window. A good percentage of the time P3D will instantly shut itself down. If I let it boot back up and do not try to use my browser it usually boots without a hitch.
Just one observation that may be helpful.
One observation. I've installed every revision of P3D since 2.0 was first released. I maintain a dedicated SSD for the sim, and only the sim. The "finicky" nature of P3D has been a constant since the beginning. I rarely update P3D, usually doing a clean install to make sure my R&D has not translated from previous version to the newest revision.
My observation has been that the sim FSX, FSX/SE and especially P3D does not like any disturbances i.e. things multi tasking in a multi-core processor, while it the sim is operating.
Case in point. I often open my internet browser (Microsoft Edge) while P3D is booting. Usually there is no issue, but many times if I drag a menu, or click a mouse button, that action translates to a mouse drag across the live Prepar3D window. A good percentage of the time P3D will instantly shut itself down. If I let it boot back up and do not try to use my browser it usually boots without a hitch.
Just one observation that may be helpful.
UnknownGuest12
New member
Quit FSX entirely. Using P3D 3.5 on Windows 10, with no problems at all. Asus 970. Good frame rates no or very rare crashes.
txnetcop
Charter Member
Didn't really have any problems of any consequence on Win 10, still kind of wonky at times. Besides I just would rather use Win 10 for other things so dual booted Win 7 to my 1TB HD and FSX Gold with Orbx and FSX Steam (plain) run just beautifully, nice frame rates, no stutters, runs all the new stuff so far on an old high end socket 775 system. I swear that sometimes I think Windows 10 is being watched by Big Brother! I did just build a new high-end system with an Intel 6700K and 16GB of fast ram and an Nvidia EVGA Superclocked GTX970 that got me salivating...man there is some nice hardware out there and cheap! By the way, P3d is nice but I highly recommend trying X-Plane 10.5...very stable!
Ted
Ted
BendyFlyer
Charter Member
Cees, Gman5250, yep I agree re instability. I can't add much as I am off-grid in a very primary way and rely only on solar/generator for power which limits my technological adoption. I have kept my box a basic off the shelf HP with WIN 7, dual-core chip set and 4.0 GB speed, I have rebuilt FSX so many times (hardware and scenery issues dominate the stuff ups for me) that I began to carve up the system to be kept in discreet parcels (directories) which I can put back in on a rebuild (All my scenery now resides outside of FSX except the default stuff and I have a minimum of aircraft to use unless I switch in a directory to replace the sim-objects (so I parcel them up according to eras, pre WWII, post WWII, the jet age etc) after a corruption occurs (and MS FS is really good at getting itself twisted a lot). I guess on one rebuild I looked closely at what the install was doing and realised that FSX likes the mundane or ordinary in hardware and trying to go super fast trips it right up, the other thing is I give it space and time when loading or shutting down. The other thing I shut off was all WIN7 updates (yes and the PC has run just fine ever since and as browser or internet access and work is a different beast [Java etc] so I dont care if there is another so called update, update what, they stopped developing WIN7 years and years ago) when I realised they were all to get me to go to WIN10 of which I have no interest in whatsoever. It seems to me that the FSX was really designed for the boxes available at the time and the coding gets easily fragmented or the run routines get out of whack easily if there is competition on the chip for space and if script calls are interfered with.
That being said all I have found so far is that a lot of tweaks have been abandoned and I just run a bog standard box with the settings FSX thought were appropriate for my system at set up and left it at that. I do not get CTD's or mid flight crashes at all. Where I get crashes or stuff ups is in the menu section or sim settings selections where FSX has to reset itself and the time function most of all will cause a major hiccup. This is where I discovered that FSX actually references non FSX software and hardware PC settings to provide information about windows behaviour, units of measurement, time etc. My thoughts about this is the more patches the worse that will get, so no more patches. Have I fix for any of this, nope, but I sure have mitigated the problems by not adding to them.
Just another way of looking at the same problem I guess. FWIW. Yeah and as an old hand Unix programmer I despise MS stuff always have, inelegant convoluted crap! But that is what is that is what is, now If I could make FSX run on Linux properly that would be the solution, but I can't, too hard to emulate.
That being said all I have found so far is that a lot of tweaks have been abandoned and I just run a bog standard box with the settings FSX thought were appropriate for my system at set up and left it at that. I do not get CTD's or mid flight crashes at all. Where I get crashes or stuff ups is in the menu section or sim settings selections where FSX has to reset itself and the time function most of all will cause a major hiccup. This is where I discovered that FSX actually references non FSX software and hardware PC settings to provide information about windows behaviour, units of measurement, time etc. My thoughts about this is the more patches the worse that will get, so no more patches. Have I fix for any of this, nope, but I sure have mitigated the problems by not adding to them.
Just another way of looking at the same problem I guess. FWIW. Yeah and as an old hand Unix programmer I despise MS stuff always have, inelegant convoluted crap! But that is what is that is what is, now If I could make FSX run on Linux properly that would be the solution, but I can't, too hard to emulate.
Killbilly
SOH-CM-2026
I'm sorry to hear so many people having trouble. I run on Windows 10, allowing updates -- even the scary new one, and I just must be lucky. FSX is pretty smooth with detailed planes over FTX detailed airports (FPS usually around 35 where I have it locked). It does slow down over big cities, but not so bad that I can't enjoy the flight. I do some long flights, and I have yet to have a crash of the sim (plenty of crashes IN the sim). Once in a GREAT while, my screen will go black for just a second, but it comes right back.
Anyway, just know that it can be done. I don't know how I'm doing it, but it can be done.
Here are my system specs:
Intel Quad Core i7-6700K 4.1 GHz OC
Nvidia GTX 980 TI
Asetek Premium 240mm Sealed-Loop Liquid Cooler
32 GB DDR4 Corsair Vengeance 2666 MHz RAM
2 TB ADATA SP510 SSD
Windows 10 Pro
FSX + Acceleration from original discs.
CH yoke, pedals, throttle quadrant, and fighterstick.
TrakIR 5
Anyway, just know that it can be done. I don't know how I'm doing it, but it can be done.
Here are my system specs:
Intel Quad Core i7-6700K 4.1 GHz OC
Nvidia GTX 980 TI
Asetek Premium 240mm Sealed-Loop Liquid Cooler
32 GB DDR4 Corsair Vengeance 2666 MHz RAM
2 TB ADATA SP510 SSD
Windows 10 Pro
FSX + Acceleration from original discs.
CH yoke, pedals, throttle quadrant, and fighterstick.
TrakIR 5
manfredc3
SOH-CM-2022
This thread is an interesting read.
I have FSX A running on a dedicated computer, with FTX Global/Vector/OpenLC for scenery improvement. I have the PMDG 737NGX running smooth, and fly that in a multiplayer session every Saturday with no issues.
Over the years I have developed a specific routine when performing a clean install. My last clean install was last January, after 3 years of running FSX. The clean install was initiated after deciding to give windows 10 a chance. No regrets so far.
For the clean install I stick with a document I compiled, using my own experiences, as well as suggestions from Flight sim "guru's" that can be found on diverse forums.
My computer specs are:
PC 1:
Windows 10 (upgraded from W7 last December)
Intel I7 2600k Overclocked to 4.3GHZ. (Water cooled with a Corsair H70)
EVGA GTX 770, 4GB DDR5
120GB solid state for the OS.
A 500GB WD Black HDD for FSX-A and FSX-SE.
A 1TB WD Black HDD for FSX add-ons
PC 2 (networked):
Intel Q6600
Low end pc (approx 10 years old)
Windows 10 (upgraded from XP/W7 a few weeks ago)
Runs add-on's like ASN, FSC, Plan-G and Skype for communicating during multiplayer sessions.
Oh, and did I mention that the main FSX pc has 4 monitors connected? 3 for the outside.cockpit view, and one for the gauges.
I use NVidia Inspector and some FSX.cfg tweaks.
Settings are pretty much maxed out.
As I mentioned earlier, The sim is running smooth. And I think that is because I don't chase frame rates, but look for the soft spot.
I do use two different settings profiles, one for multiplayer, and one for free flight. (mainly as I limit AI Traffic during multiplayer sessions).
I hardly ever run in to crashes. I think that, for me, it is due to the way I have set up and tweaked FSX, and the fact that the FS pc is used for nothing else but running the sim, LUA and GoFlight.
I also know, due to my experience, that two computers with exactly the same components will still have differences in performance.
Cees if there is anything I can help you with that you may not have already tried, then feel free to shoot me a PM.
A happy FSX-A/Windows 10 flight simmer.
I have FSX A running on a dedicated computer, with FTX Global/Vector/OpenLC for scenery improvement. I have the PMDG 737NGX running smooth, and fly that in a multiplayer session every Saturday with no issues.
Over the years I have developed a specific routine when performing a clean install. My last clean install was last January, after 3 years of running FSX. The clean install was initiated after deciding to give windows 10 a chance. No regrets so far.
For the clean install I stick with a document I compiled, using my own experiences, as well as suggestions from Flight sim "guru's" that can be found on diverse forums.
My computer specs are:
PC 1:
Windows 10 (upgraded from W7 last December)
Intel I7 2600k Overclocked to 4.3GHZ. (Water cooled with a Corsair H70)
EVGA GTX 770, 4GB DDR5
120GB solid state for the OS.
A 500GB WD Black HDD for FSX-A and FSX-SE.
A 1TB WD Black HDD for FSX add-ons
PC 2 (networked):
Intel Q6600
Low end pc (approx 10 years old)
Windows 10 (upgraded from XP/W7 a few weeks ago)
Runs add-on's like ASN, FSC, Plan-G and Skype for communicating during multiplayer sessions.
Oh, and did I mention that the main FSX pc has 4 monitors connected? 3 for the outside.cockpit view, and one for the gauges.
I use NVidia Inspector and some FSX.cfg tweaks.
Settings are pretty much maxed out.
As I mentioned earlier, The sim is running smooth. And I think that is because I don't chase frame rates, but look for the soft spot.
I do use two different settings profiles, one for multiplayer, and one for free flight. (mainly as I limit AI Traffic during multiplayer sessions).
I hardly ever run in to crashes. I think that, for me, it is due to the way I have set up and tweaked FSX, and the fact that the FS pc is used for nothing else but running the sim, LUA and GoFlight.
I also know, due to my experience, that two computers with exactly the same components will still have differences in performance.
Cees if there is anything I can help you with that you may not have already tried, then feel free to shoot me a PM.
A happy FSX-A/Windows 10 flight simmer.
Paul Domingue
SOH-CM-2023
OpEd
I have a mid-range computer, 3gig processor, with a fair to middling graphics card and running Windows 10 fully updated.
I get excellent results with FS9 and P3D and while not the best on FSX it is tolerable. One thing I don't have is extensive scenery addons and this is probably the reason for decent flying experiences in FSX.
My opinion is that recent developments in scenery and aircraft are exceeding the capabilities of this aged flight simulator software and I am hopeful that we shall see some vast improvements in the near future for both divergent systems of Microsoft's ESP.
LM has made some notable improvements for the technology industry and now DTG is making a strong effort to address the constraints of this software to reach a larger market share from the general public.
For the simmers this is an excellent outlook on a new horizon but for the developers, especially commercial, it will be problematic.
To say that you want FS to improve and blame all the problems on the OS sounds to me like a conservative mind frame. We all want everything to stay the same but better. It's just not going to happen.
For those who want to stay with earlier versions of Windows, and I can understand the frustrations, you will eventually find everything passing you by and the worst part of it, nobody will care.
For me, I will try to have the greener grass if I can and let my neighbor worry about his own.
I have a mid-range computer, 3gig processor, with a fair to middling graphics card and running Windows 10 fully updated.
I get excellent results with FS9 and P3D and while not the best on FSX it is tolerable. One thing I don't have is extensive scenery addons and this is probably the reason for decent flying experiences in FSX.
My opinion is that recent developments in scenery and aircraft are exceeding the capabilities of this aged flight simulator software and I am hopeful that we shall see some vast improvements in the near future for both divergent systems of Microsoft's ESP.
LM has made some notable improvements for the technology industry and now DTG is making a strong effort to address the constraints of this software to reach a larger market share from the general public.
For the simmers this is an excellent outlook on a new horizon but for the developers, especially commercial, it will be problematic.
To say that you want FS to improve and blame all the problems on the OS sounds to me like a conservative mind frame. We all want everything to stay the same but better. It's just not going to happen.
For those who want to stay with earlier versions of Windows, and I can understand the frustrations, you will eventually find everything passing you by and the worst part of it, nobody will care.
For me, I will try to have the greener grass if I can and let my neighbor worry about his own.
Windows 10 is blamed by W8 users, W7 users decry W8 as wonky gadgetware, XP users insist W7 is the spawn of the devil and Windows 2000 users shake heads in despair as the world goes to hell in a handcart. Somewhere out there are the last adherents to Muppet Edition and 98 steadfastly serving their masters and FS 98. 'Twas ever thus and ever shall be.
FSX was rushed to market and the two service packs never really fixed everything as we now know all too well. At least they're still the same bugs we encounter as ever more ambitious add-ons drain the 32-bit memory model to the dregs. Now, about those artefacts I get on final to JFK in an evening thunderstorm...
FSX was rushed to market and the two service packs never really fixed everything as we now know all too well. At least they're still the same bugs we encounter as ever more ambitious add-ons drain the 32-bit memory model to the dregs. Now, about those artefacts I get on final to JFK in an evening thunderstorm...
Jafo
SOH-CM-2024
Mostly.
I remember 2000 was touted as 'bullet proof' ....and yet I could break it at will.
In the GUI skinning game you could even 'skin' the BSOD ...into any colour or style you liked. You may as well...as you'd see it often enogh you may as well make it 'pretty'.
"Ultramarine" was the colour of choice....cos that made it "U-SOD" - somewhat apt.
Windows 8 and beyond was Microsoft's FAILED attempt to make a universal OS for all applications/hardware....particularly for the 'Windows Phone' ....and just how well is that now going?...
The dumbing-down and blandness of all things post 7 simply demonstrate that the GUI [specifically] of 7 was the pinnacle of the Windows development for the Desktop user....[what everyone into Flight Simulators is].
The OS Kernel improved admittedly but the general user was and always will be oblivious to that.
The single most absurd 'requirement' of Win 10 is Forced Updates which can AND DO cause system failures.
The latest Anniversary Update is the perfect example. Many [if not most] survive the update seemlessly. Those who don't lose data, sanity and access to their computers without resorting to the jumping through hoops to get to Safe Mode [remember 'dumbing down'?].
If [and that's an 'if'] people survive whatever updates surreptitiously are inserted into your system then all is well and good....spiffy, even.
But WHEN it goes to poo you'll go find that baseball bat and beat the living crap out of an OS that thoroughly deserves it...
I have 6 systems....and 4 are on 10. One of those in particular is still a disaster. Edge is unusable, IE is no better, and I've made sure Chrome is the default as it's the most reliable/functioning.
All are 'Pro' so I'm still avoiding anything 'Anniversary'....until Redmond pulls its finger out of its bum and gets it right - properly.
IanHenry
Charter Member
I've never had any problems with W10. I think you need to wipe your disk and do a fresh install and use FSX-SE it performs far better than the boxed edition or, if your computers up to it P3D. There far better than the original FSX, the only drawback is the possibility of OOM's but they have never been that big a problem for me.
Ian
Ian
Dutcheeseblend
Blenderer
Hi,
I feel sorry for all your troubles.. Well, I don't have really those crashes. I run FSXA on W7, with a 4-year old HP Elitebook 8570w Workstation: 3rd gen i7 with 2.3 GHz, 8GB RAM and a Nvidia Quadro K1000M videocard. I often run Blender next to FSX and it works fine. No crashes at all.. Did have them before, but I downloaded the uiautomationcore thingy and now it runs well. With NL2000 and my own development aircraft.
I feel sorry for all your troubles.. Well, I don't have really those crashes. I run FSXA on W7, with a 4-year old HP Elitebook 8570w Workstation: 3rd gen i7 with 2.3 GHz, 8GB RAM and a Nvidia Quadro K1000M videocard. I often run Blender next to FSX and it works fine. No crashes at all.. Did have them before, but I downloaded the uiautomationcore thingy and now it runs well. With NL2000 and my own development aircraft.
YoYo
SOH-CM-2023
...of all the crashes, low framerates and hughe loading times I'm about to give up on this sim.
Cees
I understand it.
Check DCS.
Sametimes I also need a fresh air without crashes and jumping fps. It's a time to leave FSX and go to DCS World for few weeks/months.
btw. Now I'm returned to P3D but ... v3 and I'm very happy with this new version. Its a very stable sim, good fps (near stable 60) and no any CTD (!!!).
My FSX stayed on the top high shelf.
ChipShop
Charter Member
I'm on windows 8.1 and have FSX Acceleration in place with ORBX FTX EU scenery; up until recently everything was running perfectly smoothly, even with some of the larger aircraft like the RL A400M for example. But now, I find that my FSX now, takes a ridiculously long time to load; occasionally freezes and is rather stuttery in the frame rate department.
I thought perhaps, it was to do with a slow internet connection or such like; or even that I had too many aircraft in my sim objects library; failing that, it might have been the recent ORBX SP5 update. But now having read this, I'm wondering if maybe it's to do with FSX as a whole!?
Hopefully a solution or some sort of service pack update will be forth coming and get things working smoothly again?
ChipShop
I thought perhaps, it was to do with a slow internet connection or such like; or even that I had too many aircraft in my sim objects library; failing that, it might have been the recent ORBX SP5 update. But now having read this, I'm wondering if maybe it's to do with FSX as a whole!?
Hopefully a solution or some sort of service pack update will be forth coming and get things working smoothly again?
ChipShop
...of all the crashes, low framerates and hughe loading times I'm about to give up on this sim.
Cees
I gave up on FSX Acc. last year. Constant crashes, OOM, decreasing performance with add ons and loading time made feel more like work than fun. I am using P3D V3.2 on Windows 10 now and I have no problems what so ever. I am enjoying "flight simming" again like I was with FS9 prior to FSX.
