DynamicFriction LUA for the NGX in P3D not loading anymore?

[WebMaximus]

I've noticed how the ground friction has reverted back to default in the NGX in P3Dv2 latest version and I'm thinking if maybe the Dynamic Friction LUA isn't loading correctly anymore. I checked the fsuipc logfile and couldn't find anything in there that the module has been loaded, not sure if that would normally be displayed in the log file?

 

I also noticed now that I came here that the latest version of fsuipc is 4.939k while I'm using 4.939j so maybe updating will fix this issue but thought I would still ask about this issue in here and if someone else noticed the same problem?

[Pete Dowson]

I've noticed how the ground friction has reverted back to default in the NGX in P3Dv2 latest version and I'm thinking if maybe the Dynamic Friction LUA isn't loading correctly anymore. I checked the fsuipc logfile and couldn't find anything in there that the module has been loaded, not sure if that would normally be displayed in the log file?

 

Unless you've disabled it, the default FSUIPC access capability to frictions is listed n the start of the log like this:

 

--- SIM1 Frictions access gained and basic values patched

 

along with several other successful hooks  So check that. 

 

If you want logging of Lua plug-ins loading and ending then you have to enable Button/Key logging, or for much more info, Lua debug/trace.

 

You don't mention how you are loading the Lua plug-in, so I can't really suggest much else.

 

Pete

[WebMaximus]

Please delete.

[Pete Dowson]

 

After upgrading to the latest version of FSUIPC it appears the dynamic friction is working again but will do some more testing.

This is what my log file looks like

      546 --- SIM1 Frictions access gained

 

 

That's okay. The log for a working install isn't really of a lot of interest of course! ;-)

 

Pete

[Pete Dowson]

I also removed 31899 lines of this error message from the log file for posting here, I asked about this error message in another thread.

5852783 Exception 3 "UNRECOGNIZED_ID", Ref 108391, Index param 3 on write SetData for "ELECTRICAL BATTERY VOLTAGE"

 

 

Where is the other thread? Can't find it.

 

The battery voltage is written to in order to operate the extended battery life option on FSUIPC's Miscellaneous options tab. The ID should be the ID of the user aircraft, and is standard. At what stage in that log did the first such error message get logged? Does it occur with all aircraft? Does it occur without that option enabled? 

 

I have enabled the battery life option here and do not get the same problem with the aircraft I have tried. It is possible for other addons to send these things to FS through FSUIPC, so check addons too.

 

Pete

 

[WebMaximus]

Either the other thread somehow disappeared or I'm going crazy because I did create a new thread asking about this yesterday but now I can't find it.

 

Anyway the first occurrence of the error message in the log file is the one seen in my posted log file above.

 

Have only checked with PMDG's NGX since that is the only addon a/c I've installed, haven't tried with any of the default P3D a/c.

 

Haven't tried disabling the extended battery life option but will do and report back.

[Pete Dowson]

Anyway the first occurrence of the error message in the log file is the one seen in my posted log file above.

 

Oh, so nearly 1 hour and 40 minutes into the session? Hmm. I've never run P3D for that long! What are all the "stops" before it?

 

 

Have only checked with PMDG's NGX since that is the only addon a/c I've installed, haven't tried with any of the default P3D a/c.

 

 

I only have default aircraft. But if it does it with any of those I suspect there's something wrong in your installation.

 

Pete

[WebMaximus]

Well...1 hour and 40 minutes isn't much in my case doing online flight in Europe. As for the stops I'm not 100% sure but might have been when I've been accessing the P3D menus trying out various settings in an attempt to get rid of some stuttering I've seen on my last couple of flights and so far I haven't been able to track down the cause of them. Most annoying and was thinking maybe what I've seen in the fsuipc log could explain the stuttering considering the number of entries found in the log. Took all of the lines containing this error message and pasted them into an online web service that will let you count the lines and almost fell out of my chair when I realized there were almost 32.000 of them...

 

Very strange all this because I've been using FSUIPC for years and same thing goes for the NGX and never seen anything like this before and have always had the extended battery option set to '0' for infinite but I've now disabled that option for testing purposes so will be interesting to see if I get the same thing on next flight. Did a quick test earlier today and just fired up P3D with the NGX and switched on the battery to see if that would log any errors but nothing.

[Pete Dowson]

Well...1 hour and 40 minutes isn't much in my case doing online flight in Europe.

 

Ha ha. It's just that I don't much like P3D so don't use it. It is only installed on my development PC for testing and development.

 

Most annoying and was thinking maybe what I've seen in the fsuipc log could explain the stuttering considering the number of entries found in the log. Took all of the lines containing this error message and pasted them into an online web service that will let you count the lines and almost fell out of my chair when I realized there were almost 32.000 of them..

 

