Hi everyone 

If you own a GTX 1080Ti card then you're snookered!! ... The .33 family of drivers will not install and you have no choice but to use the latest ones 

Paul 

10 minutes ago, Paul_ said:

Hi everyone 

If you own a GTX 1080Ti card then you're snookered!! ... The .33 family of drivers will not install and you have no choice but to use the latest ones 

Paul 

I was able to install the .33 drivers on my 1080 Non-Ti card. Is the Ti really that different?

56 minutes ago, Ray Proudfoot said:

I was able to install the .33 drivers on my 1080 Non-Ti card. Is the Ti really that different?

Hi Ray, If you gopgleI 980ti v 1080 you will get some compar , from userbenchmark.

Bob

Edit sorry about text pad keeps locking up.

 

3 hours ago, tooting said:

All of them after the. 33 drivers.   Although the leaks are in different places on the p3d globe. 

I have downloaded and installed the latest driver which is 382.05 and am not getting any OOM anymore.

No  of course not.   I think theres leaks in different parts of the p3d scenery areas and in varying sizes. Some bigger than others.  I also think there's leaks when the sceney areas transition from land to water.

For example the London sink hole has always been there since fs2002.  Now that leaks,  as does the Lax area.

You tell me why it doesnt leak from Hk to Moscow Russia some 4000 miles but it leaks from London to Paris some 400.

Or why suddenly when you hit the northern East coast of Canada on a flight say from Manchester to Orlando the leak happens.

As I said before and numerous other people have said it's a terribly coded sim that was given up on by aces all those years ago so trying to get it to work with new drivers is always going to be hard.  

It's basically a coding conflict between 15 year old rushed botched coding and the drivers.

I'm sure LM will spend millions trying to fix it before they flog it to the US military 

 

 

 

 

1 hour ago, Canuck said:

I have downloaded and installed the latest driver which is 382.05 and am not getting any OOM anymore.

That's great.  It works for some cards bit not all.  I can promise you with a 980ti and an Asus board it doesn't.

Like Baron said each system is different.

For example on mine and my mates Asus boards if you remove a USB joystick or pedals by mistake by knocking it while p3d is running it ctds.  Now you could argue until the cows come home thats bad coding, but p3d would blame windows and windows would blame Lm.  So the problem never gets fixed.  Same with these drivers.   No ones going to claim responsibly for it.  It costs time and money 

6 hours ago, Paul_ said:

Hi everyone 

If you own a GTX 1080Ti card then you're snookered!! ... The .33 family of drivers will not install and you have no choice but to use the latest ones 

Paul 

I have a 1080TI 

Worked with every driver from 376.33 till 382.05, which I am using at the moment

Did anybody try the 382.05 on GTX TitanX? How does it fare against 376.33 one?

I'm concerned my GTX TitananX is too old already for 382.05.

Thanks,

Dirk.

6 hours ago, onebob said:

Hi Ray, If you gopgleI 980ti v 1080 you will get some compar , from userbenchmark.

Bob

Edit sorry about text pad keeps locking up.

 

Hi Bob,

I'm finalising my settings with P3D so won't be changing my 376.33 drivers.

Not sure why I need to compare the 1080Ti with a 980Ti when I have neither.  

4 hours ago, tooting said:

As I said before and numerous other people have said it's a terribly coded sim that was given up on by aces all those years ago so trying to get it to work with new drivers is always going to be hard.  

It's basically a coding conflict between 15 year old rushed botched coding and the drivers.

Oh c'mon, Pete. If you are insisting on making statements like that you might at least spend some time getting your facts right. 'Numerous other people' may be as ill-informed as you seem to be.

To my knowledge ACES did not give up on the sim, they had the rug torn from under them by Microsoft thereby causing the project to be abandoned. As for being a 'terribly coded sim' that may, to a degree be true, but let's not forget that you are making such judgements based on what is known now. At the time they were working with code that had been around for years and, to my mind, with the expertise and knowledge available at that time did a pretty good job of maintaining compatibility with legacy products. There lies the problem. If they had dared to break compatibility there would have been an outcry from the community. Now, with the prospect of a 64bit version the Developers have an opportunity to start more or less from scratch. However, something tells me that we will still see a degree of compatibility built in somehow, time will tell.

