Jump to content
The simFlight Network Forums

Flightoff27

Members
  • Posts

    17
  • Joined

  • Last visited

Everything posted by Flightoff27

  1. Well, in this case I will make more flights in next few days. I will then send you logs via e-mail (this time in archives). Thank you for your answer. With best regards, Alex.
  2. Small addition - list of all addons I used in last flight: (FSX with Acceleration Pack) 1) Aerosoft Airbus Extended 2) SimPhysics X 3) FS Real TIme 4) AI Smooth 5) ORBX - both FTX Global and Vectors 6) FS Acars 7) Ultimate Traffic 2
  3. Hello again Pete. Well, I made a flight and this time I had different error. Now problem is g3d.dll. Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: g3d.dll, version: 10.0.61637.0, time stamp: 0x46fadb58 Exception code: 0xc0000005 Fault offset: 0x000122fa Faulting process id: 0x%9 Faulting application start time: 0x%10 Faulting application path: %11 Faulting module path: %12 Report Id: %13 FSUIPC log is too big, so, I uploaded it. Please check following link (log file is 64MB). https://mega.co.nz/#!lhdFgCzb!Yq5fDxXl1GknFrBT9EfCAB5kZxoLwRnpKUViA-hsu7k One more thing - please notice that I continued to use sim for 14 minutes after error window appeared (I'm using pseudo fullscreen, so, it was possible for me). If you need anything else, please inform me. With best regards, Alex.
  4. Ok, I understood. I will try to make a flight with 4.927f and following FSUIPC.ini (please check in attached) today in evening. I will upload log after it. You can tell me if you think that I need to add or remove anything from .ini for test. With best regards, Alex. FSUIPC4.rar
  5. Actually, I added Wilco Airbuses (for some tests) and I also started to use AI Smooth. CTD occurred on first flight with A330 from Wilco. With AI Smooth I was able to complete 1 flight only (with 737NGX, on second flight I had CTD with Wilco A330), so it's hard to say if AI Smooth can be a problem. Actually, before I always turned off this option (Hide extensions of known file types)... I forgot to do it this time. Thank you for advice!
  6. One more thing - can you please tell which log do you need? Is it FSUIPC text document in Modules folder?
  7. Hello Pete, thank you very much for your answer. I will download 4.927f and will try it. Also, I added 2 lines to FSUIPC.ini file. I will try to make a flight today in evening and will write about results after it. One more thing (not sure if it has to do anything with our problem, but anyway): my friend is using FSUIPC 4.927a and ASN with latest hotfix and he never had CTDs. We decided to compare fsx.cfg and dll.xml. And we noticed one interesting thing - following lines somehow disappeared from my dll.xml: <Launch.Addon> <Name>as_connect</Name> <Disabled>False</Disabled> <Path>as_srv\as_btstrp.dll</Path> </Launch.Addon> I checked backups of dll.xml and I'm sure it was there. But, as I said, I'm not sure that it can be part of our problem. However, I never had any CTDs before yesterday and was able to complete a lot of flights with ASN and 4.927a. Anyway, will write later. Thank you for your help, Pete. With best regards, Alex.
  8. I forgot to add that I'm using FSUIPC 4.927a and ASN with latest Hotifx installed. Today I installed 4.927b and will check it later. With best regards, Alex. P.S. thank you for your message, Paul. It's nice to see that I'm not only one who has this problem.
  9. Hello! Today I had FSX CTD during my flight. Log said that faulting module is FSUIPC. Can you please check logs and tell me any suggestions? Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: fsx.exe P2: 10.0.61637.0 P3: 46fadb14 P4: FSUIPC4.dll P5: 4.9.2.7 P6: 52b0eeeb P7: c0000005 P8: 00013691 P9: P10: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: FSUIPC4.dll, version: 4.9.2.7, time stamp: 0x52b0eeeb Exception code: 0xc0000005 Fault offset: 0x00013691 Faulting process id: 0x%9 Faulting application start time: 0x%10 Faulting application path: %11 Faulting module path: %12 Report Id: %13 With best regards, Alex.
×
×
  • 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.