Jump to content

Sarowa

Members
  • Posts

    86
  • Joined

  • Last visited

Everything posted by Sarowa

  1. Honestly if you're interested in actually learning how to fly, go take an online ground school course. Maybe go for a discovery flight with an instructor. If you like it, get your medical certificate and start training. As far as home simulators, X-Plane or MSFS, paired with VATSIM, are much better for learning and practicing procedures than DCS.
  2. "Responsible" may be a bit harsh against Why485.
  3. That's the thing: it did. ED implemented that mod virtually unchanged in 2.9.0. It highlighted a lot of issues with spotting in DCS, which is why this thread exists.
  4. @YoYo You do realize you're replying to the OP from this thread? @Why485 is the spotting person.
  5. No, you can refuel and rearm with the f5's engines running and canopy closed. If you're having issues requesting air supply connect/apply to start the engines while refueling or rearming, that's because the ground crew only does one thing at a time.
  6. That's probably due to the ARU. It's a mechanical pseudo-FBW. It reduces stick pitch sensitivity as speed increases.
  7. I suspect this is a Tacview inaccuracy. The DCS F-5's wings suffer catastrophic structural failure at 11g in the best of cases. Sometimes this occurs at a lower g if there's more payload on the aircraft (e.g. greater than half internal fuel, external fuel tanks, bombs, rockets, etc.). 7.3 g is the rated limit, but all(most?) aircraft have a design load factor of 150% applied to this number, where the structure meets or exceeds the capability to hold such a load without failure. At least in the F-5's case, DCS interprets this as the exact point catastrophic structural failure will occur. Here's an example from the Cessna 172 Pilot's Operating Handbook (POH):
  8. I'll once again argue, the lack of feedback indicating catastrophic structural failure is approaching is also a major issue.
  9. I tried using the new option to turn off the larger dots and revert to the smaller dots. I experienced exactly the same issue with dots disappearing based on where I look or my zoom level. (see Item 2 in the original post)
  10. That video looks more like a tire losing grip momentarily while trying to hold back all that force, imo, which then gets translated into a slightly exaggerated camera shake. It appears the nose continues pointing the same direction. If you look at the pipper, it's still pointing at the same tree the whole time. I wonder if this is similar to the zero or near-zero speed friction issue a lot of racing games deal with. In those, you can sometimes see a car on a hill with the wheels/brakes locked up, but the car veeeery slowly slides down the hill. I feel watching the runway texture movement seems to indicate this is happening, but also the game seems to rubber band you back to where you were when you throttle down. In the video, watch the runway texture here at the bottom left of the canopy:
  11. Without dots, and without a suitable replacement (e.g. smart scaling), you're at the mercy of your display technology and various DCS graphical effects (or lack thereof) that may insufficiently replicate real life effects at long distances (e.g. sun glint). Even effects like contrails are invisible at long range until you zoom in, likely due to frustum culling. Even then, a computer display cannot perfectly replicate the detail you can see IRL with your naked eye, and getting even close is prohibitively expensive for the average player. Your average player would be completely blind until around 1nm, which does not reflect reality at all. This would kill the WW2 and cold war communities who rely much more heavily on spotting than modern.
  12. I played with the LOD slider some more and saw no changes with regards to aircraft spotting.
  13. Now you see them. Now you don't. All I did was move my head very slightly. These images were taken less than 1 second apart.
  14. You can see the disappearing dots as I move my head around in this video, especially towards the end with the dots against the blue sky just above the horizon. When I'm looking at them, they're invisible, then reappear when I look to the side. They disappear when I look at them again.
  15. The old dots had similar problems, they were just less obvious due to their smaller size. As such, I'm not interested in reverting. I'd rather see the new system improved. I have DLSS disabled. I'll play with the LOD slider a bit more but my initial testing did not reveal any obvious changes.
  16. Spotting dots are very large in VR. With my Valve Index, at certain ranges, both the dot and model are rendered. In this situation, the dot can obscure the aircraft, such that I can't see the aircraft model and its heading and attitude. I'd like to see some kind of slider to reduce the dot size. Dots disappear seemingly at random based upon where I'm looking and whether I'm using no zoom, VR zoom, or VR spyglass zoom. Aircraft at ~2nm (3.5km) only have the model rendered, no dot. With no zoom, aircraft can be extremely difficult to see at this range*. The abrupt change from a huge dot to a tiny model (or vice versa) is extremely jarring. Maybe add a slider to adjust the minimum dot range? *I'm a pilot IRL and I can easily spot tiny aircraft like the C172 at 2nm
  17. Taking off on one engine while the other engine is still starting.
  18. This might be related to the f5 RWR bug I found. It seems like it affects (most?) western RWRs.
  19. Normally yes, there is a fox1 launch warning when there are few radar pings on the RWR. The issue is that when there are many other radar pings, the RWR does not prioritize launch warnings. The RWR gets saturated, and search radar pings are prioritized over launch warnings, which seems to be a bug. See the tracks in the OP for examples.
  20. I saw this, but it doesn't tell us anything about their plans.
×
×
  • Create New...