KA350i Version 1.1.33 Beta (V4 + V5)

[Turbofandude]

Hello all,

We have updated the installer to fix some of the issues with the installation process! 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 ... 200716.zip

[richbonneau]

Hi Colin,
So, no other changes outside of installer fixes?
Rich

[bmw969]

LegacyRender folder what is it ?

[jonahdesrochers]

I think so, because I have the same issues as the previous build, which on my end is 1 major issue and 1 minor issue.

Major: display flickering. All cockpit displays and FMS flicker. This seems to induce stutters to the whole sim as well.

Minor: VC display colors are washed out and cockpit is dark in general. I know LM is still tweaking this and further changes are expected in 5.1, so not sure if this is worth correcting right now.

[Sharpedge]

Install was fine. looks great until I try to fire up the systems. None of the caution, master caution and annunciator panel lights work. Battery power established and the the Press to Test button on the glare shield does not light up the panels. The fire text does however appear on the MFD.

Was there not a similar issue a few builds back in 4.5? Interior lighting does not work but I don't have flicker that others have.

[Slayer]

LegacyRender folder what is it ?

"LegacyRender replaces the PDK rendering system with the older gauges system - lower quality/lower performance, but more compatible (SLI, V5/Win7)"

That was the info I have.

[Slayer]

I think so, because I have the same issues as the previous build, which on my end is 1 major issue and 1 minor issue.

Major: display flickering. All cockpit displays and FMS flicker. This seems to induce stutters to the whole sim as well.

Minor: VC display colors are washed out and cockpit is dark in general. I know LM is still tweaking this and further changes are expected in 5.1, so not sure if this is worth correcting right now.

Have you tried turning off Fullscreen optimizations yet? ?

[Slayer]

Since this is a dual install version if you are wanting to report an issue please specify if you are using V4 or V5.

Thanks

[bmw969]

LegacyRender folder what is it ?

"LegacyRender replaces the PDK rendering system with the older gauges system - lower quality/lower performance, but more compatible (SLI, V5/Win7)"

That was the info I have.

Without LegacyRender, I have weird artifacts in the display and blinking.

[Thorsten42]

Hi all,

installed low res version in v5. Installer still creating unwanted p3dv4 folder structure for reallight and trueglass. Low res version with disabled render to tranparent surfaces loads up with 6.3gb vram. Sim has EA off and general texture size 1024. Turning on systems vram goes up to 6.6. Hitting the engine starter giving me oom popup. Thats it.

Sorry to say but the v5 version is not usable in a normal medium setting config setup sim environment with a 8gb gpu.

BUT: If you for a test disable the reallight dll you get a perfect stable nice running sim with a vram footprint of 4.3gb with all systems running.

I don't want to criticize anyone or anything and really wan't to help to get this thing perfectly running but honestly in my humble opinion reallight is killing this wonderful addon and preventing a proper usage. It is not the KA that needs further fixing, its reallight that needs to be worked on.

and now throw the stones

Cheers
Thorsten

[bmw969]

Throw stones at the LM. The problem is on their side.

[Thorsten42]

Throw stones at the LM. The problem is on their side.

Seriously? In my opinion the switch to DX12 is just showing a general problem. With v4 and dx11 all devs including lm were "safe" cause the dx implementation was hiding the hunger for ultra hd pixelgeddon for every nut and bolt on the cost on performance. Need more vram? Sure os and dx will handle it but you will see bad performance cause all the memory shifting comes at a price. Now with dx12 the devs including lm BUT also 3d party devs need to take into account that resources are limited. LM could have inplemented a more stable and failsafe solution that pauses sim at a certain point and gives you the possibility to tune down your settings to match the resource demand (actually even I have seen this screen from time to time but not consistent). But then there is the sim user, thats us. Putting all sliders to max and still wondering why the sim fails. But even if we go back to normal settings that the sim can handle we put in a lot of addons having impact.

I know even if MV together with tfdi could bring down the KA to a proper vram footprint of lets say 4.5gb (in a simple default scenario) they would even not be safe cause we the users are installing airports like for example KMIA that were implemented for old style DX11 and just converted to v5 to install correctly and baaam oom again.

Ever asked yourself why msfs will use dx11 from the start? Their new engine will cover some of the performance issues at a price of higher hardware demand. Vulkan and DX12 clearly show that performance - that is what we actually want as a smooth sim - is possible. But that means that all involved parties (lm, 3rd party dev and the enduser) have to accept the limitations while developing and using.

