Bryn Posted February 13, 2015 Report Share Posted February 13, 2015 Hi, Despite turning off lua logging and not having anything in my fsuipc that would enable it, my FSUIPC keeps on logging LUA events over and over. The consequence is that I have a file that keeps growing in size through the flight to a rather large size. Here's an example of what it keeps logging: 5823362 LUA.0: c:\fsx\Modules\DynamicFriction.lua:61 5823362 LUA.0: c:\fsx\Modules\DynamicFriction.lua:91 5824376 LUA.0: c:\fsx\Modules\DynamicFriction.lua:52 5824376 LUA.0: c:\fsx\Modules\DynamicFriction.lua:53 etc, etc Is there something I've missed that would turn all that off? Bryn. Link to comment Share on other sites More sharing options...
Thomas Richter Posted February 13, 2015 Report Share Posted February 13, 2015 Hi, does it physically switch the LUA logging on in FSUIPC Logging section, marked? If so, then a program that runs on the server or on a client is doing this! I found that e.g. Opencockpit software is doing that by using the Offset 3400 for that, for no reason of course. Just log the Offset 3400 (U16) in FSUIPC and check which program (thread number) is doing that. If it is not possible to stop a program doing that then just add this to [WideFS] section in FSUIPC Deny=3400,2 or on the client under [user] section Deny=3400,2 That prevents programs to activate or de-activate logging options via Offset 3400. Link to comment Share on other sites More sharing options...
Bryn Posted February 13, 2015 Author Report Share Posted February 13, 2015 Thanks for your thoughts - I bet that was a painful debugging session to work that out! Alas, so far as I can see, Offset 3400 is not being used in my setup. I did notice one more odd thing, though. If I tick the box for debug/trace lua plugins in the FSUIPC UI, and then click 'stop' it doesn't untick the box. That is different behaviour to all of the other logging options. Bryn. Link to comment Share on other sites More sharing options...
Bryn Posted February 13, 2015 Author Report Share Posted February 13, 2015 Perhaps this is also a bit revealing. All the bits in LogOptions are zero, except the last one, which turns logging on (I think I'm reading that right). 15195730 LogOptions changed, now 00000000 00000001 15196370 LUA.0: c:\fsx\Modules\DynamicFriction.lua:52 15196370 LUA.0: c:\fsx\Modules\DynamicFriction.lua:53 15196370 LUA.0: Global: GS_ipc = 19388886 If that's the case, why is LUA getting logged? Bryn. Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 13, 2015 Report Share Posted February 13, 2015 Perhaps this is also a bit revealing. All the bits in LogOptions are zero, except the last one, which turns logging on (I think I'm reading that right). 15195730 LogOptions changed, now 00000000 00000001 15196370 LUA.0: c:\fsx\Modules\DynamicFriction.lua:52 15196370 LUA.0: c:\fsx\Modules\DynamicFriction.lua:53 15196370 LUA.0: Global: GS_ipc = 19388886 If that's the case, why is LUA getting logged? Bryn. Last reply till 28th -- just on my way to Sri Lanka. How are you starting that DynamicFriction? If you start it with "LuaDebug ..." then it does the same as using the Debug/Trace Lua option. "STOP" on the Logging tab only affects the main internal logging options. Pete Link to comment Share on other sites More sharing options...
Bryn Posted February 14, 2015 Author Report Share Posted February 14, 2015 Thanks Pete. As usual, it's all my own fault. For some reason (which doesn't look to have been terribly sensible), I had these lines in the fsuipc.ini: LogLua=No DebugLua=Yes Removing them stopped the logging. Cheers, Bryn. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now