WideFS and Flightlogger

[EHM-1651 Christian]

Is it possible to run Flightlogger on a different computer than the one running Flight simulator using WideFS??

[EHM-0654 Murray]

Christian,

As a pilot with 4 PCs in my current cockpit setup, yes. I think I'm right in saying you'll need paid for FSUIPC/WideFS.

[EHM-1651 Christian]

I got that so it's possible, just bought both FSUIPC and WideFS last year, didn't have any use for it until now;)

"CTRL+SHIFT+F1";D

[EHM-1242 Stef]

Ok, don't have 4 pc's, but two will do as well:

Why is it that with the new FLogger (3.0. for some reason can not get the FLogger to connect to my FS-pc through my - registered - WideFS (ver 6.7.1). Any special tricks i need to apply to get things up-and-running?

Tried installing already in all possible ways (under Admin and normal Power User account, with and without WideFS running in background etc.) Even manually editted the registry since i found on my FS-pc there were few more keys then on my WideFS-pc (including altering some registry permissions)... All to no avail.

WideFS (-connection) runs beautifully for my other software (FS-Commander, FS Flightkeeper, ActiveSky 6.5), but it's just the new FLogger which keeps coming back with "Can not connect to FS".

Oh, and while being at it: on my WideFS pc FLogger also ONLY runs under Administrator login. When started as Power User i come as far as my EHM-login, after which... well, she just disappears. On my FS-pc she runs ok as she should. No problems there.

If anybody can help me out, many thanks already in advance!

Best regards,
Stef

[EHM-1651 Christian]

Murray where are you now? This must be something for you;)

[EHM-0654 Murray]

Hmm... Never heard that one before.

Only things I can suggest are:-

1. Start FS in Window mode so you can see the title bar. FSUIPC prints some useful stuff to it when it's running happily.

2. Start order is vitally important to WideFS, hence the "client" config having commands for "RunReady" and such. Start FS, get it to "sat at the gate", and only then start WideFS client on your second PC (disable all your "Run" and "RunReady" commands on the client so you can debug). Now start FLogger and see if it works.

Re: power users, I really couldn't say as my three "not FS" PCs all run WinXP as Administrators - I find WinXP is just happier that way.

[EHM-1242 Stef]

Hi Murray,

Thanks for getting into this. Regarding your suggestions:

1. My FS always runs in Window mode, to take advantage of the better framerates achieved this way. Known fact from FS has always been already that price to pay for running full-screen mode is 3-4 fps... All titlebar shows is a happily running WideServer with 1 connected (after i start my WideClient on my WideFS-pc)

2. Know about the "Run" and "RunReady" commands but i don't use them (don't always run everything). My procedure is as you described:

a. start FS2004 (the 9.1 version) on my FS-pc;
b. after titlebar displays "waiting for client" (or similar, can't check right now as i'm not at home), start WideClient on my WideFS pc and check proper indication on my FS-pc to see if all connected correctly;
c. first then one by one start my 'WideFS'-software and check it connects ok.

As said earlier, it all works except for FLogger (even when FLogger is started as single program with 'exclusive use' of the WideFS pipe).

Power User vs. Administrator, well... everybody as they like, right? Indeed, running a Power User system might require some(!) additional administration, but pays it's dividends the moment things start getting hairy. However, don't want to go into that discussion here since even MS still apparently haven't understood the principle they themselves (ok, 'copied' from others...) introduced: understood the default user in new Vista gets once again per default Administrator privileges (and if not then they for sure are using it now for marketing purposes under the motto 'Increased Security!' bla-bla-bla)...

Thanks plenty and am open for any more suggestions anyone might have.

Stef
EHM-1242

[EHM-1242 Stef]

Got it running!

Long story short: changed security settings on all FLogger installed dll's and ActiveX objects in folder C:\Windows\System32 to include Power Users to have 'Full Control'. That did the trick in the end!

Perseverance wins once again!

Thanks and have fun!

Stef
EHM-1242

[EHM-0654 Murray]

Well done Stef, one for the "FAQ"