Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

zap737

Members
  • Joined

  • Last visited

Everything posted by zap737

  1. This may be a silly question, but if a part of the load is being taken by the GPU in P3D, then will this platform significantly benefit from GPUs in SLI? (Or Tri SLI, or Quad SLI?). From my understanding FSX didn't benefit from SLI, but perhaps P3D will.
  2. Danieln, The DME readout is irrelevant to the issue. Have you selected "Fail Operational" in the equipment options? I have hotfix 3 installed and no problems Pete
  3. Danieln, I have tried an autoland at YMML RWY 16 with no problems. Have you selected "Fail Operational" in the equipment options? Do you have both autopilots engaged? Pete
  4. First of all, thanks to ******* for his awesome work on this problem.*******, you said you were working on the black screen problem, but I wonder if the problem I have is related to that as well.The problem I have is with a white/cream window that appears when switching from full screen to windowed mode after about 15-20 Alt-Enters (NOT Alt-Tab).The sound keeps going and the simulation keeps going, but the window/full screen is cream/white.On rare occasions you can recover but most times you cannot.This happens in windows XP SP2 x64 with Nvidia 8800 GTS.Is this related to the black screen or is it something different?Tim (tfm) do you think this cream window problem is a fan speed issue?Pete
  5. OK,If this is an OS memory management issue, then how do we go about requesting Microsoft fixes the issue?Would it be better that the developers (PMDG, Aerosoft etc) approach Microsoft on the users behalf?Pete
  6. Tim,I don't use the [bUFFERPOOLS] entry in my .cfg file.Do I need to put it in?Also, is it UsePools=0 or Poolsize=0 ??I am gobsmacked that we seem to be making headway. Thanks to all who have tried so hard.Thanks,Pete
  7. I do not have UT II and I still had the problem. I do have lots of WOAI traffic though.Pete
  8. **** Update on Cream Screen of Death ******Hi All,Just a quick recap........I have a dual boot system with Windows XP x64 (SP2) & VISTA x64 Home premium (SP2). I have FSX installed on both systems. Full system specs below.With XP 64 and using the PMDG MD-11, I get a cream/white coloured window after I use ALT-enter a few times (sometimes 3 times, sometimes 10 or so times).The sound keeps going & there isn't any texture corruption on the aircraft or scenery with this event. Sometimes you can recover, but most times you cannot recover the visuals.And now.......I have done a complete re-install of XP x64 (with SP2 included on the install disk) and set up FSX and the XP OS exactly as per NickN's procedure but the problem persists.The ONLY add-ons are the PMDG 747 & the PMDG MD-11.Does anyone have a fix for the cream/white coloured window problem??????Pete
  9. Bryan,Can you post the exact link of this file....."XP64 pro Service pack 2 for IT developer's" I cannot find any XP x64 SP2 file of 517 mb - the only one I could find was 350 mb.Pete
  10. Update:I have reinstalled FSInn with latest versions.I have .Net framework 3.5 SP1 installed.Light bloom is off.I have deleted the fsx.cfg file and let it build a new one, updated sound drivers, run registry repair tool, installed latest FSUIPC.I have returned the bios to stock standard - no overclock.I still get the CSOD although it takes more Alt-Enters to get it and it is more, though not always, recoverable.Pete
  11. Gary thanks for the reply.I am pretty sure I had SP2 on XP 64 as the contents of the disk have a file which refers to SP2 in its name.The rest of the list I will go through in time and report back.The obvious problem with all this "stabbing in the dark" is that if I could get it working, I would be at a loss to recreate it if I had to do a fresh install of XP64 & FSX.Thanks,Pete
  12. Gary,Re CSOD problem......I noticed that my version (FSX Acceleration) is 10.0.61637.0 .Yours is 10.0.61472.Could this be a factor in the CSOD problem??I have also uninstalled and re-installed the 182.50 drivers using Driver sweeper and nHancer as per NickN - same problem.I have also uninstalled and re-installed the latest drivers using Driver sweeper and nHancer as per NickN - same problem.I also get the problem with or without FSInn running.If I just stay in full screen mode (or windowed mode) at all times the problem doesn't arise, but it is unrealistic never to get out of full screen mode during a long flight.Also windowed mode has problems with the jaggies - full screen is by far the best.Perhaps it is time for a change to the latest ATI cards.Has anyone with ATI cards on XP64 experienced the CSOD??Pete
  13. Update:Tried all the above and sfc/scannow and disabled physics.Still get CSOD.Pete
  14. I have only had this problem with the MD-11, not the 747.Anyone else found this?Pete
  15. Thanks Rich,Some good detective work there.Unfortunately I don't have that scenery to remove, so I wouldn't know where to start.I already have nHancer set up as per NickN.Pete
  16. Rich,Which addon scenery file/s did you remove??How did you confirm the addon scenery file was causing the TCAS.dll problem?Pete
  17. Hi All,On short finals with MD-11 at KJFK had a fatal error problem with TCAS2V7.DLL.The event viewer log showed:Faulting application fsx.exeversion 10.0.61637.0,time stamp 0x46fadb14,faulting module TCAS2v7.dll,version 1.1.6.0time stamp 0x428913d5exception code 0xc0000005fault offset 0x00005bfd,process id 0xffc, application start time 0x01cab0fe38f0716e.System as in sig below with Vista x64.I have tried the PMDG Ops wiki http://ops.precisionmanuals.com/wiki/PMDG_...ing_TCAS2V7.dll and I have the correct dll version.Any ideas on this one?Pete
  18. Gary and all,Tried the re-install of the video drivers using driver sweeper to remove them and then installed 182.50 as per Nick N's process and set up nHancer.Still getting the CSOD in XP 64.Gary, do you use "heavies" such as PMDG 747/MD11?Also, is your system overclocked (mine is)?Pete
  19. Gary,Thanks for the reply.I have XP x64 with SP2 on my system but I can't remember if I got to SP2 through Windows update or off the disk.Is there any way of telling from the disk contents?I am indeed running an Nvidia 8800 GTS with the good old 182.50 drivers but I have not tried a reinstall of the video drivers.I will give that a try.Thanks,Pete
  20. Scott,I have XP 64 SP2 as you do but, as I have posted before, I get the cream screen of death (CSOD) after I alt-enter a few times.Sometimes I can recover, other times I cannot.Can you please post your full system specs - eg motherboard brand and sound setup (onboard or dedicated sound card) and video card driver version?Also, did your XP 64 version come with service pack 2 on the disk or did you get SP2 via microsoft update?thanks,Pete
  21. I wish it were so simple......With XP 64 I get a cream/white coloured window after I use ALT enter a few times (about 10 or so times).The sound keeps going - but you cannot recover the visuals. There doesn't seem to be any texture corruption on the aircraft or scenery with this event.Does anyone have a fix for the cream/white coloured window problem??????If I can fix this problem then I would gladly stay with XP 64.Pete
  22. Dan,See my post above re XP with FSX:http://forums1.avsim.net/index.php?s=&...t&p=1676622With XP you get the same problem but the variation is that it is a white screen instead of the black screen.For the record, the rig I use is an overclocked Q6600 to 3.2 GHz. I have not adjusted the memory timings as wrbrd has suggested however.The more I think about this it seems to be an FSX resource allocation issue.Unfortunately the ACES team is no longer so we may never see a proper fix for this issue.I fervently hope I am wrong.Regards,Pete
  23. Hi Sean,Just a question, how did you remove the Soundmax card? I thought the Soundmax was on board sound and as such couldn't be physicaly removed.Pete

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.