How to start EFIS?

[perstahle]

Dear jarek! This is odd, isnt it? I have never ever experienced somethig like this strange and odd issue over my 25 years in this hobby...
Lets pray for a soon fix/solution! I have spend days, hours trying to fix this, as You read in my previus posts.

[Slayer]

I suspect he has leftovers somewhere either in programdata and or appdata. Either that or it is a permissions issue.

Has anyone tried to check your machine via teamviewer?

[perstahle]

Teamviewer?

[Slayer]

A program that lets you share yor pc with someone else temporarily for troubleshooting

[Slayer]

Also i havent seen any suggestion to remove MVAMS and make sure it is wiped from p3d and appdata/program data. There may be leftovers in there from a old beta and wiping p3d wouldnt get rid of those either

[perstahle]

But I completley "blowed out" of my computer a few days ago, and did all things from scratch, win10, etc etc... So it cant be any "left overs", can it???

[perstahle]

what did You mean with "permissions issue"? Run as adim? I always do that.

[perstahle]

...Example, when I do a startup, I can see the didgits "rising" when the engines spools up, etc... all that, is there! But no "didgital LCD gauges" etc
All numbers, letters and didgits are there, but not "the rest"... Gosh, this drives me nuts...

[hillal.alkhanjiry]

A program that lets you share yor pc with someone else temporarily for troubleshooting

It can't be "left over", in my case i just buy K.A.350 on 24th this December and never use Beta version, in "perstahle" case he already provide even his log file for review, so let keep "Teamviewer" thing aside for now, this is not issue which effect just one person on one PC. I believe there's a lot of people have the same issue and following this topic patiently. there's a lot of professional suggestions back in topic which we go though almost all of them. we must agree that there's a bug/missing file or something go wrong somewhere and need to be fixed.

[perstahle]

I agree "hillal.alkhanjiry"
Lets keep our fingers crossed for a fix/solution for this as soon as possible, like You said, You and me cant be the only ones having this issue out there, and like stated before, there has to be something in the KA file causing this.
I am sure of that this proffesional and serviceminded team behind this awsome bird digging into this right now, as much as they can... For sure as confused as we are "hillal.alkhanjiry", They have been fantastic so far, and so have all of You others out there trying Your best to find a way to nail this problem.
Love ya all!
Per

[perstahle]

After days and days of "trial and error", my "gut feeling" is that there HAS to be something within the KA file iteslf, cant be anyting else...
Where is my magic wand?...

[Turbofandude]

The incomplete looking displays is caused by Sparse Grid Super Sampling. Please disable this via NVIDIA Inspector (even if it is uninstalled, the settings it changes may remain).

[perstahle]

Ok... How to disable that? I mean "remove it" or just disable it, (?) I have tried different settings including non Sparase Grid Super Sampling in Nvidia inspector, so far without positive result, (is there another way to "remove" it?)
I will give it a try. Again.
What do You recomend? in the settings if not use Sparase, what "value" should I use?
Best regards
Per

[Turbofandude]

I’m not an NVIDIA Inspector user, so I’ve always deferred to built in SSAA/FXAA.

[perstahle]

Please Sir, explain this "deferred to built in SSAA/FXAA"
I have tried OFF, 2, 4, 8 Supersampling and 2, 4, 8 Sparase Grid Supersampling
Non of them is any soultion for this problem, witch value I choose, same "negative" result... No screens working as they should in the cockpit.
Sorry, but thats not the problem. There is someting else, it has to be.
But huge thank You for Your advise "Turbofandude"
Best regards
Per