Jump to content

mousemansteven

Members
  • Content Count

    95
  • Joined

  • Last visited

Community Reputation

10 Good

About mousemansteven

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. morning all and pray all is well. i can load the default a320 neo or the a320nx fine at a parking stand. but if i attempt to load an exported flightplan from simbrief or pfpx the sim ctd's has anyone else have this problem or discovered a workaround. regards steve the old fart Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5f7c8cf2 Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5f7c8cf2 Exception code: 0xc0000005 Fault offset: 0x00000000004d65bf Faulting process id: 0x19e0 Faulting application start time: 0x01d6aac10d0
  2. afternoon. in mfs go to load save and see the location. that is what i did to get simbrief fp to mfs. cheers
  3. morning all. just a thought. put up a survey page for for aircraft to be first in the new mfs. my vote would be a330. cheers Steve
  4. afternoon Ron. I was getting ctd from active sky with this new update p3dv5 hotfix 2 . if i do not run active sky i can fly the a330 all day. so i believe the bus may not be at fault. cheers
  5. Morning all i am experiencing the same error in p3dv5 . the install is in a new machine where is that simconnect cfg file located? cheers steve i managed to find it i cut and pasted to my desktop attempted the same flight and it ctd while taxi out to runway. - System - Provider
  6. morning all. just built a new flight sim pc. new windows install current nvidia drivers and im still getting warp error and ctd after 2 hours into flight. Hardware -------- CPU Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz GPU NVIDIA GeForce RTX 2080 (1920 x 1080 x 4294967296 colors) GPU Driver 445.87 RAM 32GB @ 2133MHz Microsoft Windows ----------------- Windows 10 Post April 2020 (2004) Update 64-bit User Profile and Document Folders --------------------------------- User Profile Location: Environment.GetFolderPath = C:\Users\steve Volatile Environment\
    very good work i just wish he would go the next step and package the livery before posting so it would work in the new livery installerv2100
  7. afternoon all i think the new livery manager would be excellent if the re painters would just use the package option in the livery installer. the issue is not with aerosoft but the re painters that do not feel the necessity of packaging their repaints before posting. if you wish to see if the new livery manager works open it and find a manually installed livery and do the package option then remove the manual install and drag and drop the newly created package into the livery manager.. so you see until the wonderful re painters do this the only route to follow is the manual install. chee
  8. here is my info Hardware -------- CPU Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz GPU NVIDIA GeForce GTX 1080 (1920 x 1080 x 4294967296 colors) GPU Driver 445.75 RAM 32GB @ 2133MHz Microsoft Windows ----------------- Windows 10 1903 May 2019 Update 64-bit Microsoft .NET Framework 1.0 - 4.0 ---------------------------------- .NET Framework DF .NET Framework 2.0.50727 Service Pack 2 .NET Framework 3.0 Service Pack 2 .NET Framework 3.5 Service Pack 1 .NET Framework 4 .NET Framework 4.0 Microsoft .NET Framework 4.5+ ---------------------
  9. i have the default raas cheers Steve not fs2crew also this started with the last update i believe. thanks MK
  10. Morning all i have the same issue but on during the call for tray tables when on approach i have the default raas cheers Steve using the A330
  11. dear Mr Kok. I have to admit publicly that i am truly an old fart. I finally got the clue to getting this installer to work. i was just using the version 2000 alone and did not drop it in the aerosoft folder in documents. please forgive me for any thing i have said in the previous posts. trust that you and yours are safe and well. i must admit that your response to issues is very prolific. have a great day steve the old fart.
  12. morning all. yes you will get this message on new liveries. that is because the painter did not include the new required file "liveryinstaller.txt" that is required and the painters dont know or dont care to add it. those liveries can be installed manually. so the clever installer will work if the file is included. still trying to figure out why aerosoft did the upgrade. ive asked but could not get a response. warm regards to all and stay home and fly. steve Repainter Guide.pdf
  13. yes sir it is downright easy if the repainters would include the liveryinstaller.txt file in there paints. regards steve the old fart
×
×
  • Create New...