Jump to content

SharpeXB

Members
  • Posts

    8005
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by SharpeXB

  1. Yeah basically all you have to do is, using Explorer, paste the new file name containing the new ID onto your old controls file. Very fast and easy to do.
  2. True but that would require a very high res screen ie Apple “retina” level. Or a very small or far away display. At normal sizes and viewing distances even a 4K screen needs AA to remove jaggies. Most gamers use 1080p and 1440p. Not sure why this requires explaining as it’s all fairly obvious. Suit yourself but to me AA Off looks like hot garbage.
  3. Turn off DLSS and use MSAA instead of DLAA. You shouldn’t need DLSS with a 5080
  4. The right side you’re pointing at is the Fwd Aft indicator, not elevation. According to that tutorial, the indicator is green and turns red when you’re out of limits. Again I can see the red light in your screenshot, so how is that hard to see in the game? That’s certainly worth adding. The only nighttime AAR I’ve done with the boom was in the A-10C which doesn’t use the belly lights. Those flood lights would be very welcome in that situation.
  5. I’ll take your word for it, I don’t AAR in aircraft that use this. What part of that is broken exactly? I still see the lights there in your screenshot.
  6. Well that should certainly be fixed if it’s broken, then the graphic overlay wouldn’t be needed. It looks visible enough here although this was two years ago
  7. nVIDIA is the stylized logo text. The written form of the name is Nvidia or NVIDIA.
  8. I’m curious where all these different versions of “Nvidia” come from… nVidia? NVidia?
  9. Not sure why you need the overlay when you can just look at the lights on the tanker. Yes they’re a bit dim but I can still see them clearly in this small screenshot. They appear well enough in this example
  10. Chuck’s Guides are very nicely done but they have a big flaw. They don’t highlight changes like this. That makes them way too difficult to use when there are updates. They might be ok to read through just once but they aren’t very good for ongoing use.
  11. To keep things simple just look at the illustration of the HOTAS in the manual and copy those with your bindings. That’s all you really need. You can add more as your preference but all that’s necessary to get started is to emulate what the real controls have in them. I would add the Zoom View commands to that though. It’s not necessary to have every single binding mapped to your controls. That’s what the clickable cockpit is for.
  12. I find the Frame Generation to actually work very well in other games. That’s not available (or needed for myself) in DCS.
  13. Try this. From the Library, right click on the title. Select Properties / General. There it will list Launch Options where you can choose VR, normal or if to ask when starting. I don’t have DCS on Steam but that’s how it works in another game.
  14. Yeah, using a gamepad controller for the Apache TEDAC presents this problem if you want to use the triggers. Easily solved with JoyToKey but still…
  15. Interesting. So I guess the difference between this and Frame Generation is that it doesn’t need support within the game? Looks like this feature is coming to the 40-series as well. https://www.tomshardware.com/pc-components/gpu-drivers/nvidias-new-driver-update-finally-brings-smooth-motion-to-rtx-40-series-gpus-works-like-amds-fluid-motion-frames-and-claims-to-double-your-fps-with-a-single-click-in-any-game
  16. Right. So just cap your frame rate at or 2-3 frames below your screen rate. That prevents tearing without the latency added by Vsync. Fast may be doing almost the same thing though. I think the limit is better in NCP than DCS. For myself I leave DCS at 300 (ie off) and set 117 in NCP for my 120Hz display.
  17. I don’t see what the difference between that and what any other game or sim does with its FOV. No other game I know of has such a wide limit, they usually have this set to some reasonable value.
  18. Yeah I don’t know why DCS has that distorted wide view. If you’re using an axis for the command you can set a limit with the saturation in the response menu.
  19. Gamers can never be convinced that seeing small distant aircraft IRL would be difficult. They’re too conditioned by video games using icons and labels.
  20. Vsync is best turned off in any form when using G-Sync. If you see tearing just cap your refresh rate at or 2-3 frames below your screen. I think it’s better to use NCP for that since I see the DCS limiter may cause problems and you can’t fine tune it.
  21. I always found Fast Sync in NCP to work really well for DCS back when I had a fixed rate display.
  22. “Zoom Normal” returns you to the value you set with RAlt+Num0. Snap View Saving needs to be enabled for this to work.
×
×
  • Create New...