25 minutes ago, FSXCYYZEGLL said:

I assume you mean the FSUIPC6 log? I don't know if RC4 has a logging system. And if it does I don't know how to use it.

Yes, FSUIPC log. There is a logging system on RC4 but it gets huge very quickly and only John Decker could decipher it. Send it to John Dowson when you post there too.

On 9/24/2024 at 3:33 PM, Ray Proudfoot said:

Yes, FSUIPC log. There is a logging system on RC4 but it gets huge very quickly and only John Decker could decipher it. Send it to John Dowson when you post there too.

So did that for logging. There's a few problems coming up.

Which settings should I use for logging RC4? My last settings lead to a 430 mb log in one hour and made it impossible for me to find out the problem or error that occurred.

However there could be some other issues. For example I wonder if my FSUIPC6 install or the way I installed RC4 was messed up, I sort of was haphazard with both of em, and the folder locations don't make a ton of sense to me.

The only other thing I can think of is that the Flight number for the QW787 is normally 787, however the one time I flew a successful flight the flight number for that (in the P3D aircraft selection settings) was 7. I don't know why that would make a blind bit of difference and it's probably nothing more than a coincidence.

Finally put a post on Pete's forum, hopefully he has some ideas.

Signed Jon.

Edited September 26, 20241 yr by FSXCYYZEGLL

3 hours ago, FSXCYYZEGLL said:

Which settings should I use for logging RC4?

No point as the log can only be analysed by John Decker who is no longer active.

3 hours ago, FSXCYYZEGLL said:

However there could be some other issues. For example I wonder if my FSUIPC6 install or the way I installed RC4 was messed up, I sort of was haphazard with both of em, and the folder locations don't make a ton of sense to me.

This concerns me. You were asked to install the latest version of FSUIPC and said you did but I want to know the version number. It’s in the log. The version of FSUIPC that came with RC4 is out of date. You must install the latest I linked to.

Haphazard installs tend not to end well as you’re proving. Please post the FSUIPC log here. And what is the title of your post on the FSUIPC forum? I can’t see anything relevant.

1 hour ago, Ray Proudfoot said:

No point as the log can only be analysed by John Decker who is no longer active.

This concerns me. You were asked to install the latest version of FSUIPC and said you did but I want to know the version number. It’s in the log. The version of FSUIPC that came with RC4 is out of date. You must install the latest I linked to.

Haphazard installs tend not to end well as you’re proving. Please post the FSUIPC log here. And what is the title of your post on the FSUIPC forum? I can’t see anything relevant.

My bad, I meant what settings should I use for the FSUIPC6 log. I did take an initial log but it's over 400mb large, so something tells me my settings were too broad.

I would post the log here, but again its over 400mb large so something tells me it contains way too much info to allow for meaningful breakdown.

So for the next flight (as one of the flightplans I have has been able to induce crashes consistently), which settings do you want me to use for the logging process?

My FSUIPC6 version is 6.2.1.

