SP1 issues so far

[FinnJacobsen]

Are the fps issues related to nightlighting - are any lights on?
Do they persist if you uncheck render transparent surfaces?
Are mipmaps enabled? (please disable)

Bad FPS here too (as told in my post).
Mipmap disabled, daytime, and I tried both with and without the checkbox for "Render to transparent texture".

As I said...
Before the SP, fps was the highest for any of my aircraft with glass cockpit (and I have many), but now it´s the worst.

[doodlebug]

can you quantify that so I can use the info in my chat with the devs?

[FinnJacobsen]

can you quantify that so I can use the info in my chat with the devs?

Before the SP I had around 25 FPS, daytime at Vidan EKBI (NGXu had around 18-20 fps under same conditions).
Position, taxi and beacon lights on, aircraft started and configured for flight.

Now after the SP i get 18-20 fps, but worse - fps flucturates alot more.

[xender]

can you quantify that so I can use the info in my chat with the devs?

I think the performance issues are related to the vram usage. Even in the middle of nowhere it consumes all my vram (4gb). Its by far the only plane that does that. I made a few tests and even after switching the texture resolution to 512 (from 2048 previously) it still uses 100% of my vram. In a default airport in the middle of nowhere.

If possible maybe Milviz can offer lower resolution textures as an option? Maybe just lowering the passenger cabin resolution a bit (But not the ones in the cockpit, leave those as they are )

[alex.767]

Are the fps issues related to nightlighting - are any lights on?
Do they persist if you uncheck render transparent surfaces?
Are mipmaps enabled? (please disable)

My comparisons were taken during the day. I'm sure night would be worse.

Unchecking render transparent surfaces helps only slightly.

Render on - all 8GB in use
Render OFF - 7.3GB
NGXu (again, a similar aircraft in terms of graphics features) - 4.6GB

Something is going on. 7.3GB is better but it leaves little margin.

Mipmaps are disabled.

[Matthieu-C]

I had the same issue (98% VRAM usage, low FPS) and also tried to reduce all the P3D settings... nothing better...
But if you disable Render to transparent textures, it is far better!

[alex.767]

I had the same issue (98% VRAM usage, low FPS) and also tried to reduce all the P3D settings... nothing better...
But if you disable Render to transparent textures, it is far better!

What's your VRAM usage (GB) with it on vs. off?

[xender]

On my case, checking the "Render to transparent textures" option makes the plane not flyable (3fps, 4fps). That wasn't the case before.

Now i have to use it with that option unchecked. Its not fluid, it still uses 100% of my vram and gets painful from time to time but i can fly it if i overlook the stutters.

I think something is going on with the vram usage.

[edpatino]

Not possible to calibrate my Throttle TM TWCS with MVAMS. It simply does nothing.
Hopefully someone at MV could look into this.
Ed

[mvanoverdijk]

Just chiming in to say I am not having issues with performance as a data point for you guys.

[Matthieu-C]

What's your VRAM usage (GB) with it on vs. off?

Suprisingly, the same! But really, FPS increases a lot and movments in the plane are fluid.

[matpietsch]

Just chiming in to say I am not having issues with performance as a data point for you guys.

Me neither. Even when flying ORBX regions.

[Bushido]

I'm having worse FPS with the SP1 than before.
Unchecking the transparent texture and mipmap does'nt seem to change much.
In a random airport, day time, few clouds I have 35 - 40 FPS with Majestic Q400 and 15/20 with the KA 350.
So yes it is now too heavy on frame to really enjoy it.

[SAS443]

I just did a VRAM comparison.
ORBX ESGG (Landvetter, parked right outside the Jet center,GA parking #1)
Stock shaders, Active Sky online wx. 4K monitor, RTX2080ti videocard, 11264 MB VRAM

Scenario 1: Render to transparent surfaces CHECKED. VRAM : 10600 MB
Scenario 2: Render to transparent surfaces UNCHECKED .VRAM : 8800 MB

Clearly something is eating away on our video memory here, which is at least for me, causing stutters in cruise with that option enabled.

[alex.767]

Here is another comparison, this time at LatinVFR's FLL with rendering to surfaces OFF. It's getting literally half of the FPS of today's worst-performing add-ons and more than 1GB more in VRAM usage.


FPS VRAM

KA350 15.3 7,889
NGXu 28.1 6,659
FSL 321 30.9 6,566