Jump to content
The simFlight Network Forums

beechcaptain

Members
  • Posts

    13
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    Deep South

Recent Profile Visitors

342 profile views

beechcaptain's Achievements

Rookie

Rookie (2/14)

  • Collaborator Rare
  • First Post Rare
  • Conversation Starter Rare
  • Week One Done Rare
  • One Month Later Rare

Recent Badges

0

Reputation

  1. I am happy to report the issue has been resolved. I updated my P3Dv5.3 client to v5.4 and all is back to normal now.
  2. I almost forgot to ask, since my memory fails me sometimes (a lot according to my wife, ha, ha) can I install v6.2.0 over existing 6.1.9? I assume so but want to be sure it's safe. <--- I should have read the provided guide first, it answered my question. Thanks. & thanks for the tip on the profile listing format! Glenn
  3. Oh, darn, I meant to check for latest version and forgot. Let me update and then I'll keep the logging window active for all of my future flights and closely monitor so when the gremlin strikes again, hopefully the culprit will be detectable. Thanks & kindest regards, Glenn
  4. John, would you mind reviewing my attached FSUIPC.ini file and see if there is anything unusual or potential problem causer? Kindest regards, Glenn FSUIPC6.ini
  5. Yes, I did redo my settings, et al. Yes, I agree, it is drastic action taken on my part, but I did make a backup copy. However, after two successful flights without incident, I just encountered the issue again on taxi after pushback. Unfortunately, I forgot to turn the event logging window back on so I don't know what events took place. I will fly another flight tomorrow and will keep events logging turned on. I rechecked the current FSUIPC.ini and nothing had changed since it rebuilt two flights prior. I'll report back after the next flight.
  6. Good news. 2 most recent flights, since deleting fsuipc.ini and letting it rebuild, I have not experienced any issues! Nothing unusual showed up in the Events logging window. Fingers crossed, hoping all is good from now on. Kindest regards, Glenn
  7. [quote]And if anything in the file had changed, then you must have done this via changing the settings in the UI (or editing directly). Doing this would also delete all your assignments, if you are using a registered version of FSUIPC6.[/quote] Ah, yes I have directly edited the ini file. I am a registered version user. 🙂 Thanks for your help. Kindest regards, Glenn
  8. I ran a short test with logging console window open and kept getting 2 events frequently: EVENT: Cntrl= 66587 (0x0001041b), Param= 97903 (0x00017e6f) ROTOR_BRAKE EVENT: Cntrl= 66734 (0x000104ae), Param= 1 (0x00000001) MOUSE_LOOK_TOGGLE I have the mouse look active so I understand that event will occur every time I use the mouse to look around within the sim. However, I'm puzzled about the Rotor Brake event. I wasn't doing much in the aircraft (PMDG 737-800 NGXu), sitting on the runway, engines running, parking brake set. I was going through the FMC looking for any item that might have shft+B (Rotor Brake) assigned but found none. I also verified that Rotor Brake shft+B was not checked in the P3D Controls, Key assignment section. I also looked in my FSUIPC aircraft profile that I previously created for jet aircraft and did not find anything for shft+B or 66587. I also did not find it in the FSUIPC.ini either. Are there any other files I should check for this? I did not touch my flight controls - joystick and throttle, so there were no hardware buttons pressed during this test. After searching for ROTOR_BRAKE in the forum I believe "Cntrl= 66587 (0x0001041b), Param= 97903 (0x00017e6f) ROTOR_BRAKE" could be associated with the mouse & possible mouse look. Would this be correct, and not a rogue assignment somewhere? Thanks, Glenn
  9. I meant to say deleting my FSUIPC.ini instead of .log. I'll try that with the logging console window open and see what happens. Thanks.
  10. I have an ongoing problem in P3Dv5.3.17.28160 with all of my addon jetliner aircraft. After engine startup and commencing taxi to departure runway, the aircraft's engine generators get tripped (go offline) and the systems all shut down. Note: I do not have any failures turned on in PMDG a/c or P3D Vehicles sub menu sections. Fortunately, with the PMDG 737NGXu a/c, probably because the 737 systems don't draw as much juice, if I immediately reset the engine generators, power & systems are restored. I only have to reset yaw damper, autobrake and efb and then can continue taxi and complete my flight. I can't reset the engine gens to restore everything in the Quality Wings 787 and Captain Sim 757/767 aircraft. With those, it's flight over. Someone on the Avsim P3D forums suggested deleting my FSUIPC.ini and letting it regenerate after starting P3D. I did so and it seems to have worked, but only able to test once thus far. Can do another test flight tomorrow morning. Here is the before deletion FSUIPC.log from the previous flight in the PMDG 738NGXu that had the issue: https://www.mediafire.com/file/732t9bpnd8lnnvw/FSUIPC6.log/file Here is the rebuilt FSUIPC's log from my latest, successful test flight in the PMDG 738NGXu: https://www.mediafire.com/file/v6r34189y57iw34/FSUIPC_20231103.log/file Can someone with in-depth knowledge of FSUIPC log data translate what was happening in the older log? It definitely shows some issues, imho and perhaps one or more of those events caused the loss of power/generators to trip. The latest rebuilt FSUIPC.ini's log file from the latest test was very clean, so I'm assuming whatever hiccup that was encountered by FSUIPC in the past is now gone. Kindest regards, Glenn W. / beechcaptain
  11. I'm having a problem where I run Makerwys 4.82 in P3Dv4 root directory, but RC4 is not seeing the updated runways at FSDT KORD (eg 28/10). P3Dv4 sees the afcad and all the runways. I have latest version of Loorby's Addon Manager installed and it sees the two addon airports I've added so far (FSDT KORD & KDFW). However, the Rwys.txt file in the P3Dv4 root directory does not show the updated runways. Which file RC4 reads for the runway data, perhaps Rwys.txt? Any ideas on what I've done wrong, perhaps? Thanks, Glenn Wilkinson Edited for update: Please disregard, I thought I had v4.82 but instead discovered it was v4.80. Using v4.82 solved the problem. All is well!
  12. I have a green ATC window for Radar Contact 4 in P3Dv4 with FSUIPC5. I have searched but can't find any related topics anywhere. My question: is there any way FSUIPC can change the semi-transparent green window to transparent like it is in P3Dv3.4 and FSX? Not sure if it is a P3Dv4 issue. Thanks.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.