what did 2004 break?

[ha5mvo 237]

Everyone is singing the praises of the latest windows update in saving vram.

While this may be justified, it did break my F1 gtn gauge for one. 

Wonder if there's anything else that is not working properly since the update?

[Nemo 1,305]

 

[ha5mvo 237]

Hi Harry, thanks for the tip.

I think I might be having issues replacing the trainer though. I managed to run it properly as the standalone trainer but it won't load the database in sim...

What am I doing wrong??

 

 

Edit:

It works just fine! had a glitch with the database which was entirely my fault...

Edited May 31, 2020 by ha5mvo

[Gridley 257]

I've also read that updated GPU drivers are a must for 2004.

[Nemo 1,305]

48 minutes ago, ha5mvo said:

Hi Harry, thanks for the tip.

I think I might be having issues replacing the trainer though. I managed to run it properly as the standalone trainer but it won't load the database in sim...

What am I doing wrong??

 

 

Edit:

It works just fine! had a glitch with the database which was entirely my fault...

Good to hear that it worked for you too. I hope that F1/Garmin will update soon as 2004 is currently arriving for all W10 users.

[CFIJose 5,485]

56 minutes ago, Gridley said:

I've also read that updated GPU drivers are a must for 2004.

What are the recommended drivers?

I'm currently using 445.87 with 1809.

[captain420 3,099]

Flight1 GTN 750/650 works, but is very slow and unresponsive in Windows 10 2004 update.

[Nemo 1,305]

11 minutes ago, captain420 said:

Flight1 GTN 750/650 works, but is very slow and unresponsive in Windows 10 2004 update.

See the linked post above. It contains a description how to get F1/GTN to work correctly with Win10 2004.

[mrlip 56]

29 minutes ago, DJJose said:

What are the recommended drivers?

I'm currently using 445.87 with 1809.

446.14 if using 2004

[vgbaron 3,486]

2004 made my #2 system unusable - BSOD on boot - ultimately had to restore from backup. Didn't even try it on my main system.

Vic

[Pete Dowson 558]

2 hours ago, mrlip said:

446.14 if using 2004

I updated to 446.14 immediately after updating to Win10 2004.

I then discovered that the frame rate in P3Dv5 was stuck at 12.5 fps, half my VS of 25.

Strangely, it was locked at 12.5 even when I tried turning off all limiters -- no VSync, no FR Limit, no RTSS, no NVCP limit. Nothing to keep it down to any specific value. Really weird.

I reinstalled my previous driver (442.50, quite an old one) and everything was back to normal.

So I am very suspicious of 446.14. I'm going to investigate other recent versions, see which is the latest without such a devastating problem.

Note that I am using two scenery windows in P3D, with ViewGroups (not Surround Mode).

Pete

 

[Mace 1,902]

3 hours ago, vgbaron said:

2004 made my #2 system unusable - BSOD on boot - ultimately had to restore from backup. Didn't even try it on my main system.

Vic

Your #2 rig and mine both have 1080ti's.  That might be why, when I go to Windows Update, it tells me that 2004 is not yet available for my device.  Here is the quoted text from the dialog box:

The Windows 10 May 2020 Update is on its way. We’re offering this update to compatible devices, but your device isn’t quite ready for it. Once your device is ready, you’ll see the update available on this page. There’s nothing you need to do at this time.

[Jetman67 506]

I have a 1080ti with the latest nvidia drivers, no bsod or issues with 2004 yet

[FlavioSSA 44]

4 hours ago, Nemo said:

See the linked post above. It contains a description how to get F1/GTN to work correctly with Win10 2004.

Isn´t it better if we wait a bit for F1 Staff give some word about this?

[Jetman67 506]

I downloaded windows media tool