Jump to content

RyanR

Members
  • Posts

    269
  • Joined

  • Last visited

Everything posted by RyanR

  1. I think you are correct. I tried a few presets, including J and K, but wasn't super happy with any of them when it comes to spotting. I feel like DLSS just sees other aircraft as "noise". -Ryan
  2. One thing that needs to be tweaked is when "the dot" turns into the plane model. Right now, the dot disappears when the model is still smaller than the dot. DLSS has its own problems, and it's a moving target as nVidia keeps kicking out new presets. -Ryan
  3. I'm having much better luck with DLAA, but running not-VR at 1440px with a 5080 doesn't require DLSS. -Ryan
  4. Thanks! It's not a big deal. -Ryan
  5. THX @BIGNEWY! -Ryan
  6. I feel like 50% of the time, AWACS isn't anywhere near as good as it is in that video. When you need it most, it's not there. -Ryan
  7. OK. So it is supposed to be hidden? No way to unhide it other than to lase? -Ryan
  8. I thought to grab a couple screenshots last night from saving the new head position after an FOV change. I think the only way to start over is to delete the the snapview.lua in Saved Games. the one in the DCS directory doesn't do anything. The lua in the Saved Games directory will persist after a module reinstall or repair, so you must delete it. Once you do that, start DCS without head tracking, hop into the Fulcrum, adjust the FOV, and then save the snap view. Good luck. -Ryan
  9. Something more than the FOV got changed. You may need to delete your snapview.lua and start over. -Ryan
  10. Here are the conditions to get the empty bracket. Uncheck the MiG-29 in the NS430 special options, but enable the NS430 for the Fulcrum in the ME. So if a server is running a mission with the NS430 enabled, you'll get the empty bracket, unless you disable the NS430 module. Could I simply be trying to disable the NS430 wrong? -Ryan NS430.trk
  11. I'll try to reproduce. If I can, I'll send a track. Backstory: I was connected to a friend's server, and he did have the NS430 enabled in the mission. I can say that when the NS430 is not enabled in MP, the bracket and NS430 are removed. I dunno if that helps. Thanks! -Ryan
  12. This was the same problem I had with the Fulcrum that took me 3 hours to figure out. In my head I thought it would be easiest to find and change the FOV in a LUA, but if you have never saved a snap view, you won't have a snapview.lua in the Saved Games folder to change. You have to adjust and save the default snap view in game from 118 to something around 80-ish. The Fulcrum is the only module in DCS with this strange default FOV. -Ryan
  13. I got the NS430. I absolutely love the implementation in the Fulcrum. However, when I wanted to remove the NS430 by unchecking it from the NS430 Special menu, I still had the empty bracket when I popped into the plane. My first thought is that it's actually a fantastic bracket!.... and I love that you can see in in the external model. The only way to get rid of the bracket seems to be disabling the NS430 module, which requires a restart of DCS. Not a big deal. Would it be difficult to have the bracket disappear with the NS430 when simply unchecking it? Otherwise, incredible module! -Ryan
  14. The Fulcrum has to be one of the best modules in DCS for something at this point in EA. It's *really* good out of the box. -Ryan
  15. Thx! I remember in the jet, but forget in the forum. If you have "reliable" datalink, you can get a smidgen of stealth by running in QUIET mode, as the AI won't "see" you on RWR. -Ryan
  16. I *have* noticed that turning emissions switch to the middle position will reduce how likely you are to get intercepted. Enemy radars are going to still see you, and based on mission scripting those radars can feed your position down the air-defense chain. -Ryan
  17. I think deleting the launcher.lsqlite3 fixed the problem! Thanks so much! -Ryan
  18. This dialog pops up in the Launcher... and keeps popping up after clicking OK. Only fix is to "ctrl-alt-del" and kill DCS with the task manager. This happened immediately after installing the latest patch (yesterday?). I've never had a lick of trouble with the launcher since its release. Any thoughts? Thanks! -Ryan
  19. Thanks! Apologies for not catching it! -Ryan
  20. Just wondering! -Ryan
  21. It's amazing how "primitive" the avionics are..... which makes the module that much more interesting. I really like the Mirage F-1 for this reason. Yet the Fulcrum has so much power and maneuverability for the time period. ED really captured the essence(?) of this jet! The first time the ground crew pulled the chocks, and I clumsily advanced the throttles, I thought it just felt insane! -Ryan
  22. Thanks! I got it sorted last night after way too much googling. The default FOV for the Fulcrum is 119. Delete the snapview.lua, and that's what you get (though I started out with no snapview.lua, as I have no saved snapviews). This is an unnatural FOV. The Fulcrum module is the outlier relative to all other DCS modules (and I own all the modules). I adjusted FOV to 80-90-ish, and then and saved the view. It looks amazing. ED looks to have done a great job! -Ryan
  23. Which HOTAS button does this function, again? Thanks! -Ryan
  24. More info: default FOV for MiG-29A is 119 degrees. All other DCS modules use ~82 degrees. If I could find a LUA to change this, I'll be home free. -Ryan
  25. It should live in "saved games\DCS\Config". If you don't have an autoexec.cfg, just make one.
×
×
  • Create New...