My post on the FSUIPC forum was entitled D008, it just got approved by the moderator ( I'm a new poster to the website). Here's the link. https://forum.simflight.com/topic/98908-rc4-and-qw787-d008-crash/#comment-594805

Yeah, similar issues of problems with the install came about with AIG. Hopefully the fix for this one is simpler.

Signed Jon.

Edited September 26, 20241 yr by FSXCYYZEGLL

Jon, why is your log so huge? Mine is 7Kb. Look at your fsuipc6.ini and in the General section see if you have an entry named Debug=Please. If so, please remove it because that could be a factor.

Make that one change if necessary and try another flight. v6.2.1 is the current version which I have.

On 8/18/2024 at 3:37 PM, Bob Scott said:

FSUIPC offset D008 is a timer value that's used in two types of queries, one for active runway info at an airport, the other for AI traffic ID.  Apparently the timer has stopped updating after RC4 makes one of those types of queries.

Given the huge size of his FSUIPC logs do you think extra logging is going on here? It's only meant to be used sparingly to resolve problems. If logging is enabled might that cause the problem? I'll ask John Dowson.

There are a number of logging options, all set in the [General] section of the FSUIPCx.ini file.  Default is no logging options turned on.  Clearly the OP has one or more prolific logging options enabled.

It sounds to me like the QW 787 is overloading simconnect and it stops responding to FSUIPC's queries, stalling the D008 timer/counter for long enough to trigger the error in RC4.  Given that there's no longer support for either the QW 787 or Radar Contact, I would do what I can to reduce the load on simconnect.  Turning TCAS off might help, in addition to turning off AI reporting in FSUIPC as Pete suggested on his support forum.

The OP hasn't said if he's running other software that's also hitting simconnect, e.g. ActiveSky, FSTrafficBoard etc.

One other thought--AI traffic using traffic bgls instead of AIG's traffic injector would also reduce the simconnect load considerably.

Ok so I read the replies on the forum by John.

The logging options I had enabled that led to such a large file was the read and write options were enabled. From what I understand for logging purposes just have all the settings unchecked and run a log file, that will pick any issues as needed.

It can't be the logs as an issue as I only turned them on for diagnosing this problem, so the logs came after the problem already asserted itself, not before.

I am running Active Sky for P3D. I also use AI Companion, I don't know if that uses Simconnect or not.

And all my traffic uses BGLs instead of the injector system.

Signed Jon.

Edited September 26, 20241 yr by FSXCYYZEGLL

35 minutes ago, FSXCYYZEGLL said:

I am running Active Sky for P3D. I also use AI Companion, I don't know if that uses Simconnect or not.

And all my traffic uses BGLs instead of the injector system.

It does use SimConnect as does Active Sky. I also use BGLs with injected only for a small number of airlines.

I suggest you turn off all FSUIPC logging and don’t run AI Companion. See if that makes a difference. Also, stick to the PMDG 777 as I can confirm no issues with that aircraft.

Where is RC4 installed? Inside Program Files? If so move it to C:\RC4 away from the extra protection of Windows. You can just drag the rcv4x folder to C:. No registry entries.

If you still get the error reduce Ai by 50% and see if that stops the problem.

 

On 9/26/2024 at 1:22 PM, Ray Proudfoot said:

It does use SimConnect as does Active Sky. I also use BGLs with injected only for a small number of airlines.

I suggest you turn off all FSUIPC logging and don’t run AI Companion. See if that makes a difference. Also, stick to the PMDG 777 as I can confirm no issues with that aircraft.

Where is RC4 installed? Inside Program Files? If so move it to C:\RC4 away from the extra protection of Windows. You can just drag the rcv4x folder to C:. No registry entries.

If you still get the error reduce Ai by 50% and see if that stops the problem.

 

The issue with turning off AI Companion is that would lead to quite a bit of AI clutter and Frame rate issues, that could unintentionally aggravate the situation to be honest, as there'd be dozens of AI on the ground.

It was installed in Program Files, and has now been moved to C, I just moved the rcv4x folder to C.

I've made some alterations to the FSUIPC ini (I discussed them on the Forum post for FSUIPC) and added flight numbers to all 787 liveries I'm using, to see if that makes a difference (it shouldn't but there's no harm in trying).

Finally I want to confirm, what is the procedure for Rebuilding the Scenery Database? Because the fact that it keeps happening at a certain waypoint for a certain flightplan indicates it could be a scenery issue.

The way I do it is click Rebuild Scenery DB, then no say no for WideFS (as it isn't) and then put in the file where P3D is located. Then MakeRwys automatically activates and then RC4 reads the database.

It seems to work, cause when I change airports around RC4 recognizes those changes, but am I doing something wrong there?

Jon

25 minutes ago, FSXCYYZEGLL said:

Finally I want to confirm, what is the procedure for Rebuilding the Scenery Database? Because the fact that it keeps happening at a certain waypoint for a certain flightplan indicates it could be a scenery issue.

The way I do it is click Rebuild Scenery DB, then no say no for WideFS (as it isn't) and then put in the file where P3D is located. Then MakeRwys automatically activates and then RC4 reads the database.

It seems to work, cause when I change airports around RC4 recognizes those changes, but am I doing something wrong there?

I have RC4 on a network computer so gave never tried that on a single computer. The manual should tell you. Make sure you have the latest MakeRwys from Pete’s site.

The files RC needs are created in the root P3D folder. Check they’re being copied to the RC4\data folder. I’d be inclined to run MakeRwys first.

https://forum.simflight.com/topic/66136-useful-additional-programs/

Stick to the 777. If the problem goes away the 787 was the problem. If it doesn’t then further investigation is required.

I'll try it on the PMDG to see if the problem remains. I hope it doesn't.

Tried making the FSUIPC ini changes and flew the 787, crashed again, and around the same area.

It's a shame both RC4 and the QW787 aren't being updated anymore cause I like em both, ah well such is life.

Jon.

On 9/26/2024 at 11:17 AM, Bob Scott said:

There are a number of logging options, all set in the [General] section of the FSUIPCx.ini file.  Default is no logging options turned on.  Clearly the OP has one or more prolific logging options enabled.

It sounds to me like the QW 787 is overloading simconnect and it stops responding to FSUIPC's queries, stalling the D008 timer/counter for long enough to trigger the error in RC4.  Given that there's no longer support for either the QW 787 or Radar Contact, I would do what I can to reduce the load on simconnect.  Turning TCAS off might help, in addition to turning off AI reporting in FSUIPC as Pete suggested on his support forum.

The OP hasn't said if he's running other software that's also hitting simconnect, e.g. ActiveSky, FSTrafficBoard etc.

One other thought--AI traffic using traffic bgls instead of AIG's traffic injector would also reduce the simconnect load considerably.

As a question, if I turn off AI reporting in FSUIPC what will that do?

Will RC4 be able to tell the AI to change headings to avoid me? Will AI still request clearances from RC4, will the AI even talk on RC4? And what would it do to things like TCAS, will those just not work now?

Cause honestly if getting rid of AI reporting doesn't come with too many deficits I'm willing to try that. Testing a flight for an hour+ each time just to get a crash with no obvious cause is a bit tiring to say the least.

Jon.

Jon, have you rebuilt the RC database using the suggestion I made earlier? There’s no point testing with Ai reporting turned off. This problem is on your system, not one in FSUIPC or RC4.

1 minute ago, Ray Proudfoot said:

Jon, have you rebuilt the RC database using the suggestion I made earlier? There’s no point testing with Ai reporting turned off. This problem is on your system, not one in FSUIPC or RC4.

Well the QW787 seems to have this issue with multiple people and RC4, but I digress.

Umm, I'll be honest I'm a little confused what your suggestion is? I updated MakeRunways in the P3D folder using the latest download. Outside of that I'm not sure if I'm doing it correctly or not. I also checked the manual, but it mostly refers to WideFS, and certainly not P3D with Lorby's.

So let me describe what I do so you can tell me if I've followed your instructions correctly.

I open up RC4 ( I do not use administrator now, that's something I changed when I moved the file out of Program Files).

Then I click Rebuild Scenery DB. It asks is this WideFS, I say no. It then asks me to enter where the FS path is located, I put in the P3D path, then it states "RC Rebuilding r4.csv, running \MakeRwys.exe". MakeRwys requests admin access and I grant it, then MakeRwys 5.13 starts running and analyzing all the airports. It finishes and says "All Main Data files produced ok"

RC4 then says "RC finished Rebuilding r4.csv" I click ok. Then it says "RC Rebuilding new a4.csv file" I click ok. And finally it says "RC finished rebuilding a4.csv" and I click ok. And that's that.

Don't mean to be laborious, but as I can't show you how I do it, this is the next best thing.

I think this is how it's supposed to be done, but it wouldn't the first time I've made a basic mistake.

Thanks again Ray.

Jon