G MIDY

1070 is the way to go for an upgrade on the older stuff - 1080 is complete overkill to be honest unless you play other games.

I doubt you would notice any difference if they were on different drives. SSD's are extremely quick and whilst P3D is running the OS does practically nothing H/D wise in the background. If you load up performance monitor and click Disk, you will see that I/O is nothing at idle. Obviously it makes sense for storage reasons because you lose the space Windows takes up which pushes past 20GB and that is a lot on a smaller SSD. Personally I'd get a bigger, higher quality single SSD over justifying the cost of buying another one to put P3D on. Over here you can get a 512GB Samsung 850 Pro for £150 which is nothing compared to spending the same amount on two inferior drives. I think a lot of people use a main SSD for their C drive and then use something like a mechanical drive for large format storage. All my megasceneries and the heavy stuff all sit on another 2TB drive.

You are probably seeing GPU memory exhaustion, what size of memory is your graphics card? I'm not sure if this would crash Prepar3D but it seems suspicious if certain AA settings reproduce crashes. LM recently revised the system requirements for V3 - the bare minimum is 1GB of GPU memory but they doubled the recommended requirements from 2GB to 4GB for V2 to V3. Given 8x MSAA is the highest setting it might be necessary to dial this down unfortunately whilst using intensive aircraft/scenery.

dxgi.dll or d3d9.dll in the Prepar3D folder? Does any specific error appear in the Event Viewer?

For those with issues, try reinstalling not just your GPU drivers but also revert to your OEM GPU drivers whilst selecting a clean install under Advanced in the installer. IE, go to the OEM website and use the driver they suggest or the one that came with the CD using a clean reinstall. I use drivers dating back several years and they are perfect. The latest NVidia drivers have caused a lot of problems for a lot of people in many different games yet NVidia have been for the most part totally unwilling to fix problems they have created. Obviously this may be a problem for those on newer GPU's which are not supported with older drivers, in that case the OEM driver should still be the first port of call. After reverting leave any AA settings as default and see if the problem remains. The stutters that came with V3 for me were resolved by restoring everything to default and leaving it that way using only the P3D sliders to control AA. If you are running at 4K then you are also likely to hit problems either way because at those resolutions you need almost 4x the GPU VRAM to cope with the same thing someone running at 1080p does. Remember also that AA increases the VRAM requirement even further, I have seen sometimes 10 fold in some games! 4K resolutions also require almost 4/5x the amount of pixel rendering per second, something this platform is not properly optimized for. It would be fine if the simulator dynamically altered settings and had further optimized default models/textures so that performance is preserved but it doesn't. Slowdowns with 4k are virtually inevitable unless you have some serious hardware.

30hz burns the eyes here!

Massive leap forward and it doesn't even come at a cost, FPS for me is better with P3D than FSX. There is still work to be done and thankfully they are doing just that!

Their updated Miami and Key West are fantastic.

The price for an OEM chip should be virtually the same now. I also doubt you will be able to pickup a 4770k anymore? The big distributors (they sell it the cheapest) certainly don't stock it in my area. If you aren't bothered about a more expensive latest generation from Intel probably due this year then a 6700k is the way to go.

Go get it! http://forums.flightsimlabs.com/index.php?/topic/6393-concorde-x-v13-now-available-for-fsx-and-p3d/

I prefer not to use Inspector because it creates confusion. FXAA ingame is a fast method and works nicely for me with maximum MSAA. Anything else and you will probably see FPS problems with clouds in P3D unless you are running a Titan or something.

Potentially but v3 has changed a lot from v2.5. A lot of addons are still basically ported directly over from v2.5 or even FSX so there is a lot of room for something to go wrong. I just tested the chronograph myself with the 777 and v3 and the timing seemed more or less perfect. This problem seems to be a very specific one which I think requires the knowledge of the support guys.

