Jump to content

cakeisawesome04

members
  • Content Count

    18
  • Joined

  • Last visited

About cakeisawesome04

  • Rank
    Flight Student - Groundwork

Recent Profile Visitors

187 profile views
  1. i realized that the stars restrictions ended up eventually correcting themselves and descending a whole lot faster
  2. Now i am not sure if this is a bug, but whenever I go to check my arrival in the FMC the descent line is not properly placed. For Example...i will be cruising at FL 370 and there will be a restriction at a waypoint for FL 270...The descent line will be after that restriction, so there is no possible way I could meet the restriction. Here is an example of what I mean.... I try to correct it manually with my own restrictions but the fmc will say "not allowed" and then i will never descend fast enough and be super high by the time i'm on final.
  3. Ok...im assuming my issue is no longer existent after using the driver recommended by @frederic29. Thank you so so much my friend
  4. Hey All! I went to the recommended driver version and flew for two hours with no issues! Definitely a driver issue. I am going to keep testing and keep you all updated. Thanks!
  5. I checked and do not use nvidia inspector. I will do a clean ddu sriver install of the version recommended and see if that helps. I will report back if the issue persists
  6. I have read around and apparently reducing gpu clock speeds (Mine has a factory boost clock) can help fix the problem...I will do that and then return back for more help EDIT: Doing so did not stop the problem...anyone have any suggestions?
  7. @Mathijs KokHave you guys experienced this error in your testing. If so, are you able to replicate it under certain conditions?
  8. Hello! I am not expecting much support because this product is so new but i am getting this dreaded error about an hour into every flight i do with the new bus... dxgi_error_device_hung. (I have attached an image). Windows log keeps no log of this crash because i guess you acknowledge the sim will crash. I have searched and see that this issue has happened to many, and LM just suggests the normal trouble shooting. I have already used DDU and uninstalled and reinstalled the latest drivers. If anyone has a stable driver version that fixes that this would be great. My specs are... I5 7600K @3.8 Zotac GTX 1060 6gb default clock speed Windows 10 64bit 8gb ddr4 3200mhz ram and an Asrock z270 extreme 4 mobo I would love to fly your new product...but this error makes it impossible
  9. Hello All! Is there any update on the release of the aerosoft airbus family for p3d v4? I see that one topic on it...but it seems quiet. has not been posted on for a while.
  10. ok! I will keep you updated if the crash happens again
  11. its all in different times this time i was descending into atlanta
  12. This is the second time this crash had occurred. I updated my aerosoft airbus a320 family to the newest version and i keep getting this crash in fsx se. Please help Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a Faulting module name: fmgs.dll, version: 1.2.7.82, time stamp: 0x552db3f3 Exception code: 0xc0000005 Fault offset: 0x00036b03 Faulting process id: 0x1464 Faulting application start time: 0x01d3d4d5b5afeba4 Faulting application path: D:\SteamLibrary\steamapps\common\FSX\fsx.exe Faulting module path: D:\SteamLibrary\steamapps\common\FSX\SimObjects\Airplanes\Aerosoft Airbus A320_A321 Base\Panel_Fallback\DLLs\fmgs.dll Report Id: ea38e78f-2f4d-4036-bd67-3a0e948a079b Faulting package full name: Faulting package-relative application ID:
×
×
  • Create New...