I realize much of this depends on nvidia playing nice with LM, but it would have been nice knowing this from the beginning.  I feel like LM has't been completely forthcoming.

 

Did you look/read that link I provided above?  That was dated back in April.  I don't understand how LM can be more forth coming on something that is outside of their control?  LM never announced they would have SLI support in 2.0 or 2.1 so not sure what you are considering "the beginning"?  They were hoping to get SLI support in 2.2 ... some have got SLI working in 2.2 but it's not "officially" supported because there is no nVidia profile.  Same with 2.3, there is no nVidia profile.

 

SLI is a Graphics DRIVER implementation, it's not something LM can make happen, there is no DX11 switch that says SLI On/Off.  LM work with nVidia for feedback and information if there are any adjustments that need to be made to HELP nVidia come up with a SLI profile (or any profile, like better AA support).  This process has been this way since the introduction of SLI drivers for any game/simulation that is developed for the PC ... that's why nVidia "profiles" exist.  You also need to understand that many 3D shooters out there with SLI support that have NOT had to go thru this process are piggy backing off "graphics engines" that have already gone thru the SLI support process.  P3D is not based on any existing engine, hence the challenge for nVidia to figure out an implementation.

 

I can understand your frustration, but pointing it towards LM makes no sense when they have been forth coming with information. 

 

Cheers, Rob.

I feel like LM has't been completely forthcoming.

Perhaps you should lay off the 'juice'??

 

Lockheed-Martin has been completely transparent in their goals and where things stand.

 

 

On a side note: 2.3 RC2 will no longer allow RivaTuner/MSIAfterburner to display GPU, CPU, frame, bus load, temps, etc. values as an overlay

 

Oh well. That's okay by me. I use Fraps for FPS (fed to AIDA64) and AIDA64 for CPU and GPU usage in the OSD and I suspect that will still work.  AIDA's OSD stays on top of any Window, including the desktop.

On a side note: 2.3 RC2 will no longer allow RivaTuner/MSIAfterburner to display GPU, CPU, frame, bus load, temps, etc. values as an overlay ... they appear on initial loading screen on P3D, but no longer appear on the main view (or any view) in P3D.

 

Do you know whether this was done deliberately or is just a glitch?

...SLI is a Graphics DRIVER implementation, it's not something LM can make happen, there is no DX11 switch that says SLI On/Off.  LM work with nVidia for feedback and information if there are any adjustments that need to be made to HELP nVidia come up with a SLI profile (or any profile, like better AA support).  This process has been this way since the introduction of SLI drivers for any game/simulation that is developed for the PC ... that's why nVidia "profiles" exist.  You also need to understand that many 3D shooters out there with SLI support that have NOT had to go thru this process are piggy backing off "graphics engines" that have already gone thru the SLI support process.  P3D is not based on any existing engine, hence the challenge for nVidia to figure out an implementation.

 

I can understand your frustration, but pointing it towards LM makes no sense when they have been forth coming with information. 

 

Cheers, Rob.

 

This is why, in the beginning of my post, I stated that.  

 

I will have to do some searching but I distinctly remember them stating they wanted it in 2.1...

 

 

 

 

Perhaps you should lay off the 'juice'??

 

Perhaps you should grow up? 

 

 

Do you know whether this was done deliberately or is just a glitch?

 

I think someone on the grassy knoll did it ...

 

 

 

AIDA64 for CPU and GPU usage in the OSD and I suspect that will still work.

 

Yes AIDA64 still works, but I haven't been able to get VAS usage out of AIDA64 ... unless I missed something?

 

AIDA64 in action in v2.3 RC2

 

 

 

I will have to do some searching but I distinctly remember them stating they wanted it in 2.1

 

LM probably wanted SLi support from v2.0 ... but again, LM doesn't make the drivers, nVidia does, so LM's desires are nothing more than a desire, nVidia need to produce the goods.  It sounds like you didn't realize that nVidia hold the key, not LM ... LM can only respond to what nVidia ask of them, LM does NOT write/code graphics drivers.

 

Cheers, Rob.

Hi Rob

 

Firstly a great big thank you for your informative input here  ... it's well appreciated

 

I just wanted to say your Vimeo video was 200% smoother than the one you have just posted using You Tube

 

Maybe it might be worth sticking with Vimeo ....

 

Cheers

 

Paul

I just wanted to say your Vimeo video was 200% smoother than the one you have just posted using You Tube

 

You've demonstrated my point about different players operating differently (but keep in mind that Vimeo only support 1080p) ... I got another PM from someone telling me exactly the opposite of what you suggest -- indicating YouTube is smoother than Vimeo.

 

There are so many variances in video settings from browser, OS, video player plugin, cache data, ISP, etc. etc. ... it's for the most part impossible to determine what is more or less smooth on anyone's given PC.  Be it stand alone player or in a browser, their is a massive number codecs and within that versions of codecs ... so like I've said in the past, it's no wonder I can get complete opposite observations of the very same video from different viewers.

 

If anyone wants a evaluate stutters, the best source for that is looking at Time between frames data ... FRAPS can do this (and maybe other products).

 

Cheers, Rob.

Point taken Rob

 

Maybe it's because I am the other side of the pond!!   Hahaha

 

I have a feeling in my bones I'll be trying v2.3 this week for myself anyway  ......  hehe 

 

 

Yes AIDA64 still works, but I haven't been able to get VAS usage out of AIDA64 ... unless I missed something?

 

Not to my knowledge. All one can display is both video RAM and main RAM usage for the OS plus all running tasks. I think that you are running the sensor panel in that video, not the on-screen display. But they both can look similar. It's too bad that Process Explorer can't feed its variables to AIDA64.

2.3 is out, yay!!!!!

No sooner than I get that feeling in my bones V2.3 is released  ...... Fantastic news  

yeah but there are ghosts in the machine

 

mine did not update, and those that did are getting crashes

I'd rather go with a full install, I know it can be tedious with all the add-ons to reinstall but I always prefer to go back to a "clean" base, it's like a good old disk format every now and then, never hurts ^_^

Jonathan, the look on your face in your avatar is exactly many peoples expression right now.

Even those with full installs are getting a  CTD.