FMGS 100% CPU utilization

[OmniAtlas]

Reinstalled Windows 10, copied FMGS back over onto the system -- when I start up all the panels performances is extremely sluggish now (never had this issue before), and CPU utilization is 100%.

I find it very strange EIS is now using 100% of all cores (running on a dual core G3258 overclocked to 4.2 GHZ).

Does anyone know what is going on?

[OmniAtlas]

Reinstalled FMGS - utilisation is still 100% with 6 instances of EIS running. Response from the system is slow; FMGS is unusuable now unfortunately.

[Fritz]

I had initially also difficulties with Windows 10 but because of the network configuration.
Is Windows 10 on the most current status? I had still constantly updates in the backdrop.
After the update, everything went smoothly.
If nothing helps, then you should reinstall again.

[iwik]

Ben,
That's why I avoided Win 10 cause MS will do what it likes when it likes and all you get is a lot of frustration.
Unfortunately its what one gets to always want to be up with the latest.
les

[OmniAtlas]

Hey all -- there are no updates running on the back ground.

Strangely enough, when i've disconnected the accessory monitor (was planning to use it for OVH panel software, flight planning and vpilot) from the client computer -- so now there are only 4 acting LCD connected vs 5, it is smooth again despite still being 100% utilization.


I am not too sure why having an extra 'desktop' LCD plugged in causes havoc and slows down the system

[jeehell]

If it's an USB screen, it uses CPU to compute the displays, not the GPU.
EIS do use a lot of CPU particularly the NDs (route computations).
I will rework the architecture one day, but for now unfortunately it has to be that way.

JL

[OmniAtlas]

That screen is running of the inbult intel graphics card (DVI port) -- does that also use CPU utilization? The MCDU is also running off the intel gpu.

Regards.

[jeehell]

I guess there is a graphical chipsets built-in for that one so the driver is not hogging the CPU.
However, I believe it is often source of issues to use several different GPUs (i.e. not the same one doubled). Not sure exactly how this all works at hardware level...

JL