Would stutters or fluctuations in FPS potentially explain, the simulator clock is independent of the 'windows' or software clock and any pause in the simulator would 'freeze' time so to speak. This would not be compensated for because the simulator isn't aware of a change in the difference between your system clock and it's own simulated artificial clock. If a pause or stutter occurred say many times a minute unnoticed then that is a lot of time lost. I have seen this problem before although never to that scale where I have noticed time seems to disappear. As an example I have a clock auto synced with an atomic clock in my house and before a flight I will sync them together, they certainly are not the same a few hours later. I would consider checking whether your system is stable and also try changing settings and locking FPS internally to 30 so that there aren't any stutters or losses. If it is running at a solid 30fps constantly and time still drifts then it is very difficult to explain why it is happening beyond some very complex problem beyond P3D. Flaps and custom engine code use some kind of internal timing to make them realistic so it is very obvious they could be affected by problems with keeping time. in the aircraft.cfg, the flaps for example will have a defined extension time which then rely on the timing mechanism. If this mechanism was compromised either by a system that cannot keep time properly or one which is unstable then I'm sure you would see something go wrong. I would first try the processor at stock speed and also check the Windows event logs for any WHEA errors. A CPU cycle after all occurs every second and an unstable CPU might be compromised in properly defining what a second is.

Hi sorry for the late reply - I gave another browser a try and things work fine. Indeed for me it seems Firefox doesn't work for whatever reason, very strange!

Hi all, Sorry if Avsim is already aware - I am having an issue downloading files where I click the download link, then the message appears in my status bar : beginning FTP transaction, afterwards I get asked for a username and password, I used my Avsim file library credentials but the login fails resulting in a 530 authentication error. Sometimes I get a connection reset message without any message to authenticate. Many Thanks!

For those who lock FPS externally like me it might be worth notching your lock up to 65fps, this can be done very nicely in Inspector. It is difficult to attain all the time but it seems far smoother obviously when it hits it. Anything below 40fps is completely unacceptable on my monitor - <40fps looks choppy to the point that it starts to hurt my eyes, I have tried setting my monitor to 30hz but that was a very painful experience. I don't know if Vsync works with Prepar3d properly but in my situation it seems that stutters are caused by adaptive vsync flicking on and off due to FPS being for example 1 fps below 60, turning vsync to standard however causes problems all the time rather than some of the time. That could be completely a placebo effect though, I rarely mess with it because to be honest there is no real fix beyond messing with things until becomes acceptable. For those having lateral stutters or movement related stutters, try turning down your pan rates, it helps considerably!

You are kind of correct but kind of not. A 32-bit application like Prepar3d can only address or 'write/read' to 4GB of VAS space, not RAM. RAM can be thought of as an empty space that needs to be filled, VAS is a kind of empty reservation of space within your RAM... So we'll just call it 4GB of reserved space somewhere in your RAM and this is known as Virtual Address Space (VAS). As you play Prepar3d, your VAS reservation naturally fills up as stuff is loaded and unloaded but the hard limit is that it can never exceed the reserved 4GB of space whilst the application remains 32bit. A fully loaded Prepar3d will use 4GB maximum of VAS before it runs out of space and you will see an OOM error. If you have less than 4GB of RAM for Prepar3d than it will either use your hard drive or you will OOM through memory exhaustion as there is no space left anyway. OOM by memory exhaustion is very different to simply exceeding the 4GB VAS limit, in fact as you go beyond 8GB, your RAM size becomes pretty irrelevant. If Prepar3d was made into a 64bit application, RAM does now become important because as explained before, once your RAM or available memory elsewhere is exhausted the application will be exhausted of memory That is the only concern over RAM we can have beyond the speed really - it is also very doubtful any simulator running Prepar3d will ever need more than 16GB total RAM even if it went 64bit.

HT should always be off to allow for the highest, stable overclock unless an application specifically will use it. A higher overclock will always yield better performance in P3D/FSX because more processor cycles means more work can get done. HT allows for better multi-tasking but ultimately no matter how many threads exist, the processor can only do so much per cycle - HT doesn't change performance the same increasing the amount of memory doesn't.

