Jump to content


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

75 Good

About Truthan

  • Rank
  • Birthday 12/12/1956

Contact Methods

  • Website URL
  • ICQ

Profile Information

  • Gender
  • Location
    Garberville, CA

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines

Recent Profile Visitors

2,240 profile views
  1. There's been some discussion on the FlightFX Discord about the XXX's appearing for some users. It seems to have been traced to the PMS50 mods somehow hooking into the custom built PFD for the HondaJet, but I'm not sure if it was the GNS530 or the GTN750 mod. Try removing them from your community folder and reboot the sim and see if that fixes the all XXX's for you.
  2. If your talking about changing the line "isAirTraffic=0" to "isAirTraffic=1" in each of your desired AI livery "aircraft.cfg" file, this can easily be accomplished using Notepad++, the indispensable "go to" advanced text editor for most techies for years. It can quickly find and replace a single word, phrase, or line of code in multiple files (even thousands) in just a few seconds. And it's totally FREE. You can download it here: https://notepad-plus-plus.org/downloads/ Just Install Notepad++, then just temporarily move all the livery folders you want to use for AI into a single folder for bulk processing. I used "C:\Liveries-For-AI" in the image example below. Then start Notepad++ and choose the Search>Find in Files tab, and set your fields as shown in the image below, (with the Directory: field pointing to wherever you temporarily moved the livery folders). Make sure that "In all sub-folders" is checked, and then hit the "Replace in Files" button. It'll process hundreds in just a matter of seconds. Then move the livery folders back into the MSFS Community folder and your good to go. Done!
  3. Those DLL’s appear to be those that are routinely associated with MS Visual Basic & the ubiquitous MS .NET framework, so essentially are systems files often associated with many MS programs. If you check their properties dialogue boxes most if not all will contain MS digital security signatures. In fact, if you do a search across your C drive for any of those file names you’ll typically find multiples of them in other programs, games, and system files on your computer, sometimes a few dozen of a given file actually. For me, nothing in the app folder was flagged by Windows Defender and a Malwarebytes scan of the these files turns up absolutely nothing. Personally speaking, I don't sense, nor have seen, any adverse effects or issues with using this app.
  4. Just a quick heads up for anyone who hasn’t got wind of this dandy little tool yet... "Flight Recorder" was released on Feb. 17th with a minor update just today. With an interface as simple and clean as its unassuming name - it records live flight data and replays your flight from start to finish in both 2D AND IN VR - with flawless perfection on my Oculus Rift S. Haven't tried it in my Reverb G2 yet so I can't attest to it working there, but based on how I believe it records and replays data I don't think it'd be an issue. Mind you, the UI control panel DOES NOT appear in VR however, but I don’t mind a bit tilting my Headset up for a few seconds if I need to access a button. Just being able to REPLAY an entire flight - in VR and rewind or fast forward to anywhere in the flight is worth that minor (and maybe temporary?) caveat. You can grab it for free here: https://flightsim.to/file/8163/flight-recorder The author’s GitHub page is here: https://github.com/nguyenquyhy/Flight-Recorder/releases And check out this quick hands-on look (and install tips) from Flying Theston on YouTube here: https://www.youtube.com/watch?v=OUHlePjNxk8 During a replay you can: - Change cameras and freely control them. - Change time and weather. - Stop the replay at any point in the flight and resume live aircraft control. - Pause and resume replay at any point to setup screenshots. - Scrub backwards or forwards during replay. - Save to a “.flightrecorder” file and replay entire flight at any time in the future. - Export all raw data to a .CSV file. It doesn’t feature an export to MP4 or other video format, but I presume one can use other apps for recording a replay (with their own custom camera work to boot). It operates from completely outside the sim and there's virtually no install, just unzip the file and boot the exe once a flight is loaded and engines are running. I’ve only taken a few test flights thus far, but it worked right out of the box without a hitch and with ZERO noticeable hit on performance during recording so far as I can detect on my RTX3090 / I9-10900KF setup. And the replays are – refreshingly - smooth as butter. Lastly, make sure and READ ALL the author's notes to save yourself a few minor headaches. It's all pretty basic, but especially read the "Current Limitations and Other Notes" section. A big hat’s off to the author Nguyen Quy Hy for this enjoyable slice of Techno-Zen. Nice work my man. Thank you!
  5. Not sure if this will help, but another Reverb G2 user with an AMD setup in this thread at Tom's Hardware said he also had crashes with a "Driver Timeout" and said he solved the problem by disabling XMP (Extreme Memory Profiles) in the BIOS. XMP is what boosts your RAM speed to above it's default speed. You might want to try that. So far as getting the G2 to "act nice" without stutters, I've been in the same pickle, and it's puzzling and frustrating to be sure. I have an I9-10900KF processor with a 24GB RTX3090 and 64GB of 3400mhz RAM and I still cannot get the Reverb G2 to render acceptably smooth performance without stutters and judders when turning my head or the aircraft, or looking straight down out the side window. And even after numbing down OpenXR and/or in-game render scaling and settings to get to even a "tolerable" performance, with those lowered settings it gets to point of diminishing returns. Because by then, I can actually get equal if not better visible resolution and gauge clarity along with butter smooth performance to boot with my good old RIFT S which allows me to crank MSFS settings to the max at Ultra & High, and even pump up to 120 render scaling in rural areas. The only difference is the slight screen door effect which, considering the overall clarity and performance, I can certainly live with. I'm gonna keep trying to get the G2 to "act nice", and if a magic bullet is found, will certainly share it. So far as an FPS monitor, I've been turning on the MSFS developer options and engaging the FPS screen. It's a bit wonky because it's only in one eye, but while testing the G2 I can lift my head slightly out of the headset and check it.
  6. I had the same issue... The G2 would go dark and all I could see was a volume icon. Solved the problem by changing the USB port (i.e. the usb-c cable, using either a direct to usb-c port or with the usb-c to usb-a converter that comes with the G2).
  7. And one last note Republic3D... since you have an R9 5900x processor, and thus may possibly have the an X570 mother board, the Reverb G2 has been widely reported as having issues with AMD boards. A Google search for "Reverb G2" along with "AMD" and/or "X570" will bring up a host of recent issues from many other users. Thus going with a Rift S may likely save you a ton of headaches.
  8. I have the Reverb G2 and Rift S, but I'm staying with my Rift S for now in MSFS. Here's why... I too have an RTX3090 but with an I9-10900KF processor and 64GB of 3400 RAM, so our rigs are similar in their "beef" as it were. However, over the last several days since the MSFS VR release happened, getting my Reverb G2 to consistently deliver smoothness in the sim has been a struggle to say the least. I've tried every technique and tweak out there but the results are totally inconsistent. The clarity is truly awesome, and the screen door effect is essential non-existent, but different weather, scenery density, or just changing my view direction frequently throws it into a stuttering mess time and again. The WMR / OpenXR reprojection algorithms frequently refuse to lock the frames into a consistent divisive of the G2's 90hz refresh rate (i.e. 45hz, 30hz, 22.5hz, etc.) It's really frustrating. It'll be smooth one minute and stuttering again the next. My trusty old Oculus Rift S on the other hand is a totally different story. It requires so much less from the sim or my system that I can overcome the lower resolution by cranking up the MSFS VR graphics settings to ULTRA / HIGH and Super Sampling to 1.5 or higher, and with Oculus' proprietary ASW reprojection locking down on a solid frame rate it remains buttery smooth almost all the time. What's more, if if I fly into denser scenery areas or heavier weather, it adjusts the ASW divisive values of the Rift S native 80hz on the fly (with amazing precision) to either 40, 27.5, or even 20, and sometimes at values in between them - but remarkably, it remains smooth in the sim, with little to no stuttering - and pretty much all the time. I'll continue to try and find ways to get the Reverb G2 to "act nice" with MSFS, but in the meantime... With the RIFT S I can crank the MSFS VR graphics settings to ULTRA, set super sampling at 1.5, and then (aside from the unavoidable - but still slight - screen door effect) actually enjoy as good if not slightly better visually immersive results than I have with a "settings turned way down" Reverb G2 in order to get it to run smoothly. I don't worry about tweaking or monitoring FPS... I just fly. Bottom line for me thus far: A "settings all maxed out" Rift S currently beats a "settings all hobbled down" Reverb G2 for performance, reliability, good visual immersion, and consistently hassle free flying.
  9. My temporary FPS fix was to remove the PBR & Normal textures for now. Lowered VRAM slightly, and doesn't effect the overall experience for me, especially at night. Got the extra 8-10 FPS needed to raise things above a slide show. I posted the steps to do so in separate topic for better visibility for users looking for a quick fix:
  10. FlyTampa's Las Vegas is spectacular, but depending on one's system and graphic settings, the FPS can be less than optimal. I was able to gain substantial performance while retaining both the city and airport by removing all the PBR Maps (reflections) and Normal Maps (bump mapping) as well as their associated .json files from the respective city and airport folders. Reflections and bump mapping are gone of course, but the scenery boots without errors, and all the buildings, night lighting, animated signs, and Bellagio fountains are essentially unaffected. FlyTampa has indicated a fix for FPS will forthcoming this week, but it's effectiveness has yet to be tested. So in the meantime, if you're having FPS issues you may want try this. For the record, my current (relatively modest by 2021 standards) rig is: Razer Blade Pro 2017 4k Laptop, i7-7820 HK processor, GTX1080 8GB, 32GB ram, porting via HDMI to Alienware AW3420DW 3440x1440 monitor. (I'll have an Alienware R11 with i9-10900kf and an RTX3090 arriving this week though and it'll be interesting to see the difference, but that's for another post). Before the following fix everything at night (airport and city) was 12-13 FPS slide show, period. Day time was a bit better but not by much. I am now able to fly the strip at night and at and over the airport at a consistent 20-24 FPS, sometimes much more, with dips to 18-19 FPS only near the Bellagio fountains area. For the record both were tested with FlyTampa's expanded night lighting addition active, and at 3440x1440 resolution with MSFS settings on the HIGH preset. Naturally, lowering your graphics settings or screen resolution will result in a relative improvement with or without the fix below. Here's what I did: --------------------------- 1. For good measure, back-up your "flytampa-lasvegas-airport" & "flytampa-lasvegas-city" folders from the Community Folder to a secure location outside the sim. As you've backed up the default files, we'll DELETE rather than BACK-UP redundant files in the steps below for expediency. Steps 2 thru 4 should repeated for both the city and airport folders. We'll start with the airport folder... 2. In your Community folder, navigate to your "flytampa-lasvegas-airport > scenery > global > scenery > TEXTURE" folder. 3. Do a folder search for "_M.PNG.DDS" (without the quotes of course). 106 files should be found with those characters ending their filename. These are the PBR (reflections) files. Delete them all. 4. In the same TEXTURE folder, do a search for "_N.PNG.DDS". 54 files should be found. These are the Normal (bump map) files. Delete them all. 5. Repeat steps 2 - 4 in the city texture folder ("flytampa-lasvegas-city > scenery > global > scenery > TEXTURE"). For the city folder there are 160 "_M.PNG.DDS" files and 166 "_N.PNG.DDS" files. 6. Boot MSFS and see if your FPS have improved. ---------------------------- All together, the total removed files equal almost 1.5GB and I noticed a relative reduction in VRAM usage by removing them too. As stated, you'll lose bump mapping and reflections in both the city and airport, but for me at least - compared to flying in a slide show - it doesn't vastly detract from the overall immersion that everything else brings to the table. We'll see what patches or improvements FlyTampa brings to the table (perhaps a "Configurator" as in previous releases), but until then, this gave me the 8-10 plus FPS I needed to fly "relatively" smoothly throughout this spectacular scenery.
  11. I use GreenShot to capture screens on the fly. It's free and works great. It sits in the tray ready to use anytime. Just hit "CTRl+Shift+C" and mini window pops up that lets you take the whole screen or a crop of it. Set your output folder to your desktop (or any preferred location) and you can take as many screens as you want as you fly and they're sent directly to that location.
  12. Moonlit nights are a such a soothing and immersive pleasure to fly thanks to MSFS's gorgeously lit night time clouds. Here's Carenado's Mooney Ovation M20R headed into a full moon dusk at 16k above western Colorado. I could easily overshoot my destination and run out of fuel just enjoying that intoxicating view...
  13. FYI to anyone following this thread, Carenado has released a patch for the M20R (and the C182) that fixes the Zig-Zag NAV and APR issue. If you purchased through the MSFS Marketplace, go to your Content Manager, search for "Carenado" and download the update. She holds rock solid on course now. This Post has more user comments about it.
  14. Patch installed... Just had a rock-solid ILS approach into KACV descending into LIVE weather injection of some thick coastal fog on the way down. She captured the course and glide slope perfectly with no zig-zagging. Couldn't see a thing in that thick fog until a few looming treetops confirmed my AGL. And there's the threshold... and yesiree ... she's right on the center line! Am stoked the APR and NAV zig-zagging issue is fixed. Can reliably fly this nice bird now. Much THX to Carenado devs for such a quick patch.
  15. To be sure, no, I don't own it, but by no means mean to criticize the work REX has done, or the unique accuracy that it offers - for a given Metar station anyway. I've chosen not to foot the expense thus far, based on the numerous reports from numerous new REX owners that it loads the departure location's Metar GLOBALLY until (while flying) it loads the next encountered Metar GLOBALLY and so forth. It's clear from these first round of test drive YouTube reviews that REX has quite admirably achieved a more accurate representation of a given Metar's ACTUAL conditions. Admittedly, the default weather does not consistently do this. So yes, REX IS BETTER in this regard. But... The point of my post above is simply to point out that I prefer to have the ENTIRE REGION around the aircraft (for what appears to be a few hundred miles at that...) load at launch with "reasonably accurate" depiction of the locally occurring and regional cloud distribution over a WIDE AREA from the get go. Whether it is SPOT ON at the departure airport for that exact minute is a secondary priority. For instance, I flew out of Havre Montana a few days ago headed south to Jackson, Wyoming. Once in the air it was clear that a line of thunderheads with rain falling to the ground blocked my flight plan a good 20 miles to south. OAT was already approaching 0 degrees centigrade so going over them was not an option due to icing considerations. Thus I immediately, altered course to the west to skirt around them, and watched in delight out the left window for the next half hour or so, as the occasional lighting bolt emanated from them as they slid away behind me. Other knots of towering clouds appeared southward and was forced to make similar course adjustments to skirt them. Checking the real world Doppler radar during the flight confirmed these knots of thunderheads appeared in reasonably close proximity to those I saw in the sim. This was a wonderful confirmation of this delightful experience. So with what I understand from REX's Metar-by-Metar GLOBAL loading behavior I'd have never been able to experience this. With the Asobo/MetarBlue engine at work, once aloft, having the ENTIRE REGION around me offer the diverse and challenging conditions I was presented with that needed to be assessed, skirted around, and - from a visual standpoint, enjoyed - cannot be underestimated. Having a dynamically changing cloud matrix of storm cells interspersed with more benign clouds - that to a pretty close degree - was reflective of the actual conditions in North Central Montana at the time was pretty awesome to say the least. To sum up, whether the micro-weather at HAVRE was PERFECTLY RENDERED for the few minutes I was there before departure isn't worth trading the diversity, dynamics, and relative accuracy of what I experienced during the REST OF THE ENTIRE FLIGHT for. Not even in the ballpark.
  • Create New...