Jump to content

ddwg72

Members
  • Posts

    47
  • Joined

  • Last visited

Recent Profile Visitors

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

  1. One of the upgrades to the NA included a wide area visible hud. The same upgrade with the 2+. Below is a shot of a 2+ trainer where you an see the circles you see in the above pic are gone as the items reach almost to the edge of the hud. You can tell if you are looking at the older huds by the prominent circles. Be glad of the upgrade, can you imagine what FLIR on hud would look like on that older style hud.
  2. I haven't done it so wont comment but if you need a work around TOO waypoint 1 after INS and it should work as a stop gap fix for you. I got in the habit of it and have not had any crashes.
  3. That number is for casualty radius not kill radius. There is as kill radius and casualty radius for weapons. Kill radius is your are dead if you are that close if nothing is shielding you. Casualty radius is that is "can" cause serious injury up to that range if nothing shielding you. Not saying they don't need to be increased and really need it just that the kill radius is generally around 1/10th or so of casualty radius.
  4. Cool video of the TAV-8 118/119 RPM on that move
  5. I didn't think it was right either till I went to the charts. In the fleet, they almost never take off in a hover as they have to go up with so little fuel. It is usually a STO. You really have to look at the VRest pages now. If you want to know required rpm to take off you can look at NFM-400 based on weight.
  6. Takes awhile to get used to but interesting to fly now. The current performance is well within the margin of error of an estimated performance chart.
  7. I don't have one as I swapped to Virpil but if you need help setting one up feel free to jump on our discord and I can walk you thru it real quick.. Look for Roth https://discord.gg/w2HVcsQq
  8. It was so iffy if it did it for me or not I just added it to my startup.. Get in the adjust throttle to where it needs to be then do the rest of the startup. Glad it worked out for you
  9. its your setup. try setting back to 100%, redo virpil config and windows config. Either that or your mapping is off. to go from idle to off you can see the lever sticking out of the throttle. I have virpil and usually have to go from idle to off to get engine spooling then push up to idle
  10. Turning off the G-Sync helped but it did not get rid of the issue. I think I did find out what caused it and it may help some others. I turned off Hardware-accelerated GPU scheduling in the Windows Graphics settings and it removed the stuttering when the game was in focus. Played a few missions and did a few full restarts and the stuttering never came back. To be clear the problem I had was when the game was in focus I had bad stuttering/ghosting but as soon as the game was out of focus the game ran great.
  11. I need to keep testing more but I turned of g-sync on the set up g-sync tab and not just turning off v-sync on the manage 3d settings and it seemed to get rid of it. Will need to do more testing but work keeps getting in the way of proper testing.. need to send an email to my boss about work interfering with dcs time.
  12. not sure what is causing it but I have a strange issue could use some help figuring out. I get bad stuttering in VR but only when the window is in focus and I move my head. I have the Pimax 8kx/3090 ect.. I tried Smarth Smoothing off and on. It is not bottlenecking as frames, ect.. all work great and the game runs great as long as I dont move my head but when I do I get bad suttering/ghosting and only in DCS even though frames stay the same. It works great when not in focus with no stuttering when looking around. Anyone have an idea of what to look at or run into this before?
  13. Many of the bugs are issues with a persons install, not actual bugs, already been resolved, issues with ED and not the harrier, ect. Sure there are bugs listed trying to dig out useful information would be a waste of time.
  14. Just give it time. I recently had to order the controller for mine and it spent from April 22 "Prepared for shipment from Russia" to June 16th Processing in the US with nothing in between. All in all, it took from April 17th to June 24th for shipping.
  15. Well you see, it is called troubleshooting. By switching to IFA before start, it would eliminate all the things you do during startup if it crashed. If it didn't then we would try engines only, add some more of the process next time, ect.. trying to isolate it down until we find it crashes. Then once we find the magic sequence, have a few other people try it. This helps with the bug report and to help the programmers know there is a repeatable problem and how to exactly replicate it. It is a process of narrowing down the problem so you can actually see what the problem is. Right now there is no way to know is it a game bug or bad/corrupt file on your end, server or really anything. Going back to the original topic.. yes it is well worth half off. A lot of people fly all the time and sure there are some minor bugs but nothing show stopping. It is also missing some really cool features I hope we get, but again nothing show stopping. Razbam does need to do a better job telling people when they fix bugs as they do fix stuff that they do not mention such as recently fixing the volume know to 0 after takeoff bug. There are also quite a few bugs that are process so far down into the systems the most pilots will never see and/or they do not matter such as alignment. You should be flying coupled with the GPS in IFA as they do in the fleet from what I hear now and thus alignment entering and drift do not matter. It should be fixed but no way a show stopping or bug even most pilots will ever see.
×
×
  • Create New...