• Content count

  • Joined

  • Last visited

Community Reputation

21 Neutral

1 Follower

About Mace

  • Rank
    Member - 3,000+
  • Birthday 04/18/1973

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines

Profile Information

  • Gender

Recent Profile Visitors

2,568 profile views
  1. You could use a program like Process Lasso to do that to some extent.
  2. PMDG 777-200LR for Prepar3D v4.2

    heh. Nice topic. I'd definitely be in for the MD-11 for P3Dv4. :)
  3. Use a program like ADE to exclude the stock ILS scenery objects.
  4. GTX 1080 TI = Blurries

    Wow. The cryptocurrency miners (?) have really messed us over. I guess I'm lucky I got in at $850 for the watercooled eVGA 1080Ti in early December.
  5. Realair Duke v2 Piston in P3D v4

    I ran into the same problem with the CLS DC-10 HD. The Turbine Duke method doesn't work for me on that aircraft. I installed the 64-bit sound gauge, edited the ini files with explicit paths to the .wav files, etc. etc. -- and no go. My latest theory is that the xml gauges on some aircraft need to be modified also. Does the piston Duke have xml gauges? With the DC-10, I have been playing around with the xml gauges, and managed to modify the simplest of them (SEAT BELT gauge - on or off) and have successfully gotten it to activate its click sound. However, in doing so I somehow broke the animation part of the gauge....still working on that.... Maybe you're seeing a similar thing with the piston Duke?
  6. Too Dark at Night

    Except that a 1080Ti has 11 GB :) unless I'm really missing something.
  7. No, I know what you mean. Are there any current add-ons that help with the shimmer and coloration?
  8. P3D 4.1 CTD near Labrador

    I have FSDT KMEM, which has couatl, and I didn't get the crash. i ran right over HOIST, too. My sim's navdata is the ancient '06 era navdata P3D comes with. What do you guys mean, "With couatl open"? I have KMEM installed, does that qualify as having couatl "open"? Or is there some other step I should take to have it "open"?
  9. P3D 4.1 CTD near Labrador

    Hmm interesting. You know, I have couatl and never had a CTD though. At least I think I have it -- I have installed FSDreamTeam's KMEM, which I believe installs couatl Another thing I thought of -- was the possibility that it could be the navdata being used. ?? I am using whatever P3Dv4.1 came with, that probably being the same old 2006-era navdata from FSX days. I wonder if the CTD people are using some newer navdata? The HOIST waypoint, cited by the OP as a crash area, is not in the default P3D least as far as I can tell.
  10. P3D 4.1 CTD near Labrador

    No, I don't think so. Windows has virtual memory. Not sure, but modern versions of Windows may still have a swap file as per the old days. Anyway, if 8 gb were the problem, we'd have a lot of people crashing in mem-intensive areas like Tokyo or London, I would think...
  11. P3D 4.1 CTD near Labrador

    I am running Orbx OpenLC NA and Orbx Vector and did not get the crash. Of course, that's only one data point. And I've only run the OP's flight plan one time.
  12. P3D 4.1 CTD near Labrador

    Completed the flight. No crash. Mem usage did pass 10 gb near IAD. Around the CTD area (HOIST) mem usage was at about 8 GB. Surely there is something in common with the crashers vs. non-crashers.
  13. P3D 4.1 CTD near Labrador

    Ok -- so I'm doing this FRA - IAD flight right now using the OP's flight plan and the PMDG 777 with UTLive and ASP4 + ASCA going. I do use a PTA also. The OP said his crash was before HOIST waypoint -- well, I've already passed HOIST and no problems. I dropped the sim down to 1x time compression about 150 nm before HOIST, and ran at 1x all the way inland to Goose Bay (that's where I am now). The entire time I've been monitoring a couple of things...system memory, via Task Manager, has remained fairly steady at around 9 GB. (People who have had the CTD -- do they all have 8 gb of system memory?) Monitoring vid card memory usage, too -- been pretty steady at around 3 GB - 3.3 GB. I haven't seen any mem use spiking, or anything else that would make me worry about the stability of the sim. Passing over YYR / Goose Bay right now. I may have a rough ride into IAD -- a big storm is exiting to the northeast -- turb is reported north and west of IAD. At least the snow will be to my east.
  14. P3D 4.1 CTD near Labrador

    You may be on to something. My new machine has 32 gb of mem, and I haven't gotten the CTD. My old machine had 8 gb but I only ran FSX. I will monitor mem usage if and when I can do that flight. One of you will probably beat me to it, I'll be working a lot this week.
  15. P3D 4.1 CTD near Labrador

    I run UTLive. I may have forgotten to list it. Anyway, I've never had a crash near Labrador, or anywhere else. I'm just going to replicate the OP's flight plan with the 777 soon. I have never heard of injection-style AI (UTLive style) crashing the sim. But I used to compile my own traffic bgl's, and as i recall (it's been about 10 years), if you had a bad AI flight plan, it would indeed crash the sim.