Whatever is causing the error could well be causing the problem,yes, but the logging itself won't. I've had full SimConnect logging on and 32000 lines is nothing once you've seen what that can produce -- and in a lot less that 1 hour 40!   32000 lines a minute, is closer (exaggeration for effect, sorry) -- but no stuttering is caused even then, just a large file which would be written at low priority by the clever Windows file system.

 

But if you really think it might simply be the logging of the errors causing your problems, I can add an option to suppress it. Trouble is it will suppress logging of all reported SimConnect errors and some may be (more) important.

 

Very strange all this because I've been using FSUIPC for years and same thing goes for the NGX and never seen anything like this before and have always had the extended battery option set to '0' for infinite but I've now disabled that option for testing purposes so will be interesting to see if I get the same thing on next flight. Did a quick test earlier today and just fired up P3D with the NGX and switched on the battery to see if that would log any errors but nothing.

 

Something is happening after a time, though, that's the point. What other add-ons are you running?  The Battery Voltage is FSUIPC offset 2834. Other programs might be accessing it too. FSUIPC only uses it for the "magic battery" facility.  The thing is, though the ID it uses is always the standard one meaning the User Aircraft. I've no idea how that can be corrupted -- it is used for many of FSUIPC's actions so if it was truly bad in FSUIPC you'd get thousands of other similar errors too. So it must be somethinig happening further down, in SimConnect.

 

You could actually get a SimConnect log which would show more -- but with it not starting for 1h 40m you'd have millions of lines of entries before the bit we'd need. Especially with PMDG which uses SimConnect even more than FSUIPC does!

 

Pete

[WebMaximus]

32.000 lines in a minute...now that's what I call some serious logging :LOL:

 

Right now I think my main problem is trying to track down what could actually be causing this stuttering I've seen. As for the FSUIPC logging maybe I was unclear but I don't think the logging in itself is to blame but more just like you mention what is actually causing all these errors to end up in the log. Clearly something is not right, I just need to figure out the culprit.

 

First I thought it might have been related to the latest beta build of Active Sky Next because I'm part of that team and these stuttering happened shortly after I upgraded ASN to the latest build. For that reason that was my first stop asking about this but no one else seem to have seen the same problem so doens't appear to be ASN causing my problem.

 

In situations like this one where you all of a sudden get a problem 'out of the blue' and you can't really figure out why I wish there was some kind of "superlogging" feature in FSX/P3D you could enable that would help you troubleshoot exactly what is causing your issue in my case stuttering. Imagine how nice it would have been in a situation like this one to have a log where you clearly could see the stutters listed somehow marked as 'Poor performance' entries or something like that and then an explanation what is the reason/bottleneck...that would really be awsome!

 

Oh well...will not bore you to death with my issue but instead I'll keep trying to exclude one thing at a time doing more testing and hopefully I'll find the culprit eventually. Problem is the testing is rather time consuming since I don't see this until I'm up in the air and have been flying for some time and time currently isn't one of my biggest resources.

 

Many thanks Pete for trying to help me out, much appreciated!!

 

Here's what my simulator looks like and this is my hardware config.

[WebMaximus]

I'm very happy to tell you I just completed a flight and this time without any stuttering and no error entries in the FSUIPC log file.

 

Since I changed several things I can't know for sure what was actually the culprit but at this point I don't really care to be honest, I'm just happy my performance is back to normal. I've come to the conclusion that I often spend far more time tweaking and troubleshooting vs flying and I intend to change that...at least that's my plan :wink:

 

What I changed before this flight include:

 

- disabled the extended battery option in FSUIPC

- did a clean install of the Nvidia drivers (347.88)

- upgraded ASN to the latest private beta version

- flew to FlyTampa Copenhagen rather than Aerosoft Oslo

 

Now I'll make sure to perform a complete backup of my PC to make sure I'll be able to revert to this point should I face any additional issues...

 

Thanks again Pete for your interest in my issue!

[WebMaximus]

Unfortunately the luck didn't last...just experienced really bad stuttering on my return leg to Stockholm from Copenhagen. Checking the FSUIPC log file there's still no error messages so I guess that means whatever was causing them that was not the cause of my stuttering issue.

 

Right now I'm thinking maybe the stuttering issue is related to another issue I have with TrackIR that for some reason stop working mid-flight and has done so a couple of times now. Reason I'm suspecting there's a relation between these two issues is on today's flight everthing started when I noticed how the stuttering got worse and worse during the approach and then on final when the stuttering was really bad all of a sudden TrackIR stopped working.

 

Not sure how TrackIR is communicating with P3Dv2, if it's via SimConnect or FSUIPC. Was thinking if it might be a SimConnect flooding issue causing both the stuttering and then eventually the TrackIR software crash where the head movement stops working totally instead of just being jerky.

 

Don't you just love these kind of problems spoiling the fun in flying...

[Pete Dowson]

Not sure how TrackIR is communicating with P3Dv2, if it's via SimConnect or FSUIPC.

 

Certainly not FSUIPC.

 

Pete

[WebMaximus]

Got it.