just my 2 cents...

Cheers
T.

[Turbofandude]

Throw stones at the LM. The problem is on their side.

Seriously? In my opinion the switch to DX12 is just showing a general problem. With v4 and dx11 all devs including lm were "safe" cause the dx implementation was hiding the hunger for ultra hd pixelgeddon for every nut and bolt on the cost on performance. Need more vram? Sure os and dx will handle it but you will see bad performance cause all the memory shifting comes at a price. Now with dx12 the devs including lm BUT also 3d party devs need to take into account that resources are limited. LM could have inplemented a more stable and failsafe solution that pauses sim at a certain point and gives you the possibility to tune down your settings to match the resource demand (actually even I have seen this screen from time to time but not consistent). But then there is the sim user, thats us. Putting all sliders to max and still wondering why the sim fails. But even if we go back to normal settings that the sim can handle we put in a lot of addons having impact.

I know even if MV together with tfdi could bring down the KA to a proper vram footprint of lets say 4.5gb (in a simple default scenario) they would even not be safe cause we the users are installing airports like for example KMIA that were implemented for old style DX11 and just converted to v5 to install correctly and baaam oom again.

Ever asked yourself why msfs will use dx11 from the start? Their new engine will cover some of the performance issues at a price of higher hardware demand. Vulkan and DX12 clearly show that performance - that is what we actually want as a smooth sim - is possible. But that means that all involved parties (lm, 3rd party dev and the enduser) have to accept the limitations while developing and using.

just my 2 cents...

Cheers
T.

I'd tend to agree here - DX12 offers more control over the rendering pipeline, but with more control, of course, comes greater responsibility and difficulty to accomplish the same task(s) properly. We (TFDi) has also noticed increases in VRAM consumption, but we've done as much digging as possible. I did an extended diagnostic where I measure various scenarios and sent a full breakdown of VRAM consumption to Lockheed Martin (we determined it was 2-3x higher than it needed to be). They asked me to try again with HF2 and it was indeed somewhat improved.

If we do the math for the number of textures and surfaces that are present in the KA specifically (remember, RealLight's memory consumption is also based on how the product uses it), it comes up relatively close to what it's using now. The reality of the situation is that some products will simply require turning down settings or disabling optional features when you are approaching the limit. For example, I've found unchecking the "Render to transparent surfaces" option (although disabling TrueGlass) will save you ~300MB of VRAM. In my scenario (with default settings and TrueGlass enabled), I was only using 4.8GB of VRAM.

It will be a case of using manageable settings and addons at this point.

[tredsell]

Hi Colin

Forgive me for querying, are you saying that you've done all you can with the KA (and TG/RL) at this stage?

Is there no way for a VRAM footprint to be narrowed down further to find the culprit? As more addons are migrated over to V5 they are not all showing a 2 or 3x increase in VRAM consumption, I can fly the FSL A320 at major airfields using ORBX TE and never breach the VRAM limit and it spends 90% of its time below 6GB. I see the same result with the PMDG NGXu and QOTSII.

For some reason, the King Air beta, the 717 beta, and the public version of the QW 787 are all using enormous chunks of VRAM even when C&D, and almost immediately swallow up all the available VRAM once you fire it up. If TG or RL arent the common denominator amongst those particular addons then there must be something that is using twice the available VRAM to addons with a more significant graphical and system output such as the FSL?

If we disable RealLight or TrueGlass independently, what functionality would we lose in the King Air? I seem to recall when I did it that I lost the annunciators, could some fundamentals like that not be made functional without RL/TG? I always (mis)understood that RL was to provide dynamic cockpit lighting, and TG was for rain (and now ice) effects,

I for one really enjoyed flying this product in V4, so would love to get it airborne again in V5, but not at the expense of similar settings which were manageable before (and now in most other addons I am using).

Hopefully you'll persevere

Tom

[jonahdesrochers]

I think so, because I have the same issues as the previous build, which on my end is 1 major issue and 1 minor issue.

Major: display flickering. All cockpit displays and FMS flicker. This seems to induce stutters to the whole sim as well.

Minor: VC display colors are washed out and cockpit is dark in general. I know LM is still tweaking this and further changes are expected in 5.1, so not sure if this is worth correcting right now.

Have you tried turning off Fullscreen optimizations yet? ?

Yes, tried with and without. Still flickering.