My experience, for what it's worth, is that for all it's few remaining shortcomings Prepar3D 3.4 is stable, has few vices and performs very well, assuming you have a half decent rig to handle it. In fact, I would go as far as to say that while it is likely I will be installing the 64bit version (if it exists) alongside I will keep my customised v3.4 as my core sim for some time to come as it satisfies all my current needs.

The code for releasing unused memory in certain situations is already present and introduced by LM some time ago. Unfortunately something changed in NVIDIA's drivers to interfere. We know LM are in discussions with NVIDIA and the early signs are that this may be producing some worthwhile results for, in common with others, I too am seeing better VAS management than before with the 382.05 driver set.

Regards,

Mike

 Very well written Mike.

5 hours ago, GSalden said:

I have a 1080TI 

Worked with every driver from 376.33 till 382.05, which I am using at the moment

That's very interesting .... For the life of me I couldn't get it installed 

 

11 hours ago, Ray Proudfoot said:

I was able to install the .33 drivers on my 1080 Non-Ti card. Is the Ti really that different?

I have a 1080 too Ray and the .33 drivers installed fine ... I need some of G's magic  dust for the 1080Ti haha 

 

Paul

Mine is a Gigabyte 1080 TI Gamers OC and I use the drivers from the Nvidia site.

At the install screen I always choose for Manual installation , where I select drivers + Physics only...

I hope you guys can install the drivers too.

Mine are : WHQL  382.05 and language Other !

Pete,

Why don't you share your settings with us and what aircraft you were flying?

I haven't had a single crash of P3D since I started using it a month ago and I've been hammering it in the last few days with FSLabs Concorde. Just as complex as your 3rd party aircraft, maybe more so.

How many addons do you have running alongside P3D?

Just a note on the Locked vs Unlimited situation; there's a lot of differences from system to system mainly from monitor and monitor connection producing a great combination of setups. So both views are correct with respect to Locked vs Unlimited. The important stuff to note is that P3D is not the same as FSX when it updates the display.

FSX is an exclusive mode app D3D can control the VSync to the monitor, we can use the free Inspector tool to change response to VSync and even set to a half, a third or a quarter refresh frequency to allow the monitor to update the image more quickly in full screen whenever each new frame arrives.

With P3D it's a desktop only app which utilises a full screen sized window with no caption and border, there's no access to exclusive mode, instead P3D responds to the desktop VSync. In the P3D Display Settings page the VSync setting cannot alter that, but rather when used with Unlimited fps set on the slider it responds to the refresh frequency of the monitor by limiting frame drawing at that frequency. With Unlimited the frame drawing will pause if the sim has time between frames if they constantly reach the monitor refresh frequency. We can turn on the Triple Buffer and the draw does not cease, the third buffer is drawn first.

Lets say we set Unlimited and VSync=On and use a 30Hz refresh: If the sim can keep up with the monitor refresh frequency at all times the results are effectively accurate. If we don't display each frame at exactly the right time, 33.33ms later, we are not where we are supposed to be. The next frame along is built to adhere to the average time of the previous frames, effectively we never appear in the right place whenever the sim alters in speed.

With Locked fps set on the slider the sim enters a different mode of operation. The D3D system makes a look ahead buffer - default three frames. So it's constantly making the next frame ahead; each one exactly 1/30s ahead of the last if we are set to 30fps. If it cannot keep up then we lose the frame and apply the next until we run out of buffer. If we only see 40-50fps a locked setting of 30fps will run out of the buffer very quickly and take ages to refill, with only seeing around 35fps in unlimited mode (no VSync limit) and set locked to 30, we may lose the buffer and it never catches up - a very unsatisfactory state.

If we don't use Locked properly we can get very poor results. If we can see 40fps we can just about utilise 20fps locked effectively but seeing 60fps all the time would be preferable. Setting 30 Locked requires a powerful PC, but these sims don't need to run fast if we have slow or non-acrobatic aircraft.

With the triple buffer the system can be drawing the next frame, showing the last frame, and while exchanging the backbuffer for monitor updates, can continue drawing the next frame on the spare buffer. So in conclusion with P3D and VSync on, TP=Off the lower the refresh frequency the less work the sim does.