Jump to content

MadDog

Members
  • Content Count

    598
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

186 Excellent

About MadDog

  • Rank
    Member

Profile Information

  • Gender
    Male
  • Location
    Atlanta, GA

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

Recent Profile Visitors

2,431 profile views
  1. Just a theory... but I'm thinking that the infinite looping during installation may be caused by altering the original files inside the /Official target folders. Before now, I rarely experienced any loops/freezes (maybe 2 or 3 total in 8 months); but I needed to restart the installation about 15 times this patch... and it always got stuck when installing aircraft files. That got me to thinking... since the last patch, I went in and customized a bunch of tail numbers and callsigns by editing the original aircraft.cfg for the default aircraft. I didn't verify it; but I'm willing to bet that the packages that got stuck were for the aircraft that I changed previously.
  2. I think the M$ download server is fubar. Got a looping file at 35... restarted, loop at 23... restarted, loop at 5... restarted. Now I'm just stuck at "Please Wait...". Think I may have to wait for the Europeans to go to bed. Based on all the flight dynamics changes listed, it's probably a good idea to remove aircraft mods from the community folder. I doubt they'll crash the sim; but will likely result in some odd aircraft behavior until the mods are updated.
  3. Thanks Filbert... looking forward to checking it out when I have a couple hours to spare. I'm sure it's excellent!
  4. Here's a step by step: 1. Go into Options > General > Camera (NOT the in-flight Camera Menu) and make absolutely sure that Height, Horizontal Position, and Zoom are set to 50! These are the global values and if they're not set to default (50), all of your future custom views will not save correctly. This is probably a bug because it's counter intuitive to apply global changes all over again when trying to save a view; but it is what it is. 2. In Options > Controls, search for the command "VFR Pilot View Save" and assign a key binding. By default, this command is unassigned... I assigned it to Ctrl + Alt + V. 3. Make a note of your controller assignments for "Reset Cockpit View". Default is Left Ctrl + Spacebar and/or "F" (I also have it assigned to the trigger on my joystick). 4. Load the aircraft of your choice and use the translation, look, and zoom controls to position the camera exactly where you want it. When you have what you want for a default view, press the "VFR Pilot View Save" binding assigned in step 2 (Ctrl + Alt + V in my case). Now, every time you press the "Reset Cockpit View" button(s), it will go back to this view and will NOT alternate to other intermediate views with subsequent presses... yay! 5. Now that you have a default view defined, custom cameras may also be saved the same way using the associated key bindings... default is Left Ctrl + Left Alt + Numpad 0 to 9. These views are recalled using the corresponding "Load Custom Camera #" commands... default is Left Alt + Numpad 0 to 9 6. Repeat steps 4 and 5 to set individualized default and custom views for each aircraft you own. 7. To save yourself a lot of pain... never, ever, EVER change the global settings in Options > General > Camera again... forget those settings even exist... they are evil !!!
  5. Nyxx, Dogmanbird, Thanks for the video references, I think they're both very accurate assessments. From my own experience, I just want to emphasize that although the design of the Crosswind pedals results in a very slight inward shift when pushed, the effect is barely noticeable and the orientation of the pedals does not change in the slightest (there really is no "twist" or obvious offset). I do agree with one criticism that Robert very gracefully pointed out in his video... the further you push the Crosswind pedals, the more effort it requires. Depending on the amount of tension dialed in, this can get a little tiring, especially when dealing with the overblown impact of crosswinds on the ground in MSFS. Fortunately, the need to apply copious amounts of rudder tends to be pretty short-lived and the new damper option for the MFG should help to resolve that minor issue. I've ordered the damper for my v2 pedals and look forward to trying it out. Bottom line, the TPRs look very impressive and would probably be the best choice if money wasn't an object; but the MFGs also do a fantastic job and they're well over $200 cheaper.
  6. My MFG Crosswind pedals don't move side to side... nor do they "twist" as a previous poster claimed... they travel straight back and forward. I agree they look a bit unusual; but they're high quality, accurate, and act like real rudder pedals. I'm sure the TPRs are great pedals (haven't had a chance to try them out myself); but they're also a good bit more expensive.
  7. Nice try... but no, I'm not responding to any more blanket comments. You win! I wish you (and the rest of the world) luck in convincing AMD to fix their broken drivers.
  8. Yes, Bob, that's exactly what I was saying... in the whole universe of Flight Simming, I'm the ONLY person not experiencing any issues with AMD drivers. Sometimes I wonder why I bother replying....
  9. Not sure I would call it luck... I've been at this a long time, so know how to keep a clean system. No issues with XP11 either (although I do wish the AMD drivers supported 1/2 refresh vsync in full-screen exclusive).
  10. Time to let the past be the past. I've been running MSFS on a 6900XT for months (currently using the 21.3.1 drivers) and have no issues with crashes or performance. In fact, I can't even remember the last time I've had a CTD. For all of its other flaws, MFS2020 is probably the most stable sim I've ever owned... and it's running on a 100% AMD platform.
  11. The Recently Troublesome Cinematic (RTC) has been fixed with the latest patch.
  12. Yes, the monitor will continue to reproduce the last full frame it received until it gets a new one. By locking framerates to 30, the video card doesn't need to work as hard and can more consistently deliver a new frame every 1/30 of a second. Consistency is the key to smoothness. Here are some typical examples for a 60 Hz monitor (each number represents the number of identical frames that the monitor displays): FPS locked at 30: 2-2-2-2-2-2-2-2-2-3-2-2-2-2-3-2-2-2-2-2-2-2 FPS locked at 20: 3-3-3-3-3-3-3-4-3-3-3-3-3-4-3-3-3-3-3-3-3-3 FPS locked at 60: 1-1-1-2-1-3-1-1-3-1-1-1-2-1-1-1-1-2-1-1-1-1 For simming, we want those numbers to stay the same... we perceive micro-stutters when the number of identical frames exceeds the average. 1-1-1-1-1-1-1-1-1-1-1-1 would be ideal; but maintaining that at 60 Hz is difficult with today's hardware, so we target 2-2-2-2-2-2-2-2-2-2-2. I'm really not sure. I thought that setting was aimed at higher performing games that exceeded 60 FPS; but it certainly can't hurt to try it out. I don't think it will eliminate input lag... which is just an unavoidable consequence of slower framerates.
  13. In-sim Vsync = On with FPS = 30 works perfectly on my 60 Hz screen. Nvidia settings (GTX 1070) are completely default. I was formerly having to change my monitor to 30 Hz with Vsync/60 FPS; but the new settings provide identical smoothness (maybe even better) with much less fuss. Great job MS... with this enhancement, I'm even willing to forgive the snafu with the flaps and airport signage! Just please don't mess this up in a future patch!
  14. Air Traffic Control... we announce unplanned delays all the time.
×
×
  • Create New...