FSXCYYZEGLL

Hi All. So I don't know if this is the wrong forum for this so apologies in advance if it is. In short I learned that PF3 is now freeware and as I wanted to try it out. I install it (not in the program files or X86) and start it up. I enter 999 as the activation code (and make sure that I'm running it on administrator), it then asks for a password and an email, I don't enter the email cause I figure there's no reason, but I do enter a basic password (cause if I don't it says "invalid password" and ends the process). This is where the issue starts, when I click ok afterwards the program just quits, it just ends right then and there. No warning, no lag or stutter, it just stops. Furthermore when I click it again it starts the whole activation process again. A piece of advice I saw was to modify the ini file, however my folder doesn't even appear to have one, and each time I've reinstalled it the PF3 folder did not have an ini file within it. So long story short, anyone have any idea what to do? Jon.

Oh my bad. Yes they show the correct date and time, so they're updating correctly. One of the suggestions made on the FSUIPC6 forums way back when for this issue was to alter the CPU priority of the RC4, I know how to do that, but what would that entail, and could it lead to issues? I know this almost certainly a QW787 issue, I'm still just hopeful that somehow I can find a way to allow the 787 to work with RC4, as I do enjoy the plane. Jon.

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

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.

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.

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

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.

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.

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.

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. Will do on John Downson's forum. Signed Jon.

Yeah no luck on mine. It worked for a bit and crashed within 2 hours, same D008 issue. I'm not sure what's going on here. Signed Jon.

Hey Ray. Yeah I updated the RC database after MakeRwys. I tried the solution you found, for a flight to Heathrow. The initial flight there worked fine, but there were issues on the way back and it crashed as I climbed unfortunately. However I've edited the TrafficStallTime=10 instead of 5, hopefully that may help. Testing a flight at the moment. Do you know what traffic stall time and the 2 entries underneath it mean in FSUIPC? And why it appears to not play nice with RC4 sometimes? Signed Jon.

Bad news unfortunately. Updated MakeRwys and reinstalled FSUIPC. Crashed again, same issue. Also I'm on V 5.3 HF2 as well. Signed Jon.

Well updated the Airport Database and it had the same issue just at TOC and stopped working. So the airport database update doesn't do it. I'll try to reinstall FSUIPC 6 next and see if that helps, maybe some wires got crossed somewhere. Jon.

Apologies Ray. It only comes up later in the flight, never right at the beginning or even during the early portions like take-off. Normally during cruise or climb out. I think I have the latest version of FSUIPC, version 6 I believe? I don't think its third party ones, cause it can occur in any of them though the 787 is a bit more frequent. I'll try to update the airport database before flight each time and see if that helps. Jon.