wideview-question: FPS difference, what then?

Hello!
In another thread I asked about how to move the LevelD-gauges to another computer, to save som FPS.
But the gentlemans answers were conclusive: Rund LevelD and its gauges only, on a not-so-super-computer, and let the super-computer deal only with the outside view.
Now I have tried the Wideview software, which actually (!) worked with no fuss.
However, I wonder:
If the server, where I run LevelD, ActiveSky, Squawkbox, etc, has a FPS of 25 (which is good enough for gauge updates), and the outside view-computer has 60, will it then stutter in a way? It will be updated only 25FPS, and the reason for doing it this way is because I will have 60 FPS instead of 25 when I remove the panels!
So the question is: Must the server computer actually be on the fast side, not to slow down the clients?

And maybe anyone has an ultimate WideView-setting to share from the .ini-file?

I don't know this as fact, but I've read that FS is only as fast as the slowest computer using WidevieW.

Here is something to think about. How is it physically connected and what protocol is used for the app? I know those answers. Are you limited to what your system hardware capability is through your ethernet port and any hardware in between. Use a packet sniffer and watch what is passed. You will be amazed at the overhead. But can you make changes that your eye can see? Maybe. Don't chase frame rates, focus instead on fluidity in temporary high graphic situations. At FL320 and 480+ knots is tree detail important? I myself would rather have responsive instruments and some detail during taxi, takeoff & landing. Oh and some darn nice clouds and sky color to transition through. As with everything, your milage will vary from other hardware. I think that is one of the best things about flight simulation, nothing is the same. But then again, are we ever satisfied with it?

I see what you mean.
I just wondered what is really happening when the WV-server is haveing fewer FPS than the client;
the client stays at, say 100FPS, but the server only sends out 20 changes pr. second.. Another kind of stutter;)
But with a proper server-computer, not expensive, but better than "the old one up on the attic", should manage to get 60 FPS with absolutely no scenery to draw.

And if it is important, I will buy two additional network cards,
to get a direct line with its own protocol.