Jump to content
The simFlight Network Forums


  • Posts

  • Joined

  • Last visited

Everything posted by TextRich

  1. Thank you Roman. I'll look into adding that toggle to my controls and adding a reminder to my checklist for final approaches.
  2. Thank you both. I am using the same aircraft for both sims (a simple Virtualcol with different versions for FSX and P3D) but yes, I have heard of the PMDG complex saving issue. I also recall that P3D has an option to save the status of a panel along with the save file so I wonder if that makes the save a little more complicated than FSX's, which did not offer that option. Sometimes resuming an Autosaved flight in FSX with an add-on aircraft entails re-starting the engines if the sim crashed in cruising altitude. Pete, I see that the script is for FSUIPC 4 only. I am a little confused... is it to prevent autosaving during approaches? Or to enable autosaving during approaches only? Does FSUIPC 5+ already do that?
  3. Here's my reply from my AVSim forum Pete alluded to: I just read John's reply for the first time. Yes, I overlooked antivirus. In addition I use a SSD so it isn't an issue of fragmentation, etc. I agree with you that it may be a P3D issue that hopefully can be fixed by LM to make autosaving much more smooth. AutoSaving was never this slow in FSX and I just got P3D for the first time last weekend after I gave up on managing VAS LOL. You both are legends and thank you for supporting us simmers all those years.
  4. Greetings. I am a longtime FSX:SE and FSUIPC 4 user who last weekend made the switch to P3D 5.2 and a registered copy of FSUIPC 6.1.2. An issue I have noticed that was not apparent using the same setting in FSUPIC 4 and FSX:SE is that when FSUIPC 6 AutoSaves, my sim freezes for one second. This happens with no other add-ons enabled or running and with both third-party and default P3D aircraft. Is this a known issue? I do not get those stutters when I disable AutoSave. Please let me know if you would like more information.
  5. I just tried to access that link but got a message saying I did not have permission to view it. Is there a way to see this? I am interested in purchasing the v.2 E175 and 195 but am concerned if there would be a paint kit available direct from FeelThere. Or is this fan offering the only known one? https://fsbrasil.wordpress.com/2010/08/24/ejet-v2-paintkit/
  6. Nice trick, thank you. I was just experiencing the same issue. What I did was remove (not delete - move) the logbook file to my desktop, run FSX, say yes at the error message, and quit FSX after successful startup (and new, blank logbook). I replaced the new logbook file with the original logbook file. Hopefully that would qualify as a permanent workaround in the future as that bug popped up for me two months or so ago.
  7. You're a living legend, Pete. Thank you so much for doing this for the benefit of FSX:SE users.
  8. I personally don't need or use any of the features you have boldfaced, Pete. Thank you very much.
  9. Here is the list of fixes. A couple of them would be very worthwhile for me, at least. 🙂 Thank you for at least looking into this Pete!
  10. Microsoft has a new beta program for FSX:SE users that came out yesterday. It even fixes several FSX:SE bugs like real world weather. https://steamcommunity.com/gid/103582791436916733/announcements/detail/2549529393507642734 I can confirm that the beta FSX:SE crashes in free flight with FSUIPC installed. When FSUIPC4.DLL is removed from the Modules folder then the beta works. I am wondering if it is a conflict with the telemetry collection method that Microsoft is using with the beta. So either Microsoft will need to update the bug to make it compatible with FSUIPC or FSUIPC will need to be somehow updated. For now I have reverted to the non-beta version as I use FSUIPC extensively. Thank you for your time.
  • 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.