As far as I can tell on my work laptop, Windows 10 is Windows 8.1 with a start bar, there is no way I will risk a stable W7 running P3D so well for W10. For your average consumer there is absolutely no reason right now to consider anything else but their existing, stable W7 setup. Windows 7 really was for me the last OS that MS got right, everything else has been more and more steps in the wrong direction. At least W10 is a step back in the right direction but still, what does it offer to us still on W7? Until they start to consider what they can improve as opposed to what more rubbish they can include, they won't get my business free or not. An OS is not an Apple iPhone where they must add or change something in each build to make it worthwhile, adding a store and apps really was a shoddy 'improvement', the latest stuff really is not designed around someone who wants a clean, performance driven OS but rather for people who just want a click and go solution. MS once offered the best usability and best common compatibility out there but that has been turned into an obssession to make some iOs like app/store driven nightmare. I am hoping and praying that one day these companies will realize what they have done well and try to improve upon it instead - it is ironically the one thing that Apple fails constantly on but something which it's competitiors seem to be stupidly trying to emulate.

My experience with Prepar3d since I installed it for the first time several weeks ago has been second to none, it is completely superior to FSX in every single way. The only downside I have found is older and more traditional 2D panel type addons just do not work properly and come with drawbacks. If you fly with the Level-D 767 or anything as old as that for example you will see crashes and problems.

HT = more heat which means less stability. AFAIK, neither FSX or P3D gains any benefit from HT being on so try to use the higher overclock if possible. Obviously it goes without saying that stability should be of primary concern as you go higher..

Tired of hearing the conspiracy theories in the media. Simple math tells you this cannot have a link to Diego Garcia. The crash occurred in March 2014 which is around 500 days ago. The distance between Reunion and Diego Garcia is very small which means this thing must of floated very slowly which cannot be possible in those waters unless it has been undiscovered for almost a year.. Even at 1mph, it travels 24 miles a day which is over 4x the distance between the two in 1 year. It seems to me this aircraft hit the water and hit it hard. It is the only thing that can explain the absence of any wreckage washing similarly elsewhere.

As a side fix, you can always create a transparent 2D window in the panel.cfg and resize it to say fit the left hand 33% of your screen where in the captains seat you will never click. Upon not needing to use the cursor just drag your cursor to that section and FPS will be like when the cursor is not present. In P3D this issue is seemingly fixed.

I have finally made the big switch this week and I am dumbfounded as to what is achievable. I tried P3D at 1.4 but was really disappointed with performance. That however seems to of changed - 60FPS rock solid whilst flying the NGX with almost all the shadow stuff turned on is absolutely incredible. The cursor FPS problem is also gone for me which means performance is far superior with better visuals, it is a complete no brainer to change now if you have the hardware.

It is not quite as simple as that. The entire support structure of P3D would have to be completely redone to also support 64-bit. The .exe is not all that is 64-bit but think about every single .DLL file that must also be reworked. This will also no doubt introduce bugs everywhere because you are talking a huge change which will also down the line definitely cause people many problems at some point. I think because of this LM will avoid 64-bit whilst there is no outright need for it. The visuals achievable right now are astonishing compared to FSX whilst still OOM's are very avoidable, push it too far and it inevitably will crash of course but whilst simmers manage to avoid the OOM surely this makes a move to 64-bit irrelevant. Personally, I just can't see the justification for 64-bit and particularly the programming effort and expense that would be required to implement it not to mention the consequences. It would be far easier to instead completely rework the core autogen and other files so that the VAS footprint is reduced. Basically their biggest market will determine whether we see 64-bit, something tells me it is not something they see as important or it would be here and announced already. If anything I'm sure they need to first investigate as to whether it is even feasible to implement into what is at the core a decade old piece of code.