Jump to content


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

79 Good

About mmcmah

  • Rank

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines

Recent Profile Visitors

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

  1. I've seen this occur, also largely with small aircraft. Nico has previously mentioned the QNH as being a source for potentially having the wrong altitude. Surely that wouldn't impact the altitude for such a long way. I believe the issue is with the data stream from the aircraft and that PSXT/RT must not be getting a steady stream and interpolating a straight line movement until it receives the next data point. How much of a delay do you have programmed in the interface? Longer delays allow for better interpolation, if I recall correctly.
  2. Very kind of you. No, I'm not actively running it, so please feel free. Thank you.
  3. I ran Learner for a few hours on the airport to give whoever wants it as a base with which to open the airport: This is one consistenly busy airport! Landing pattern
  4. Here is a similar shot at EKCH with DLSS with DLAA at 1.78x DL upsampling with NCP: DLSS-DLAA With Upsampling DLSS-DLAA Without Upsampling For this scene there is very little difference between upsampling and no upsampling because most of the scene is fairly close and uniform. I find that upsampling makes a big difference where there are things shown that are farther away and where fine details can be seen with things with different colors and shapes.
  5. I tried DLSS-DLAA with the native NVIDIA upscaling and it looked better than TAA (and easier on the frames). I then tried the same without upscaling and it looked about the same as DLSS Quality with native upscaling (which is better than DLSS Quality without upscaling). With TAA I get shimmering in DX12. I tried going back to DX11, but the frames and stutters were too bad. I think DLSS-DLAA with 1.78x DL scaling through the NCP will be a good option to try. I didn't try it with a glass panel plane, but I will try it with the Fenix when I get the chance.
  6. You are absolutely correct that DLAA is better than DLSS! Thank you!! One question - with DLSS, I was using the NVIDIA control panel to upsample the image. Do I no longer need that with DLAA (using 1.78x DL scaling on the DSR Factors option with a native 4k resolution)?
  7. My experience is the same with a 4090. I have it locked at 60fps even though it's a 144Hz sxreen and it's super smooth. Even the iniBuilds sceneries with heavy PSXT/RT traffic maintain the 60fps. I find that turning the options on/off on the airports only make a handful of fps differences. @Sethos what's the benefit of DLAA?
  8. Thanks for the explanation of what to expect, Nico.
  9. Yes, we'll have to wait and see what V10 brings. EGLC does seem to be particularly bad with it's traffic movements.
  10. Frame generation only works with DX12. It works with either DLSS or TAA. My experience in terms of smoothness is much better in DX12 than DX11. I do have some visual artifacts now and then, which caused me to try DX11 again, but I was getting lots of stuttering, much worse frames and it just wasn't smooth. Went back to DX12 and I'm happy again.
  11. You are correct @neilhewitt, the same happens with the Orbx version as well. I have seen it all as well and have attributed it to the lack of good transponder data there. I HOPE, the new V10 of RT that Blathasar has mentioned (due out soon? -ish??) will improve things as it uses GPS for many aircraft that have the capability and apparently provides 99%+ coverage around the world when given 24+ hours of offset. Here's his blurb about it: "Our ADS-B data is now aggregated from 5 different providers, each with their own terrestrial networks. The soon to be released RealTraffic version 10 will also include satellite derived positions in the system (the yellow positions in the plot above). Due to the latency involved with satellite position reporting however, these positions are generally only visible when flying with a time offset of at least 20 minutes. An offset of 2h recovers 90% of all satellite derived traffic, and with a one day offset, you're getting 99.5% of all traffic in the air, even in some of the most remote corners of the planet! That's pretty nifty, and a good reason to go for a pro subscription!" Of course, we still don't have historical weather in the sim, but hopefully this will make traffic movements on the ground much better.
  12. Here are the contents of my EGLC.xml file after leaving it running for a few hours today. Hopefully it works as a good starting point for whomever wants:
  13. When I want traffic, I only use PSXT and RT. I use historical mode because I too like to time shift very often. Since Nico and Balthasar introduced the feature to allow the simulator to control the time, it's been so easy to change the time that the traffic is shown! Also, I saw Balthasar mention that v10 of RT will be even better with GPS tracking, but also that a 24+ hour offset will make 99%+ of traffic appear most anywhere in the world.
  14. Nico, restoring the file into the airports_archive folder caused the problem to reappear of the wrong parking positions and facing the wrong way. It also caused my new EGLC v2 updated file to be moved to EGLC0.xml and be replaced with the archive EGLC.xml, which is wrong for this version of the airport. I will re-delete the archive EGLC file and have it function correctly. @neilhewitt I think the problem lies with the archive file and the fact that the program is automatically loading it when it doesn't find one already installed (or it finds one with a lower rating than what it has). Unfortunately, that file has the wrong parking positions. I am including below the original archive file and below it the one that I had created yesterday after moving EGLC.xml out of the airports_archive folder so that you can see that the parking positions are different. Archive file: EGLC v2 file:
  15. Hi Nico, I got the new Orbx EGLV v2 and leaded into it with PSXT. I first deleted by updated airports file for it and then I scanned for Airports. When I loaded into the airport and ran PSXT, it loaded the one from the airports archive. Then I deleted the airports archive file and re-ran PSXT and it thought I was using the stock EGLC airport. It was only when I deleted the EGLC from the stock airports folder and rescanned that it started with an empty file and new parking positions (v1 had the parking positions facing the terminal and v2 has them - correctly - facing out). Did I follow the correct procedure? Thank you.
  • Create New...