Blackbird Sims / Milviz Forum Archive

Hello all,

This update seeks to address a few snags we've seen recently. As was the case before, the high resolution and low resolution options are now included in the installer. You can select "Custom Install" and unselect the "High Resolution" features to install only the low resolution options.

Note: If you have both V4 and V5 installed you must pick "Custom" install to select which simulators to install to ("Typical" is V5 High resolution )

Installer: https://milviz.com/Online_products/Prod ... 200827.exe

PL21 Changes
-Fixed stuck chart loading message

FMS-3000 Changes
-Fixed incorrect naming of pilot defined waypoints

Other Changes
-Fixed broken readme in installer
-Fixed incorrect TrueGlass/RealLight installations for V5*

*This fix also now means the improvement in VRAM consumption should be in effect.

Hello all,
The 1.1.36 crashed my P3DV5 HF2, with the "DXGI_ERROR_DEVICE HAS BEEN REMOVED" ! Never had this issue before. The culprit is probably TrueGlass, because I had the same issue with the Leonardo Maddog after a fresh reinstall of it. As far as I kown, the Maddog installs the latest beta True Glass available. Reinstalling the Maddog without TrueGlass fixed the issue. On the Maddod forum, an another Milviz KA350i customer post the same issue with the same conclusion.

I tried several Nvidia drivers from 446.14 to the latest 452.06 but that didn't fixe the issue.

My System
win2004 (fresh install) updated
P3D5 HF2
9900KS
2080Ti
32 GB Ram

Thank you

Georges

Hi,

Thanks.

My experience on the first flight - VRAM useage doesn't seem any less than before on high res; also I didn't get the choice of what version to install.

Then got a CTD when switching over to Radar (i.e from Terrain) - for the first time in a long time...

Ray

Eariler beta version stopped working for me. First charts and now it says my activation is invalid. Going to try installing newest version before opening support thread.

Hello

• YES, pilot waypoint numbering is correct .
• YES,VRAM consumption is really less than before and I was, for the first time with P3D v5 and KA250i, able to land at LEMD with LVFR NON PBR scenery...
  Shortly I'll try with the PBR one
• It's still necessary to insert a SID before inserting any leg (at least starting from LEAL!) otherwise SID legs are not inserted before the first waypoint (not a pilot one). Ok...
• I noticed that the green line on PFD may disappear too early (before reaching the next way point... A couple of seconds I believed the AP had lost the route... with a longer range I saw that it was correctly flying toward the newt waypoint...
  Could the problem arise because I was flying from a pilot waypoint?

Well, IMHO... KA350i is back

Hope that Brunner Electronik AG will solve their own issue (AP conflict with CLS2Sim software as reported months ago by MilViz), in Swiss watchmaking we trust, isn't it?
Message received on august, 24th:

Did a flight with latest beta. It does use less vram. But I noticed my screens are wayyyyy darker (including the fmc) and the brightness buttons don’t do anything. Any tips? (Using hdr with v5 - stock shaders). Cheers.

rayharris51 wrote: ↑

Sat Aug 29, 2020 6:26 pm

Hi,

Thanks.

My experience on the first flight - VRAM useage doesn't seem any less than before on high res; also I didn't get the choice of what version to install.

Then got a CTD when switching over to Radar (i.e from Terrain) - for the first time in a long time...

Ray

I'm also getting the radar crash.

alessandro.devoto.fly wrote: ↑

Sun Aug 30, 2020 9:10 pm

Did a flight with latest beta. It does use less vram. But I noticed my screens are wayyyyy darker (including the fmc) and the brightness buttons don’t do anything. Any tips? (Using hdr with v5 - stock shaders). Cheers.

This is actually by design. In the initial versions of Prepar3D v5, the displays/surfaces were significantly brighter than their V4 counterparts. I've manually applied a correction factor to get them closer - can you screenshot what you're seeing (to make sure it's as it should be)?

Hello
I installed the update 1.1.36. after that I was able to take a flight without any problems.
But the next time the scenario was called, the message came up
"The product is either not activated or the activation is invalid. Please contact support." I bought the product in version 1.1.28 on May 25th, 2020. What can you do?

alessandro.devoto.fly wrote: ↑

Sat Aug 29, 2020 9:10 pm

Eariler beta version stopped working for me. First charts and now it says my activation is invalid. Going to try installing newest version before opening support thread.

Please email info@milviz.com if you need your product key reset. Thanks

I had the radar crash but other than that excellent performance no stuttering so going well.
Not sure if its the beta but im not burning fuel and i have the pressurisation sting at departure airport elevation no matter what i set on press control panel.
Looks great perf well and Vram usage way down well done.

I managed to get in a few flights in Prepar3d v5 before getting the "DXGI_ERROR_DEVICE HAS BEEN REMOVED" message and a CTD. Since then the sim basically won't operate with the Kingair loaded.

Hi All

Update - VRAM is much better as I said before, but each flight I tried I got a DXGI error or CTD. Other planes have not given this issue.

Not positive it's the KA, but I'd had lots of perfect flights in the same area before with v1.34.

Ray

Please place the attached file in Prepar3Dv5\Gauges\ and tell me if it still causes the device hung.