Do the AMD cards have a problem with the airport lights?

 

I have an old Nvidia card but it has been ok in FSX and all versions of P3D so far.

 

I have tessellation processing ON in P3Dv2.4.

I just went from an AMD to Nvidia... Best decision I ever made. AMD just doesn't cut it at all. But, you get what you pay for.

So what two cards are we talking about here Chris?

 

gb.

Let's make a very important distinction here. AMD does perform very well in DX11 game that were design with modern hardware. It actually neck and neck to the Nvidia in many modern games in terms of performance. There is an issue with the AMD drivers/shader in regards to FSX. Nvidia architectural strength is with how they can outperform their competitor when it comes to tessellation. You can read about how Nvidia gameworks dll have been optimized with heavy tessellation in mind (tons of triangles). When a game has been using Nvidia gameworks library, an AMD card will be about 20-30% slower. AMD have been very vocal about how nvidia do this on purpose and its not a very efficient way to design modern graphic. Flight simulator requires a higher number of tessellation processing therefore outperform AMD in that regards. It doesn't mean AMD cards are bad. They are actually on par for less money. If you play other  games that were design with the Mantle API, they run more efficiently with less CPU usage than any nvidia card. 

Since this is a Flight Sim Web site then let's make that important distinction and understand that Nvidia has been proven to be the best choice for us and we really do not care how well AMD runs the Goat simulator.

Why are people reporting that the runway lights don't work when vonmar has posted a screenshot with the runway lights clearly working?

In a previous thread about driver 347.09, people posted that not all airports are affected.

Since this is a Flight Sim Web site then let's make that important distinction and understand that Nvidia has been proven to be the best choice for us and we really do not care how well AMD runs the Goat simulator.

Precisely my point.

Sli profile would be fantastic, not sure how well this would benifit me though, my 690 is a single but Sli card, exciting times ahead with 2.5 plus Sli profile

Just as a test, I updated to the latest driver...347.25. I started a flight at night at KFHR, Orbx PNW. Within the confines of the airport, the restaurant and the revolving beacon were lit up. No taxi or runway marker lights. No PAPI lights. Now I can certainly understand that it might take awhile to get an SLI profile. However, you would think that a driver that broke the lights in the sim (even if it's not all airports) would be on somebody's priority list. How many iterations of Nvidia drivers has it been since this problem raised its head?

Just as a test, I updated to the latest driver...347.25. I started a flight at night at KFHR, Orbx PNW. Within the confines of the airport, the restaurant and the revolving beacon were lit up. No taxi or runway marker lights. No PAPI lights. Now I can certainly understand that it might take awhile to get an SLI profile. However, you would think that a driver that broke the lights in the sim (even if it's not all airports) would be on somebody's priority list. How many iterations of Nvidia drivers has it been since this problem raised its head?

 

I always advise using DDU, see link: http://www.wagnardmobile.com/DDU/ddudownload.htm, when changing drivers.  Go to the NVIDIA Control panel click on system information, then Components. Make sure everything is updated and there are no stragglers left behind from other drivers.

 

I can confirm 347.25 still have problems with PAPI lights in 2.5 Beta also.  Reverting back to nVidia 337.88 drivers and the PAPI lights return and work correctly.  

 

I do NOT recommend you install these drivers for use with P3D v2.x.  I'm staying with 337.88 drivers that seem to work the best with P3D ... hopefully nVidia will get P3D profiles soon as I know LM have been working with nVidia.

 

Cheers, Rob.

Thanks for the confirmation, Rob. I rolled back to 337.88 yesterday following your recommendation in another thread. I had no visual issues with 344.75, but frame rates seemed to fluctuate a lot for no apparent reason. Things are looking better with the older driver. BTW, how do you set your FPS limit? I've always limited it to 30 as I'd done in FSX, but I seem to be getting much better results running unlimited in P3Dv2.

 

Tym

Thanks Rob for update.

 

Tym it's the very same for me, in Southampton airport with sliders set to High in a C182 I was shocked I was only getting 18/19ish and couldn't understand what the problem was until I realised my FPS slider was at 60, I moved it to unlimited (one click) and bang I'm up to 29/30ish FPS, Makes a big difference for me anyway.

"Now I can certainly understand that it might take awhile to get an SLI profile."

 

Is this "SLI" causing the no PAPI problem with P3D?

And what about the lights?

LM can not call Nvidia on this?

 

I actually submitted a bug report and they were very responsive.

 

They asked for screenshots of before/after using newer drivers as opposed to older 344.xx drivers and I provided them.

 

The last response I had was they would look into it, though that was weeks ago.

Anybody know a driver version for a Nvidia 970 that will work to show the runway lights etc. ?

 

Rob's 337.88 are not supported for my video card.

Anybody know a driver version for a Nvidia 970 that will work to show the runway lights etc. ?

 

Rob's 337.88 are not supported for my video card.

I guess you must wait till nVidia has fixed it. There's a feedback button at the GeForce Experience tool. You should tell them about your problem.

Spirit